From: Christian Brauner <brauner@kernel.org>
To: Jan Kara <jack@suse.cz>
Cc: Christian Brauner <brauner@kernel.org>,
linux-fsdevel@vger.kernel.org, Ruikai Peng <ruikai@pwno.io>
Subject: Re: [PATCH v2] fs: Handle multiply claimed blocks more gracefully with mmb
Date: Thu, 23 Apr 2026 13:54:53 +0200 [thread overview]
Message-ID: <20260423-relevant-zaungast-6ab72fecb116@brauner> (raw)
In-Reply-To: <20260423090311.10955-2-jack@suse.cz>
On Thu, 23 Apr 2026 11:03:12 +0200, Jan Kara wrote:
> When a metadata block is referenced by multiple inodes and tracked by
> metadata bh infrastructure (which is forbidden and generally indicates
> filesystem corruption), it can happen that mmb_mark_buffer_dirty() is
> called for two different mmb structures in parallel. This can lead to a
> corruption of mmb linked list. Handle that situation gracefully (at
> least from mmb POV) by serializing on setting bh->b_mmb.
>
> [...]
Applied to the vfs.fixes branch of the vfs/vfs.git tree.
Patches in the vfs.fixes branch should appear in linux-next soon.
Please report any outstanding bugs that were missed during review in a
new review to the original patch series allowing us to drop it.
It's encouraged to provide Acked-bys and Reviewed-bys even though the
patch has now been applied. If possible patch trailers will be updated.
Note that commit hashes shown below are subject to change due to rebase,
trailer updates or similar. If in doubt, please check the listed branch.
tree: https://git.kernel.org/pub/scm/linux/kernel/git/vfs/vfs.git
branch: vfs.fixes
[1/1] fs: Handle multiply claimed blocks more gracefully with mmb
https://git.kernel.org/vfs/vfs/c/85cd1b6eda78
prev parent reply other threads:[~2026-04-23 11:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-23 9:03 [PATCH v2] fs: Handle multiply claimed blocks more gracefully with mmb Jan Kara
2026-04-23 11:54 ` Christian Brauner [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=20260423-relevant-zaungast-6ab72fecb116@brauner \
--to=brauner@kernel.org \
--cc=jack@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=ruikai@pwno.io \
/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