Linux IIO development
 help / color / mirror / Atom feed
From: William Breathitt Gray <vilhelm.gray@gmail.com>
To: Jonathan Cameron <jic23@kernel.org>, trix@redhat.com
Cc: nathan@kernel.org, ndesaulniers@google.com,
	Jonathan.Cameron@huawei.com, linux-iio@vger.kernel.org,
	linux-kernel@vger.kernel.org, llvm@lists.linux.dev
Subject: Re: [PATCH] counter: add defaults to switch-statements
Date: Mon, 28 Feb 2022 08:03:18 -0500	[thread overview]
Message-ID: <YhzIFofXbnbFe9N6@ishi> (raw)
In-Reply-To: <20220227174610.0e0e73e4@jic23-huawei>

On Sun, Feb 27, 2022 at 05:46:10PM +0000, Jonathan Cameron wrote:
> On Sun, 27 Feb 2022 08:17:46 -0800
> trix@redhat.com wrote:
> 
> > From: Tom Rix <trix@redhat.com>
> > 
> > Clang static analysis reports this representative problem
> > counter-chrdev.c:482:3: warning: Undefined or garbage value
> >   returned to caller
> >   return ret;
> >   ^~~~~~~~~~
> > 
> > counter_get_data() has a multilevel switches, some without
> > defaults, so ret is sometimes not set.
> > Add returning -EINVAL similar to other defaults.
> > 
> > Fixes: b6c50affda59 ("counter: Add character device interface")
> > Signed-off-by: Tom Rix <trix@redhat.com>
> I'm fairly sure this one is warning supression rather than a fix as
> that type u8 being used in the switch is storing an enum which is
> set only by kernel code and all values of the enum are covered.
> 
> However, that's not locally visible so to me the addition looks good, I'd
> just be tempted to drop the fixes tag as backporting this looks like noise
> to me.
> 
> Reviewed-by: Jonathan Cameron <Jonathan.Cameron@huawei.com>

Yes, this isn't really a bug because the only values available are those
from the enum, but I see how this is not immediately obvious at first.
If Tom has no objections, I'll pick this up and drop the fixes tag so
that we have it along with the other counter changes for the 5.18 merge.

Thanks,

William Breathitt Gray

> > ---
> >  drivers/counter/counter-chrdev.c | 4 ++++
> >  1 file changed, 4 insertions(+)
> > 
> > diff --git a/drivers/counter/counter-chrdev.c b/drivers/counter/counter-chrdev.c
> > index b7c62f957a6a8..69d340be9c93f 100644
> > --- a/drivers/counter/counter-chrdev.c
> > +++ b/drivers/counter/counter-chrdev.c
> > @@ -477,6 +477,8 @@ static int counter_get_data(struct counter_device *const counter,
> >  		case COUNTER_SCOPE_COUNT:
> >  			ret = comp->count_u8_read(counter, parent, &value_u8);
> >  			break;
> > +		default:
> > +			return -EINVAL;
> >  		}
> >  		*value = value_u8;
> >  		return ret;
> > @@ -496,6 +498,8 @@ static int counter_get_data(struct counter_device *const counter,
> >  		case COUNTER_SCOPE_COUNT:
> >  			ret = comp->count_u32_read(counter, parent, &value_u32);
> >  			break;
> > +		default:
> > +			return -EINVAL;
> >  		}
> >  		*value = value_u32;
> >  		return ret;
> 

  reply	other threads:[~2022-02-28 13:03 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-27 16:17 [PATCH] counter: add defaults to switch-statements trix
2022-02-27 17:46 ` Jonathan Cameron
2022-02-28 13:03   ` William Breathitt Gray [this message]
2022-02-28 13:18     ` Tom Rix

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=YhzIFofXbnbFe9N6@ishi \
    --to=vilhelm.gray@gmail.com \
    --cc=Jonathan.Cameron@huawei.com \
    --cc=jic23@kernel.org \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=llvm@lists.linux.dev \
    --cc=nathan@kernel.org \
    --cc=ndesaulniers@google.com \
    --cc=trix@redhat.com \
    /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