netdev - Re: Inconsistent lock state and possible irq lock inversion dependency detected in ax25.ko

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <47532B60.8030205@o2.pl>
Date:	Sun, 02 Dec 2007 23:02:08 +0100
From:	Jarek Poplawski <jarkao2@...pl>
To:	Bernard Pidoux <pidoux@....jussieu.fr>
CC:	ralf@...ux-mips.org, davem@...emloft.net, netdev@...r.kernel.org,
	Alexey Dobriyan <adobriyan@...il.com>
Subject: Re: Inconsistent lock  state and possible irq lock inversion dependency
 detected in ax25.ko

Bernard Pidoux wrote, On 12/02/2007 06:37 PM:

> Hi,
> 
> Many thanks for your patch for ~/net/ax25/ax25_subr.c
> 
> Introduction of local_bh_disable() ... local_bh_enable()
> 
> cured the inconsistent lock state related to AX25 connect timeout.
> 
> I have now a stable monoprocessor system running AX25 and ROSE network 
> packet switching application FPAC, whether kernel is compiled with or 
> without hack option.
> 
> There is no more problem during normal operations.
> 
> This was achieved, thanks to your AX25 patch and the patch from Alexey 
> Dobriyan for rose module.
> 
> I also patched rose module in order to get packet routing more 
> efficient, taking into account the "restarted" flag that is raised when 
> a neighbour node is already connected.
> 
> To summarize the present situation on my Linux machine, I built a patch 
> against kernel 2.6.23.9.
> 
> I would appreciate if you could make it included into a next kernel release.
... 

Bernard, I'm very glad I could be a little helpful, but I'm not sure of
your intentions: my patch proposal is rather trivial interpretation of
lockdep's report; I haven't studied AX25 enough even to be sure there is
a real lockup possible in this place. Since this change looks not very
costly and quite safe, I can 'take a risk' to sign this off after your
testing. But anything more is beyond my 'range'.

So, since you've spent quite a lot of time on this all, maybe it would
be simpler if you've tried the same with the current kernel, and resent
"proper" (not gzipped and with changelog) patch or patches. Then, I hope,
Ralf, as the maintainer, will make the rest.

Regards,
Jarek P.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html