All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chuck Lever <cel@kernel.org>
To: NeilBrown <neil@brown.name>, Jeff Layton <jlayton@kernel.org>,
	Olga Kornievskaia <okorniev@redhat.com>,
	Dai Ngo <dai.ngo@oracle.com>, Tom Talpey <tom@talpey.com>
Cc: <linux-nfs@vger.kernel.org>
Subject: [PATCH 0/3] Move NFS filehandle defs into separate include
Date: Mon, 20 Jul 2026 10:14:39 -0400	[thread overview]
Message-ID: <20260720141442.783935-1-cel@kernel.org> (raw)

struct nfs_fh is defined in linux/nfs.h, which also pulls in cred.h,
a pair of sunrpc headers, and uapi/linux/nfs.h. A consumer that
wants nothing but the file handle definition drags all of those
items with it.

Relocate struct nfs_fh and its helpers to a new minimal header:
linux/nfs_fh.h. This series introduces two consumers for this
header. More will follow in subsequent series.

Chuck Lever (3):
  NFS: Add linux/nfs_fh.h
  lockd: Switch linux/nfs.h to linux/nfs_fh.h
  NFSD: Use struct knfsd_fh in struct pnfs_ff_layout

 fs/lockd/svc.c              |  1 -
 fs/lockd/trace.h            |  1 -
 fs/lockd/xdr.h              |  2 +-
 fs/nfsd/flexfilelayout.c    |  3 +-
 fs/nfsd/flexfilelayoutxdr.c |  4 +--
 fs/nfsd/flexfilelayoutxdr.h |  3 +-
 include/linux/nfs.h         | 39 ++---------------------
 include/linux/nfs_fh.h      | 63 +++++++++++++++++++++++++++++++++++++
 8 files changed, 71 insertions(+), 45 deletions(-)
 create mode 100644 include/linux/nfs_fh.h

-- 
2.54.0


             reply	other threads:[~2026-07-20 14:14 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-20 14:14 Chuck Lever [this message]
2026-07-20 14:14 ` [PATCH 1/3] NFS: Add linux/nfs_fh.h Chuck Lever
2026-07-20 14:14 ` [PATCH 2/3] lockd: Switch linux/nfs.h to linux/nfs_fh.h Chuck Lever
2026-07-20 14:14 ` [PATCH 3/3] NFSD: Use struct knfsd_fh in struct pnfs_ff_layout Chuck Lever

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=20260720141442.783935-1-cel@kernel.org \
    --to=cel@kernel.org \
    --cc=dai.ngo@oracle.com \
    --cc=jlayton@kernel.org \
    --cc=linux-nfs@vger.kernel.org \
    --cc=neil@brown.name \
    --cc=okorniev@redhat.com \
    --cc=tom@talpey.com \
    /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.