All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sasha Levin <sashal@kernel.org>
To: stable@vger.kernel.org
Cc: bin.lan.cn@eng.windriver.com, Sasha Levin <sashal@kernel.org>
Subject: Re: [PATCH 6.1] ext4: fix uninitialized ratelimit_state->lock access in __ext4_fill_super()
Date: Fri, 13 Dec 2024 10:13:12 -0500	[thread overview]
Message-ID: <20241213095854-2f81422cdd663754@stable.kernel.org> (raw)
In-Reply-To: <20241213071055.3601224-1-bin.lan.cn@eng.windriver.com>

[ Sasha's backport helper bot ]

Hi,

The upstream commit SHA1 provided is correct: b4b4fda34e535756f9e774fb2d09c4537b7dfd1c

WARNING: Author mismatch between patch and upstream commit:
Backport author: bin.lan.cn@eng.windriver.com
Commit author: Baokun Li <libaokun1@huawei.com>


Status in newer kernel trees:
6.12.y | Present (exact SHA1)
6.6.y | Present (different SHA1: 23afcd52af06)
6.1.y | Not found

Note: The patch differs from the upstream commit:
---
1:  b4b4fda34e535 ! 1:  5f07a4e2bb575 ext4: fix uninitialized ratelimit_state->lock access in __ext4_fill_super()
    @@ Metadata
      ## Commit message ##
         ext4: fix uninitialized ratelimit_state->lock access in __ext4_fill_super()
     
    +    [ Upstream commit b4b4fda34e535756f9e774fb2d09c4537b7dfd1c ]
    +
         In the following concurrency we will access the uninitialized rs->lock:
     
         ext4_fill_super
    @@ Commit message
         Reviewed-by: Jan Kara <jack@suse.cz>
         Link: https://lore.kernel.org/r/20240102133730.1098120-1-libaokun1@huawei.com
         Signed-off-by: Theodore Ts'o <tytso@mit.edu>
    +    [ Resolve merge conflicts ]
    +    Signed-off-by: Bin Lan <bin.lan.cn@windriver.com>
     
      ## fs/ext4/super.c ##
     @@ fs/ext4/super.c: static int __ext4_fill_super(struct fs_context *fc, struct super_block *sb)
    @@ fs/ext4/super.c: static int __ext4_fill_super(struct fs_context *fc, struct supe
      
     -failed_mount10:
     +failed_mount9:
    - 	ext4_quotas_off(sb, EXT4_MAXQUOTAS);
    + 	ext4_quota_off_umount(sb);
     -failed_mount9: __maybe_unused
     +failed_mount8: __maybe_unused
      	ext4_release_orphan_info(sb);
---

Results of testing on various branches:

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

      parent reply	other threads:[~2024-12-13 15:13 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-13  7:10 [PATCH 6.1] ext4: fix uninitialized ratelimit_state->lock access in __ext4_fill_super() bin.lan.cn
2024-12-13 11:14 ` Greg KH
2024-12-13 15:13 ` 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=20241213095854-2f81422cdd663754@stable.kernel.org \
    --to=sashal@kernel.org \
    --cc=bin.lan.cn@eng.windriver.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.