kernel-janitors.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Khaled Romdhani <khaledromdhani216@gmail.com>
To: Dan Carpenter <dan.carpenter@oracle.com>
Cc: clm@fb.com, josef@toxicpanda.com, dsterba@suse.com,
	linux-btrfs@vger.kernel.org, linux-kernel@vger.kernel.org,
	kernel-janitors@vger.kernel.org
Subject: Re: [PATCH-V2] fs/btrfs: Fix uninitialized variable
Date: Fri, 30 Apr 2021 15:01:28 +0100	[thread overview]
Message-ID: <20210430140128.GA2565@ard0534> (raw)
In-Reply-To: <20210429141200.GB1981@kadam>

On Thu, Apr 29, 2021 at 05:12:00PM +0300, Dan Carpenter wrote:
> On Tue, Apr 27, 2021 at 06:16:27PM +0100, Khaled ROMDHANI wrote:
> > The variable 'zone' is uninitialized which
> > introduce some build warning.
> > 
> > Reported-by: kernel test robot <lkp@intel.com>
> > Signed-off-by: Khaled ROMDHANI <khaledromdhani216@gmail.com>
> > ---
> > v2: catch the init as an assertion
> > ---
> >  fs/btrfs/zoned.c | 2 +-
> >  1 file changed, 1 insertion(+), 1 deletion(-)
> > 
> > diff --git a/fs/btrfs/zoned.c b/fs/btrfs/zoned.c
> > index 432509f4b3ac..70c0b1b2ff04 100644
> > --- a/fs/btrfs/zoned.c
> > +++ b/fs/btrfs/zoned.c
> > @@ -144,7 +144,7 @@ static inline u32 sb_zone_number(int shift, int mirror)
> >  	case 1: zone = 1ULL << (BTRFS_SB_LOG_FIRST_SHIFT - shift); break;
> >  	case 2: zone = 1ULL << (BTRFS_SB_LOG_SECOND_SHIFT - shift); break;
> >  	default:
> > -		ASSERT(zone);
> > +		ASSERT(zone = 0);
> 
> I'm sorry but this doesn't make any kind of sense.
> 
> >  		break;
> >  	}
> 
> regards,
> dan carpenter
>

The idea behind this is to force the assertion failure 
in default when no valid 'mirror' value was entered.
But as all caller pass valid mirror values, this case 
will not happen. So, I just fix the warning of the uninitialized 
variable 'zone' as reported by the kernel test robot. 
Thus I guarantee the failure when 'mirror' was invalid.

If I am wrong, please clarify.

Thanks.

      reply	other threads:[~2021-04-30 14:01 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-27 17:16 [PATCH-V2] fs/btrfs: Fix uninitialized variable Khaled ROMDHANI
2021-04-29 14:12 ` Dan Carpenter
2021-04-30 14:01   ` Khaled Romdhani [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=20210430140128.GA2565@ard0534 \
    --to=khaledromdhani216@gmail.com \
    --cc=clm@fb.com \
    --cc=dan.carpenter@oracle.com \
    --cc=dsterba@suse.com \
    --cc=josef@toxicpanda.com \
    --cc=kernel-janitors@vger.kernel.org \
    --cc=linux-btrfs@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).