kernel-janitors.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kees Cook <keescook@chromium.org>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Colin King <colin.king@canonical.com>,
	Arnd Bergmann <arnd@arndb.de>,
	kernel-janitors@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH][next] lkdtm: remove redundant initialization of ret
Date: Fri, 21 Jun 2019 16:26:05 +0000	[thread overview]
Message-ID: <201906210920.E133B26C@keescook> (raw)
In-Reply-To: <20190621140509.GB7011@kroah.com>

On Fri, Jun 21, 2019 at 04:05:09PM +0200, Greg Kroah-Hartman wrote:
> On Fri, Jun 21, 2019 at 04:03:47PM +0200, Greg Kroah-Hartman wrote:
> > On Fri, Jun 14, 2019 at 10:43:11AM +0100, Colin King wrote:
> > > From: Colin Ian King <colin.king@canonical.com>
> > > 
> > > The variable ret is being initialized with the value -EINVAL however
> > > this value is never read and ret is being re-assigned later on. Hence
> > > the initialization is redundant and can be removed.
> > > 
> > > Addresses-Coverity: ("Unused value")
> > > Signed-off-by: Colin Ian King <colin.king@canonical.com>
> > > Acked-by: Kees Cook <keescook@chromium.org>
> > > ---
> > >  drivers/misc/lkdtm/core.c | 2 +-
> > >  1 file changed, 1 insertion(+), 1 deletion(-)
> > > 
> > > diff --git a/drivers/misc/lkdtm/core.c b/drivers/misc/lkdtm/core.c
> > > index bba093224813..92df35fdeab0 100644
> > > --- a/drivers/misc/lkdtm/core.c
> > > +++ b/drivers/misc/lkdtm/core.c
> > > @@ -390,7 +390,7 @@ static int __init lkdtm_module_init(void)
> > >  {
> > >  	struct crashpoint *crashpoint = NULL;
> > >  	const struct crashtype *crashtype = NULL;
> > > -	int ret = -EINVAL;
> > > +	int ret;
> > >  	int i;
> > >  
> > >  	/* Neither or both of these need to be set */
> > > -- 
> > > 2.20.1
> > > 
> > 
> > With this patch now applied, I get this build warning:
> > drivers/misc/lkdtm/core.c: In function lkdtm_module_init:
> > drivers/misc/lkdtm/core.c:467:9: warning: ret may be used uninitialized in this function [-Wmaybe-uninitialized]
> >   return ret;
> >          ^~~
> > 
> > So are you _sure_ it shouldn't be initialized?
> 
> In looking at the code in my tree, ret is used uninitialized with this
> patch, so maybe coverity is wrong, or I don't have all of the needed
> patches?

The path went away when the check for debugfs_create_file() was removed.
I thought that patch was in your tree already?

In master, this is the path to "return ret" without prior assignment:

                de = debugfs_create_file(cur->name, 0644, lkdtm_debugfs_root,
                                         cur, &cur->fops);
                if (de = NULL) {
                        pr_err("could not create crashpoint %s\n", cur->name);
                        goto out_err;
                }


-- 
Kees Cook

  reply	other threads:[~2019-06-21 16:26 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-14  9:43 [PATCH][next] lkdtm: remove redundant initialization of ret Colin King
2019-06-20 18:13 ` Kees Cook
2019-06-21 13:50   ` Greg Kroah-Hartman
2019-06-21 14:03 ` Greg Kroah-Hartman
2019-06-21 14:05   ` Greg Kroah-Hartman
2019-06-21 16:26     ` Kees Cook [this message]
2019-06-23  5:00       ` Greg Kroah-Hartman

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=201906210920.E133B26C@keescook \
    --to=keescook@chromium.org \
    --cc=arnd@arndb.de \
    --cc=colin.king@canonical.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=kernel-janitors@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).