From: Steve Dickson <SteveD@redhat.com>
To: Chuck Lever <chuck.lever@oracle.com>
Cc: linux-nfs@vger.kernel.org
Subject: Re: [PATCH] rpcdebug: Add new "state" flag for the nfs module
Date: Tue, 19 Jun 2012 10:41:52 -0400 [thread overview]
Message-ID: <4FE08FB0.70204@RedHat.com> (raw)
In-Reply-To: <20120604210153.13269.10747.stgit@oracle-2.citi.umich.edu>
On 06/04/2012 05:01 PM, Chuck Lever wrote:
> Kernel 3.5 adds a debugging flag for showing NFS client debugging
> messages having to do with NFSv4 state operations.
>
> Signed-off-by: Chuck Lever <chuck.lever@oracle.com>
Committed... Sorry for taking so long... Pings do work!!! ;-)
steved.
> ---
>
> support/include/nfs/debug.h | 1 +
> tools/rpcdebug/rpcdebug.c | 1 +
> 2 files changed, 2 insertions(+), 0 deletions(-)
>
> diff --git a/support/include/nfs/debug.h b/support/include/nfs/debug.h
> index dbec5ba..80a1b1d 100644
> --- a/support/include/nfs/debug.h
> +++ b/support/include/nfs/debug.h
> @@ -79,6 +79,7 @@ enum {
> #define NFSDBG_FSCACHE 0x0800
> #define NFSDBG_PNFS 0x1000
> #define NFSDBG_PNFS_LD 0x2000
> +#define NFSDBG_STATE 0x4000
> #define NFSDBG_ALL 0xFFFF
>
> #endif /* _NFS_DEBUG_H */
> diff --git a/tools/rpcdebug/rpcdebug.c b/tools/rpcdebug/rpcdebug.c
> index 444616d..d6e10d3 100644
> --- a/tools/rpcdebug/rpcdebug.c
> +++ b/tools/rpcdebug/rpcdebug.c
> @@ -170,6 +170,7 @@ static struct flagmap {
> FLAG(NFS, FSCACHE),
> FLAG(NFS, PNFS),
> FLAG(NFS, PNFS_LD),
> + FLAG(NFS, STATE),
> FLAG(NFS, ALL),
>
> /* nfsd */
>
prev parent reply other threads:[~2012-06-19 14:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-04 21:01 [PATCH] rpcdebug: Add new "state" flag for the nfs module Chuck Lever
2012-06-18 14:58 ` Fwd: " Chuck Lever
2012-06-19 14:41 ` Steve Dickson [this message]
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=4FE08FB0.70204@RedHat.com \
--to=steved@redhat.com \
--cc=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).