From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-kernel@vger.kernel.org
Cc: Kangjie Lu <kjlu@umn.edu>, Jacek Anaszewski <jacek.anaszewski@gmail.com>
Subject: Re: [PATCH 6/7] Revert "leds: lp5523: fix a missing check of return value of lp55xx_read"
Date: Thu, 29 Apr 2021 16:12:27 +0200 [thread overview]
Message-ID: <YIq+y1dKTOXnJhxy@kroah.com> (raw)
In-Reply-To: <YIq4VD0NyUGv0uy1@kroah.com>
On Thu, Apr 29, 2021 at 03:44:52PM +0200, Greg Kroah-Hartman wrote:
> On Thu, Apr 29, 2021 at 03:08:10PM +0200, Greg Kroah-Hartman wrote:
> > This reverts commit 248b57015f35c94d4eae2fdd8c6febf5cd703900.
> >
> > Commits from @umn.edu addresses have been found to be submitted in "bad
> > faith" to try to test the kernel community's ability to review "known
> > malicious" changes. The result of these submissions can be found in a
> > paper submitted to the 42nd IEEE Symposium on Security and Privacy
> > entitled, "Open Source Insecurity: Stealthily Introducing
> > Vulnerabilities via Hypocrite Commits" written by Qiushi Wu (University
> > of Minnesota) and Kangjie Lu (University of Minnesota) but later
> > withdrawn.
> >
> > Because of this, all submissions from this group must be reverted from
> > the kernel tree and will need to be re-reviewed again to determine if
> > they actually are a valid fix. Until that work is complete, remove this
> > change to ensure that no problems are being introduced into the
> > codebase.
> >
> > Cc: Kangjie Lu <kjlu@umn.edu>
> > Cc: Jacek Anaszewski <jacek.anaszewski@gmail.com>
> > Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
> > ---
> > drivers/leds/leds-lp5523.c | 4 +---
> > 1 file changed, 1 insertion(+), 3 deletions(-)
> >
> > diff --git a/drivers/leds/leds-lp5523.c b/drivers/leds/leds-lp5523.c
> > index fc433e63b1dc..5036d7d5f3d4 100644
> > --- a/drivers/leds/leds-lp5523.c
> > +++ b/drivers/leds/leds-lp5523.c
> > @@ -305,9 +305,7 @@ static int lp5523_init_program_engine(struct lp55xx_chip *chip)
> >
> > /* Let the programs run for couple of ms and check the engine status */
> > usleep_range(3000, 6000);
> > - ret = lp55xx_read(chip, LP5523_REG_STATUS, &status);
> > - if (ret)
> > - return ret;
> > + lp55xx_read(chip, LP5523_REG_STATUS, &status);
> > status &= LP5523_ENG_STATUS_MASK;
> >
> > if (status != LP5523_ENG_STATUS_MASK) {
> > --
> > 2.31.1
> >
>
> This looks incorrect to me as lp5523_run_engine() has been called and
> not cleaned up from properly.
>
> I'll keep the revert and fix this up correctly.
I already reviewed this one too, sorry for the noise.
greg k-h
next prev parent reply other threads:[~2021-04-29 14:12 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-29 13:08 [PATCH 0/7] Second set of revertion of all of the umn.edu commits Greg Kroah-Hartman
2021-04-29 13:08 ` [PATCH 1/7] Revert "rocker: fix incorrect error handling in dma_rings_init" Greg Kroah-Hartman
2021-04-29 13:54 ` Greg Kroah-Hartman
2021-04-29 19:30 ` Pavel Machek
2021-04-29 13:08 ` [PATCH 2/7] Revert "rtc: mc13xxx: fix a double-unlock issue" Greg Kroah-Hartman
2021-04-29 13:52 ` Greg Kroah-Hartman
2021-04-29 13:08 ` [PATCH 3/7] Revert "orinoco: avoid assertion in case of NULL pointer" Greg Kroah-Hartman
2021-04-29 13:50 ` Greg Kroah-Hartman
2021-04-29 13:08 ` [PATCH 4/7] Revert "ethtool: fix a potential missing-check bug" Greg Kroah-Hartman
2021-04-29 13:48 ` Greg Kroah-Hartman
2021-04-29 13:08 ` [PATCH 5/7] Revert "regulator: tps65910: fix a missing check of return value" Greg Kroah-Hartman
2021-04-29 13:47 ` Greg Kroah-Hartman
2021-04-29 13:08 ` [PATCH 6/7] Revert "leds: lp5523: fix a missing check of return value of lp55xx_read" Greg Kroah-Hartman
2021-04-29 13:44 ` Greg Kroah-Hartman
2021-04-29 14:12 ` Greg Kroah-Hartman [this message]
2021-04-29 13:08 ` [PATCH 7/7] Revert "serial: max310x: pass return value of spi_register_driver" Greg Kroah-Hartman
2021-04-29 13:41 ` Greg Kroah-Hartman
2021-04-29 14:12 ` Greg Kroah-Hartman
2021-04-29 19:28 ` [PATCH 0/7] Second set of revertion of all of the umn.edu commits Pavel Machek
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=YIq+y1dKTOXnJhxy@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=jacek.anaszewski@gmail.com \
--cc=kjlu@umn.edu \
--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
all inboxes | Powered by JetHome®