From: Christian Brauner <brauner@kernel.org>
To: Christian Brauner <brauner@kernel.org>,
David Howells <dhowells@redhat.com>
Cc: Paulo Alcantara <pc@manguebit.com>,
netfs@lists.linux.dev, linux-afs@lists.infradead.org,
linux-cifs@vger.kernel.org, linux-nfs@vger.kernel.org,
ceph-devel@vger.kernel.org, v9fs@lists.linux.dev,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/4] netfs: Miscellaneous fixes
Date: Tue, 20 May 2025 13:34:14 +0200 [thread overview]
Message-ID: <20250520-aufnimmt-abgemacht-9b1ddff0e6af@brauner> (raw)
In-Reply-To: <20250519090707.2848510-1-dhowells@redhat.com>
On Mon, 19 May 2025 10:07:00 +0100, David Howells wrote:
> Here are some miscellaneous fixes and changes for netfslib, if you could
> pull them:
>
> (1) Fix an oops in write-retry due to mis-resetting the I/O iterator.
>
> (2) Fix the recording of transferred bytes for short DIO reads.
>
> [...]
Applied to the vfs-6.16.netfs branch of the vfs/vfs.git tree.
Patches in the vfs-6.16.netfs branch should appear in linux-next soon.
Please report any outstanding bugs that were missed during review in a
new review to the original patch series allowing us to drop it.
It's encouraged to provide Acked-bys and Reviewed-bys even though the
patch has now been applied. If possible patch trailers will be updated.
Note that commit hashes shown below are subject to change due to rebase,
trailer updates or similar. If in doubt, please check the listed branch.
tree: https://git.kernel.org/pub/scm/linux/kernel/git/vfs/vfs.git
branch: vfs-6.16.netfs
[1/4] netfs: Fix oops in write-retry from mis-resetting the subreq iterator
https://git.kernel.org/vfs/vfs/c/cd084c7184ce
[2/4] netfs: Fix setting of transferred bytes with short DIO reads
https://git.kernel.org/vfs/vfs/c/2973904c9b79
[3/4] netfs: Fix the request's work item to not require a ref
https://git.kernel.org/vfs/vfs/c/537b296114cc
[4/4] netfs: Fix wait/wake to be consistent about the waitqueue used
https://git.kernel.org/vfs/vfs/c/2a6d0284a4a3
next prev parent reply other threads:[~2025-05-20 11:34 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-19 9:07 [PATCH 0/4] netfs: Miscellaneous fixes David Howells
2025-05-19 9:07 ` [PATCH 1/4] netfs: Fix oops in write-retry from mis-resetting the subreq iterator David Howells
2025-05-19 9:07 ` [PATCH 2/4] netfs: Fix setting of transferred bytes with short DIO reads David Howells
2025-05-19 9:07 ` [PATCH 3/4] netfs: Fix the request's work item to not require a ref David Howells
2025-05-19 9:07 ` [PATCH 4/4] netfs: Fix wait/wake to be consistent about the waitqueue used David Howells
2025-05-20 11:34 ` Christian Brauner [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-04-11 8:56 [PATCH 0/4] netfs: Miscellaneous fixes David Howells
2025-03-14 16:41 David Howells
2025-03-14 20:44 ` Paulo Alcantara
2025-03-19 9:04 ` 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=20250520-aufnimmt-abgemacht-9b1ddff0e6af@brauner \
--to=brauner@kernel.org \
--cc=ceph-devel@vger.kernel.org \
--cc=dhowells@redhat.com \
--cc=linux-afs@lists.infradead.org \
--cc=linux-cifs@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=netfs@lists.linux.dev \
--cc=pc@manguebit.com \
--cc=v9fs@lists.linux.dev \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).