From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-kernel@vger.kernel.org
Cc: Kangjie Lu <kjlu@umn.edu>
Subject: Re: [PATCH 7/7] Revert "serial: max310x: pass return value of spi_register_driver"
Date: Thu, 29 Apr 2021 16:12:07 +0200 [thread overview]
Message-ID: <YIq+t/JbpSR4eezH@kroah.com> (raw)
In-Reply-To: <YIq3nzLCKEKI/Mnx@kroah.com>
On Thu, Apr 29, 2021 at 03:41:51PM +0200, Greg Kroah-Hartman wrote:
> On Thu, Apr 29, 2021 at 03:08:11PM +0200, Greg Kroah-Hartman wrote:
> > This reverts commit 51f689cc11333944c7a457f25ec75fcb41e99410.
> >
> > 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>
> > Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
> > ---
> > drivers/tty/serial/max310x.c | 4 ++--
> > 1 file changed, 2 insertions(+), 2 deletions(-)
> >
> > diff --git a/drivers/tty/serial/max310x.c b/drivers/tty/serial/max310x.c
> > index 8534d6e45a1d..a3ba0e6520a1 100644
> > --- a/drivers/tty/serial/max310x.c
> > +++ b/drivers/tty/serial/max310x.c
> > @@ -1518,10 +1518,10 @@ static int __init max310x_uart_init(void)
> > return ret;
> >
> > #ifdef CONFIG_SPI_MASTER
> > - ret = spi_register_driver(&max310x_spi_driver);
> > + spi_register_driver(&max310x_spi_driver);
> > #endif
> >
> > - return ret;
> > + return 0;
> > }
> > module_init(max310x_uart_init);
> >
> > --
> > 2.31.1
> >
>
> This is incorrect because if spi_register_driver fails, the uart needs
> to be properly unregistered before the module is unloaded automatically,
> causing a crash.
>
> I'll keep the revert and fix this up properly.
Argh, I already reviewed this one, sigh...
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
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 [this message]
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+t/JbpSR4eezH@kroah.com \
--to=gregkh@linuxfoundation.org \
--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