lists.openwall.net | 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
| ||
|
Date: Thu, 18 Aug 2022 20:51:16 +0530 From: Siddh Raman Pant <code@...dh.me> To: "Matthew Wilcox" <willy@...radead.org> Cc: "david" <david@...morbit.com>, "djwong" <djwong@...nel.org>, "fgheet255t" <fgheet255t@...il.com>, "hch" <hch@...radead.org>, "linux-ext4" <linux-ext4@...r.kernel.org>, "linux-fsdevel" <linux-fsdevel@...r.kernel.org>, "linux-kernel" <linux-kernel@...r.kernel.org>, "linux-xfs" <linux-xfs@...r.kernel.org>, "riteshh" <riteshh@...ux.ibm.com>, "syzbot+a8e049cd3abd342936b6" <syzbot+a8e049cd3abd342936b6@...kaller.appspotmail.com>, "syzkaller-bugs" <syzkaller-bugs@...glegroups.com> Subject: Re: [syzbot] WARNING in iomap_iter On Thu, 18 Aug 2022 20:20:02 +0530 Matthew Wilcox wrote: > I don't think changing these from u64 to s64 is the right way to go. Why do you think so? Is there somnething I overlooked? I think it won't intorduce regression, since if something is working, it will continue to work. If something does break, then they were relying on overflows, which is anyways an incorrect way to go about. Also, it seems even the 32-bit compatibility structure uses signed types. Thanks, Siddh
Powered by blists - more mailing lists