[PATCH -next v2 2/3] devtmpfs: add debug info to handle()

From: Longlong Xia <xialonglong1@huawei.com>
To: <gregkh@linuxfoundation.org>
Cc: <chenwandun@huawei.com>, <linux-kernel@vger.kernel.org>,
	<rafael@kernel.org>, <sunnanyong@huawei.com>,
	<wangkefeng.wang@huawei.com>, <xialonglong1@huawei.com>
Subject: [PATCH -next v2 2/3] devtmpfs: add debug info to handle()
Date: Fri, 10 Feb 2023 09:54:43 +0000	[thread overview]
Message-ID: <20230210095444.4067307-3-xialonglong1@huawei.com> (raw)
In-Reply-To: <20230210095444.4067307-1-xialonglong1@huawei.com>

Because handle() is the core function for processing devtmpfs requests,
Let's add some debug info in handle() to help users know why failed.

Signed-off-by: Longlong Xia <xialonglong1@huawei.com>
---
 drivers/base/devtmpfs.c | 12 ++++++++++--
 1 file changed, 10 insertions(+), 2 deletions(-)

diff --git a/drivers/base/devtmpfs.c b/drivers/base/devtmpfs.c
index ae72d4ba8547..7789b7be4ee5 100644
--- a/drivers/base/devtmpfs.c
+++ b/drivers/base/devtmpfs.c
@@ -389,10 +389,18 @@ static __initdata DECLARE_COMPLETION(setup_done);
 static int handle(const char *name, umode_t mode, kuid_t uid, kgid_t gid,
 		  struct device *dev)
 {
+	int ret;
+
 	if (mode)
-		return handle_create(name, mode, uid, gid, dev);
+		ret = handle_create(name, mode, uid, gid, dev);
 	else
-		return handle_remove(name, dev);
+		ret = handle_remove(name, dev);
+
+	if (ret)
+		dev_err(dev, "failed to %s %s, ret = %d\n",
+			mode ? "create" : "remove", name, ret);
+
+	return ret;
 }
 
 static void __noreturn devtmpfs_work_loop(void)
-- 
2.25.1

