From: Alessandro Rubini <rubini@gnudd.com>
To: wangyun@linux.vnet.ibm.com
Cc: fengguang.wu@intel.com, gregkh@linuxfoundation.org,
linux-kernel@vger.kernel.org
Subject: Re: [fmc] BUG: scheduling while atomic: swapper/0/1/0x00000002
Date: Mon, 12 Aug 2013 14:42:27 +0200 [thread overview]
Message-ID: <20130812124227.GA22310@mail.gnudd.com> (raw)
In-Reply-To: <52088127.7070109@linux.vnet.ibm.com>
> On 08/11/2013 09:52 PM, Fengguang Wu wrote:
>> FYI, the bug still exists in the upstream and linux-next kernels.
Strange. Greg approved the patch I sent. I see it in next-20130809
but also next-20130801 and other ones with the same hash:
783c2fb FMC: fix locking in sample chardev driver
However, it is not in master.
It was sent as https://lkml.org/lkml/2013/7/16/196 .
Greg, can you please put the patch in the bugfix queue?
Thanks
/alessandro
next prev parent reply other threads:[~2013-08-12 12:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-11 13:52 [fmc] BUG: scheduling while atomic: swapper/0/1/0x00000002 Fengguang Wu
2013-08-12 6:31 ` yun wang
2013-08-12 12:42 ` Alessandro Rubini [this message]
2013-08-12 12:49 ` Fengguang Wu
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=20130812124227.GA22310@mail.gnudd.com \
--to=rubini@gnudd.com \
--cc=fengguang.wu@intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=wangyun@linux.vnet.ibm.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).