* a suspected race bug at locks_remove_flock()
@ 2009-07-24 7:55 홍신 shin hong
0 siblings, 0 replies; only message in thread
From: 홍신 shin hong @ 2009-07-24 7:55 UTC (permalink / raw)
To: linux-fsdevel
Hi. I found a suspected race condition bug at locks_remove_flocks()
in fs/locks.c of recent Linux kernel.
This bug is similar to the one reported in
ChangeLog 2.6.24 (commit 85c59580b30c82aa771aa33b37217a6b6851bc14)
and also to the one I report right before.
During the execution of locks_remove_flock(),
Big Kernel Lock(BKL) might be released and re-taken
at the call site of locks_delete_lock() unintentionally
due to the Releasing-On-Block semantics of BKL.
This is because locks_delete_lock() can invoke kmem_cache_alloc()
which can be blocked.
BKL releasing an retaking may result race condition
by breaking atomic execution of the code block
guarded by lock_kernel() and unlock_kernelt().
Please examine the possbility of race condition of this code
and let me know your opinion.
Shin Hong
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2009-07-24 7:55 UTC | newest]
Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2009-07-24 7:55 a suspected race bug at locks_remove_flock() 홍신 shin hong
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).