Linux NFS development
 help / color / mirror / Atom feed
From: Anna Schumaker <anna@kernel.org>
To: linux-nfs@vger.kernel.org, torvalds@linux-foundation.org
Cc: anna@kernel.org
Subject: [GIT PULL] Please pull NFS Client Bugfixes for Linux 6.3-rc
Date: Mon, 20 Mar 2023 13:50:44 -0400	[thread overview]
Message-ID: <20230320175044.173626-1-anna@kernel.org> (raw)

Hi Linus,

The following changes since commit eeac8ede17557680855031c6f305ece2378af326:

  Linux 6.3-rc2 (2023-03-12 16:36:44 -0700)

are available in the Git repository at:

  git://git.linux-nfs.org/projects/anna/linux-nfs.git tags/nfs-for-6.3-2

for you to fetch changes up to 21fd9e8700de86d1169f6336e97d7a74916ed04a:

  NFS: Correct timing for assigning access cache timestamp (2023-03-14 15:19:44 -0400)

----------------------------------------------------------------
NFS Client Bugfixes for Linux 6.3-rc

Bugfixes:
  * Fix /proc/PID/io read_bytes accounting
  * Fix setting NLM file_lock start and end during decoding testargs
  * Fix timing for setting access cache timestamps

Thanks,
Anna

----------------------------------------------------------------
Chengen Du (1):
      NFS: Correct timing for assigning access cache timestamp

Dave Wysochanski (1):
      NFS: Fix /proc/PID/io read_bytes for buffered reads

Jeff Layton (1):
      lockd: set file_lock start and end when decoding nlm4 testargs

 fs/lockd/clnt4xdr.c        |  9 +--------
 fs/lockd/xdr4.c            | 13 ++++++++++++-
 fs/nfs/dir.c               |  2 +-
 fs/nfs/read.c              |  3 +++
 include/linux/lockd/xdr4.h |  1 +
 5 files changed, 18 insertions(+), 10 deletions(-)

             reply	other threads:[~2023-03-20 17:58 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-20 17:50 Anna Schumaker [this message]
2023-03-20 18:26 ` [GIT PULL] Please pull NFS Client Bugfixes for Linux 6.3-rc pr-tracker-bot

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=20230320175044.173626-1-anna@kernel.org \
    --to=anna@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