Linux kernel -stable discussions
 help / color / mirror / Atom feed
From: Sasha Levin <sashal@kernel.org>
To: stable@vger.kernel.org
Cc: alvalan9@foxmail.com, Sasha Levin <sashal@kernel.org>
Subject: Re: [PATCH 6.12.y] f2fs: fix to avoid accessing uninitialized curseg
Date: Tue,  3 Jun 2025 14:36:07 -0400	[thread overview]
Message-ID: <20250603141552-7a6a230121fa0c39@stable.kernel.org> (raw)
In-Reply-To: <tencent_381A1068DD6A903EBA2513AD817046602209@qq.com>

[ Sasha's backport helper bot ]

Hi,

✅ All tests passed successfully. No issues detected.
No action required from the submitter.

The upstream commit SHA1 provided is correct: 986c50f6bca109c6cf362b4e2babcb85aba958f6

WARNING: Author mismatch between patch and upstream commit:
Backport author: alvalan9@foxmail.com
Commit author: Chao Yu<chao@kernel.org>

Status in newer kernel trees:
6.15.y | Present (exact SHA1)
6.14.y | Present (different SHA1: 7f90e5d423cd)

Note: The patch differs from the upstream commit:
---
1:  986c50f6bca10 ! 1:  7a4b17ea75981 f2fs: fix to avoid accessing uninitialized curseg
    @@ Metadata
      ## Commit message ##
         f2fs: fix to avoid accessing uninitialized curseg
     
    +    [ Upstream commit 986c50f6bca109c6cf362b4e2babcb85aba958f6 ]
    +
         syzbot reports a f2fs bug as below:
     
         F2FS-fs (loop3): Stopped filesystem due to reason: 7
    @@ Commit message
         Closes: https://lore.kernel.org/all/67973c2b.050a0220.11b1bb.0089.GAE@google.com
         Signed-off-by: Chao Yu <chao@kernel.org>
         Signed-off-by: Jaegeuk Kim <jaegeuk@kernel.org>
    +    Signed-off-by: Alva Lan <alvalan9@foxmail.com>
     
      ## fs/f2fs/inode.c ##
     @@ fs/f2fs/inode.c: int f2fs_write_inode(struct inode *inode, struct writeback_control *wbc)
---

Results of testing on various branches:

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

      reply	other threads:[~2025-06-03 18:36 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-03  6:47 [PATCH 6.12.y] f2fs: fix to avoid accessing uninitialized curseg alvalan9
2025-06-03 18:36 ` 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=20250603141552-7a6a230121fa0c39@stable.kernel.org \
    --to=sashal@kernel.org \
    --cc=alvalan9@foxmail.com \
    --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