Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1317690
| From | Johannes Berg <johannes@sipsolutions.net> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: net/rfkill: WARNING in rfkill_fop_read |
| Date | 2016-01-26 11:10 +0100 |
| Message-ID | <qV8Jr-2AB-7@gated-at.bofh.it> (permalink) |
| References | <qV8zM-2fZ-29@gated-at.bofh.it> <qV8Jr-2AB-9@gated-at.bofh.it> <qV8zM-2fZ-29@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
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
Back to linux.kernel | Previous | Next — Previous in thread | Find similar | Unroll thread
net/rfkill: WARNING in rfkill_fop_read Dmitry Vyukov <dvyukov@google.com> - 2016-01-26 11:00 +0100 Re: net/rfkill: WARNING in rfkill_fop_read Johannes Berg <johannes@sipsolutions.net> - 2016-01-26 11:10 +0100
csiph-web