[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20240306124054.1785697-1-colin.i.king@gmail.com>
Date: Wed, 6 Mar 2024 12:40:54 +0000
From: Colin Ian King <colin.i.king@...il.com>
To: Wedson Almeida Filho <walmeida@...rosoft.com>,
Christian Brauner <brauner@...nel.org>,
linux-fsdevel@...r.kernel.org
Cc: kernel-janitors@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: [PATCH][next] hfsplus: remove dev_err message "xattr exists yet"
While exercising hfsplus with stress-ng with xattr tests the kernel
log was spammed with many "xattr exists yet" messages. The error
EOPNOTSUPP is returned, so the need to emit these error messages is
not necessary; removing them reduces kernel error spamming.
Signed-off-by: Colin Ian King <colin.i.king@...il.com>
---
fs/hfsplus/xattr.c | 2 --
1 file changed, 2 deletions(-)
diff --git a/fs/hfsplus/xattr.c b/fs/hfsplus/xattr.c
index 9c9ff6b8c6f7..57101524fff4 100644
--- a/fs/hfsplus/xattr.c
+++ b/fs/hfsplus/xattr.c
@@ -288,7 +288,6 @@ int __hfsplus_setxattr(struct inode *inode, const char *name,
if (!strcmp_xattr_finder_info(name)) {
if (flags & XATTR_CREATE) {
- pr_err("xattr exists yet\n");
err = -EOPNOTSUPP;
goto end_setxattr;
}
@@ -335,7 +334,6 @@ int __hfsplus_setxattr(struct inode *inode, const char *name,
if (hfsplus_attr_exists(inode, name)) {
if (flags & XATTR_CREATE) {
- pr_err("xattr exists yet\n");
err = -EOPNOTSUPP;
goto end_setxattr;
}
--
2.39.2
Powered by blists - more mailing lists