From: Bernard Pidoux <pidoux@ccr.jussieu.fr>
To: Jarek Poplawski <jarkao2@o2.pl>
Cc: ralf@linux-mips.org, davem@davemloft.net, netdev@vger.kernel.org,
Alexey Dobriyan <adobriyan@gmail.com>
Subject: Re: Inconsistent lock state and possible irq lock inversion dependency detected in ax25.ko
Date: Sun, 02 Dec 2007 18:37:01 +0100 [thread overview]
Message-ID: <4752ED3D.2060204@ccr.jussieu.fr> (raw)
In-Reply-To: <4744AD8B.2000908@ccr.jussieu.fr>
[-- Attachment #1: Type: text/plain, Size: 910 bytes --]
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.
Many thanks and best regards,
Bernard Pidoux
F6BVP
[-- Attachment #2: rose-patch-2.6.23.9.tgz --]
[-- Type: application/x-compressed-tar, Size: 1745 bytes --]
next prev parent reply other threads:[~2007-12-02 17:39 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-03 18:54 [PATCH] Fix rose.ko oops on unload Alexey Dobriyan
2007-10-03 19:04 ` Jeff Garzik
2007-10-03 19:21 ` Alexey Dobriyan
2007-10-08 6:44 ` David Miller
2007-12-14 21:58 ` [PATCH] [ROSE] reverts commits d85838c55d836c33077344fab424f200f2827d84 Bernard Pidoux
2007-11-21 22:13 ` Inconsistent lock state and possible irq lock inversion dependency detected in ax25.ko Bernard Pidoux
2007-11-28 13:48 ` Jarek Poplawski
2007-12-02 17:37 ` Bernard Pidoux [this message]
2007-12-02 22:02 ` Jarek Poplawski
2007-12-04 22:26 ` Bernard Pidoux
2007-12-04 23:17 ` Jarek Poplawski
2007-12-05 0:45 ` Ralf Baechle
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4752ED3D.2060204@ccr.jussieu.fr \
--to=pidoux@ccr.jussieu.fr \
--cc=adobriyan@gmail.com \
--cc=davem@davemloft.net \
--cc=jarkao2@o2.pl \
--cc=netdev@vger.kernel.org \
--cc=ralf@linux-mips.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).