[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <YwTyO0yZmUT1MVZW@casper.infradead.org>
Date: Tue, 23 Aug 2022 16:28:59 +0100
From: Matthew Wilcox <willy@...radead.org>
To: Siddh Raman Pant <code@...dh.me>
Cc: david@...morbit.com, djwong@...nel.org, fgheet255t@...il.com,
hch@...radead.org, linux-ext4@...r.kernel.org,
linux-fsdevel@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-xfs@...r.kernel.org, riteshh@...ux.ibm.com,
syzbot+a8e049cd3abd342936b6@...kaller.appspotmail.com,
syzkaller-bugs@...glegroups.com
Subject: Re: [syzbot] WARNING in iomap_iter
On Tue, Aug 23, 2022 at 08:51:01PM +0530, Siddh Raman Pant wrote:
> + if (lo->lo_offset < 0 || lo->lo_sizelimit < 0 || lo->lo_flags < 0)
The lo_flags check is still there?
> + return -EOVERFLOW;
> +
> memcpy(lo->lo_file_name, info->lo_file_name, LO_NAME_SIZE);
> lo->lo_file_name[LO_NAME_SIZE-1] = 0;
> lo->lo_flags = info->lo_flags;
> --
> 2.35.1
>
>
Powered by blists - more mailing lists