aboutsummaryrefslogtreecommitdiffstats
path: root/include/asm-powerpc
diff options
context:
space:
mode:
authorEric Paris <eparis@redhat.com>2008-04-18 10:11:04 -0400
committerAl Viro <viro@zeniv.linux.org.uk>2008-04-28 06:19:13 -0400
commitf09ac9db2aafe36fde9ebd63c8c5d776f6e7bd41 (patch)
treeae2123e2bd6c054d82d5d2a3b81fdfb30c53e46e /include/asm-powerpc
parentf3d357b092956959563398b59ef2fdd10aea387d (diff)
downloadkernel_samsung_smdk4412-f09ac9db2aafe36fde9ebd63c8c5d776f6e7bd41.zip
kernel_samsung_smdk4412-f09ac9db2aafe36fde9ebd63c8c5d776f6e7bd41.tar.gz
kernel_samsung_smdk4412-f09ac9db2aafe36fde9ebd63c8c5d776f6e7bd41.tar.bz2
Audit: stop deadlock from signals under load
A deadlock is possible between kauditd and auditd under load if auditd receives a signal. When auditd receives a signal it sends a netlink message to the kernel asking for information about the sender of the signal. In that same context the audit system will attempt to send a netlink message back to the userspace auditd. If kauditd has already filled the socket buffer (see netlink_attachskb()) auditd will now put itself to sleep waiting for room to send the message. Since auditd is responsible for draining that socket we have a deadlock. The fix, since the response from the kernel does not need to be synchronous is to send the signal information back to auditd in a separate thread. And thus auditd can continue to drain the audit queue normally. Signed-off-by: Eric Paris <eparis@redhat.com> Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
Diffstat (limited to 'include/asm-powerpc')
0 files changed, 0 insertions, 0 deletions