All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chuck Lever <chuck.lever@oracle.com>
To: anna.schumaker@netapp.com, trondmy@hammerspace.com
Cc: linux-nfs@vger.kernel.org
Subject: [PATCH v2 0/4] Pre-requisites for client-side RPC-with-TLS support
Date: Fri, 22 Jul 2022 15:07:58 -0400	[thread overview]
Message-ID: <165851677341.2312015.16636288284789960852.stgit@morisot.1015granger.net> (raw)

As Jeff recently suggested, here are a few generic patches from my
RPC-with-TLS series that I believe can go in now.

Changes since v1:
- Record presentation addresses in trace_xs_data_ready()
- Drop trace_nfs_mount_addr_err()

---

Chuck Lever (4):
      SUNRPC: Fail faster on bad verifier
      SUNRPC: Widen rpc_task::tk_flags
      SUNRPC: Replace dprintk() call site in xs_data_ready
      NFS: Replace fs_context-related dprintk() call sites with tracepoints


 fs/nfs/fs_context.c           | 24 ++++++++------
 fs/nfs/nfstrace.h             | 59 +++++++++++++++++++++++++++++++++++
 include/linux/sunrpc/clnt.h   |  6 ++--
 include/linux/sunrpc/sched.h  | 32 +++++++++----------
 include/trace/events/sunrpc.h | 20 ++++++++++++
 net/sunrpc/clnt.c             | 13 ++++----
 net/sunrpc/debugfs.c          |  2 +-
 net/sunrpc/xprtsock.c         |  6 ++--
 8 files changed, 125 insertions(+), 37 deletions(-)

--
Chuck Lever


             reply	other threads:[~2022-07-22 19:08 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-22 19:07 Chuck Lever [this message]
2022-07-22 19:08 ` [PATCH v2 1/4] SUNRPC: Fail faster on bad verifier Chuck Lever
2022-07-22 19:08 ` [PATCH v2 2/4] SUNRPC: Widen rpc_task::tk_flags Chuck Lever
2022-07-22 19:08 ` [PATCH v2 3/4] SUNRPC: Replace dprintk() call site in xs_data_ready Chuck Lever
2022-07-25 14:03   ` Jeff Layton
2022-07-22 19:08 ` [PATCH v2 4/4] NFS: Replace fs_context-related dprintk() call sites with tracepoints 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=165851677341.2312015.16636288284789960852.stgit@morisot.1015granger.net \
    --to=chuck.lever@oracle.com \
    --cc=anna.schumaker@netapp.com \
    --cc=linux-nfs@vger.kernel.org \
    --cc=trondmy@hammerspace.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.