From: Greg KH <gregkh@linuxfoundation.org>
To: Daniel Rosenberg <drosen@google.com>
Cc: Todd Kjos <tkjos@google.com>, stable <stable@vger.kernel.org>,
Android Kernel Team <kernel-team@android.com>,
Theodore Ts'o <tytso@mit.edu>
Subject: Re: f2fs: Introduce linear search for dentries
Date: Tue, 4 Feb 2025 12:33:44 +0100 [thread overview]
Message-ID: <2025020423-paycheck-strength-75ff@gregkh> (raw)
In-Reply-To: <2025020432-stiffen-expire-30bd@gregkh>
On Tue, Feb 04, 2025 at 12:32:22PM +0100, Greg KH wrote:
> On Mon, Feb 03, 2025 at 03:07:10PM -0800, Daniel Rosenberg wrote:
> > On Sat, Feb 1, 2025 at 12:29 AM Greg KH <gregkh@linuxfoundation.org> wrote:
> > >
> > > As the original commit that this says it fixes was reverted, should that
> > > also be brought back everywhere also? Or did that happen already and I
> > > missed that?
> > >
> > > thanks,
> > >
> > > greg k-h
> >
> > The revert of the unicode patch is in all of the stable branches
> > already. That f2fs patch is technically a fix for the revert as well,
> > since the existence of either of those is a problem for the same
> > reason :/
>
> Ok, so that means that the original issue is still in mainline but now
> it is safe to bring the unicode patch back there and add it to the
> stable branches if we also take this one?
It also does not apply cleanly to 5.4.y and 5.10.y so can we get
backports for that sent here?
thanks,
greg k-h
next prev parent reply other threads:[~2025-02-04 11:33 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-31 21:49 f2fs: Introduce linear search for dentries Daniel Rosenberg
2025-02-01 8:28 ` Greg KH
2025-02-01 17:06 ` Todd Kjos
2025-02-03 23:07 ` Daniel Rosenberg
2025-02-04 11:32 ` Greg KH
2025-02-04 11:33 ` Greg KH [this message]
2025-02-04 21:24 ` Daniel Rosenberg
2025-02-05 4:41 ` Theodore Ts'o
2025-02-08 5:30 ` Theodore Ts'o
2025-02-10 21:21 ` Gabriel Krisman Bertazi
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=2025020423-paycheck-strength-75ff@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=drosen@google.com \
--cc=kernel-team@android.com \
--cc=stable@vger.kernel.org \
--cc=tkjos@google.com \
--cc=tytso@mit.edu \
/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