From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Johannes Thumshirn <morbidrsa@gmail.com>
Cc: Alexey Khoroshilov <khoroshilov@ispras.ru>,
linux-kernel <linux-kernel@vger.kernel.org>,
ldv-project@linuxtesting.org
Subject: Re: [PATCH] mcb: Do not return zero on error path in mcb_pci_probe()
Date: Sun, 1 Nov 2015 19:15:11 -0800 [thread overview]
Message-ID: <20151102031511.GA21893@kroah.com> (raw)
In-Reply-To: <CAGH8bx5ZbyS+ELyGSVMdpC_KMp_cFf26mrRaWmJLnh4bGBR33Q@mail.gmail.com>
On Thu, Oct 22, 2015 at 09:28:57AM +0200, Johannes Thumshirn wrote:
> On Sat, Oct 17, 2015 at 11:33 PM, Alexey Khoroshilov
> <khoroshilov@ispras.ru> wrote:
> > There is an error path in mcb_pci_probe() where
> > it returns zero instead of error code.
> >
> > Found by Linux Driver Verification project (linuxtesting.org).
> >
> > Signed-off-by: Alexey Khoroshilov <khoroshilov@ispras.ru>
> > ---
> > drivers/mcb/mcb-pci.c | 1 +
> > 1 file changed, 1 insertion(+)
> >
> > diff --git a/drivers/mcb/mcb-pci.c b/drivers/mcb/mcb-pci.c
> > index 051645498b53..67d5e7d08df6 100644
> > --- a/drivers/mcb/mcb-pci.c
> > +++ b/drivers/mcb/mcb-pci.c
> > @@ -51,6 +51,7 @@ static int mcb_pci_probe(struct pci_dev *pdev, const struct pci_device_id *id)
> > priv->mapbase = pci_resource_start(pdev, 0);
> > if (!priv->mapbase) {
> > dev_err(&pdev->dev, "No PCI resource\n");
> > + ret = -ENODEV;
> > goto out_disable;
> > }
> >
> > --
> > 1.9.1
> >
>
> Applied, thanks.
>
> @Greg, shall I forward you the patch or do a pull request?
Please forward on, I don't do many pull requests.
greg k-h
prev parent reply other threads:[~2015-11-02 3:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-17 21:33 [PATCH] mcb: Do not return zero on error path in mcb_pci_probe() Alexey Khoroshilov
2015-10-22 7:28 ` Johannes Thumshirn
2015-11-02 3:15 ` Greg Kroah-Hartman [this message]
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=20151102031511.GA21893@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=khoroshilov@ispras.ru \
--cc=ldv-project@linuxtesting.org \
--cc=linux-kernel@vger.kernel.org \
--cc=morbidrsa@gmail.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