From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Tong Zhang <ztong0001@gmail.com>
Cc: Arnd Bergmann <arnd@arndb.de>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] misc: alcor_pci: fix null-ptr-deref when there is no PCI bridge
Date: Mon, 10 May 2021 16:36:41 +0200 [thread overview]
Message-ID: <YJlE+Z2VKhamVWaw@kroah.com> (raw)
In-Reply-To: <20210426220728.1230340-1-ztong0001@gmail.com>
On Mon, Apr 26, 2021 at 06:07:27PM -0400, Tong Zhang wrote:
> the PCI bridge might be NULL, so we'd better check before use it
>
> [ 1.246492] BUG: kernel NULL pointer dereference, address: 00000000000000c0
> [ 1.248731] RIP: 0010:pci_read_config_byte+0x5/0x40
> [ 1.253998] Call Trace:
> [ 1.254131] ? alcor_pci_find_cap_offset.isra.0+0x3a/0x100 [alcor_pci]
> [ 1.254476] alcor_pci_probe+0x169/0x2d5 [alcor_pci]
>
> Signed-off-by: Tong Zhang <ztong0001@gmail.com>
> ---
> drivers/misc/cardreader/alcor_pci.c | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/drivers/misc/cardreader/alcor_pci.c b/drivers/misc/cardreader/alcor_pci.c
> index cd402c89189e..1c33453fd5c7 100644
> --- a/drivers/misc/cardreader/alcor_pci.c
> +++ b/drivers/misc/cardreader/alcor_pci.c
> @@ -102,6 +102,9 @@ static int alcor_pci_find_cap_offset(struct alcor_pci_priv *priv,
> u8 val8;
> u32 val32;
>
> + if (!pci)
> + return 0;
> +
> where = ALCOR_CAP_START_OFFSET;
> pci_read_config_byte(pci, where, &val8);
> if (!val8)
> --
> 2.25.1
>
I do not understand, how can pci ever be NULL? There is only 1 way this
function can be called, and it's through the alcor_pci_probe() call,
which should have always set up the parent and pci pointers that get
passed to this function.
How can that not happen? If it can happen, then something earlier than
this should be fixed instead of papering over the root problem here.
How did you duplicate the crash you list above?
thanks,
greg k-h
next prev parent reply other threads:[~2021-05-10 14:39 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-26 22:07 [PATCH] misc: alcor_pci: fix null-ptr-deref when there is no PCI bridge Tong Zhang
2021-05-10 14:36 ` Greg Kroah-Hartman [this message]
2021-05-10 22:20 ` Tong Zhang
2021-05-11 7:03 ` Greg Kroah-Hartman
2021-05-11 17:17 ` Tong Zhang
2021-05-11 17:57 ` Greg Kroah-Hartman
2021-05-11 21:29 ` [PATCH v2] " Tong Zhang
2021-05-12 6:24 ` Greg Kroah-Hartman
2021-05-12 16:24 ` Tong Zhang
2021-05-12 16:41 ` Greg Kroah-Hartman
2021-05-13 4:07 ` [PATCH v3] " Tong Zhang
2021-05-19 8:40 ` Dan Carpenter
2021-05-19 20:20 ` Tong Zhang
2021-05-13 4:09 ` [PATCH v2] " Tong Zhang
2021-05-11 21:32 ` [PATCH] " Tong Zhang
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=YJlE+Z2VKhamVWaw@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=arnd@arndb.de \
--cc=linux-kernel@vger.kernel.org \
--cc=ztong0001@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 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.