lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:   Sat, 19 Dec 2020 10:00:02 +0900
From:   Tetsuo Handa <>
To:     "Paul E. McKenney" <>
Cc:     Daniel Vetter <>,
        syzbot <>,
        Steven Rostedt <>,
        Josh Triplett <>,,
        Bartlomiej Zolnierkiewicz <>,
        dri-devel <>,
        Geert Uytterhoeven <>,
        "Gustavo A. R. Silva" <>,
        Linux Fbdev development list <>,
        Linux Kernel Mailing List <>,
        Nathan Chancellor <>,
        Peter Rosin <>,
        syzkaller-bugs <>,
        Dmitry Vyukov <>,
        Boqun Feng <>
Subject: Re: WARNING: suspicious RCU usage in modeset_lock

On Wed, Dec 16, 2020 at 5:16 PM Paul E. McKenney <> wrote:
> In my experience, lockdep will indeed complain if an interrupt handler
> returns while in an RCU read-side critical section.

Can't we add lock status checks into the beginning and the end of interrupt handler functions
(e.g. whether "struct task_struct"->lockdep_depth did not change) ?

Powered by blists - more mailing lists