From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Chuck Lever <chuck.lever@oracle.com>
Cc: viro@zeniv.linux.org.uk, brauner@kernel.org, jack@suse.cz,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
stable <stable@kernel.org>, Takashi Iwai <tiwai@suse.de>
Subject: Re: [PATCH] Revert "libfs: Use d_children list to iterate simple_offset directories"
Date: Wed, 26 Feb 2025 08:21:11 -0800 [thread overview]
Message-ID: <2025022621-worshiper-turtle-6eb1@gregkh> (raw)
In-Reply-To: <a7fe0eda-78e4-43bb-822b-c1dfa65ba4dd@oracle.com>
On Wed, Feb 26, 2025 at 10:57:48AM -0500, Chuck Lever wrote:
> On 2/26/25 9:29 AM, Greg Kroah-Hartman wrote:
> > This reverts commit b9b588f22a0c049a14885399e27625635ae6ef91.
> >
> > There are reports of this commit breaking Chrome's rendering mode. As
> > no one seems to want to do a root-cause, let's just revert it for now as
> > it is affecting people using the latest release as well as the stable
> > kernels that it has been backported to.
>
> NACK. This re-introduces a CVE.
As I said elsewhere, when a commit that is assigned a CVE is reverted,
then the CVE gets revoked. But I don't see this commit being assigned
to a CVE, so what CVE specifically are you referring to?
thanks,
greg k-h
next prev parent reply other threads:[~2025-02-26 16:22 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-26 14:29 [PATCH] Revert "libfs: Use d_children list to iterate simple_offset directories" Greg Kroah-Hartman
2025-02-26 15:57 ` Chuck Lever
2025-02-26 16:21 ` Greg Kroah-Hartman [this message]
2025-02-26 16:28 ` Chuck Lever
2025-02-26 19:13 ` Greg Kroah-Hartman
2025-02-26 20:33 ` Chuck Lever
2025-03-10 16:29 ` Greg Kroah-Hartman
2025-03-10 17:30 ` Chuck Lever
2025-03-11 13:55 ` Sun Yongjian
2025-03-11 15:23 ` Chuck Lever
2025-03-11 18:11 ` Darrick J. Wong
2025-03-11 18:25 ` Chuck Lever
2025-03-11 18:52 ` Darrick J. Wong
2025-03-11 19:39 ` Chuck Lever
2025-03-11 21:47 ` Kent Overstreet
2025-03-12 15:39 ` Christoph Hellwig
2025-03-12 15:47 ` Christoph Hellwig
2025-03-13 13:45 ` Chuck Lever
2025-03-18 11:38 ` Sun Yongjian
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=2025022621-worshiper-turtle-6eb1@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=brauner@kernel.org \
--cc=chuck.lever@oracle.com \
--cc=jack@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=stable@kernel.org \
--cc=tiwai@suse.de \
--cc=viro@zeniv.linux.org.uk \
/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