From: Dominique Martinet <asmadeus@codewreck.org>
To: Christian Brauner <brauner@kernel.org>
Cc: Maximilian Bosch <maximilian@mbosch.me>,
Ryan Lahfa <ryan@lahfa.xyz>,
Christian Theune <ct@flyingcircus.io>,
Arnout Engelen <arnout@bzzt.net>,
linux-kernel@vger.kernel.org, linux-block@vger.kernel.org,
linux-fsdevel@vger.kernel.org, stable@vger.kernel.org,
"Matthew Wilcox (Oracle)" <willy@infradead.org>,
David Howells <dhowells@redhat.com>,
Alexander Viro <viro@zeniv.linux.org.uk>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH v3 0/2] iterate_folioq bug when offset==size (Was: [REGRESSION] 9pfs issues on 6.12-rc1)
Date: Sat, 16 Aug 2025 05:49:07 +0900 [thread overview]
Message-ID: <aJ-dQ2QN26h24Nz9@codewreck.org> (raw)
In-Reply-To: <20250815-scheckig-depesche-5de55f7855d1@brauner>
Hi Christian,
Christian Brauner wrote on Fri, Aug 15, 2025 at 04:16:33PM +0200:
> Applied to the vfs.fixes branch of the vfs/vfs.git tree.
> Patches in the vfs.fixes branch should appear in linux-next soon.
I'm not sure which is better as this is halfway between vfs and mm,
but Andrew seems to have picked this up in the mm tree:
- patch1 to mm-hotfixes-unstable
https://lkml.kernel.org/r/20250813231639.B7E61C4CEEB@smtp.kernel.org
- patch2 to mm-nonmm-unstable
https://lkml.kernel.org/r/20250813231515.7AADEC4CEF5@smtp.kernel.org
(and both patches are in -next right now, so I expect you'll get pinged
by Stephen in a bit...)
Thanks,
--
Dominique Martinet | Asmadeus
prev parent reply other threads:[~2025-08-15 20:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-13 6:04 Dominique Martinet via B4 Relay
2025-08-13 6:04 ` [PATCH v3 1/2] iov_iter: iterate_folioq: fix handling of offset >= folio size Dominique Martinet via B4 Relay
2025-08-13 6:04 ` [PATCH v3 2/2] iov_iter: iov_folioq_get_pages: don't leave empty slot behind Dominique Martinet via B4 Relay
2025-08-15 14:16 ` [PATCH v3 0/2] iterate_folioq bug when offset==size (Was: [REGRESSION] 9pfs issues on 6.12-rc1) Christian Brauner
2025-08-15 20:49 ` Dominique Martinet [this message]
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=aJ-dQ2QN26h24Nz9@codewreck.org \
--to=asmadeus@codewreck.org \
--cc=akpm@linux-foundation.org \
--cc=arnout@bzzt.net \
--cc=brauner@kernel.org \
--cc=ct@flyingcircus.io \
--cc=dhowells@redhat.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maximilian@mbosch.me \
--cc=ryan@lahfa.xyz \
--cc=stable@vger.kernel.org \
--cc=viro@zeniv.linux.org.uk \
--cc=willy@infradead.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 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®