mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Miles Lane" <miles.lane@gmail.com>
To: "Ingo Molnar" <mingo@elte.hu>
Cc: "Andrew Morton" <akpm@osdl.org>,
	LKML <linux-kernel@vger.kernel.org>,
	"Arjan van de Ven" <arjan@infradead.org>
Subject: Re: 2.6.17-mm4 + hostap + pcmcia + lockdep -- possible recursive locking detected -- (af_callback_keys + sk->sk_family#3){-.-?}, at: [<c119d8db>] sock_def_readable+0x15/0x69
Date: Sun, 2 Jul 2006 23:08:03 -0700	[thread overview]
Message-ID: <a44ae5cd0607022308n646af3dh836df90b31e60dc@mail.gmail.com> (raw)
In-Reply-To: <20060702133451.GA27425@elte.hu>

On 7/2/06, Ingo Molnar <mingo@elte.hu> wrote:
>
> * Ingo Molnar <mingo@elte.hu> wrote:
>
> > * Miles Lane <miles.lane@gmail.com> wrote:
> >
> > > I have patches for hostap, pcmcia and lockdep applied to this kernel.
> > > These patches are the ones resulting from several recent message
> > > threads. I just noticed this in my kernel log:
> > >
> > > [ INFO: possible recursive locking detected ]
> > > ---------------------------------------------
> >
> > ok, lockdep should allow same-class read-lock recursion too, because
> > it's used by real code and is being relied upon. Could you try the patch
> > below? [...]
>
> the patches are also included in the latest -mm5 combo patch at:
>
>   http://redhat.com/~mingo/lockdep-patches/lockdep-combo-2.6.17-mm5.patch

I have not seen this particular INFO message show up again.
Therefore, I haven't tested your latest patch yet.  I wanted to determine
whether this problem would occur often.  If you like I can go ahead and
test the patch anyhow.  I am currently testing mm5 + the pcmcia patch and
the hostap patch.  I am looking into a crashing (system lockup) bug that is
triggered by removing my Linksys USB 10/100 Ethernet adapter.  This
problem is 100% repeatable.  I am working on setting up a remote
debugging configuration.

Would you like me to go ahead and test your latest patch?

Thanks,
            Miles

  reply	other threads:[~2006-07-03  6:08 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-02  1:04 Miles Lane
2006-07-02 13:29 ` Ingo Molnar
2006-07-02 13:34   ` Ingo Molnar
2006-07-03  6:08     ` Miles Lane [this message]
2006-07-03  6:10       ` Ingo Molnar
2006-07-05  7:56         ` Miles Lane

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=a44ae5cd0607022308n646af3dh836df90b31e60dc@mail.gmail.com \
    --to=miles.lane@gmail.com \
    --cc=akpm@osdl.org \
    --cc=arjan@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    /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

all inboxes | Powered by JetHome®