From: Chengguang Xu <cgxu519@gmx.com>
To: clm@fb.com, jbacik@fb.com, dsterba@suse.com
Cc: linux-btrfs@vger.kernel.org, Chengguang Xu <cgxu519@gmx.com>
Subject: [PATCH v4 4/5] btrfs: avoid error code overriding in btrfs_get_acl()
Date: Wed, 27 Jun 2018 12:16:37 +0800 [thread overview]
Message-ID: <20180627041638.13210-5-cgxu519@gmx.com> (raw)
In-Reply-To: <20180627041638.13210-1-cgxu519@gmx.com>
It's no good to override error code when failing from
btrfs_getxattr() in btrfs_get_acl() because it will hide
real root cause.
Signed-off-by: Chengguang Xu <cgxu519@gmx.com>
Reviewed-by: Nikolay Borisov <nborisov@suse.com>
---
v4:
- Split patch to series.
v3:
- Fix some toher bad practices.
- Add more information to commit log.
v2:
- Avoid errno overriding instead of print error message in error case.
- Chagne commit log for better understanding.
fs/btrfs/acl.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/fs/btrfs/acl.c b/fs/btrfs/acl.c
index a1d7211c8884..7d673ec9e54a 100644
--- a/fs/btrfs/acl.c
+++ b/fs/btrfs/acl.c
@@ -45,7 +45,7 @@ struct posix_acl *btrfs_get_acl(struct inode *inode, int type)
} else if (size == -ENODATA || size == 0) {
acl = NULL;
} else {
- acl = ERR_PTR(-EIO);
+ acl = ERR_PTR(size);
}
kfree(value);
--
2.17.1
next prev parent reply other threads:[~2018-06-27 4:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-27 4:16 [PATCH v4 0/5] code cleanups for btrfs_get_acl() Chengguang Xu
2018-06-27 4:16 ` [PATCH v4 1/5] btrfs: return error instead of crash when detecting unexpected type in btrfs_get_acl() Chengguang Xu
2018-06-27 4:16 ` [PATCH v4 2/5] btrfs: replace empty string with NULL when getting attribute length " Chengguang Xu
2018-06-27 4:16 ` [PATCH v4 3/5] btrfs: remove unnecessary -ERANGE check " Chengguang Xu
2018-06-27 4:16 ` Chengguang Xu [this message]
2018-06-27 4:16 ` [PATCH v4 5/5] btrfs: remove unnecessary bracket " Chengguang Xu
2018-06-27 7:21 ` [PATCH v4 0/5] code cleanups for btrfs_get_acl() David Sterba
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=20180627041638.13210-5-cgxu519@gmx.com \
--to=cgxu519@gmx.com \
--cc=clm@fb.com \
--cc=dsterba@suse.com \
--cc=jbacik@fb.com \
--cc=linux-btrfs@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).