locking, printk: Annotate logbuf_lock as raw

Browse source

The logbuf_lock lock can be taken in atomic context and therefore
cannot be preempted on -rt - annotate it.

In mainline this change documents the low level nature of
the lock - otherwise there's no functional difference. Lockdep
and Sparse checking will work as usual.

Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
[ merged and fixed it ]
Signed-off-by: Ingo Molnar <mingo@elte.hu>

...

This commit is contained in:

Thomas Gleixner 2009-07-25 17:50:36 +02:00 • committed by Ingo Molnar

parent 5389f6fad2

commit 07354eb1a7

3 changed files with 28 additions and 28 deletions

Show all changes Ignore whitespace when comparing lines Ignore changes in amount of whitespace Ignore changes in whitespace at EOL

Download patch file Download diff file Expand all files Collapse all files

6

include/linux/ratelimit.h

View file

46

kernel/printk.c

View file

4

lib/ratelimit.c

View file