diff options
author | WANG Cong <xiyou.wangcong@gmail.com> | 2016-11-17 15:55:26 -0800 |
---|---|---|
committer | David S. Miller <davem@davemloft.net> | 2016-11-18 13:58:39 -0500 |
commit | 06a77b07e3b44aea2b3c0e64de420ea2cfdcbaa9 (patch) | |
tree | 35be97e54af45ef40e4b8a1aea158c8c0ebd352b /include | |
parent | 0e2d1af399a3674351a5d0b8da5ba5764e0973a4 (diff) | |
download | linux-06a77b07e3b44aea2b3c0e64de420ea2cfdcbaa9.tar.bz2 |
af_unix: conditionally use freezable blocking calls in read
Commit 2b15af6f95 ("af_unix: use freezable blocking calls in read")
converts schedule_timeout() to its freezable version, it was probably
correct at that time, but later, commit 2b514574f7e8
("net: af_unix: implement splice for stream af_unix sockets") breaks
the strong requirement for a freezable sleep, according to
commit 0f9548ca1091:
We shouldn't try_to_freeze if locks are held. Holding a lock can cause a
deadlock if the lock is later acquired in the suspend or hibernate path
(e.g. by dpm). Holding a lock can also cause a deadlock in the case of
cgroup_freezer if a lock is held inside a frozen cgroup that is later
acquired by a process outside that group.
The pipe_lock is still held at that point.
So use freezable version only for the recvmsg call path, avoid impact for
Android.
Fixes: 2b514574f7e8 ("net: af_unix: implement splice for stream af_unix sockets")
Reported-by: Dmitry Vyukov <dvyukov@google.com>
Cc: Tejun Heo <tj@kernel.org>
Cc: Colin Cross <ccross@android.com>
Cc: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
Cc: Hannes Frederic Sowa <hannes@stressinduktion.org>
Signed-off-by: Cong Wang <xiyou.wangcong@gmail.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'include')
0 files changed, 0 insertions, 0 deletions