From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
        id S1751338AbdBZWOA (ORCPT <rfc822;w@1wt.eu>);
        Sun, 26 Feb 2017 17:14:00 -0500
Received: from ec2-52-27-115-49.us-west-2.compute.amazonaws.com ([52.27.115.49]:59947
        "EHLO osg.samsung.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org
        with ESMTP id S1751221AbdBZWN6 (ORCPT
        <rfc822;linux-kernel@vger.kernel.org>);
        Sun, 26 Feb 2017 17:13:58 -0500
Subject: Re: [ieee802154_unregister_hw] bea5b158ff BUG: scheduling while
 atomic: swapper/1/0x00000002
To: Alexander Aring <aar@pengutronix.de>,
        Fengguang Wu <fengguang.wu@intel.com>
References: <20170226094334.z4sz7yk3loxagi7z@wfg-t540p.sh.intel.com>
 <79b37cfd-5084-59a6-9044-cdc2017e1fa2@pengutronix.de>
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>
From: Stefan Schmidt <stefan@osg.samsung.com>
Message-ID: <429e0a0c-dc05-0785-5885-01bc19c8e502@osg.samsung.com>
Date: Sun, 26 Feb 2017 23:12:54 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101
 Thunderbird/45.4.0
MIME-Version: 1.0
In-Reply-To: <79b37cfd-5084-59a6-9044-cdc2017e1fa2@pengutronix.de>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

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