sched, inotify: Deal with nested sleeps 28/222428/1 tizen_5.5_tv accepted/tizen/5.5/unified/20200115.122800 submit/tizen_5.5/20200115.034736
authorPeter Zijlstra <peterz@infradead.org>
Wed, 24 Sep 2014 08:18:50 +0000 (10:18 +0200)
committerSeung-Woo Kim <sw0312.kim@samsung.com>
Wed, 15 Jan 2020 02:19:13 +0000 (11:19 +0900)
commit31fd3809f4460b5ff4c2a013970566dbdb95f8da
treeb533e53707bc7805d717e283209cdbb9ce9d8b3f
parent82bdb8eb9ae843078fddac4a43674332ab7da2d6
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