From: Christoph Hellwig <hch@lst.de>
To: Christian Brauner <brauner@kernel.org>
Cc: Christoph Hellwig <hch@lst.de>,
linux-fsdevel@vger.kernel.org, Chris Mason <clm@meta.com>,
Josef Bacik <josef@toxicpanda.com>,
Matthew Wilcox <willy@infradead.org>,
Zhang Yi <yi.zhang@huaweicloud.com>,
Joanne Koong <joannelkoong@gmail.com>,
"Darrick J. Wong" <djwong@kernel.org>,
Brian Foster <bfoster@redhat.com>,
linux-xfs@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH 1/2] iomap: don't mark unwritten parts of a folio uptodate
Date: Thu, 29 Oct 2026 13:21:55 +0100 [thread overview]
Message-ID: <20261029122155.GB24811@lst.de> (raw)
In-Reply-To: <20261029-betuchte-unzeit-heimcomputer-392ff6bd4772@brauner>
On Thu, Oct 29, 2026 at 01:20:09PM +0100, Christian Brauner wrote:
> > Can we wire this up to xfstests, please?
>
> I have an endless queue of additional bugs to go through so I can say
> yes but I can't commit to any timeframe nor the ability to remember.
>
> > > Willy reported this back in 2024 (cf. [1]) and Zhang Yi posted the same
> > > fix (cf. [2]) but it never got merged.
> >
> > Should we credit the original submission then?
>
> It's references in the commit message already. Tell me what you think we
> need to see there and I'll amend in-tree.
Usually that just means taking the older patch instead of the newer one.
Although chances are that this one might not apply anymore, in which
case taking the new one should be ok.
next prev parent reply other threads:[~2026-10-29 12:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-29 10:34 [PATCH 0/2] iomap: fixes for short copies and integrity bio sizes Christian Brauner
2026-10-29 10:34 ` [PATCH 1/2] iomap: don't mark unwritten parts of a folio uptodate Christian Brauner
2026-10-29 12:12 ` Christoph Hellwig
2026-10-29 12:20 ` Christian Brauner
2026-10-29 12:21 ` Christoph Hellwig [this message]
2026-10-29 20:08 ` Joanne Koong
2026-10-30 1:07 ` Zhang Yi
2026-10-29 10:34 ` [PATCH 2/2] iomap: keep large chunks from defeating the bio cap Christian Brauner
2026-10-29 12:12 ` Christoph Hellwig
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=20261029122155.GB24811@lst.de \
--to=hch@lst.de \
--cc=bfoster@redhat.com \
--cc=brauner@kernel.org \
--cc=clm@meta.com \
--cc=djwong@kernel.org \
--cc=joannelkoong@gmail.com \
--cc=josef@toxicpanda.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=stable@vger.kernel.org \
--cc=willy@infradead.org \
--cc=yi.zhang@huaweicloud.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