https://www.open-mesh.org/https://www.open-mesh.org/favicon.ico?16699090422016-06-24T10:09:31ZOpen Meshbatman-adv - Bug #261: Refcount for usage wrong againhttps://www.open-mesh.org/issues/261?journal_id=8612016-06-24T10:09:31ZSven Eckelmann
<ul></ul><p>Since you can reproduce it - please bisect which commit introduced the problem. Otherwise we will not be able to fix the problem in time.</p>
<p>You can also force a reboot via:</p>
<pre>
echo s > /proc/sysrq-trigger
echo b > /proc/sysrq-trigger
</pre> batman-adv - Bug #261: Refcount for usage wrong againhttps://www.open-mesh.org/issues/261?journal_id=8622016-06-25T07:45:52ZSven Eckelmann
<ul><li><strong>Status</strong> changed from <i>New</i> to <i>Feedback</i></li><li><strong>Assignee</strong> set to <i>Ruben Kelevra</i></li></ul> batman-adv - Bug #261: Refcount for usage wrong againhttps://www.open-mesh.org/issues/261?journal_id=8652016-07-05T11:28:25ZSven Eckelmann
<ul></ul><p>Were you able to find the faulty commit via git-bisect?</p>
<p>There are also a couple of reference counting related fixes in the maint branch. I know that they are not for things which broke after v2016.0 but maybe your problem was already in v2016.0.</p>
<ul>
<li>20df5c5 batman-adv: Free last_bonding_candidate on release of orig_node
<ul>
<li>fix for problem since v2014.1.0</li>
</ul>
</li>
<li>6ecc711 batman-adv: Fix reference leak in batadv_find_router
<ul>
<li>fix for problem since v2014.1.0</li>
</ul>
</li>
<li>e401297 batman-adv: Fix non-atomic bla_claim::backbone_gw access
<ul>
<li>fix for problem since v2012.2.0/v2015.2</li>
</ul>
</li>
<li>719afd2 batman-adv: Fix orig_node_vlan leak on orig_node_release
<ul>
<li>fix for problem since v2014.0.0</li>
</ul></li>
</ul>
<p>There are also other fixes in the maint branch</p> batman-adv - Bug #261: Refcount for usage wrong againhttps://www.open-mesh.org/issues/261?journal_id=8702016-07-24T07:00:19ZSven Eckelmann
<ul><li><strong>Status</strong> changed from <i>Feedback</i> to <i>Closed</i></li></ul><p>Closing because:</p>
<ul>
<li>cannot reproduce problem with maint branch (which contains fixes for pre-v2016.0 problems)</li>
<li>not enough information how to reproduce the problem at all</li>
<li>review of the changes between v2016.0 and v2016.2 was not successful in finding a problematic change which could cause reference imbalances</li>
<li>reporter doesn't react to questions since one month (even when he wanted to have it fixed "as fast as possible")</li>
</ul> batman-adv - Bug #261: Refcount for usage wrong againhttps://www.open-mesh.org/issues/261?journal_id=8712016-07-25T02:17:45ZRuben Kelevracyrond@gmail.com
<ul></ul><p>This issue does not disappear if you close this ticket, so please reopen it until it's fixed.</p>
<p>I was not able to reproduce it in a testing environment, and can't reboot a production system several dozen times to do a bisect.</p>
<p>I would still appreciate a fast fix since I have to shutdown this system hard on every reboot since I've installed this update.</p> batman-adv - Bug #261: Refcount for usage wrong againhttps://www.open-mesh.org/issues/261?journal_id=8722016-07-25T03:02:33ZMarek Lindnermareklindner@neomailbox.ch
<ul><li><strong>Status</strong> changed from <i>Closed</i> to <i>In Progress</i></li></ul><p>Ruben Kelevra wrote:</p>
<blockquote>
<p>This issue does not disappear if you close this ticket, so please reopen it until it's fixed.</p>
<p>I was not able to reproduce it in a testing environment, and can't reboot a production system several dozen times to do a bisect.</p>
<p>I would still appreciate a fast fix since I have to shutdown this system hard on every reboot since I've installed this update.</p>
</blockquote>
<p>The ticket was closed mainly due to your perceived inactivity. Except for the initial ticket description you did not respond which led us to believe this issue was forgotten.</p>
<p>Please note that with the limited information you provided we are unable to fix the issue (though we tried).</p>
<p>Since you have to reboot your system every now and then wouldn't it be possible to bisect the issue on your live system over a longer period of time ? That would provide us the information we need to get to a fix.</p>
<p>In short: Without more support from you or somebody else who can reproduce the issue we are unable to address the bug no matter how long the ticket stays open.</p> batman-adv - Bug #261: Refcount for usage wrong againhttps://www.open-mesh.org/issues/261?journal_id=8732016-07-25T06:13:41ZSven Eckelmann
<ul></ul><p>Ruben Kelevra wrote:</p>
<blockquote>
<p>This issue does not disappear if you close this ticket, so please reopen it until it's fixed.</p>
</blockquote>
<p>How should we know if it is fixed when you are not testing anything or answer questions/give status updates? We have to timeout ticket like this. Otherwise tickets with MIA reporters + unreproducable problems would take over the relevant ones.</p>
<p>And ticket updates like "you still have not fixed it and I haven't tested anything" don't count.</p>
<blockquote>
<p>I would still appreciate a fast fix since I have to shutdown this system hard on every reboot since I've installed this update.</p>
</blockquote>
<p>I have several servers running (and rebooting) perfectly fine with the maint branch. Lets start there. And if this doesn't work then try to do a slow bisect (as suggested by Marek). Just give give some status updates from time to time and and try to respond.</p> batman-adv - Bug #261: Refcount for usage wrong againhttps://www.open-mesh.org/issues/261?journal_id=10352016-12-16T20:15:54ZSven Eckelmann
<ul></ul><p>What is the state of the tests?</p> batman-adv - Bug #261: Refcount for usage wrong againhttps://www.open-mesh.org/issues/261?journal_id=11982017-02-12T07:55:55ZSven Eckelmann
<ul><li><strong>Status</strong> changed from <i>In Progress</i> to <i>Feedback</i></li></ul> batman-adv - Bug #261: Refcount for usage wrong againhttps://www.open-mesh.org/issues/261?journal_id=12432017-06-09T13:06:33ZSven Eckelmann
<ul></ul><p>Ruben, do you have gathered any kind of infos or anything which we can use to reproduce it? I was not successful when I tried to reproduce it (multiple times) - even when we tried to reproduce it on some Freifunk gateway servers (used by 300 gluon nodes as VPN servers)</p> batman-adv - Bug #261: Refcount for usage wrong againhttps://www.open-mesh.org/issues/261?journal_id=12502017-07-05T14:56:33ZSven Eckelmann
<ul></ul><p>ping?</p> batman-adv - Bug #261: Refcount for usage wrong againhttps://www.open-mesh.org/issues/261?journal_id=12512017-07-06T04:18:54ZRuben Kelevracyrond@gmail.com
<ul></ul><p>I’m sorry for the late response, this Bug is gone. Not having any issue with 2017.1 :)</p> batman-adv - Bug #261: Refcount for usage wrong againhttps://www.open-mesh.org/issues/261?journal_id=12522017-07-06T06:40:02ZSven Eckelmann
<ul><li><strong>Status</strong> changed from <i>Feedback</i> to <i>Closed</i></li><li><strong>Target version</strong> set to <i>2017.1</i></li></ul>