From: Sasha Levin <sashal@kernel.org>
To: stable@vger.kernel.org
Cc: vgiraud.opensource@witekio.com, Sasha Levin <sashal@kernel.org>
Subject: Re: [PATCH 6.1] ext4: fix access to uninitialised lock in fc replay path
Date: Wed, 29 Jan 2025 06:21:42 -0500 [thread overview]
Message-ID: <20250129055448-06eddbf7ca29c76b@stable.kernel.org> (raw)
In-Reply-To: <20250129101046.105471-1-vgiraud.opensource@witekio.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: vgiraud.opensource@witekio.com
Commit author: Luis Henriques (SUSE)<luis.henriques@linux.dev>
Status in newer kernel trees:
6.13.y | Branch not found
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: 366f73b541bff 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: Bruno VERNAY <bruno.vernay@se.com>
+ Signed-off-by: Victor Giraud <vgiraud.opensource@witekio.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:[~2025-01-29 11:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-29 10:10 [PATCH 6.1] ext4: fix access to uninitialised lock in fc replay path vgiraud.opensource
2025-01-29 11:21 ` Sasha Levin [this message]
2025-01-30 9:41 ` Greg KH
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=20250129055448-06eddbf7ca29c76b@stable.kernel.org \
--to=sashal@kernel.org \
--cc=stable@vger.kernel.org \
--cc=vgiraud.opensource@witekio.com \
/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.