From: David Howells <dhowells@redhat.com>
To: Christian Brauner <christian@brauner.io>
Cc: David Howells <dhowells@redhat.com>,
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: [PATCH 0/4] netfs: Miscellaneous fixes
Date: Mon, 19 May 2025 10:07:00 +0100 [thread overview]
Message-ID: <20250519090707.2848510-1-dhowells@redhat.com> (raw)
Hi Christian,
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.
(3) Fix a request's work item to not require a reference, thereby avoiding
the need to get rid of it in BH/IRQ context.
(4) Fix waiting and waking to be consistent about the waitqueue used.
The patches can also be found here:
https://git.kernel.org/pub/scm/linux/kernel/git/dhowells/linux-fs.git/log/?h=netfs-fixes
Thanks,
David
David Howells (3):
netfs: Fix oops in write-retry from mis-resetting the subreq iterator
netfs: Fix the request's work item to not require a ref
netfs: Fix wait/wake to be consistent about the waitqueue used
Paulo Alcantara (1):
netfs: Fix setting of transferred bytes with short DIO reads
fs/9p/vfs_addr.c | 2 +-
fs/afs/write.c | 8 +-
fs/cachefiles/io.c | 16 +--
fs/ceph/addr.c | 2 +-
fs/erofs/fscache.c | 6 +-
fs/netfs/buffered_read.c | 32 +++--
fs/netfs/buffered_write.c | 2 +-
fs/netfs/direct_read.c | 10 +-
fs/netfs/direct_write.c | 12 +-
fs/netfs/fscache_io.c | 10 +-
fs/netfs/internal.h | 42 +++++--
fs/netfs/misc.c | 218 +++++++++++++++++++++++++++++++++++
fs/netfs/objects.c | 47 ++++----
fs/netfs/read_collect.c | 178 ++++------------------------
fs/netfs/read_pgpriv2.c | 4 +-
fs/netfs/read_retry.c | 26 +----
fs/netfs/read_single.c | 6 +-
fs/netfs/write_collect.c | 81 +++++--------
fs/netfs/write_issue.c | 38 +++---
fs/netfs/write_retry.c | 19 ++-
fs/smb/client/cifsproto.h | 3 +-
fs/smb/client/cifssmb.c | 4 +-
fs/smb/client/file.c | 7 +-
fs/smb/client/smb2pdu.c | 4 +-
include/linux/fscache.h | 2 +-
include/linux/netfs.h | 14 +--
include/trace/events/netfs.h | 7 +-
net/9p/client.c | 6 +-
28 files changed, 427 insertions(+), 379 deletions(-)
next reply other threads:[~2025-05-19 9:07 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-19 9:07 David Howells [this message]
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 ` [PATCH 0/4] netfs: Miscellaneous fixes Christian Brauner
-- strict thread matches above, loose matches on Subject: below --
2026-04-11 8:56 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=20250519090707.2848510-1-dhowells@redhat.com \
--to=dhowells@redhat.com \
--cc=ceph-devel@vger.kernel.org \
--cc=christian@brauner.io \
--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 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.