[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <1453802888.2759.11.camel@sipsolutions.net>
Date: Tue, 26 Jan 2016 11:08:08 +0100
From: Johannes Berg <johannes@...solutions.net>
To: Dmitry Vyukov <dvyukov@...gle.com>,
"David S. Miller" <davem@...emloft.net>,
linux-wireless@...r.kernel.org, netdev <netdev@...r.kernel.org>,
LKML <linux-kernel@...r.kernel.org>,
João Paulo Rechi Vita <jprvita@...il.com>
Cc: syzkaller <syzkaller@...glegroups.com>,
Kostya Serebryany <kcc@...gle.com>,
Alexander Potapenko <glider@...gle.com>,
Sasha Levin <sasha.levin@...cle.com>,
Eric Dumazet <edumazet@...gle.com>
Subject: Re: net/rfkill: WARNING in rfkill_fop_read
On Tue, 2016-01-26 at 10:55 +0100, Dmitry Vyukov wrote:
> Hello,
>
> The following program triggers WARNING message in rfkill_fop_read:
>
> ------------[ cut here ]------------
> WARNING: CPU: 2 PID: 6975 at kernel/sched/core.c:7663
> __might_sleep+0x138/0x1a0()
> do not call blocking ops when !TASK_RUNNING; state=1 set at
> [<ffffffff81436e01>] prepare_to_wait_event+0x141/0x410
> kernel/sched/wait.c:210
> [< inline >] rfkill_readable net/rfkill/core.c:1102
Yeah, this should not acquire the mutex ... but luckily it's not a
problem not to anyway, so it's easy to fix. Thanks! I'll send out a fix
once I've tested it.
> // autogenerated by syzkaller (http://github.com/google/syzkaller)
gotta love the raw mmap etc. :)
johannes
Powered by blists - more mailing lists