All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chuck Lever <chuck.lever@oracle.com>
To: trondmy@hammerspace.com
Cc: linux-nfs@vger.kernel.org
Subject: [PATCH v4 0/7] Update RPC task pid as displayed by tracepoints
Date: Sat, 16 Oct 2021 18:02:18 -0400	[thread overview]
Message-ID: <163442096873.1585.8967342784030733636.stgit@morisot.1015granger.net> (raw)

Reposting this series:

https://lore.kernel.org/linux-nfs/163345354511.524558.1980332041837428746.stgit@morisot.1015granger.net/

with the final patch in that series was updated as it was here:

https://lore.kernel.org/linux-nfs/163370502469.515303.12254136133220397877.stgit@morisot.1015granger.net/

Changes since v3:
- Repost entire series with updated 5/5
- Include two more tracepoint-related clean up patches

---

Chuck Lever (7):
      SUNRPC: Tracepoints should display tk_pid and cl_clid as a fixed-size field
      SUNRPC: Avoid NULL pointer dereferences in tracepoints
      SUNRPC: Use BIT() macro in rpc_show_xprt_state()
      SUNRPC: Don't dereference xprt->snd_task if it's a cookie
      NFS: Replace dprintk callsites in nfs_readpage(s)
      SUNRPC: Trace calls to .rpc_call_done
      NFS: Remove --> and <-- dprintk call sites


 fs/lockd/clntproc.c                    |   3 -
 fs/lockd/svc4proc.c                    |   2 -
 fs/lockd/svcproc.c                     |   2 -
 fs/nfs/filelayout/filelayout.c         |   2 -
 fs/nfs/flexfilelayout/flexfilelayout.c |   2 -
 fs/nfs/nfs4proc.c                      |  54 +-------
 fs/nfs/nfs4trace.h                     |  17 +--
 fs/nfs/nfstrace.h                      | 155 ++++++++++++++++++++-
 fs/nfs/pagelist.c                      |   3 -
 fs/nfs/read.c                          |  11 +-
 fs/nfs/write.c                         |   3 -
 include/trace/events/rpcgss.h          |  36 ++---
 include/trace/events/rpcrdma.h         | 104 ++++++--------
 include/trace/events/sunrpc.h          | 183 +++++++++++--------------
 include/trace/events/sunrpc_base.h     |  42 ++++++
 net/sunrpc/sched.c                     |   1 +
 16 files changed, 351 insertions(+), 269 deletions(-)
 create mode 100644 include/trace/events/sunrpc_base.h

--
Chuck Lever

             reply	other threads:[~2021-10-16 22:02 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-16 22:02 Chuck Lever [this message]
2021-10-16 22:02 ` [PATCH v4 1/7] SUNRPC: Tracepoints should display tk_pid and cl_clid as a fixed-size field Chuck Lever
2021-10-16 22:02 ` [PATCH v4 2/7] SUNRPC: Avoid NULL pointer dereferences in tracepoints Chuck Lever
2021-10-20 18:43   ` Trond Myklebust
2021-10-20 19:39     ` Chuck Lever III
2021-10-20 20:09       ` Trond Myklebust
2021-10-16 22:02 ` [PATCH v4 3/7] SUNRPC: Use BIT() macro in rpc_show_xprt_state() Chuck Lever
2021-10-16 22:02 ` [PATCH v4 4/7] SUNRPC: Don't dereference xprt->snd_task if it's a cookie Chuck Lever
2021-10-16 22:02 ` [PATCH v4 5/7] NFS: Replace dprintk callsites in nfs_readpage(s) Chuck Lever
2021-11-02 19:36   ` David Wysochanski
2021-11-02 19:41     ` Chuck Lever III
2021-10-16 22:02 ` [PATCH v4 6/7] SUNRPC: Trace calls to .rpc_call_done Chuck Lever
2021-10-16 22:03 ` [PATCH v4 7/7] NFS: Remove --> and <-- dprintk call sites 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=163442096873.1585.8967342784030733636.stgit@morisot.1015granger.net \
    --to=chuck.lever@oracle.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.