mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Colin Ian King <colin.i.king@gmail.com>
To: Wedson Almeida Filho <walmeida@microsoft.com>,
	Christian Brauner <brauner@kernel.org>,
	linux-fsdevel@vger.kernel.org
Cc: kernel-janitors@vger.kernel.org, willy@infradead.org,
	linux-kernel@vger.kernel.org
Subject: [PATCH][next][V2] hfsplus: remove dev_err messages and fix errno values
Date: Thu,  7 Mar 2024 09:20:09 +0000	[thread overview]
Message-ID: <20240307092009.1975845-1-colin.i.king@gmail.com> (raw)

While exercising hfsplus with stress-ng with xattr tests the kernel
log was spammed with many error messages. The need to emit these
messages is not necessary, so remove them. Also fix the errno returns,
for XATTR_CREATE errors these should be -EEXIST, and for XATTR_REPLACE
this should be -ENODATA.

Kudos to Matthew Wilcox for spotting the need for -EEXIST instead of
-EOPNOTSUPP.

Signed-off-by: Colin Ian King <colin.i.king@gmail.com>
---

V2: Also remove "cannot replace xattr" message and fix the errno returns

---
 fs/hfsplus/xattr.c | 9 +++------
 1 file changed, 3 insertions(+), 6 deletions(-)

diff --git a/fs/hfsplus/xattr.c b/fs/hfsplus/xattr.c
index 9c9ff6b8c6f7..f61a9370a233 100644
--- a/fs/hfsplus/xattr.c
+++ b/fs/hfsplus/xattr.c
@@ -288,8 +288,7 @@ 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;
+			err = -EEXIST;
 			goto end_setxattr;
 		}
 		hfs_bnode_read(cat_fd.bnode, &entry, cat_fd.entryoffset,
@@ -335,8 +334,7 @@ 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;
+			err = -EEXIST;
 			goto end_setxattr;
 		}
 		err = hfsplus_delete_attr(inode, name);
@@ -347,8 +345,7 @@ int __hfsplus_setxattr(struct inode *inode, const char *name,
 			goto end_setxattr;
 	} else {
 		if (flags & XATTR_REPLACE) {
-			pr_err("cannot replace xattr\n");
-			err = -EOPNOTSUPP;
+			err = -ENODATA;
 			goto end_setxattr;
 		}
 		err = hfsplus_create_attr(inode, name, value, size);
-- 
2.39.2


             reply	other threads:[~2024-03-07  9:20 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-07  9:20 Colin Ian King [this message]
2024-03-07 10:18 ` Christian Brauner

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=20240307092009.1975845-1-colin.i.king@gmail.com \
    --to=colin.i.king@gmail.com \
    --cc=brauner@kernel.org \
    --cc=kernel-janitors@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=walmeida@microsoft.com \
    --cc=willy@infradead.org \
    /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

all inboxes | Powered by JetHome®