From: Matthew Wilcox <willy@infradead.org>
To: Chris S <coshi036@gmail.com>
Cc: Jan Kara <jack@suse.cz>,
linux-fsdevel@vger.kernel.org, viro@zeniv.linux.org.uk,
brauner@kernel.org, linux-kernel@vger.kernel.org,
Sungwoo Kim <iam@sung-woo.kim>, Dave Tian <daveti@purdue.edu>,
Weidong Zhu <weizhu@fiu.edu>
Subject: Re: [PATCH v2] fs/buffer: serialize set_buffer_uptodate against concurrent clears
Date: Thu, 30 Jul 2026 21:20:24 +0100 [thread overview]
Message-ID: <amuyCIg0Y1YRiFT7@casper.infradead.org> (raw)
In-Reply-To: <CACd_6n1Sht4xs6P_GT0-+wj1uu9Ww_4X=TysQRvq6ZSFJ71CBQ@mail.gmail.com>
On Thu, Jul 30, 2026 at 03:47:23PM -0400, Chris S wrote:
> Hi Jan, I'm currently working on the changes we discussed. Based on
> vfs.all now. Four things came out of writing it that I would rather
> resolve before posting.
>
> 1. mark_buffer_write_io_error() is not safe for jbd2's buffers yet. It
> dereferences bh->b_folio->mapping directly (fs/buffer.c:1057), and
> jbd2_journal_write_metadata_buffer() points the temporary bh at
> virt_to_folio(jh->b_frozen_data), which is slab-backed.
... yeah. That's one of the unclean things which keeps me awake at
night. Sorry you ran into it.
My longterm plan for this particular usecase (pointing a bh at slab
memory) is to have bh->b_folio = NULL, bh->b_data = (address of data).
Maybe we could do that now? That would make mark_buffer_write_io_error()
work without change today.
There might be a good reason I didn't do that yet, but I forget what it
was.
next prev parent reply other threads:[~2026-07-30 20:20 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-30 5:36 Chao Shi
2026-04-30 7:28 ` Jan Kara
2026-07-19 6:28 ` Chao S
2026-07-28 19:45 ` Jan Kara
2026-07-29 7:54 ` Chris S
2026-07-30 19:47 ` Chris S
2026-07-30 20:20 ` Matthew Wilcox [this message]
2026-07-30 22:09 ` Chris S
2026-07-31 0:45 ` Matthew Wilcox
2026-07-31 15:12 ` Chris S
2026-07-31 17:51 ` Jan Kara
2026-07-31 17:59 ` Chris S
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=amuyCIg0Y1YRiFT7@casper.infradead.org \
--to=willy@infradead.org \
--cc=brauner@kernel.org \
--cc=coshi036@gmail.com \
--cc=daveti@purdue.edu \
--cc=iam@sung-woo.kim \
--cc=jack@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=viro@zeniv.linux.org.uk \
--cc=weizhu@fiu.edu \
/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
all inboxes | Powered by JetHome®