[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20241129225147.GA2777799@bhelgaas>
Date: Fri, 29 Nov 2024 16:51:47 -0600
From: Bjorn Helgaas <helgaas@...nel.org>
To: Aleksandr Nogikh <nogikh@...gle.com>
Cc: syzbot <syzbot+fe139f9822abd9855970@...kaller.appspotmail.com>,
linux-fsdevel@...r.kernel.org, linux-kernel@...r.kernel.org,
netfs@...ts.linux.dev, syzkaller-bugs@...glegroups.com,
v9fs@...ts.linux.dev
Subject: Re: [syzbot] [netfs?] WARNING in netfs_retry_reads
On Fri, Nov 29, 2024 at 11:16:08PM +0100, Aleksandr Nogikh wrote:
> So if it's e.g. just the bisection result that was wrong, while the
> crash report itself is legit, it's better to not use the "#syz
> invalid" command. I've added +1 to our backlog issue for adding a
> special command to cancel only the misleading bisection result [1].
What's the appropriate command for a bad bisect?
Powered by blists - more mailing lists