From: Chuck Lever <chuck.lever@oracle.com>
To: linux-nfs@vger.kernel.org
Subject: [PATCH RFC 0/2] Possible new NFS trace events
Date: Wed, 23 Oct 2019 14:02:17 -0400 [thread overview]
Message-ID: <20191023180049.6450.65440.stgit@manet.1015granger.net> (raw)
Wondering if these additional trace points might be useful. Review
and comments welcome.
---
Chuck Lever (2):
NFS: Introduce trace events triggered by page writeback errors
NFS4: Report callback authentication errors
fs/nfs/callback_xdr.c | 11 ++++++++---
fs/nfs/nfs4trace.h | 35 +++++++++++++++++++++++++++++++++++
fs/nfs/nfstrace.h | 45 +++++++++++++++++++++++++++++++++++++++++++++
fs/nfs/write.c | 3 +++
4 files changed, 91 insertions(+), 3 deletions(-)
--
Chuck Lever
next reply other threads:[~2019-10-23 18:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-23 18:02 Chuck Lever [this message]
2019-10-23 18:02 ` [PATCH RFC 1/2] NFS: Introduce trace events triggered by page writeback errors Chuck Lever
2019-10-23 18:02 ` [PATCH RFC 2/2] NFS4: Report callback authentication errors 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=20191023180049.6450.65440.stgit@manet.1015granger.net \
--to=chuck.lever@oracle.com \
--cc=linux-nfs@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).