From: Christian Lamparter <chunkeey@googlemail.com>
To: Ben Greear <greearb@candelatech.com>
Cc: Ming Lei <tom.leiming@gmail.com>, linux-wireless@vger.kernel.org
Subject: Re: lockdep warning in ieee80211 rx path
Date: Mon, 4 Oct 2010 20:36:12 +0200 [thread overview]
Message-ID: <201010042036.12542.chunkeey@googlemail.com> (raw)
In-Reply-To: <4CAA17FA.3080403@candelatech.com>
On Monday 04 October 2010 20:07:54 Ben Greear wrote:
> On 10/04/2010 11:00 AM, Christian Lamparter wrote:
> > On Monday 04 October 2010 19:52:12 Ben Greear wrote:
> >> On 09/14/2010 01:51 PM, Christian Lamparter wrote:
> >>> On Sunday 05 September 2010 11:32:26 Ming Lei wrote:
> >>>> Seems the warning does not affect use of wireless, false positive?
> >>>
> >>> No, it's a bug... but please read& test the attached patch.
> >>
> >> This is not yet in wireless-testing. Should it be?
> > have you heard anything from Ming Lei about this subject?
> > Or have you reproduced the bug too?
>
> See my post about inconsistent {IN-SOFTIRQ-W} -> {SOFTIRQ-ON-W}.
>
> I'm not sure it's the same bug, but it would appear similar at least.
At first glance, your trace looks unrelated to Ming Lei's issue.
But we won't know for sure, unless you have a reliable way to
reproduce the exact circumstances.
> If your patch is probably good, I can go ahead and apply it.
> We can at least test that it doesn't obviously make things worse.
Ok, if the patch doesn't make things worse than they are, I can
risk another attempt.
Best regards,
Chr
next prev parent reply other threads:[~2010-10-04 18:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-05 9:32 lockdep warning in ieee80211 rx path Ming Lei
2010-09-08 22:40 ` Andrew Morton
2010-09-14 20:51 ` Christian Lamparter
2010-10-04 17:52 ` Ben Greear
2010-10-04 18:00 ` Christian Lamparter
2010-10-04 18:07 ` Ben Greear
2010-10-04 18:36 ` Christian Lamparter [this message]
2010-10-05 21:42 ` Ben Greear
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=201010042036.12542.chunkeey@googlemail.com \
--to=chunkeey@googlemail.com \
--cc=greearb@candelatech.com \
--cc=linux-wireless@vger.kernel.org \
--cc=tom.leiming@gmail.com \
/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).