From: majianpeng <majianpeng@gmail.com>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: Jiri Kosina <jkosina@suse.cz>,
Benjamin Tissoires <benjamin.tissoires@gmail.com>,
linux-input <linux-input@vger.kernel.org>
Subject: Re: [BUG] suspicious RCU usage
Date: Mon, 06 May 2013 09:10:31 +0800 [thread overview]
Message-ID: <51870307.2020107@gmail.com> (raw)
In-Reply-To: <20130503155113.GB5567@core.coreip.homeip.net>
On 05/03/2013 11:51 PM, Dmitry Torokhov wrote:
> On Fri, May 03, 2013 at 01:28:25PM +0200, Jiri Kosina wrote:
>> On Fri, 3 May 2013, majianpeng wrote:
>>
>>>>> Jiri, we had a similar bug in the RH bugzilla:
>>>>> https://bugzilla.redhat.com/show_bug.cgi?id=958935
>>>>>
>>>>> Are these two reports potentially fixed by your patch "HID: protect
>>>>> hid_debug_list" (https://patchwork.kernel.org/patch/2453931/)
>>>>> If so, maybe we should send it to stable as well...
>>>> I actually believe this bug is *introduced* by that patch :) All the
>>>> reports were with the kernel containing it, right?
>>>>
>>>> Does the patch below fix it, please?
>> [ ... snip ... ]
>>> Add your patch.Found the following message:
>>> [ 150.908051] ======================================================
>>> [ 150.908053] [ INFO: HARDIRQ-safe -> HARDIRQ-unsafe lock order detected ]
>>> [ 150.908056] 3.9.0+ #102 Not tainted
>> Right, oh well, I missed that scenario.
> This looks good to me.
>
> Reviewed-by: Dmitry Torokhov <dmitry.torokhov@gmail.com>
>
It's all good for me.
Thanks!
Jianpeng Ma
next prev parent reply other threads:[~2013-05-06 1:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-03 6:53 [BUG] suspicious RCU usage majianpeng
2013-05-03 8:10 ` Benjamin Tissoires
2013-05-03 8:23 ` Jiri Kosina
2013-05-03 10:35 ` majianpeng
2013-05-03 11:28 ` Jiri Kosina
2013-05-03 15:51 ` Dmitry Torokhov
2013-05-06 1:10 ` majianpeng [this message]
2013-05-06 11:09 ` Jiri Kosina
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=51870307.2020107@gmail.com \
--to=majianpeng@gmail.com \
--cc=benjamin.tissoires@gmail.com \
--cc=dmitry.torokhov@gmail.com \
--cc=jkosina@suse.cz \
--cc=linux-input@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.