summaryrefslogtreecommitdiffstats
path: root/security
diff options
context:
space:
mode:
authorTheodore Ts'o <tytso@mit.edu>2013-07-01 08:12:40 -0400
committerTheodore Ts'o <tytso@mit.edu>2013-07-01 08:12:40 -0400
commit39c04153fda8c32e85b51c96eb5511a326ad7609 (patch)
tree85f5e975d48bff40bc9a11efbb50f2cdfc212f1d /security
parente1be3a928ee0b0b2a893695e6dd5c5dbe293af16 (diff)
downloadlinux-39c04153fda8c32e85b51c96eb5511a326ad7609.tar.bz2
jbd2: fix theoretical race in jbd2__journal_restart
Once we decrement transaction->t_updates, if this is the last handle holding the transaction from closing, and once we release the t_handle_lock spinlock, it's possible for the transaction to commit and be released. In practice with normal kernels, this probably won't happen, since the commit happens in a separate kernel thread and it's unlikely this could all happen within the space of a few CPU cycles. On the other hand, with a real-time kernel, this could potentially happen, so save the tid found in transaction->t_tid before we release t_handle_lock. It would require an insane configuration, such as one where the jbd2 thread was set to a very high real-time priority, perhaps because a high priority real-time thread is trying to read or write to a file system. But some people who use real-time kernels have been known to do insane things, including controlling laser-wielding industrial robots. :-) Signed-off-by: "Theodore Ts'o" <tytso@mit.edu> Cc: stable@vger.kernel.org
Diffstat (limited to 'security')
0 files changed, 0 insertions, 0 deletions