From: Jet Chen <jet.chen@intel.com>
To: Alessandro Rubini <rubini@gnudd.com>
Cc: gregkh@linuxfoundation.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org, fengguang.wu@intel.com
Subject: Re: [FMC] BUG: scheduling while atomic: swapper/1/0x10000002
Date: Wed, 09 Apr 2014 13:26:29 +0800 [thread overview]
Message-ID: <5344DA05.5070204@intel.com> (raw)
In-Reply-To: <20140409050843.GA18949@mail.gnudd.com>
On 04/09/2014 01:08 PM, Alessandro Rubini wrote:
> Hello.
> Thank you for the report.
>
> I'm at a conference and I fear I won't be able to test myself in the
> next days, but I think this is already fixed (it is part of
> the "misc_register" call path, so it's the same problem).
>
> The fix is commit v3.11-rc2-11-g783c2fb
>
> 783c2fb FMC: fix locking in sample chardev driver
>
> This commit, however, is not part of v3.11 and I think this is why you
> are finding the problem in the v3.10..v3.11 interval.
>
> thank you again
> /alessandro
>
I find commit 783c2fb FMC: fix locking in sample chardev driver. I will help to test it.
next prev parent reply other threads:[~2014-04-09 5:26 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-09 3:32 [FMC] BUG: scheduling while atomic: swapper/1/0x10000002 Jet Chen
2014-04-09 5:08 ` Alessandro Rubini
2014-04-09 5:26 ` Jet Chen [this message]
2014-04-09 5:28 ` Fengguang Wu
2014-04-09 16:44 ` Jet Chen
2014-04-09 16:46 ` Jet Chen
[not found] ` <1397016815-74608-1-git-send-email-jet.chen@intel.com>
2014-04-16 21:10 ` [PATCH] FMC: misc_register should not be called while atomic Greg Kroah-Hartman
2014-04-16 22:39 ` Alessandro Rubini
2014-04-17 3:09 ` Greg KH
-- strict thread matches above, loose matches on Subject: below --
2013-07-03 7:15 [FMC] BUG: scheduling while atomic: swapper/1/0x10000002 Fengguang Wu
2013-07-03 7:32 ` Alessandro Rubini
2013-07-03 7:36 ` 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=5344DA05.5070204@intel.com \
--to=jet.chen@intel.com \
--cc=fengguang.wu@intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rubini@gnudd.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).