From: "Darrick J. Wong" <djwong@kernel.org>
To: Andrea Parri <parri.andrea@gmail.com>
Cc: Christian Brauner <brauner@kernel.org>,
Carlos Maiolino <cem@kernel.org>,
Joanne Koong <joannelkoong@gmail.com>,
Brian Foster <bfoster@redhat.com>,
Christoph Hellwig <hch@infradead.org>,
Damien Le Moal <dlemoal@kernel.org>,
Hannes Reinecke <hare@suse.de>,
Daniel Gomez <da.gomez@samsung.com>,
Pankaj Raghav <p.raghav@samsung.com>,
Dave Chinner <dchinner@redhat.com>,
linux-xfs@vger.kernel.org, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH v2 1/4] iomap: don't resubmit an ioend after ->writeback_submit() failed
Date: Thu, 24 Sep 2026 15:33:20 -0700 [thread overview]
Message-ID: <20260924223320.GL2705364@frogsfrogsfrogs> (raw)
In-Reply-To: <20260924203013.9967-1-parri.andrea@gmail.com>
On Thu, Sep 24, 2026 at 10:30:07PM +0200, Andrea Parri wrote:
> On Thu, Sep 24, 2026 at 11:49:10AM -0700, Darrick J. Wong wrote:
> > I looked around the codebase and saw that iomap_writepages also calls
> > ->writeback_submit. Does that need to null out wb_ctx?
> >
> > My guess is that none of the callers do anything with wpc after
> > iomap_writepages returns so it's not harming anyone, but we should drop
> > the stale context too, right?
>
> Your guess is right: that ->writeback_submit() call is the last thing
> iomap_writepages() does, and all of its callers (xfs, gfs2, zonefs,
> exfat, fuse, ntfs, ntfs3) have the wpc on the stack for that single
> call, so wb_ctx is never looked at again. Christoph made the same
> point on v1 [1], and the last paragraph of the commit message now
> spells it out.
>
> Clearing it there as well would be harmless but dead code, so I'd
> rather leave it out; happy to add it if you feel strongly about it.
>
> [1] https://lore.kernel.org/all/arITXTsUhrA0N-qr@infradead.org/
LOL ok thanks for the reminder. My brain is fried this week, in a good
way. ;)
--D
> Thanks!
> Andrea
>
next prev parent reply other threads:[~2026-09-24 22:33 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-24 9:11 [PATCH v2 0/4] iomap: fix error handling regressions Andrea Parri
2026-09-24 9:11 ` [PATCH v2 1/4] iomap: don't resubmit an ioend after ->writeback_submit() failed Andrea Parri
2026-09-24 18:49 ` Darrick J. Wong
2026-09-24 20:30 ` Andrea Parri
2026-09-24 22:33 ` Darrick J. Wong [this message]
2026-09-25 4:46 ` Christoph Hellwig
2026-09-24 9:11 ` [PATCH v2 2/4] xfs: add an error tag to inject a ->writeback_submit() failure Andrea Parri
2026-09-24 18:49 ` Darrick J. Wong
2026-09-25 4:46 ` Christoph Hellwig
2026-09-24 9:11 ` [PATCH v2 3/4] iomap: don't lose a fiemap iteration error when emitting the last extent Andrea Parri
2026-09-24 9:11 ` [PATCH v2 4/4] iomap: don't lose a failed direct I/O bio's error when zeroing the tail Andrea Parri
2026-09-24 18:53 ` Darrick J. Wong
2026-09-24 20:30 ` Andrea Parri
2026-09-24 22:36 ` Darrick J. Wong
2026-09-25 4:48 ` Christoph Hellwig
2026-09-25 6:43 ` Pankaj Raghav (Samsung)
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=20260924223320.GL2705364@frogsfrogsfrogs \
--to=djwong@kernel.org \
--cc=bfoster@redhat.com \
--cc=brauner@kernel.org \
--cc=cem@kernel.org \
--cc=da.gomez@samsung.com \
--cc=dchinner@redhat.com \
--cc=dlemoal@kernel.org \
--cc=hare@suse.de \
--cc=hch@infradead.org \
--cc=joannelkoong@gmail.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=p.raghav@samsung.com \
--cc=parri.andrea@gmail.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 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.