From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Kees Cook <keescook@chromium.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 13:50:07 +0000 [thread overview]
Message-ID: <20190621135007.GA27890@kroah.com> (raw)
In-Reply-To: <201906201112.AE06471@keescook>
On Thu, Jun 20, 2019 at 11:13:32AM -0700, Kees Cook 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>
>
> Thanks!
>
> Acked-by: Kees Cook <keescook@chromium.org>
>
> Greg, can you take this please?
Will do, thanks.
greg k-h
WARNING: multiple messages have this Message-ID (diff)
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Kees Cook <keescook@chromium.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 15:50:07 +0200 [thread overview]
Message-ID: <20190621135007.GA27890@kroah.com> (raw)
In-Reply-To: <201906201112.AE06471@keescook>
On Thu, Jun 20, 2019 at 11:13:32AM -0700, Kees Cook 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>
>
> Thanks!
>
> Acked-by: Kees Cook <keescook@chromium.org>
>
> Greg, can you take this please?
Will do, thanks.
greg k-h
next prev parent reply other threads:[~2019-06-21 13:50 UTC|newest]
Thread overview: 14+ 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-14 9:43 ` Colin King
2019-06-20 18:13 ` Kees Cook
2019-06-20 18:13 ` Kees Cook
2019-06-21 13:50 ` Greg Kroah-Hartman [this message]
2019-06-21 13:50 ` Greg Kroah-Hartman
2019-06-21 14:03 ` Greg Kroah-Hartman
2019-06-21 14:03 ` Greg Kroah-Hartman
2019-06-21 14:05 ` Greg Kroah-Hartman
2019-06-21 14:05 ` Greg Kroah-Hartman
2019-06-21 16:26 ` Kees Cook
2019-06-21 16:26 ` Kees Cook
2019-06-23 5:00 ` Greg Kroah-Hartman
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=20190621135007.GA27890@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=arnd@arndb.de \
--cc=colin.king@canonical.com \
--cc=keescook@chromium.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 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.