From: Tobias Jordan <kernel@cdqe.de>
To: Alexander Viro <viro@zeniv.linux.org.uk>,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: trivial@kernel.org
Subject: [PATCH] inode: fix comment for find_inode_by_ino_rcu
Date: Mon, 14 Feb 2022 18:57:12 +0100 [thread overview]
Message-ID: <YgqX+MMIhe8g6XC9@agrajag.zerfleddert.de> (raw)
Fix obvious copy-and-paste relics in comment for find_inode_by_ino_rcu.
Fixes: 3f19b2ab97a9 ("vfs, afs, ext4: Make the inode hash table RCU searchable")
Signed-off-by: Tobias Jordan <kernel@cdqe.de>
---
fs/inode.c | 12 ++----------
1 file changed, 2 insertions(+), 10 deletions(-)
diff --git a/fs/inode.c b/fs/inode.c
index 63324df6fa27..c297d57ee9c7 100644
--- a/fs/inode.c
+++ b/fs/inode.c
@@ -1587,19 +1587,11 @@ EXPORT_SYMBOL(find_inode_rcu);
* 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 specified by @ino 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, NULL otherwise.
*
* The caller must hold the RCU read lock.
*/
struct inode *find_inode_by_ino_rcu(struct super_block *sb,
--
2.30.2
reply other threads:[~2022-02-14 18:07 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=YgqX+MMIhe8g6XC9@agrajag.zerfleddert.de \
--to=kernel@cdqe.de \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=trivial@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 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).