diff options
| author | Oleg Nesterov <oleg@redhat.com> | 2015-08-04 19:33:34 +0300 |
|---|---|---|
| committer | David S. Miller <davem@davemloft.net> | 2015-08-07 09:52:44 +0300 |
| commit | 7ba8bd75ddc6b041b5716dbb29e49df3e9cc2928 (patch) | |
| tree | 042783b9d9b3458790c4c914e9a219e9ac69c175 /fs/omfs | |
| parent | 57b229063ae6dc65036209018dc7f4290cc026bb (diff) | |
| download | linux-7ba8bd75ddc6b041b5716dbb29e49df3e9cc2928.tar.xz | |
net: pktgen: don't abuse current->state in pktgen_thread_worker()
Commit 1fbe4b46caca "net: pktgen: kill the Wait for kthread_stop
code in pktgen_thread_worker()" removed (in particular) the final
__set_current_state(TASK_RUNNING) and I didn't notice the previous
set_current_state(TASK_INTERRUPTIBLE). This triggers the warning
in __might_sleep() after return.
Afaics, we can simply remove both set_current_state()'s, and we
could do this a long ago right after ef87979c273a2 "pktgen: better
scheduler friendliness" which changed pktgen_thread_worker() to
use wait_event_interruptible_timeout().
Reported-by: Huang Ying <ying.huang@intel.com>
Signed-off-by: Oleg Nesterov <oleg@redhat.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'fs/omfs')
0 files changed, 0 insertions, 0 deletions