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:   Thu, 22 Jul 2021 15:34:37 -0700
From:   Randy Dunlap <>
To:     Theodore Ts'o <>, Matthew Wilcox <>
Cc:     butt3rflyh4ck <>,
        LKML <>,,
        syzkaller-bugs <>
Subject: Re: A shift-out-of-bounds in minix_statfs in fs/minix/inode.c

On 7/22/21 2:58 PM, Theodore Ts'o wrote:

> So I do care about this for ext4, although I don't guarantee immediate
> response, as it's something that I usually end up doing on my own
> time.  I do get cranky that Syzkaller makes it painful to extract out
> the fuzzed file system image, and I much prefer those fuzzing systems
> which provide the file system image and the C program used to trigger
> the failre as two seprate files.  Or failing that, if there was some

gosh yes. I have added a patch to the syzkaller C reproducer multiple times
so that it would write out the fs image and then I could just use that
with 'mount' etc. instead of running the (unreadable) C reproducer.

> trivial way to get the syzkaller reproducer program to disgorge the
> file system image to a specified output file.  As a result, if I have
> a choice of spending time investigating fuzzing report from a more
> file-system friendly fuzzing program and syzkaller, I'll tend choose
> to spend my time dealing with other file system fuzzing reports first.


Powered by blists - more mailing lists