The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Shuah Khan <skhan@linuxfoundation.org>
To: "Everest K.C." <everestkc@everestkc.com.np>,
	viro@zeniv.linux.org.uk, brauner@kernel.org, jack@suse.cz
Cc: linux-fsdevel@vger.kernel.org, kernel-janitors@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	Shuah Khan <skhan@linuxfoundation.org>
Subject: Re: [PATCH][next] fs: Fix uninitialized scalar variable now
Date: Wed, 9 Oct 2024 14:38:03 -0600	[thread overview]
Message-ID: <018e525e-809c-4c69-a948-a1278af1ff2d@linuxfoundation.org> (raw)
In-Reply-To: <20241009200528.36343-1-everestkc@everestkc.com.np>

On 10/9/24 14:05, Everest K.C. wrote:
> Variable `now` is declared without initialization. The variable
> could be accessed inside the if-else statements following the
> variable declaration, before it has been initialized.

It could be, but it isn't. I am not sure if this change is needed.
> 
> This patch initializes the variable to
> `inode_set_ctime_current(inode)` by default.

Instead of "This patch initializes", change it to "Initialize ..."
Do refer to submitting patches document for information on how
to write change logs.

> 
> This issue was reported by Coverity Scan.

Include the the error/report from Coverity.

> 
> Signed-off-by: Everest K.C. <everestkc@everestkc.com.np>
> ---
>   fs/attr.c | 4 +---
>   1 file changed, 1 insertion(+), 3 deletions(-)
> 
> diff --git a/fs/attr.c b/fs/attr.c
> index c614b954bda5..77523af2e62d 100644
> --- a/fs/attr.c
> +++ b/fs/attr.c
> @@ -284,7 +284,7 @@ EXPORT_SYMBOL(inode_newsize_ok);
>   static void setattr_copy_mgtime(struct inode *inode, const struct iattr *attr)
>   {
>   	unsigned int ia_valid = attr->ia_valid;
> -	struct timespec64 now;
> +	struct timespec64 now = inode_set_ctime_current(inode);
>   
>   	if (ia_valid & ATTR_CTIME) {
>   		/*
> @@ -293,8 +293,6 @@ static void setattr_copy_mgtime(struct inode *inode, const struct iattr *attr)
>   		 */
>   		if (ia_valid & ATTR_DELEG)
>   			now = inode_set_ctime_deleg(inode, attr->ia_ctime);
> -		else
> -			now = inode_set_ctime_current(inode);

The code is clear and easy to read the way it is since it handles both cases
and does appropriate initialization.


>   	} else {
>   		/* If ATTR_CTIME isn't set, then ATTR_MTIME shouldn't be either. */
>   		WARN_ON_ONCE(ia_valid & ATTR_MTIME);

I will leave it up to the maintainers to decide whether to take
this change or not.

thanks,
-- Shuah

  reply	other threads:[~2024-10-09 20:38 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-09 20:05 [PATCH][next] fs: Fix uninitialized scalar variable now Everest K.C.
2024-10-09 20:38 ` Shuah Khan [this message]
2024-10-09 21:46   ` Everest K.C.
2024-10-09 20:45 ` Dan Carpenter
2024-10-09 21:48   ` Everest K.C.
2024-10-09 22:39   ` Jeff Layton
2024-10-09 22:55     ` Everest K.C.

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=018e525e-809c-4c69-a948-a1278af1ff2d@linuxfoundation.org \
    --to=skhan@linuxfoundation.org \
    --cc=brauner@kernel.org \
    --cc=everestkc@everestkc.com.np \
    --cc=jack@suse.cz \
    --cc=kernel-janitors@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=viro@zeniv.linux.org.uk \
    /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