linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Cengiz Can <cengiz.can@canonical.com>
Cc: Salvatore Bonaccorso <carnil@debian.org>,
	linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
	lvc-patches@linuxtesting.org, dutyrok@altlinux.org,
	syzbot+5f3a973ed3dfb85a6683@syzkaller.appspotmail.com,
	stable@vger.kernel.org
Subject: Re: [PATCH] hfs/hfsplus: fix slab-out-of-bounds in hfs_bnode_read_key
Date: Mon, 24 Mar 2025 11:53:51 -0700	[thread overview]
Message-ID: <2025032404-important-average-9346@gregkh> (raw)
In-Reply-To: <7qi6est65ekz4kjktvmsbmywpo5n2kla2m3whbvq4dsckdcyst@e646jwjazvqh>

On Mon, Mar 24, 2025 at 09:43:18PM +0300, Cengiz Can wrote:
> In the meantime, can we get this fix applied?

Please work with the filesystem maintainers to do so.

thanks,

greg k-h

  reply	other threads:[~2025-03-24 18:55 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-19 19:13 [PATCH] hfs/hfsplus: fix slab-out-of-bounds in hfs_bnode_read_key Vasiliy Kovalev
2025-03-20 19:30 ` Salvatore Bonaccorso
2025-03-24 16:14   ` Cengiz Can
2025-03-24 16:17     ` Greg KH
2025-03-24 18:43       ` Cengiz Can
2025-03-24 18:53         ` Greg KH [this message]
2025-04-06 16:07           ` Cengiz Can
2025-04-06 16:28             ` Greg KH
2025-04-07 10:59             ` Christian Brauner
2025-04-07 17:15               ` Christian Brauner
2025-04-07 17:29                 ` Attila Szasz
2025-04-07 19:08               ` Darrick J. Wong
2025-04-08 10:11                 ` Richard Weinberger
2025-04-08 14:50                   ` Darrick J. Wong
2025-04-08 15:58                     ` Richard Weinberger
2025-04-16 15:10                   ` Eric Sandeen
2025-04-08  8:03               ` Greg KH
2025-04-08 12:00                 ` Attila Szasz
2025-03-27 19:15       ` Attila Szasz
2025-04-07 17:25 ` Christian Brauner

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=2025032404-important-average-9346@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=carnil@debian.org \
    --cc=cengiz.can@canonical.com \
    --cc=dutyrok@altlinux.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lvc-patches@linuxtesting.org \
    --cc=stable@vger.kernel.org \
    --cc=syzbot+5f3a973ed3dfb85a6683@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;
as well as URLs for NNTP newsgroup(s).