[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <aA-Hc5w4DwHHikyQ@infradead.org>
Date: Mon, 28 Apr 2025 06:49:39 -0700
From: Christoph Hellwig <hch@...radead.org>
To: Lizhi Xu <lizhi.xu@...driver.com>
Cc: hch@...radead.org, axboe@...nel.dk, linux-block@...r.kernel.org,
linux-kernel@...r.kernel.org, ming.lei@...hat.com,
syzbot+6af973a3b8dfd2faefdc@...kaller.appspotmail.com,
syzkaller-bugs@...glegroups.com
Subject: Re: [PATCH V2] loop: Add sanity check for read/write_iter
On Mon, Apr 28, 2025 at 09:48:12PM +0800, Lizhi Xu wrote:
> On Mon, 28 Apr 2025 05:46:25 -0700, Christoph Hellwig wrote:
> > > > and maybe add a blurb that vfs_iter_read/write had this check.
> > > It makes no sence. The current issue context does not involve vfs layer
> > > iter_read/write related routines.
> >
> > Yes. But explaining how a change caused a regression is good
> > information for a commit log.
> What changes?
> The check in vfs_iter_read/write is not relevant to this case.
> It is best to not write something irrelevant.
It is releavant in that vfs_iter_read/write have the check, and removal
of their used caused szybot to be able to hit this issue.
Powered by blists - more mailing lists