From: Sasha Levin <sashal@kernel.org>
To: stable@vger.kernel.org
Cc: jianqi.ren.cn@windriver.com, Sasha Levin <sashal@kernel.org>
Subject: Re: [PATCH 6.1.y] ext4: fix access to uninitialised lock in fc replay path
Date: Wed, 11 Dec 2024 11:33:00 -0500 [thread overview]
Message-ID: <20241211091132-c6bd258ba4891a23@stable.kernel.org> (raw)
In-Reply-To: <20241211101304.2070456-1-jianqi.ren.cn@windriver.com>
[ Sasha's backport helper bot ]
Hi,
The upstream commit SHA1 provided is correct: 23dfdb56581ad92a9967bcd720c8c23356af74c1
WARNING: Author mismatch between patch and upstream commit:
Backport author: <jianqi.ren.cn@windriver.com>
Commit author: Luis Henriques (SUSE) <luis.henriques@linux.dev>
Status in newer kernel trees:
6.12.y | Present (exact SHA1)
6.6.y | Not found
6.1.y | Not found
Note: The patch differs from the upstream commit:
---
1: 23dfdb56581ad ! 1: a7dddfd22e8bc ext4: fix access to uninitialised lock in fc replay path
@@ Metadata
## Commit message ##
ext4: fix access to uninitialised lock in fc replay path
+ [ commit 23dfdb56581ad92a9967bcd720c8c23356af74c1 upstream ]
+
The following kernel trace can be triggered with fstest generic/629 when
executed against a filesystem with fast-commit feature enabled:
@@ Commit message
Link: https://patch.msgid.link/20240718094356.7863-1-luis.henriques@linux.dev
Signed-off-by: Theodore Ts'o <tytso@mit.edu>
Cc: stable@kernel.org
+ Signed-off-by: Jianqi Ren <jianqi.ren.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
* used to detect the metadata async write error.
*/
- spin_lock_init(&sbi->s_bdev_wb_lock);
- errseq_check_and_advance(&sb->s_bdev->bd_mapping->wb_err,
+ errseq_check_and_advance(&sb->s_bdev->bd_inode->i_mapping->wb_err,
&sbi->s_bdev_wb_err);
- EXT4_SB(sb)->s_mount_state |= EXT4_ORPHAN_FS;
+ sb->s_bdev->bd_super = sb;
---
Results of testing on various branches:
| Branch | Patch Apply | Build Test |
|---------------------------|-------------|------------|
| stable/linux-6.1.y | Success | Success |
next prev parent reply other threads:[~2024-12-11 16:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-11 10:13 [PATCH 6.1.y] ext4: fix access to uninitialised lock in fc replay path jianqi.ren.cn
2024-12-11 16:33 ` Sasha Levin [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-01-26 7:06 Imkanmod Khan
2025-01-26 17:22 ` Sasha Levin
2024-12-11 4:13 jianqi.ren.cn
2024-12-11 16:32 ` Sasha Levin
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=20241211091132-c6bd258ba4891a23@stable.kernel.org \
--to=sashal@kernel.org \
--cc=jianqi.ren.cn@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 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).