All of lore.kernel.org
 help / color / mirror / Atom feed
From: cel@kernel.org
To: <stable@vger.kernel.org>
Cc: <linux-nfs@vger.kernel.org>,
	lilingfeng3@huawei.com, Chuck Lever <chuck.lever@oracle.com>
Subject: [PATCH 6.1.y 0/7] NFSD updates for LTS 6.1.y
Date: Mon, 26 Aug 2024 11:06:56 -0400	[thread overview]
Message-ID: <20240826150703.13987-1-cel@kernel.org> (raw)

From: Chuck Lever <chuck.lever@oracle.com>

Address an NFSD crasher that was noted here:

https://lore.kernel.org/linux-nfs/65ee9c0d-e89e-b3e5-f542-103a0ee4745c@huaweicloud.com/

To apply the fix cleanly, backport a few NFSD patches into v6.1.y
that have been in the other LTS kernels for a while.

Reported-by: Li LingFeng <lilingfeng3@huawei.com>
Suggested-by: Li LingFeng <lilingfeng3@huawei.com>
Tested-by: Li LingFeng <lilingfeng3@huawei.com>

Jeff Layton (1):
  nfsd: drop the nfsd_put helper

NeilBrown (5):
  nfsd: Simplify code around svc_exit_thread() call in nfsd()
  nfsd: separate nfsd_last_thread() from nfsd_put()
  NFSD: simplify error paths in nfsd_svc()
  nfsd: call nfsd_last_thread() before final nfsd_put()
  nfsd: don't call locks_release_private() twice concurrently

Trond Myklebust (1):
  nfsd: Fix a regression in nfsd_setattr()

 fs/nfsd/nfs4proc.c         |  4 ++
 fs/nfsd/nfs4state.c        |  2 +-
 fs/nfsd/nfsctl.c           | 32 ++++++++------
 fs/nfsd/nfsd.h             |  3 +-
 fs/nfsd/nfssvc.c           | 85 ++++++++++----------------------------
 fs/nfsd/vfs.c              |  6 ++-
 include/linux/sunrpc/svc.h | 13 ------
 7 files changed, 51 insertions(+), 94 deletions(-)

-- 
2.45.1


             reply	other threads:[~2024-08-26 15:07 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-26 15:06 cel [this message]
2024-08-26 15:06 ` [PATCH 6.1.y 1/7] nfsd: Simplify code around svc_exit_thread() call in nfsd() cel
2024-08-26 15:06 ` [PATCH 6.1.y 2/7] nfsd: separate nfsd_last_thread() from nfsd_put() cel
2024-08-26 15:06 ` [PATCH 6.1.y 3/7] NFSD: simplify error paths in nfsd_svc() cel
2024-08-26 15:07 ` [PATCH 6.1.y 4/7] nfsd: call nfsd_last_thread() before final nfsd_put() cel
2024-08-26 15:07 ` [PATCH 6.1.y 5/7] nfsd: drop the nfsd_put helper cel
2024-08-26 15:07 ` [PATCH 6.1.y 6/7] nfsd: don't call locks_release_private() twice concurrently cel
2024-08-26 15:07 ` [PATCH 6.1.y 7/7] nfsd: Fix a regression in nfsd_setattr() cel
2024-08-27 12:47 ` [PATCH 6.1.y 0/7] NFSD updates for LTS 6.1.y Greg KH

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=20240826150703.13987-1-cel@kernel.org \
    --to=cel@kernel.org \
    --cc=chuck.lever@oracle.com \
    --cc=lilingfeng3@huawei.com \
    --cc=linux-nfs@vger.kernel.org \
    --cc=stable@vger.kernel.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 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.