All of lore.kernel.org
 help / color / mirror / Atom feed
From: Khaled Romdhani <khaledromdhani216@gmail.com>
To: David Sterba <dsterba@suse.cz>, clm@fb.com, josef@toxicpanda.com
Cc: linux-btrfs@vger.kernel.org, linux-kernel@vger.kernel.org,
	kernel-janitors@vger.kernel.org, khaledromdhani216@gmail.com
Subject: Re: [PATCH v2] fs/btrfs: Fix uninitialized variable
Date: Tue, 20 Apr 2021 14:20:51 +0100	[thread overview]
Message-ID: <20210420132051.GA3433@ard0534> (raw)
In-Reply-To: <20210419173225.GT7604@twin.jikos.cz>

On Mon, Apr 19, 2021 at 07:32:25PM +0200, David Sterba wrote:
> On Sat, Apr 17, 2021 at 04:36:16PM +0100, Khaled ROMDHANI wrote:
> > As reported by the Coverity static analysis.
> > The variable zone is not initialized which
> > may causes a failed assertion.
> > 
> > Addresses-Coverity: ("Uninitialized variables")
> > Signed-off-by: Khaled ROMDHANI <khaledromdhani216@gmail.com>
> > ---
> > v2: add a default case as proposed by David Sterba
> > ---
> >  fs/btrfs/zoned.c | 3 +++
> >  1 file changed, 3 insertions(+)
> > 
> > diff --git a/fs/btrfs/zoned.c b/fs/btrfs/zoned.c
> > index eeb3ebe11d7a..82527308d165 100644
> > --- a/fs/btrfs/zoned.c
> > +++ b/fs/btrfs/zoned.c
> > @@ -143,6 +143,9 @@ static inline u32 sb_zone_number(int shift, int mirror)
> >  	case 0: zone = 0; break;
> >  	case 1: zone = 1ULL << (BTRFS_SB_LOG_FIRST_SHIFT - shift); break;
> >  	case 2: zone = 1ULL << (BTRFS_SB_LOG_SECOND_SHIFT - shift); break;
> > +	default:
> > +		zone = 0;
> 
> Well yeah but this is not a valid case at all, we'd rather catch that as
> an assertion failure than letting is silently continue.

So, as all callers pass valid value. It would be
better to catch that as an assertion failure.

  reply	other threads:[~2021-04-20 13:20 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-17 15:36 [PATCH v2] fs/btrfs: Fix uninitialized variable Khaled ROMDHANI
2021-04-19 17:32 ` David Sterba
2021-04-20 13:20   ` Khaled Romdhani [this message]
2021-04-20 10:22 ` Dan Carpenter
2021-04-20 13:39   ` Khaled Romdhani

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=20210420132051.GA3433@ard0534 \
    --to=khaledromdhani216@gmail.com \
    --cc=clm@fb.com \
    --cc=dsterba@suse.cz \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.