when schedule() returns, the current state is TASK_RUNNING, no
need to set its status to TASK_INTERRUPTIBLE, and after jumping
out of the wile loop, its status will be set to TASK_RUNNING,
so, set_current_state(TASK_INTERRUPTIBLE) is redundant
Signed-off-by: Lizhe <sensor1010@163.com>
---
net/core/dev.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/net/core/dev.c b/net/core/dev.c
index b76fb37b381e..4bd2d4b954c9 100644
--- a/net/core/dev.c
+++ b/net/core/dev.c
@@ -6580,7 +6580,6 @@ static int napi_thread_wait(struct napi_struct *napi)
schedule();
/* woken being true indicates this thread owns this napi. */
woken = true;
- set_current_state(TASK_INTERRUPTIBLE);
}
__set_current_state(TASK_RUNNING);
--
2.17.1