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 for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:   Wed, 13 Jun 2018 17:55:42 +0200
From:   Dmitry Vyukov <>
To:     Jan Kara <>
Cc:     syzbot <>,
        Andreas Dilger <>,, LKML <>,
        syzkaller-bugs <>,
        "Theodore Ts'o" <>
Subject: Re: WARNING in ext4_set_page_dirty

On Mon, May 21, 2018 at 2:50 PM, Jan Kara <> wrote:
> On Sun 20-05-18 23:07:02, syzbot wrote:
>> syzbot has found a reproducer for the following crash on:
>> HEAD commit:    771c577c23ba Linux 4.17-rc6
>> git tree:       upstream
>> console output:
>> kernel config:
>> dashboard link:
>> compiler:       gcc (GCC) 8.0.1 20180413 (experimental)
>> syzkaller repro:
>> C reproducer:
>> IMPORTANT: if you fix the bug, please add the following tag to the commit:
>> Reported-by:
>> WARNING: CPU: 0 PID: 4577 at fs/ext4/inode.c:3894
>> ext4_set_page_dirty+0x28d/0x330 fs/ext4/inode.c:3894
>> Kernel panic - not syncing: panic_on_warn set ...
> Looking at the reproducer, this is the issue we have been speaking about at
> LSF/MM - direct IO read dirties pages after writeback has written them out
> and so we don't expect them to be dirtied. If someone told me I would not
> believe this is possible to hit by fuzzing ;) Good job from the syzkaller
> guys!

Thanks, Jan! Very nice to hear.
I believe we are not yet at the limit of what's possible :)

Powered by blists - more mailing lists