Re: WARNING: HARDIRQ-safe -> HARDIRQ-unsafe lock order detected (2)

2020-09-10 Thread Boqun Feng
Thanks! On Wed, Sep 09, 2020 at 06:19:06AM -0700, syzbot wrote: > syzbot has bisected this issue to: > > commit f08e3888574d490b31481eef6d84c61bedba7a47 > Author: Boqun Feng > Date: Fri Aug 7 07:42:30 2020 + > > lockdep: Fix recursive read lock related safe->unsafe detection > > bise

Re: WARNING: HARDIRQ-safe -> HARDIRQ-unsafe lock order detected (2)

2020-09-09 Thread syzbot
syzbot has bisected this issue to: commit f08e3888574d490b31481eef6d84c61bedba7a47 Author: Boqun Feng Date: Fri Aug 7 07:42:30 2020 + lockdep: Fix recursive read lock related safe->unsafe detection bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=13034be190 start commi

Re: WARNING: HARDIRQ-safe -> HARDIRQ-unsafe lock order detected

2018-04-27 Thread Tetsuo Handa
OK. Patch was sent to linux.git as 6c1e851c4edc13a4. #syz fix: random: fix possible sleeping allocation from irq context

Re: WARNING: HARDIRQ-safe -> HARDIRQ-unsafe lock order detected

2018-04-24 Thread Theodore Y. Ts'o
On Mon, Apr 23, 2018 at 10:49:12AM -0700, Dmitry Torokhov wrote: > On Sun, Apr 22, 2018 at 7:02 PM, syzbot > wrote: > > > > Hello, > > > > syzbot hit the following crash on upstream commit > > 285848b0f4074f04ab606f1e5dca296482033d54 (Sun Apr 22 04:20:48 2018 +) > > Merge tag 'random_for_linus

Re: WARNING: HARDIRQ-safe -> HARDIRQ-unsafe lock order detected

2018-04-23 Thread Dmitry Torokhov
On Sun, Apr 22, 2018 at 7:02 PM, syzbot wrote: > > Hello, > > syzbot hit the following crash on upstream commit > 285848b0f4074f04ab606f1e5dca296482033d54 (Sun Apr 22 04:20:48 2018 +) > Merge tag 'random_for_linus_stable' of > git://git.kernel.org/pub/scm/linux/kernel/git/tytso/random > syzbo