mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Lee Jones <lee@kernel.org>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Chao Yu <chao@kernel.org>,
	stable@vger.kernel.org, Sasha Levin <sashal@kernel.org>,
	jaegeuk@kernel.org, linux-f2fs-devel@lists.sourceforge.net,
	linux-kernel@vger.kernel.org
Subject: Re: [STABLE 5.15+] f2fs: sysfs: add encoding_flags entry
Date: Thu, 24 Jul 2025 11:18:17 +0100	[thread overview]
Message-ID: <20250724101817.GZ11056@google.com> (raw)
In-Reply-To: <2025072354-tricolor-annex-92fb@gregkh>

On Wed, 23 Jul 2025, Greg Kroah-Hartman wrote:

> On Wed, Jul 23, 2025 at 09:26:39AM +0100, Lee Jones wrote:
> > On Wed, 02 Jul 2025, Greg Kroah-Hartman wrote:
> > 
> > > On Tue, Jun 24, 2025 at 11:00:39AM +0100, Lee Jones wrote:
> > > > On Wed, 16 Apr 2025, Chao Yu wrote:
> > > > 
> > > > > This patch adds a new sysfs entry /sys/fs/f2fs/<disk>/encoding_flags,
> > > > > it is a read-only entry to show the value of sb.s_encoding_flags, the
> > > > > value is hexadecimal.
> > > > > 
> > > > > ===========================      ==========
> > > > > Flag_Name                        Flag_Value
> > > > > ===========================      ==========
> > > > > SB_ENC_STRICT_MODE_FL            0x00000001
> > > > > SB_ENC_NO_COMPAT_FALLBACK_FL     0x00000002
> > > > > ===========================      ==========
> > > > > 
> > > > > case#1
> > > > > mkfs.f2fs -f -O casefold -C utf8:strict /dev/vda
> > > > > mount /dev/vda /mnt/f2fs
> > > > > cat /sys/fs/f2fs/vda/encoding_flags
> > > > > 1
> > > > > 
> > > > > case#2
> > > > > mkfs.f2fs -f -O casefold -C utf8 /dev/vda
> > > > > fsck.f2fs --nolinear-lookup=1 /dev/vda
> > > > > mount /dev/vda /mnt/f2fs
> > > > > cat /sys/fs/f2fs/vda/encoding_flags
> > > > > 2
> > > > > 
> > > > > Signed-off-by: Chao Yu <chao@kernel.org>
> > > > > ---
> > > > >  Documentation/ABI/testing/sysfs-fs-f2fs | 13 +++++++++++++
> > > > >  fs/f2fs/sysfs.c                         |  9 +++++++++
> > > > >  2 files changed, 22 insertions(+)
> > > > 
> > > > This patch, commit 617e0491abe4 ("f2fs: sysfs: export linear_lookup in
> > > > features directory") upstream, needs to find its way into all Stable
> > > > branches containing upstream commit 91b587ba79e1 ("f2fs: Introduce
> > > > linear search for dentries"), which is essentially linux-5.15.y and
> > > > newer.
> > > > 
> > > > stable/linux-5.4.y:
> > > > MISSING:     f2fs: Introduce linear search for dentries
> > > > MISSING:     f2fs: sysfs: export linear_lookup in features directory
> > > > 
> > > > stable/linux-5.10.y:
> > > > MISSING:     f2fs: Introduce linear search for dentries
> > > > MISSING:     f2fs: sysfs: export linear_lookup in features directory
> > > > 
> > > > stable/linux-5.15.y:
> > > > b0938ffd39ae f2fs: Introduce linear search for dentries [5.15.179]
> > > > MISSING:     f2fs: sysfs: export linear_lookup in features directory
> > > > 
> > > > stable/linux-6.1.y:
> > > > de605097eb17 f2fs: Introduce linear search for dentries [6.1.129]
> > > > MISSING:     f2fs: sysfs: export linear_lookup in features directory
> > > > 
> > > > stable/linux-6.6.y:
> > > > 0bf2adad03e1 f2fs: Introduce linear search for dentries [6.6.76]
> > > > MISSING:     f2fs: sysfs: export linear_lookup in features directory
> > > > 
> > > > stable/linux-6.12.y:
> > > > 00d1943fe46d f2fs: Introduce linear search for dentries [6.12.13]
> > > > MISSING:     f2fs: sysfs: export linear_lookup in features directory
> > > > 
> > > > mainline:
> > > > 91b587ba79e1 f2fs: Introduce linear search for dentries
> > > > 617e0491abe4 f2fs: sysfs: export linear_lookup in features directory
> > > 
> > > Great, then can someone submit these in a format we can apply them in?
> > > or do clean cherry-picks work properly?
> > 
> > Does this work:
> > 
> > Please backport upstream commit:
> > 
> >   617e0491abe4 f2fs: sysfs: export linear_lookup in features directory
> > 
> > ... to all stable branches up to and including linux-5.15.y.
> > 
> > If there are conflicts, I can do the backport myself and submit as patches.
> 
> There are conflicts, it doesn't apply to 6.1.y or 5.15.y :(

Okay, thanks for trying.  Leave it with me.

-- 
Lee Jones [李琼斯]

      reply	other threads:[~2025-07-24 10:18 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-16  5:48 [PATCH 1/2] " Chao Yu
2025-04-16  5:48 ` [PATCH 2/2] f2fs: sysfs: export linear_lookup in features directory Chao Yu
2025-04-28 22:40 ` [f2fs-dev] [PATCH 1/2] f2fs: sysfs: add encoding_flags entry patchwork-bot+f2fs
2025-06-24 10:00 ` [STABLE 5.15+] " Lee Jones
2025-07-02 10:20   ` Greg Kroah-Hartman
2025-07-23  8:26     ` Lee Jones
2025-07-23  9:41       ` Greg Kroah-Hartman
2025-07-24 10:18         ` Lee Jones [this message]

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=20250724101817.GZ11056@google.com \
    --to=lee@kernel.org \
    --cc=chao@kernel.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=jaegeuk@kernel.org \
    --cc=linux-f2fs-devel@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sashal@kernel.org \
    --cc=stable@vger.kernel.org \
    /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

all inboxes | Powered by JetHome®