Hello Scott,
thanks for the report. I could reproduce the Bug. (i've tried something similar myself, but did not wait between the commands before...). When i reproduce, not the syscall but the module itself locks up. :(
I'll look into this, please keep me informed, i'll do the same. :)
regards, Simon
On Fri, Jul 25, 2008 at 03:14:44PM +1200, Scott Raynel wrote:
Hi all,
I'm running batman-adv-kernelland r1102 on linux-2.6.21.5. I've found I can fairly reliably deadlock the kernel by disabling and re-enabling batman a few times, e.g.
$ echo ath0 > /proc/net/batman-adv/interfaces wait a while... $ echo > /proc/net/batman-adv/interfaces wait a while and repeat.
It appears that this is deadlocking the kernel somehow, as syscalls never return, e.g. 'ps' prints the header and then freezes.
Our interface configuration system brings interfaces up and down on re- configure, so we'd like the batman interface to be able to withstand this use case. I will try to start looking through the code, but I thought I'd throw the problem out there to see what others more experienced with it think.
Thanks all,
-- Scott Raynel WAND Network Research Group Department of Computer Science University of Waikato New Zealand
B.A.T.M.A.N mailing list B.A.T.M.A.N@open-mesh.net https://list.open-mesh.net/mm/listinfo/b.a.t.m.a.n