From: Jens Axboe <jaxboe@fusionio.com>
To: Ming Lei <tom.leiming@gmail.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: block: BUG: using smp_processor_id() in preemptible [00000000] code
Date: Tue, 26 Jul 2011 15:04:06 +0200 [thread overview]
Message-ID: <4E2EBB46.6060108@fusionio.com> (raw)
In-Reply-To: <CACVXFVPK9B65-McHv9HVsmLNZdwfeLbVgYYagpK-ymEK+hC0RQ@mail.gmail.com>
On 2011-07-26 08:22, Ming Lei wrote:
> Hi,
>
> On Tue, Jul 26, 2011 at 1:26 PM, Jens Axboe <jaxboe@fusionio.com> wrote:
>> On 2011-07-26 06:49, Ming Lei wrote:
>>> Hi,
>>>
>>> The bug is observed in -next-20110725, follows the stack trace[1], and
>>> seems the attachment patch can fix the bug.
>>
>> Does this work, too? We don't necessarily need the CPU stable, but
>> spewing debug output isn't very nice.
>
> This does work, thanks,
Great, thanks for reporting and testing.
--
Jens Axboe
prev parent reply other threads:[~2011-07-26 13:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-26 4:49 block: BUG: using smp_processor_id() in preemptible [00000000] code Ming Lei
2011-07-26 5:26 ` Jens Axboe
2011-07-26 6:22 ` Ming Lei
2011-07-26 13:04 ` Jens Axboe [this message]
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=4E2EBB46.6060108@fusionio.com \
--to=jaxboe@fusionio.com \
--cc=linux-kernel@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