Prev: v2.6.35-rc3: BUG: using smp_processor_id() in preemptible [00000000] code: modprobe/1255
Next: AppArmor: LSM interface, and security module initialization
From: Andy Isaacson on 15 Jul 2010 13:20
I ran into the stale-block-directory problem while using blktrace,
and while chasing it noticed the open-coded cmpxchg.

The unlink-on-final-close is a longstanding bug that's triggerable
by the standard blktrace(1) utility (it races child threads against
the parent), and should go to -stable. The cmpxchg is a startup
race that may be easy to maliciously trigger from userspace, but
is unlikely to be triggered accidentally. (Famous last words...)

Andy Isaacson (2):
blktrace: use cmpxchg
blktrace: unlink blk directory on final trace close

kernel/trace/blktrace.c | 18 +++++++++---------
1 files changed, 9 insertions(+), 9 deletions(-)
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo(a)vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
 | 
Pages: 1
Prev: v2.6.35-rc3: BUG: using smp_processor_id() in preemptible [00000000] code: modprobe/1255
Next: AppArmor: LSM interface, and security module initialization