lkml.org 
[lkml]   [2018]   [Nov]   [23]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [PATCH v2] kmemleak: Turn kmemleak_lock to raw spinlock on RT
> is this an RT-only problem? Because mainline should not allow read->read
> locking or read->write locking for reader-writer locks. If this only
> happens on v4.18 and not on v4.19 then something must have fixed it.

Probably misunderstanding, but I'd say that read->read locking is "the
norm"...?

If you don't use qrwlock, readers are also "recursive", in part.,

P0 P1
read_lock(l)
write_lock(l)
read_lock(l)

won't block P0 on the second read_lock(). (qrwlock somehow complicate
the analysis; IIUC, they are recursive if and only if in_interrupt().).

Andrea


>
>
> Sebastian

\
 
 \ /
  Last update: 2018-11-23 12:03    [W:0.076 / U:0.516 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site