From: Greg KH <gregkh@linuxfoundation.org>
To: Dmitry Vyukov <dvyukov@google.com>
Cc: 88c258bd-3d0c-de79-b411-6552841eb8d0@gmail.com,
Linux-kernel-mentees@lists.linuxfoundation.org,
linux-kernel@vger.kernel.org, luisbg@kernel.org,
salah.triki@gmail.com,
syzbot+fc26c366038b54261e53@syzkaller.appspotmail.com,
syzkaller-bugs@googlegroups.com
Subject: Re: [PATCH] fs/befs: fix shift-out-of-bounds in befs_check_sb
Date: Thu, 4 Jul 2024 16:58:46 +0200 [thread overview]
Message-ID: <2024070419-calamity-blade-02fb@gregkh> (raw)
In-Reply-To: <CACT4Y+az44BGCQ_DjOoCjfcQHEt6YEPi=pksFCRj=-zMrPwSQQ@mail.gmail.com>
On Thu, Jul 04, 2024 at 04:13:52PM +0200, Dmitry Vyukov wrote:
> On Thu, 4 Jul 2024 at 16:11, Greg KH <gregkh@linuxfoundation.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
next prev parent reply other threads:[~2024-07-04 14:58 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-27 11:16 [PATCH] fs/befs: fix shift-out-of-bounds in befs_check_sb Manas Ghandat
2023-08-27 16:47 ` Greg KH
2024-07-04 13:50 ` Dmitry Vyukov
2024-07-04 14:04 ` Greg KH
2024-07-04 14:08 ` Dmitry Vyukov
2024-07-04 14:11 ` Greg KH
2024-07-04 14:13 ` Dmitry Vyukov
2024-07-04 14:58 ` Greg KH [this message]
2024-07-04 15:04 ` Dmitry Vyukov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2024070419-calamity-blade-02fb@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=88c258bd-3d0c-de79-b411-6552841eb8d0@gmail.com \
--cc=Linux-kernel-mentees@lists.linuxfoundation.org \
--cc=dvyukov@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luisbg@kernel.org \
--cc=salah.triki@gmail.com \
--cc=syzbot+fc26c366038b54261e53@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox