From: Hauke Mehrtens <hauke@hauke-m.de>
To: Arend van Spriel <arend@broadcom.com>
Cc: linville@tuxdriver.com, zajec5@gmail.com,
b43-dev@lists.infradead.org, linux-wireless@vger.kernel.org,
Joe Perches <joe@perches.com>
Subject: [PATCH] bcma: fix null pointer in bcma_core_pci_irq_ctl
Date: Fri, 01 Jun 2012 22:33:32 +0200 [thread overview]
Message-ID: <4FC9271C.5030608@hauke-m.de> (raw)
In-Reply-To: <4FC8796E.4060800@broadcom.com>
On 06/01/2012 10:12 AM, Arend van Spriel wrote:
> On 05/31/2012 10:39 PM, Hauke Mehrtens wrote:
>> pc could be null if hosttype != BCMA_HOSTTYPE_PCI.
>> If we are on a device without a pci core this function is called with
>> pc = null by b43 and brcmsmac. If the host type is PCI we have a pci
>> core as well and pc can not be null.
>>
>> Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
>> ---
>> drivers/bcma/driver_pci.c | 4 +++-
>> 1 file changed, 3 insertions(+), 1 deletion(-)
>>
>> diff --git a/drivers/bcma/driver_pci.c b/drivers/bcma/driver_pci.c
>> index 9a96f14..884b7af 100644
>> --- a/drivers/bcma/driver_pci.c
>> +++ b/drivers/bcma/driver_pci.c
>> @@ -232,7 +232,7 @@ void __devinit bcma_core_pci_init(struct bcma_drv_pci *pc)
>> int bcma_core_pci_irq_ctl(struct bcma_drv_pci *pc, struct bcma_device *core,
>> bool enable)
>> {
>> - struct pci_dev *pdev = pc->core->bus->host_pci;
>> + struct pci_dev *pdev;
>> u32 coremask, tmp;
>> int err = 0;
>>
>> @@ -243,6 +243,8 @@ int bcma_core_pci_irq_ctl(struct bcma_drv_pci *pc, struct bcma_device *core,
> Could you change the if statement as well:
> - if (core->bus->hosttype != BCMA_HOSTTYPE_PCI) {
> + if (!pc || core->bus->hosttype != BCMA_HOSTTYPE_PCI)
Yes that's good I will change that, just to be save.
>> /* This bcma device is not on a PCI host-bus. So the IRQs are
>> * not routed through the PCI core.
>> * So we must not enable routing through the PCI core. */
>> goto out;
> - }
Is removing the braces correct here? There is just one line of code so
it will compile and the braces are not necessary, but I think it would
looks somehow strange because there is a 3 line comment in addition to
the one line of code in that if block.
@Joe Perches what do you think about this?
>> + pdev = pc->core->bus->host_pci;
>> +
>> err = pci_read_config_dword(pdev, BCMA_PCI_IRQMASK, &tmp);
>> if (err)
>> goto out;
Hauke
WARNING: multiple messages have this Message-ID (diff)
From: Hauke Mehrtens <hauke@hauke-m.de>
To: Arend van Spriel <arend@broadcom.com>
Cc: linville@tuxdriver.com, zajec5@gmail.com,
b43-dev@lists.infradead.org, linux-wireless@vger.kernel.org,
Joe Perches <joe@perches.com>
Subject: Re: [PATCH] bcma: fix null pointer in bcma_core_pci_irq_ctl
Date: Fri, 01 Jun 2012 22:33:32 +0200 [thread overview]
Message-ID: <4FC9271C.5030608@hauke-m.de> (raw)
In-Reply-To: <4FC8796E.4060800@broadcom.com>
On 06/01/2012 10:12 AM, Arend van Spriel wrote:
> On 05/31/2012 10:39 PM, Hauke Mehrtens wrote:
>> pc could be null if hosttype != BCMA_HOSTTYPE_PCI.
>> If we are on a device without a pci core this function is called with
>> pc = null by b43 and brcmsmac. If the host type is PCI we have a pci
>> core as well and pc can not be null.
>>
>> Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
>> ---
>> drivers/bcma/driver_pci.c | 4 +++-
>> 1 file changed, 3 insertions(+), 1 deletion(-)
>>
>> diff --git a/drivers/bcma/driver_pci.c b/drivers/bcma/driver_pci.c
>> index 9a96f14..884b7af 100644
>> --- a/drivers/bcma/driver_pci.c
>> +++ b/drivers/bcma/driver_pci.c
>> @@ -232,7 +232,7 @@ void __devinit bcma_core_pci_init(struct bcma_drv_pci *pc)
>> int bcma_core_pci_irq_ctl(struct bcma_drv_pci *pc, struct bcma_device *core,
>> bool enable)
>> {
>> - struct pci_dev *pdev = pc->core->bus->host_pci;
>> + struct pci_dev *pdev;
>> u32 coremask, tmp;
>> int err = 0;
>>
>> @@ -243,6 +243,8 @@ int bcma_core_pci_irq_ctl(struct bcma_drv_pci *pc, struct bcma_device *core,
> Could you change the if statement as well:
> - if (core->bus->hosttype != BCMA_HOSTTYPE_PCI) {
> + if (!pc || core->bus->hosttype != BCMA_HOSTTYPE_PCI)
Yes that's good I will change that, just to be save.
>> /* This bcma device is not on a PCI host-bus. So the IRQs are
>> * not routed through the PCI core.
>> * So we must not enable routing through the PCI core. */
>> goto out;
> - }
Is removing the braces correct here? There is just one line of code so
it will compile and the braces are not necessary, but I think it would
looks somehow strange because there is a 3 line comment in addition to
the one line of code in that if block.
@Joe Perches what do you think about this?
>> + pdev = pc->core->bus->host_pci;
>> +
>> err = pci_read_config_dword(pdev, BCMA_PCI_IRQMASK, &tmp);
>> if (err)
>> goto out;
Hauke
next prev parent reply other threads:[~2012-06-01 20:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-31 20:39 [PATCH] bcma: fix null pointer in bcma_core_pci_irq_ctl Hauke Mehrtens
2012-06-01 8:12 ` Arend van Spriel
2012-06-01 8:12 ` Arend van Spriel
2012-06-01 20:33 ` Hauke Mehrtens [this message]
2012-06-01 20:33 ` Hauke Mehrtens
2012-06-01 22:56 ` Joe Perches
2012-06-01 22:56 ` Joe Perches
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=4FC9271C.5030608@hauke-m.de \
--to=hauke@hauke-m.de \
--cc=arend@broadcom.com \
--cc=b43-dev@lists.infradead.org \
--cc=joe@perches.com \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=zajec5@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.