From 5a29652d2ae47571e7d9e6eaec6a122ed31c2413 Mon Sep 17 00:00:00 2001
From: dongjiuzhu1 <dongjiuzhu1@xiaomi.com>
Date: Wed, 2 Oct 2024 23:32:46 +0800
Subject: [PATCH] fs/inode: using read-lock to protect inode_find

inode_find don't need to modify inode tree

Signed-off-by: dongjiuzhu1 <dongjiuzhu1@xiaomi.com>
---
 fs/inode/fs_inodefind.c | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/fs/inode/fs_inodefind.c b/fs/inode/fs_inodefind.c
index ac34e4ba70..ccf2e46546 100644
--- a/fs/inode/fs_inodefind.c
+++ b/fs/inode/fs_inodefind.c
@@ -55,7 +55,7 @@ int inode_find(FAR struct inode_search_s *desc)
    * references on the node.
    */
 
-  inode_lock();
+  inode_rlock();
   ret = inode_search(desc);
   if (ret >= 0)
     {
@@ -69,6 +69,6 @@ int inode_find(FAR struct inode_search_s *desc)
       atomic_fetch_add(&inode->i_crefs, 1);
     }
 
-  inode_unlock();
+  inode_runlock();
   return ret;
 }