mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Stefan Schmidt <stefan@osg.samsung.com>
To: Alexander Aring <aar@pengutronix.de>,
	Fengguang Wu <fengguang.wu@intel.com>
Cc: Marcel Holtmann <marcel@holtmann.org>,
	Rob Herring <robh@kernel.org>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	linux-kernel@vger.kernel.org, LKP <lkp@01.org>
Subject: Re: [ieee802154_unregister_hw] bea5b158ff BUG: scheduling while atomic: swapper/1/0x00000002
Date: Sun, 26 Feb 2017 23:12:54 +0100	[thread overview]
Message-ID: <429e0a0c-dc05-0785-5885-01bc19c8e502@osg.samsung.com> (raw)
In-Reply-To: <79b37cfd-5084-59a6-9044-cdc2017e1fa2@pengutronix.de>

Hello.

On 02/26/2017 12:07 PM, Alexander Aring wrote:
>
> Hi,
>
> On 02/26/2017 10:43 AM, Fengguang Wu wrote:
>> Greetings,
>>
>> FYI, this debug patch discloses an old-but-still-active bug in
>> ieee802154/fakelb. The attached reproduce-* script may help debug it.
>>
>
> fixed by: bdca1fd9a6df ("fakelb: fix schedule while atomic").

Some more context. Looking at your config and script file names they 
suggest this is tested with 4.8.0-rc4. Fengguang, is that correct?

The fix from above is in 4.8.0-rc7
git describe bdca1fd9a6df
v4.8-rc6-1377-gbdca1fd

> It should be send to stable. Stefan can you do that please?

The latest stable kernel is 4.10.1 and the latest longterm stable is 
4.9.13. Both of them should have this fix already.

If there is a desire I could try sending it for the older longterm 
stable tree 4.4.x. Not sure if this is really worth the effort. Comments?

regards
Stefan Schmidt

      reply	other threads:[~2017-02-26 22:14 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-26  9:43 Fengguang Wu
2017-02-26 11:07 ` Alexander Aring
2017-02-26 22:12   ` Stefan Schmidt [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=429e0a0c-dc05-0785-5885-01bc19c8e502@osg.samsung.com \
    --to=stefan@osg.samsung.com \
    --cc=aar@pengutronix.de \
    --cc=fengguang.wu@intel.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkp@01.org \
    --cc=marcel@holtmann.org \
    --cc=robh@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®