From: Tyler Hicks <tyhicks@canonical.com>
To: Hariprasad Kelam <hariprasad.kelam@gmail.com>
Cc: ecryptfs@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] fs: ecryptfs: crypto: Change return type of ecryptfs_process_flags
Date: Tue, 2 Jul 2019 14:25:51 -0500 [thread overview]
Message-ID: <20190702192551.GB8314@elm> (raw)
In-Reply-To: <20190702174723.GA4600@hari-Inspiron-1545>
On 2019-07-02 23:17:24, Hariprasad Kelam wrote:
> Change return type of ecryptfs_process_flags from int to void. As it
> never fails.
>
> fixes below issue reported by coccicheck
>
> s/ecryptfs/crypto.c:870:5-7: Unneeded variable: "rc". Return "0" on line
> 883
>
> Signed-off-by: Hariprasad Kelam <hariprasad.kelam@gmail.com>
> ---
Thanks for the cleanup! I made some minor tweaks, as noted below, and
pushed it to the eCryptfs next branch.
> fs/ecryptfs/crypto.c | 11 +++--------
> 1 file changed, 3 insertions(+), 8 deletions(-)
>
> diff --git a/fs/ecryptfs/crypto.c b/fs/ecryptfs/crypto.c
> index 509a767..55a633e 100644
> --- a/fs/ecryptfs/crypto.c
> +++ b/fs/ecryptfs/crypto.c
> @@ -864,10 +864,9 @@ static struct ecryptfs_flag_map_elem ecryptfs_flag_map[] = {
> *
> * Returns zero on success; non-zero if the flag set is invalid
I deleted this line from the function documentation.
> */
> -static int ecryptfs_process_flags(struct ecryptfs_crypt_stat *crypt_stat,
> +static void ecryptfs_process_flags(struct ecryptfs_crypt_stat *crypt_stat,
> char *page_virt, int *bytes_read)
> {
> - int rc = 0;
> int i;
> u32 flags;
>
> @@ -880,7 +879,6 @@ static int ecryptfs_process_flags(struct ecryptfs_crypt_stat *crypt_stat,
> /* Version is in top 8 bits of the 32-bit flag vector */
> crypt_stat->file_version = ((flags >> 24) & 0xFF);
> (*bytes_read) = 4;
> - return rc;
> }
>
> /**
> @@ -1306,12 +1304,9 @@ static int ecryptfs_read_headers_virt(char *page_virt,
> if (!(crypt_stat->flags & ECRYPTFS_I_SIZE_INITIALIZED))
> ecryptfs_i_size_init(page_virt, d_inode(ecryptfs_dentry));
> offset += MAGIC_ECRYPTFS_MARKER_SIZE_BYTES;
> - rc = ecryptfs_process_flags(crypt_stat, (page_virt + offset),
> + ecryptfs_process_flags(crypt_stat, (page_virt + offset),
> &bytes_read);
The line was short enough to move the last argument up to the same line
so I went ahead and did that.
Thanks again!
Tyler
> - if (rc) {
> - ecryptfs_printk(KERN_WARNING, "Error processing flags\n");
> - goto out;
> - }
> +
> if (crypt_stat->file_version > ECRYPTFS_SUPPORTED_FILE_VERSION) {
> ecryptfs_printk(KERN_WARNING, "File version is [%d]; only "
> "file version [%d] is supported by this "
> --
> 2.7.4
>
prev parent reply other threads:[~2019-07-02 19:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-02 17:47 [PATCH] fs: ecryptfs: crypto: Change return type of ecryptfs_process_flags Hariprasad Kelam
2019-07-02 19:25 ` Tyler Hicks [this message]
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=20190702192551.GB8314@elm \
--to=tyhicks@canonical.com \
--cc=ecryptfs@vger.kernel.org \
--cc=hariprasad.kelam@gmail.com \
--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