[PATCH] fs/befs: fix shift-out-of-bounds in befs_check_sb

[PATCH] fs/befs: fix shift-out-of-bounds in befs_check_sb

[Manas Ghandat]

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.

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

Re: [PATCH] fs/befs: fix shift-out-of-bounds in befs_check_sb

[Greg KH]

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

Re: [PATCH] fs/befs: fix shift-out-of-bounds in befs_check_sb

[Dmitry Vyukov]

Hi,

What's the kernel policy for such cases?
Should this be merged via some fallback fs/mm tree,
or taken directly by Linus?
The filesystem is still enabled in all major distros.
Or should we delete the filesystem from the kernel?

Re: [PATCH] fs/befs: fix shift-out-of-bounds in befs_check_sb

[Greg KH]

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...

greg k-h

Re: [PATCH] fs/befs: fix shift-out-of-bounds in befs_check_sb

[Dmitry Vyukov]

On Thu, 4 Jul 2024 at 16:04, 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/

Re: [PATCH] fs/befs: fix shift-out-of-bounds in befs_check_sb

[Greg KH]

On Thu, Jul 04, 2024 at 04:08:40PM +0200, Dmitry Vyukov wrote:
> On Thu, 4 Jul 2024 at 16:04, 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 :(

Re: [PATCH] fs/befs: fix shift-out-of-bounds in befs_check_sb

[Dmitry Vyukov]

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/

Re: [PATCH] fs/befs: fix shift-out-of-bounds in befs_check_sb

[Greg KH]

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

Re: [PATCH] fs/befs: fix shift-out-of-bounds in befs_check_sb

[Dmitry Vyukov]

On Thu, 4 Jul 2024 at 16:58, Greg KH <gregkh@linuxfoundation.org> 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.

Ack, thanks!
Manas, are you still interested in pursuing this fix?