Linux Kernel Mentees list
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: 88c258bd-3d0c-de79-b411-6552841eb8d0@gmail.com
Cc: salah.triki@gmail.com,
	syzbot+fc26c366038b54261e53@syzkaller.appspotmail.com,
	Linux-kernel-mentees@lists.linuxfoundation.org,
	linux-kernel@vger.kernel.org, luisbg@kernel.org
Subject: Re: [PATCH] fs/befs: fix shift-out-of-bounds in befs_check_sb
Date: Sun, 27 Aug 2023 18:47:34 +0200	[thread overview]
Message-ID: <2023082746-antelope-drop-down-5562@gregkh> (raw)
In-Reply-To: <24deab57-5480-3af6-17e6-0874aeaef3db@gmail.com>

On Sun, Aug 27, 2023 at 04:46:40PM +0530, Manas Ghandat wrote:
> Hi Greg,
> 
> Sorry for directly mailing to you but I tried to reach the maintainers for
> quite some time now. I haven't received any response on my patch. I was told
> to mail you in order to get my patch pulled.
> 

I have no context here, sorry.

Also, I am not a filesystem developer or maintainer.  And befs?  I doubt
that's maintained anymore as the operating system is long obsolete,
right?

confused,

greg k-h
_______________________________________________
Linux-kernel-mentees mailing list
Linux-kernel-mentees@lists.linuxfoundation.org
https://lists.linuxfoundation.org/mailman/listinfo/linux-kernel-mentees

  reply	other threads:[~2023-08-27 16:47 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 [this message]
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
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=2023082746-antelope-drop-down-5562@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=88c258bd-3d0c-de79-b411-6552841eb8d0@gmail.com \
    --cc=Linux-kernel-mentees@lists.linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luisbg@kernel.org \
    --cc=salah.triki@gmail.com \
    --cc=syzbot+fc26c366038b54261e53@syzkaller.appspotmail.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