| 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 linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <2024070419-calamity-blade-02fb@gregkh> Date: Thu, 4 Jul 2024 16:58:46 +0200 From: Greg KH <gregkh@...uxfoundation.org> To: Dmitry Vyukov <dvyukov@...gle.com> Cc: 88c258bd-3d0c-de79-b411-6552841eb8d0@...il.com, Linux-kernel-mentees@...ts.linuxfoundation.org, linux-kernel@...r.kernel.org, luisbg@...nel.org, salah.triki@...il.com, syzbot+fc26c366038b54261e53@...kaller.appspotmail.com, syzkaller-bugs@...glegroups.com Subject: Re: [PATCH] fs/befs: fix shift-out-of-bounds in befs_check_sb On Thu, Jul 04, 2024 at 04:13:52PM +0200, Dmitry Vyukov wrote: > On Thu, 4 Jul 2024 at 16:11, Greg KH <gregkh@...uxfoundation.org> wrote: > > > > On Thu, Jul 04, 2024 at 03:50:57PM +0200, Dmitry Vyukov wrote: > > > > > Hi, > > > > > > > > > > What's the kernel policy for such cases? > > > > > > > > What "case"? > > > > > > > > There is no context here at all, and I can't find any patch on lore at > > > > all. > > > > > > > > Please always properly quote stuff... > > > > > > It's not easy with kernel lists. I used the lore suggested reply-to > > > command. Here is full thread: > > > https://lore.kernel.org/all/20240704135057.1174408-1-dvyukov@google.com/ > > > > I see no patch on lore on this thread :( > > Oh, it wasn't properly threaded, sorry. > Here is the patch: > https://lore.kernel.org/all/20230801155823.206985-1-ghandatmanas@gmail.com/ Ah, ok, resend it and cc: the vfs maintainer, it should probably go through their tree for other abandoned filesystems. thanks, greg k-h
Powered by blists - more mailing lists