All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chuck Lever <cel@kernel.org>
To: NeilBrown <neil@brown.name>, Jeff Layton <jlayton@kernel.org>,
	Olga Kornievskaia <okorniev@redhat.com>,
	Dai Ngo <dai.ngo@oracle.com>, Tom Talpey <tom@talpey.com>
Cc: <linux-nfs@vger.kernel.org>, Chuck Lever <chuck.lever@oracle.com>,
	Steven Rostedt <rostedt@goodmis.org>
Subject: [PATCH v1 1/5] NFSD: Remove definition for trace_nfsd_file_unhash_and_queue
Date: Fri, 13 Jun 2025 16:07:43 -0400	[thread overview]
Message-ID: <20250613200747.7110-1-cel@kernel.org> (raw)

From: Chuck Lever <chuck.lever@oracle.com>

trace_nfsd_file_unhash_and_queue() was removed by commit ac3a2585f01
("nfsd: rework refcounting in filecache").

Reported-by: Steven Rostedt <rostedt@goodmis.org>
Signed-off-by: Chuck Lever <chuck.lever@oracle.com>
---
 fs/nfsd/trace.h | 1 -
 1 file changed, 1 deletion(-)

diff --git a/fs/nfsd/trace.h b/fs/nfsd/trace.h
index b244c6b3e905..93875c7ba358 100644
--- a/fs/nfsd/trace.h
+++ b/fs/nfsd/trace.h
@@ -1108,7 +1108,6 @@ DEFINE_NFSD_FILE_EVENT(nfsd_file_free);
 DEFINE_NFSD_FILE_EVENT(nfsd_file_unhash);
 DEFINE_NFSD_FILE_EVENT(nfsd_file_put);
 DEFINE_NFSD_FILE_EVENT(nfsd_file_closing);
-DEFINE_NFSD_FILE_EVENT(nfsd_file_unhash_and_queue);
 
 TRACE_EVENT(nfsd_file_alloc,
 	TP_PROTO(
-- 
2.49.0


             reply	other threads:[~2025-06-13 20:07 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-13 20:07 Chuck Lever [this message]
2025-06-13 20:07 ` [PATCH v1 2/5] NFSD: Remove definitions for unused trace_nfsd_file_lru trace points Chuck Lever
2025-06-13 20:07 ` [PATCH v1 3/5] NFSD: Remove definition for trace_nfsd_file_gc_recent Chuck Lever
2025-06-13 20:07 ` [PATCH v1 4/5] NFSD: Remove definition for trace_nfsd_ctl_maxconn Chuck Lever
2025-06-13 20:07 ` [PATCH v1 5/5] NFSD: Clean up kdoc for nfsd_file_put_local() Chuck Lever
2025-06-13 20:59 ` [PATCH v1 1/5] NFSD: Remove definition for trace_nfsd_file_unhash_and_queue Jeff Layton

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=20250613200747.7110-1-cel@kernel.org \
    --to=cel@kernel.org \
    --cc=chuck.lever@oracle.com \
    --cc=dai.ngo@oracle.com \
    --cc=jlayton@kernel.org \
    --cc=linux-nfs@vger.kernel.org \
    --cc=neil@brown.name \
    --cc=okorniev@redhat.com \
    --cc=rostedt@goodmis.org \
    --cc=tom@talpey.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.