[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <pdghzlvw6ypcju6ldsngka44cjp6g56bjjsmxm3sd7dqev4g6y@x72zm7vurxyz>
Date: Sat, 28 Sep 2024 04:57:32 -0400
From: Kent Overstreet <kent.overstreet@...ux.dev>
To: Tetsuo Handa <penguin-kernel@...ove.sakura.ne.jp>
Cc: Roberto Sassu <roberto.sassu@...weicloud.com>,
Paul Moore <paul@...l-moore.com>, Mimi Zohar <zohar@...ux.ibm.com>,
Roberto Sassu <roberto.sassu@...wei.com>, Casey Schaufler <casey@...aufler-ca.com>,
syzbot <syzbot+listfc277c7cb94932601d96@...kaller.appspotmail.com>, linux-kernel@...r.kernel.org,
linux-security-module@...r.kernel.org, syzkaller-bugs@...glegroups.com
Subject: Re: [syzbot] Monthly lsm report (Sep 2024)
On Sat, Sep 28, 2024 at 03:49:27PM GMT, Tetsuo Handa wrote:
> On 2024/09/28 10:25, Kent Overstreet wrote:
> > And looking further, I don't see anyhting in the console log from when
> > bcachefs actually mounted (???), which means I don't think I have enough
> > to go on. It's clearly an upgrade path issue - we didn't run
> > check_allocations as is required when upgrading to 1.11 - but it's not
> > reproducing for me when I run tests with old tools.
> >
> > Can we get some more information about the syzbot reproducer? Exact
> > tools version, format command and mount command.
>
> Reproducer for this bug is not yet found. But syzbot does not use userspace
> tools. That is, testing with old (or new) tools will not help. Please note
> that syzbot uses crafted (intentionally corrupted) filesystem images. If the
> kernel side depends on sanity checks / validations done by the userspace
> side, syzbot will find oversights on the kernel side. Please don't make any
> assumptions made by the userspace tools.
>
You seem to be confused; how do you expect sysbot to test a filesystem
without the format comand?
Powered by blists - more mailing lists