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