mirror of
https://github.com/BobTheBlinker/android_kernel_motorola_sm6375.git
synced 2026-10-28 02:32:09 -04:00
locking, printk: Annotate logbuf_lock as raw
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 <[email protected]> [ merged and fixed it ] Signed-off-by: Ingo Molnar <[email protected]>
This commit is contained in:
parent
5389f6fad2
commit
07354eb1a7
3 changed files with 28 additions and 28 deletions
|
|
@ -39,7 +39,7 @@ int ___ratelimit(struct ratelimit_state *rs, const char *func)
|
|||
* in addition to the one that will be printed by
|
||||
* the entity that is holding the lock already:
|
||||
*/
|
||||
if (!spin_trylock_irqsave(&rs->lock, flags))
|
||||
if (!raw_spin_trylock_irqsave(&rs->lock, flags))
|
||||
return 0;
|
||||
|
||||
if (!rs->begin)
|
||||
|
|
@ -60,7 +60,7 @@ int ___ratelimit(struct ratelimit_state *rs, const char *func)
|
|||
rs->missed++;
|
||||
ret = 0;
|
||||
}
|
||||
spin_unlock_irqrestore(&rs->lock, flags);
|
||||
raw_spin_unlock_irqrestore(&rs->lock, flags);
|
||||
|
||||
return ret;
|
||||
}
|
||||
|
|
|
|||
Loading…
Reference in a new issue