From: Greg KH <gregkh@linuxfoundation.org>
To: Chandra Gorentla <csgorentla@gmail.com>
Cc: johnny.kim@atmel.com, glen.lee@atmel.com, rachel.kim@atmel.com,
dean.lee@atmel.com, chris.park@atmel.com,
dan.carpenter@oracle.com, inux-wireless@vger.kernel.org,
devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org
Subject: Re: drivers: staging: wilc1000 - NULL pointer dereference
Date: Sun, 13 Sep 2015 21:45:31 -0700 [thread overview]
Message-ID: <20150914044531.GA27880@kroah.com> (raw)
In-Reply-To: <20150913124726.GA2746@gcs-HP-Compaq-nx6320>
On Sun, Sep 13, 2015 at 06:17:26PM +0530, Chandra Gorentla wrote:
> Hi,
>
> At this point I do not have the hardware.
>
> NULL pointer deference is observed in the wilc1000.ko module on x86 target
> with bus type SPI and when SPI is not ready. Following are the steps to
> reproduce.
>
> $ sudo insmod drivers/staging/wilc1000/wilc1000.ko
> $ sudo ifconfig wlan1 up
>
> wlan1 in the above command is the device controlled by 'wilc1000.ko'.
>
> Though the target I tested is not built to support WILC1000, my test
> scenario can be treated as a case where in SPI is not working or WILC1000
> is not connected to the supported hardware.
>
> I think I know a fix (pasted below) to this but cannot test it because hardware
> is not available to test positive cases.
>
> Thanks,
> chandra
>
> gcs@gcs-HP-Compaq-nx6320:~/linux/staging$ git diff
> diff --git a/drivers/staging/wilc1000/linux_wlan.c b/drivers/staging/wilc1000/linux_wlan.c
> index 63f44f8..48f063d 100644
> --- a/drivers/staging/wilc1000/linux_wlan.c
> +++ b/drivers/staging/wilc1000/linux_wlan.c
> @@ -1634,6 +1634,12 @@ int mac_open(struct net_device *ndev)
> int i = 0;
> struct WILC_WFI_priv *priv;
>
> +#ifdef WILC_SPI
> + if (!g_linux_wlan || !g_linux_wlan->wilc_spidev) {
> + netdev_err(ndev, "wilc1000: SPI device not ready\n");
> + return -ENODEV;
> + }
> +#endif
> nic = netdev_priv(ndev);
> priv = wiphy_priv(nic->wilc_netdev->ieee80211_ptr->wiphy);
> PRINT_D(INIT_DBG, "MAC OPEN[%p]\n", ndev);
> gcs@gcs-HP-Compaq-nx6320:~/linux/staging$
>
Can you resend this in a format that I can apply it?
thanks,
greg k-h
prev parent reply other threads:[~2015-09-14 4:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-13 12:47 drivers: staging: wilc1000 - NULL pointer dereference Chandra Gorentla
2015-09-14 4:45 ` Greg KH [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=20150914044531.GA27880@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=chris.park@atmel.com \
--cc=csgorentla@gmail.com \
--cc=dan.carpenter@oracle.com \
--cc=dean.lee@atmel.com \
--cc=devel@driverdev.osuosl.org \
--cc=glen.lee@atmel.com \
--cc=inux-wireless@vger.kernel.org \
--cc=johnny.kim@atmel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rachel.kim@atmel.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