From: Christoph Hellwig <hch@lst.de>
To: Christian Brauner <brauner@kernel.org>
Cc: djwong@kernel.org, Namjae Jeon <linkinjeon@kernel.org>,
willy@infradead.org, xiang@kernel.org, hch@lst.de,
linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH RESEND] iomap: remove over-strict inline data boundary check
Date: Tue, 12 May 2026 08:07:36 +0200 [thread overview]
Message-ID: <20260512060736.GA28955@lst.de> (raw)
In-Reply-To: <20260511-banden-sirenen-86654d8201a6@brauner>
On Mon, May 11, 2026 at 04:57:26PM +0200, Christian Brauner wrote:
> Applied to the vfs-7.2.iomap branch of the vfs/vfs.git tree.
> Patches in the vfs-7.2.iomap branch should appear in linux-next soon.
Shouldn't this go into 7.1 as it fixes a user triggered BUG_ON with
ntfs?
next prev parent reply other threads:[~2026-05-12 6:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-11 14:11 [PATCH RESEND] iomap: remove over-strict inline data boundary check Namjae Jeon
2026-05-11 14:57 ` Christian Brauner
2026-05-12 6:07 ` Christoph Hellwig [this message]
2026-05-12 6:33 ` Namjae Jeon
2026-05-12 12:12 ` Christian Brauner
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=20260512060736.GA28955@lst.de \
--to=hch@lst.de \
--cc=brauner@kernel.org \
--cc=djwong@kernel.org \
--cc=linkinjeon@kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=willy@infradead.org \
--cc=xiang@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.