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  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:   Wed, 16 May 2018 18:33:36 +0100
From:   Alan Jenkins <>
To:     Tetsuo Handa <>,
Cc:     syzbot <>,,
        Dan Williams <>,
        Jens Axboe <>,,,,
        Bart Van Assche <>,
        Christoph Hellwig <>,
        Hannes Reinecke <>,
        Johannes Thumshirn <>,
        Keith Busch <>,
        "Martin K. Petersen" <>,
        Martin Steigerwald <>,
        Ming Lei <>,
        Oleksandr Natalenko <>,
        Ross Zwisler <>
Subject: Re: INFO: task hung in blk_queue_enter

 > jbd2/sda1-8(PID=2271) is stuck waiting for journal commit operation.
 > I don't know how this thread is involved to this problem.

It feels like it should be a necessary link in the chain. This is the 
filesystem underneath the loop device. If that hangs, we would expect 
the loop device to hang, but not vice versa.

AIUI, you couldn't reproduce this hang on your own machine.

Don't you think, your fuzzer has just found a nice exploit for reiserfs?


(It's interesting that you found this hang just after we fixed 
block_queue_enter() to wait in D state instead of S state.[1]  I don't 
know syszkaller, so I assume from this it only flagged this case up 
because of the hung task warning. I.e. syzkaller didn't have its own 
watchdog that would have failed the test anyway.

[1] the commit that caused you to CC me. "block: do not use 
interruptible wait anywhere"


Powered by blists - more mailing lists