sched, inotify: Deal with nested sleeps 60/222360/3 accepted/tizen/unified/20200115.123401 submit/tizen/20200115.004607
authorPeter Zijlstra <peterz@infradead.org>
Wed, 24 Sep 2014 08:18:50 +0000 (10:18 +0200)
committerSeung-Woo Kim <sw0312.kim@samsung.com>
Tue, 14 Jan 2020 09:04:22 +0000 (18:04 +0900)
commit5661b84ba5578e1d2d2111268627f024585ea9f6
tree79e21a2a327d8174d083a925bc0126bbe6cbe4c5
parentc35b3ccd638dcc0d3f54c28e525d2558f8d3a295
sched, inotify: Deal with nested sleeps

inotify_read is a wait loop with sleeps in. Wait loops rely on
task_struct::state and sleeps do too, since that's the only means of
actually sleeping. Therefore the nested sleeps destroy the wait loop
state and the wait loop breaks the sleep functions that assume
TASK_RUNNING (mutex_lock).

Fix this by using the new woken_wake_function and wait_woken() stuff,
which registers wakeups in wait and thereby allows shrinking the
task_state::state changes to the actual sleep part.

Signed-off-by: Peter Zijlstra (Intel) <peterz@infradead.org>
Cc: Al Viro <viro@zeniv.linux.org.uk>
Cc: Linus Torvalds <torvalds@linux-foundation.org>
Cc: tglx@linutronix.de
Cc: ilya.dryomov@inktank.com
Cc: umgwanakikbuti@gmail.com
Cc: Robert Love <rlove@rlove.org>
Cc: Eric Paris <eparis@parisplace.org>
Cc: John McCutchan <john@johnmccutchan.com>
Cc: Robert Love <rlove@rlove.org>
Cc: Oleg Nesterov <oleg@redhat.com>
Link: http://lkml.kernel.org/r/20140924082242.254858080@infradead.org
Signed-off-by: Ingo Molnar <mingo@kernel.org>
[jh80.chung, sw0312.kim: cherry-pick mainline commit e23738a7300a to fix inotify read block issue]
Suggested-by: Jaehoon Chung <jh80.chung@samsung.com>
Signed-off-by: Seung-Woo Kim <sw0312.kim@samsung.com>
Change-Id: Ia87818db31987a34b6cca25f4f70947a8dac9483
fs/notify/inotify/inotify_user.c