summaryrefslogtreecommitdiff
path: root/security/selinux
diff options
context:
space:
mode:
authorChandra Seetharaman <sekharan@us.ibm.com>2013-07-20 02:31:38 +0400
committerBen Myers <bpm@sgi.com>2013-07-22 22:58:10 +0400
commit297aa63769e6ae06b7db97eb76c9211beeb32c69 (patch)
tree151526cae76c8c74d22024ff2ef02df37d9888f6 /security/selinux
parent58e59854a3dfa9ab1fa1bcfc6324646cd77046a7 (diff)
downloadlinux-297aa63769e6ae06b7db97eb76c9211beeb32c69.tar.xz
xfs: Fix a deadlock in xfs_log_commit_cil() code path
While testing and rearranging pquota/gquota code, I stumbled on a xfs_shutdown() during a mount. But the mount just hung. Debugged and found that there is a deadlock involving &log->l_cilp->xc_ctx_lock. It is in a code path where &log->l_cilp->xc_ctx_lock is first acquired in read mode and some levels down the same semaphore is being acquired in write mode causing a deadlock. This is the stack: xfs_log_commit_cil -> acquires &log->l_cilp->xc_ctx_lock in read mode xlog_print_tic_res xfs_force_shutdown xfs_log_force_umount xlog_cil_force xlog_cil_force_lsn xlog_cil_push_foreground xlog_cil_push - tries to acquire same semaphore in write mode This patch fixes the deadlock by changing the reason code for xfs_force_shutdown in xlog_print_tic_res() to SHUTDOWN_LOG_IO_ERROR. SHUTDOWN_LOG_IO_ERROR is the right reason code to be set since we are in the log path. Thanks to Dave for suggesting this solution. Signed-off-by: Chandra Seetharaman <sekharan@us.ibm.com> Reviewed-by: Ben Myers <bpm@sgi.com> Signed-off-by: Ben Myers <bpm@sgi.com>
Diffstat (limited to 'security/selinux')
0 files changed, 0 insertions, 0 deletions