stable.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sasha Levin <sashal@kernel.org>
To: stable@vger.kernel.org, chao@kernel.org
Cc: Sasha Levin <sashal@kernel.org>
Subject: Re: [PATCH 1/2] f2fs: sysfs: add encoding_flags entry
Date: Wed, 25 Jun 2025 10:07:15 -0400	[thread overview]
Message-ID: <20250624185610-72bf30d9c2d40956@stable.kernel.org> (raw)
In-Reply-To: <20250416054805.1416834-1-chao@kernel.org>

[ Sasha's backport helper bot ]

Hi,

Summary of potential issues:
⚠️ Found matching upstream commit but patch is missing proper reference to it

Found matching upstream commit: 3fea0641b06ff4e53d95d07a96764d8951d4ced6

Note: The patch differs from the upstream commit:
---
1:  3fea0641b06ff ! 1:  14acd457cfe03 f2fs: sysfs: add encoding_flags entry
    @@ Commit message
         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
    @@ Commit message
         2
     
         Signed-off-by: Chao Yu <chao@kernel.org>
    -    Signed-off-by: Jaegeuk Kim <jaegeuk@kernel.org>
     
      ## Documentation/ABI/testing/sysfs-fs-f2fs ##
     @@ Documentation/ABI/testing/sysfs-fs-f2fs: Description:	For several zoned storage devices, vendors will provide extra space
    @@ Documentation/ABI/testing/sysfs-fs-f2fs: Description:	For several zoned storage
     +Description:	This 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
    -+		============================     ==========
    ++		===========================      ==========
     
      ## fs/f2fs/sysfs.c ##
     @@ fs/f2fs/sysfs.c: static ssize_t encoding_show(struct f2fs_attr *a,
---

Results of testing on various branches:

| Branch                    | Patch Apply | Build Test |
|---------------------------|-------------|------------|
| stable/linux-5.4.y        |  Success    |  Success   |

      parent reply	other threads:[~2025-06-25 14:07 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20250416054805.1416834-1-chao@kernel.org>
2025-06-24 10:00 ` [STABLE 5.15+] f2fs: sysfs: add encoding_flags entry 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
2025-06-25 14:07 ` Sasha Levin [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=20250624185610-72bf30d9c2d40956@stable.kernel.org \
    --to=sashal@kernel.org \
    --cc=chao@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;
as well as URLs for NNTP newsgroup(s).