From: Joe Perches <joe@perches.com>
To: Colin King <colin.king@canonical.com>,
David Howells <dhowells@redhat.com>,
linux-afs@lists.infradead.org
Cc: kernel-janitors@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] afs: remove redundant assignment to variable ret
Date: Sat, 11 May 2019 15:35:52 +0000 [thread overview]
Message-ID: <eb1862ebb97f41dcdf85abbea43a22d51ec94c9c.camel@perches.com> (raw)
In-Reply-To: <20190511123603.3265-1-colin.king@canonical.com>
On Sat, 2019-05-11 at 13:36 +0100, Colin King wrote:
> The variable ret is being assigned a value however this is never
> read and later it is being reassigned to a new value. The assignment
> is redundant and hence can be removed.
[]
> diff --git a/fs/afs/xattr.c b/fs/afs/xattr.c
[]
> @@ -71,7 +71,6 @@ static int afs_xattr_get_acl(const struct xattr_handler *handler,
> if (ret = 0) {
> ret = acl->size;
> if (size > 0) {
> - ret = -ERANGE;
> if (acl->size > size)
> return -ERANGE;
> memcpy(buffer, acl->data, acl->size);
It looks like the ret = acl->size immediately
after the memcpy should be removed as well.
---
fs/afs/xattr.c | 2 --
1 file changed, 2 deletions(-)
diff --git a/fs/afs/xattr.c b/fs/afs/xattr.c
index c81f85003fc7..e21de2f166a4 100644
--- a/fs/afs/xattr.c
+++ b/fs/afs/xattr.c
@@ -71,11 +71,9 @@ static int afs_xattr_get_acl(const struct xattr_handler *handler,
if (ret = 0) {
ret = acl->size;
if (size > 0) {
- ret = -ERANGE;
if (acl->size > size)
return -ERANGE;
memcpy(buffer, acl->data, acl->size);
- ret = acl->size;
}
kfree(acl);
}
next prev parent reply other threads:[~2019-05-11 15:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-20 13:58 [PATCH] afs: remove redundant assignment of dvnode to itself Colin King
2017-11-20 22:20 ` David Howells
2019-05-11 12:36 ` [PATCH] afs: remove redundant assignment to variable ret Colin King
2019-05-11 15:35 ` Joe Perches [this message]
2019-05-12 6:56 ` David Howells
2019-05-12 6:55 ` David Howells
2020-05-27 12:06 ` Colin King
2020-07-22 15:22 ` Colin King
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=eb1862ebb97f41dcdf85abbea43a22d51ec94c9c.camel@perches.com \
--to=joe@perches.com \
--cc=colin.king@canonical.com \
--cc=dhowells@redhat.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-afs@lists.infradead.org \
--cc=linux-kernel@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