From: Flavio Leitner <fbl@redhat.com>
To: mjr@cs.wisc.edu
Cc: davem@davemloft.net, sboyd@codeaurora.org, ben@simtec.co.uk,
netdev@vger.kernel.org
Subject: Re: [PATCH] Fix missing mutex_lock/unlock
Date: Thu, 12 Apr 2012 16:23:19 -0300 [thread overview]
Message-ID: <20120412162319.377ae3cf@asterix.rh> (raw)
In-Reply-To: <1334244396-6978-1-git-send-email-mjr@cs.wisc.edu>
On Thu, 12 Apr 2012 10:26:36 -0500 mjr@cs.wisc.edu wrote:
> From: Matt Renzelmann <mjr@cs.wisc.edu>
>
> All calls to ks8851_rdreg* and ks8851_wrreg* should be protected
> with the driver's lock mutex. A spurious interrupt may otherwise cause a
> crash.
>
> Signed-off-by: Matt Renzelmann <mjr@cs.wisc.edu>
> ---
> Hello,
>
> I'm new to the kernel development process so I hope I've not screwed
> this up with this extra text. We found a potential issue using a new
> driver testing tool called SymDrive. It looks legitimate to me, so
> I'm reporting it. We hope to make this tool available in the future.
> Please let me know if I should modify the patch or re-send without
> this commentary. Thanks in advance for your patience.
>
It is recommended to put the driver name in the subject,
for instance:
[PATCH] ks8851: Fix missing mutex_lock/unlock
See the driver log for more examples.
> drivers/net/ethernet/micrel/ks8851.c | 4 ++++
> 1 files changed, 4 insertions(+), 0 deletions(-)
>
> diff --git a/drivers/net/ethernet/micrel/ks8851.c b/drivers/net/ethernet/micrel/ks8851.c
> index c722aa6..fa2001a 100644
> --- a/drivers/net/ethernet/micrel/ks8851.c
> +++ b/drivers/net/ethernet/micrel/ks8851.c
> @@ -1515,11 +1515,15 @@ static int __devinit ks8851_probe(struct spi_device *spi)
> goto err_netdev;
> }
>
> + mutex_lock(&ks->lock);
> +
> netdev_info(ndev, "revision %d, MAC %pM, IRQ %d, %s EEPROM\n",
> CIDER_REV_GET(ks8851_rdreg16(ks, KS_CIDER)),
> ndev->dev_addr, ndev->irq,
> ks->rc_ccr & CCR_EEPROM ? "has" : "no");
>
> + mutex_unlock(&ks->lock);
> +
> return 0;
It's weird to look a mutex being hold to call netdev_info().
Perhaps change it to look like below as the netdev_info()
does a lot more things and holding the lock during that
seems to be a waste.
diff --git a/drivers/net/ethernet/micrel/ks8851.c b/drivers/net/ethernet/micrel/ks8851.c
index c722aa6..20237dc 100644
--- a/drivers/net/ethernet/micrel/ks8851.c
+++ b/drivers/net/ethernet/micrel/ks8851.c
@@ -1417,6 +1417,7 @@ static int __devinit ks8851_probe(struct spi_device *spi)
{
struct net_device *ndev;
struct ks8851_net *ks;
+ int result;
int ret;
ndev = alloc_etherdev(sizeof(struct ks8851_net));
@@ -1515,9 +1516,12 @@ static int __devinit ks8851_probe(struct spi_device *spi)
goto err_netdev;
}
+ mutex_lock(&ks->lock);
+ result = CIDER_REV_GET(ks8851_rdreg16(ks, KS_CIDER));
+ mutex_unlock(&ks->lock);
+
netdev_info(ndev, "revision %d, MAC %pM, IRQ %d, %s EEPROM\n",
- CIDER_REV_GET(ks8851_rdreg16(ks, KS_CIDER)),
- ndev->dev_addr, ndev->irq,
+ result, ndev->dev_addr, ndev->irq,
ks->rc_ccr & CCR_EEPROM ? "has" : "no");
return 0;
fbl
prev parent reply other threads:[~2012-04-12 19:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-12 15:26 [PATCH] Fix missing mutex_lock/unlock mjr
2012-04-12 19:23 ` Flavio Leitner [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=20120412162319.377ae3cf@asterix.rh \
--to=fbl@redhat.com \
--cc=ben@simtec.co.uk \
--cc=davem@davemloft.net \
--cc=mjr@cs.wisc.edu \
--cc=netdev@vger.kernel.org \
--cc=sboyd@codeaurora.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;
as well as URLs for NNTP newsgroup(s).