Linux XFS filesystem development
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: Tal Zussman <tz2294@columbia.edu>
Cc: Christoph Hellwig <hch@infradead.org>,
	Jens Axboe <axboe@kernel.dk>,
	"Matthew Wilcox (Oracle)" <willy@infradead.org>,
	Christian Brauner <brauner@kernel.org>,
	"Darrick J. Wong" <djwong@kernel.org>,
	Carlos Maiolino <cem@kernel.org>,
	Alexander Viro <viro@zeniv.linux.org.uk>, Jan Kara <jack@suse.cz>,
	Gao Xiang <xiang@kernel.org>, Chao Yu <chao@kernel.org>,
	Yue Hu <zbestahu@gmail.com>,
	Jeffle Xu <jefflexu@linux.alibaba.com>,
	Sandeep Dhavale <dhavale@google.com>,
	Hongbo Li <lihongbo22@huawei.com>,
	Chunhai Guo <guochunhai@vivo.com>, Dave Chinner <dgc@kernel.org>,
	Bart Van Assche <bvanassche@acm.org>,
	Hillf Danton <hdanton@sina.com>,
	Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
	linux-block@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-xfs@vger.kernel.org, linux-fsdevel@vger.kernel.org,
	linux-mm@kvack.org, linux-erofs@lists.ozlabs.org,
	Christoph Hellwig <hch@lst.de>
Subject: Re: [PATCH v7 3/5] iomap: use BIO_COMPLETE_IN_TASK for dropbehind writeback
Date: Tue, 4 Aug 2026 06:03:55 -0700	[thread overview]
Message-ID: <anHjO1vokMmADsZP@infradead.org> (raw)
In-Reply-To: <15506dc8-e5b8-4fa8-a85f-912a92edb83f@columbia.edu>

On Thu, Jul 30, 2026 at 04:39:03PM -0400, Tal Zussman wrote:
> Sorry, I misunderstood and assumed you'd take care of it in a follow-up.
> I'll adjust it as below and send v8.

My plan was to move from the version you had to something better in a
follow-up.  Anyway, Jens merged it as-is so I'll look into a fixup.
Travelling for two conferences this week might make this a bit slow,
though.

> > And move setting the flag to iomap_ioend_writeback_submit, and only
> > for the case where no io_bio.bi_end_io is already assigned.
> > 
> 
> To confirm, this would only work because XFS provides its own task context
> and is the only consumer of iomap that sets its own io_bio.bi_end_io.
> If another filesystem set it and didn't provide task context, this would
> break, right? I can add a comment about this requirement, but I want to
> confirm the intent, as it feels a little fragile as-is.

Yes.  And I think this might be a good time to actually open code
iomap_ioend_writeback_submit in XFS and remove the "accept an overriden
bi_io_end" thing entirely.  Back in the original code that was required,
but now that the submission happens from a file system methods there is
no good reason for keeping it.


  reply	other threads:[~2026-08-04 13:04 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-30  6:57 [PATCH v7 0/5] block: enable RWF_DONTCACHE for block devices Tal Zussman
2026-07-30  6:57 ` [PATCH v7 1/5] block: introduce bio_in_atomic() Tal Zussman
2026-07-30  8:06   ` Christoph Hellwig
2026-07-30  9:02   ` Jan Kara
2026-07-30  6:57 ` [PATCH v7 2/5] block: add task-context bio completion infrastructure Tal Zussman
2026-07-30  8:09   ` Christoph Hellwig
2026-07-30  9:29   ` Jan Kara
2026-07-30  6:57 ` [PATCH v7 3/5] iomap: use BIO_COMPLETE_IN_TASK for dropbehind writeback Tal Zussman
2026-07-30  8:13   ` Christoph Hellwig
2026-07-30 20:39     ` Tal Zussman
2026-08-04 13:03       ` Christoph Hellwig [this message]
2026-07-30  6:57 ` [PATCH v7 4/5] buffer: set " Tal Zussman
2026-07-30  9:31   ` Jan Kara
2026-07-30  6:57 ` [PATCH v7 5/5] block: enable RWF_DONTCACHE for block devices Tal Zussman
2026-07-30  9:33   ` Jan Kara
2026-07-31 23:55   ` Tal Zussman
2026-07-31 15:01 ` [PATCH v7 0/5] " Jens Axboe

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=anHjO1vokMmADsZP@infradead.org \
    --to=hch@infradead.org \
    --cc=axboe@kernel.dk \
    --cc=bigeasy@linutronix.de \
    --cc=brauner@kernel.org \
    --cc=bvanassche@acm.org \
    --cc=cem@kernel.org \
    --cc=chao@kernel.org \
    --cc=dgc@kernel.org \
    --cc=dhavale@google.com \
    --cc=djwong@kernel.org \
    --cc=guochunhai@vivo.com \
    --cc=hch@lst.de \
    --cc=hdanton@sina.com \
    --cc=jack@suse.cz \
    --cc=jefflexu@linux.alibaba.com \
    --cc=lihongbo22@huawei.com \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-erofs@lists.ozlabs.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=linux-xfs@vger.kernel.org \
    --cc=tz2294@columbia.edu \
    --cc=viro@zeniv.linux.org.uk \
    --cc=willy@infradead.org \
    --cc=xiang@kernel.org \
    --cc=zbestahu@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox