From: Al Viro <viro@zeniv.linux.org.uk>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Chuck Lever III <chuck.lever@oracle.com>,
Olga Kornievskaia <aglo@umich.edu>,
Jeff Layton <jlayton@kernel.org>,
Linux NFS Mailing List <linux-nfs@vger.kernel.org>,
Benjamin Coddington <bcodding@redhat.com>
Subject: [pull request] vfs.git: fix for nfsd regression caused by iov_iter stuff
Date: Tue, 13 Sep 2022 03:43:38 +0100 [thread overview]
Message-ID: <Yx/uWom4QeQrTJz5@ZenIV> (raw)
In-Reply-To: <2F22D90A-3B64-43F0-899D-E41001DF3021@redhat.com>
The following changes since commit 568035b01cfb107af8d2e4bd2fb9aea22cf5b868:
Linux 6.0-rc1 (2022-08-14 15:50:18 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs.git tags/pull-fixes
for you to fetch changes up to bfbfb6182ad1d7d184b16f25165faad879147f79:
nfsd_splice_actor(): handle compound pages (2022-09-12 22:38:36 -0400)
----------------------------------------------------------------
fix for nfsd regression caused by iov_iter stuff this window
----------------------------------------------------------------
Al Viro (1):
nfsd_splice_actor(): handle compound pages
fs/nfsd/vfs.c | 12 ++++++++----
1 file changed, 8 insertions(+), 4 deletions(-)
next prev parent reply other threads:[~2022-09-13 2:44 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-30 17:14 Is this nfsd kernel oops known? Olga Kornievskaia
2022-08-30 17:49 ` Jeff Layton
2022-08-30 18:22 ` Olga Kornievskaia
2022-08-30 18:26 ` Chuck Lever III
2022-08-30 18:33 ` Olga Kornievskaia
2022-08-30 18:41 ` Chuck Lever III
2022-08-30 18:54 ` Olga Kornievskaia
2022-09-01 13:51 ` Olga Kornievskaia
2022-09-01 14:33 ` Benjamin Coddington
2022-09-01 20:08 ` Chuck Lever III
2022-09-02 1:27 ` Olga Kornievskaia
2022-09-02 20:58 ` Benjamin Coddington
2022-09-02 21:13 ` Chuck Lever III
2022-09-03 0:38 ` Benjamin Coddington
2022-09-03 3:34 ` Olga Kornievskaia
2022-09-03 16:41 ` Chuck Lever III
2022-09-06 18:28 ` Benjamin Coddington
2022-09-06 19:12 ` Olga Kornievskaia
2022-09-07 4:58 ` Chuck Lever III
2022-09-07 12:52 ` Benjamin Coddington
2022-09-10 21:14 ` Al Viro
2022-09-10 21:21 ` Chuck Lever III
2022-09-10 22:13 ` Al Viro
2022-09-10 22:35 ` Chuck Lever III
2022-09-11 3:51 ` Al Viro
2022-09-11 10:47 ` Benjamin Coddington
2022-09-11 18:36 ` Chuck Lever III
2022-09-11 19:39 ` Al Viro
2022-09-12 18:45 ` Benjamin Coddington
2022-09-13 2:43 ` Al Viro [this message]
2022-09-13 13:16 ` [pull request] vfs.git: fix for nfsd regression caused by iov_iter stuff pr-tracker-bot
2022-09-03 4:25 ` Is this nfsd kernel oops known? NeilBrown
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=Yx/uWom4QeQrTJz5@ZenIV \
--to=viro@zeniv.linux.org.uk \
--cc=aglo@umich.edu \
--cc=bcodding@redhat.com \
--cc=chuck.lever@oracle.com \
--cc=jlayton@kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=torvalds@linux-foundation.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