From: Sasha Levin <sashal@kernel.org>
To: stable@vger.kernel.org
Cc: Chen Hanxiao <chenhx.fnst@fujitsu.com>,
Jeff Layton <jlayton@kernel.org>,
Chuck Lever <chuck.lever@oracle.com>,
Sasha Levin <sashal@kernel.org>
Subject: [PATCH 6.6.y 1/3] NFS: trace: show TIMEDOUT instead of 0x6e
Date: Mon, 12 Jan 2026 09:26:59 -0500 [thread overview]
Message-ID: <20260112142701.711948-1-sashal@kernel.org> (raw)
In-Reply-To: <2026011222-giggle-goofiness-bbd1@gregkh>
From: Chen Hanxiao <chenhx.fnst@fujitsu.com>
[ Upstream commit cef48236dfe55fa266d505e8a497963a7bc5ef2a ]
__nfs_revalidate_inode may return ETIMEDOUT.
print symbol of ETIMEDOUT in nfs trace:
before:
cat-5191 [005] 119.331127: nfs_revalidate_inode_exit: error=-110 (0x6e)
after:
cat-1738 [004] 44.365509: nfs_revalidate_inode_exit: error=-110 (TIMEDOUT)
Signed-off-by: Chen Hanxiao <chenhx.fnst@fujitsu.com>
Reviewed-by: Jeff Layton <jlayton@kernel.org>
Signed-off-by: Chuck Lever <chuck.lever@oracle.com>
Stable-dep-of: c6c209ceb87f ("NFSD: Remove NFSERR_EAGAIN")
Signed-off-by: Sasha Levin <sashal@kernel.org>
---
include/trace/misc/nfs.h | 1 +
1 file changed, 1 insertion(+)
diff --git a/include/trace/misc/nfs.h b/include/trace/misc/nfs.h
index 0d9d48dca38a8..5b6c36fe9cdfe 100644
--- a/include/trace/misc/nfs.h
+++ b/include/trace/misc/nfs.h
@@ -52,6 +52,7 @@ TRACE_DEFINE_ENUM(NFSERR_JUKEBOX);
{ NFSERR_IO, "IO" }, \
{ NFSERR_NXIO, "NXIO" }, \
{ ECHILD, "CHILD" }, \
+ { ETIMEDOUT, "TIMEDOUT" }, \
{ NFSERR_EAGAIN, "AGAIN" }, \
{ NFSERR_ACCES, "ACCES" }, \
{ NFSERR_EXIST, "EXIST" }, \
--
2.51.0
next prev parent reply other threads:[~2026-01-12 14:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-12 10:33 FAILED: patch "[PATCH] NFSD: Remove NFSERR_EAGAIN" failed to apply to 6.6-stable tree gregkh
2026-01-12 14:26 ` Sasha Levin [this message]
2026-01-12 14:27 ` [PATCH 6.6.y 2/3] nfs_common: factor out nfs_errtbl and nfs_stat_to_errno Sasha Levin
2026-01-12 14:27 ` [PATCH 6.6.y 3/3] NFSD: Remove NFSERR_EAGAIN Sasha Levin
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=20260112142701.711948-1-sashal@kernel.org \
--to=sashal@kernel.org \
--cc=chenhx.fnst@fujitsu.com \
--cc=chuck.lever@oracle.com \
--cc=jlayton@kernel.org \
--cc=stable@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