All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeffle Xu <jefflexu@linux.alibaba.com>
To: viro@zeniv.linux.org.uk, dhowells@redhat.com
Cc: linux-fsdevel@vger.kernel.org, joseph.qi@linux.alibaba.com,
	Jeffle Xu <jefflexu@linux.alibaba.com>
Subject: [PATCH] vfs: fix the kernel-doc of find_inode_by_ino_rcu
Date: Mon, 13 Jul 2020 15:25:27 +0800	[thread overview]
Message-ID: <20200713072527.22377-1-jefflexu@linux.alibaba.com> (raw)

Fixes: 3f19b2ab97a9 ("vfs, afs, ext4: Make the inode hash table RCU searchable")
Signed-off-by: Jeffle Xu <jefflexu@linux.alibaba.com>
---
 fs/inode.c | 14 +++-----------
 1 file changed, 3 insertions(+), 11 deletions(-)

diff --git a/fs/inode.c b/fs/inode.c
index 72c4c347afb7..1807c0d336b1 100644
--- a/fs/inode.c
+++ b/fs/inode.c
@@ -1494,21 +1494,13 @@ struct inode *find_inode_rcu(struct super_block *sb, unsigned long hashval,
 EXPORT_SYMBOL(find_inode_rcu);
 
 /**
- * find_inode_by_rcu - Find an inode in the inode cache
+ * find_inode_by_ino_rcu - Find an inode in the inode cache
  * @sb:		Super block of file system to search
  * @ino:	The inode number to match
  *
- * Search for the inode specified by @hashval and @data in the inode cache,
- * where the helper function @test will return 0 if the inode does not match
- * and 1 if it does.  The @test function must be responsible for taking the
- * i_lock spin_lock and checking i_state for an inode being freed or being
- * initialized.
+ * Search for the inode by inode number in the inode cache.
  *
- * If successful, this will return the inode for which the @test function
- * returned 1 and NULL otherwise.
- *
- * The @test function is not permitted to take a ref on any inode presented.
- * It is also not permitted to sleep.
+ * If successful, this will return the inode and NULL otherwise.
  *
  * The caller must hold the RCU read lock.
  */
-- 
2.27.0


                 reply	other threads:[~2020-07-13  7:25 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20200713072527.22377-1-jefflexu@linux.alibaba.com \
    --to=jefflexu@linux.alibaba.com \
    --cc=dhowells@redhat.com \
    --cc=joseph.qi@linux.alibaba.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=viro@zeniv.linux.org.uk \
    /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.