mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Daniel J Blueman <daniel.blueman@gmail.com>
Cc: Francois Romieu <romieu@fr.zoreil.com>,
	"David S. Miller" <davem@davemloft.net>,
	Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [2.6.37-rc1, patch v2] r8169: fix sleeping while holding spinlock...
Date: Tue, 2 Nov 2010 04:45:23 +0100	[thread overview]
Message-ID: <201011020445.23367.rjw@sisk.pl> (raw)
In-Reply-To: <AANLkTinzQGzsUGgzrhFo8eS1_OcnkVDOXRuc1C=0nMx=@mail.gmail.com>

On Tuesday, November 02, 2010, Daniel J Blueman wrote:
> Hi Francois,
> 
> On 1 November 2010 23:46, Francois Romieu <romieu@fr.zoreil.com> wrote:
> > Daniel J Blueman <daniel.blueman@gmail.com> :
> >> Recent changes to the r8169 driver cause it to call
> >> device_set_wakeup_enable under spinlock, which may sleep.
> >
> > The change is fine but the description is misleading : the r8169
> > driver has been issuing device_set_wakeup_enable under spinlock since
> > october 2008. device_set_wakeup_enable did not sleep until recently
> > (see f2dc0d1809ab7e0147c7e4ac837be1682f706538 for instance).

Yes, sorry about that.  I overlooked the fact that these drivers called
device_set_wakeup_enable() under spinlocks.

> Good catch; I also find that only the gainfar is the other driver
> needing fixing; I'll follow up with this.

Thanks a lot for taking care of this!

> Patch with updated description for David:
> 
> As device_set_wakeup_enable can now sleep, move the call to outside
> the critical section.
> 
> Signed-off-by: Daniel J Blueman <daniel.blueman@gmail.com>

Acked-by: Rafael J. Wysocki <rjw@sisk.pl>

> diff --git a/drivers/net/r8169.c b/drivers/net/r8169.c
> index d88ce9f..894e7c7 100644
> --- a/drivers/net/r8169.c
> +++ b/drivers/net/r8169.c
> @@ -846,10 +846,10 @@ static int rtl8169_set_wol(struct net_device
> *dev, struct ethtool_wolinfo *wol)
>  	else
>  		tp->features &= ~RTL_FEATURE_WOL;
>  	__rtl8169_set_wol(tp, wol->wolopts);
> -	device_set_wakeup_enable(&tp->pci_dev->dev, wol->wolopts);
> -
>  	spin_unlock_irq(&tp->lock);
> 
> +	device_set_wakeup_enable(&tp->pci_dev->dev, wol->wolopts);
> +
>  	return 0;
>  }
> 
> 


      reply	other threads:[~2010-11-02  3:46 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-01 21:35 [2.6.37-rc1, patch] " Daniel J Blueman
2010-11-01 23:46 ` Francois Romieu
2010-11-02  0:17   ` [2.6.37-rc1, patch v2] " Daniel J Blueman
2010-11-02  3:45     ` Rafael J. Wysocki [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=201011020445.23367.rjw@sisk.pl \
    --to=rjw@sisk.pl \
    --cc=daniel.blueman@gmail.com \
    --cc=davem@davemloft.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=romieu@fr.zoreil.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

all inboxes | Powered by JetHome®