summaryrefslogtreecommitdiff
path: root/security/keys
diff options
context:
space:
mode:
authorRainer Weikusat <rweikusat@mobileactivedefense.com>2015-12-16 20:09:25 +0000
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>2016-01-22 19:47:56 -0800
commit3a57e783016bf43ab9326172217f564941b85b17 (patch)
tree5e14b37cb8c4bb1c95f4f8af2e3c7b90e92bd7b7 /security/keys
parentaea23834fd3daa60039be8773aa39fb039aac945 (diff)
downloadlwn-3a57e783016bf43ab9326172217f564941b85b17.tar.gz
lwn-3a57e783016bf43ab9326172217f564941b85b17.zip
af_unix: Revert 'lock_interruptible' in stream receive code
[ Upstream commit 3822b5c2fc62e3de8a0f33806ff279fb7df92432 ] With b3ca9b02b00704053a38bfe4c31dbbb9c13595d0, the AF_UNIX SOCK_STREAM receive code was changed from using mutex_lock(&u->readlock) to mutex_lock_interruptible(&u->readlock) to prevent signals from being delayed for an indefinite time if a thread sleeping on the mutex happened to be selected for handling the signal. But this was never a problem with the stream receive code (as opposed to its datagram counterpart) as that never went to sleep waiting for new messages with the mutex held and thus, wouldn't cause secondary readers to block on the mutex waiting for the sleeping primary reader. As the interruptible locking makes the code more complicated in exchange for no benefit, change it back to using mutex_lock. Signed-off-by: Rainer Weikusat <rweikusat@mobileactivedefense.com> Acked-by: Hannes Frederic Sowa <hannes@stressinduktion.org> Signed-off-by: David S. Miller <davem@davemloft.net> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'security/keys')
0 files changed, 0 insertions, 0 deletions