All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeremy Fitzhardinge <jeremy@goop.org>
To: "Graham, Simon" <Simon.Graham@stratus.com>
Cc: xen-devel@lists.xensource.com
Subject: Re: 3.0.4: Soft lockup in netfront in SMP build
Date: Sat, 21 Apr 2007 15:14:16 -0700	[thread overview]
Message-ID: <462A8CB8.4080008@goop.org> (raw)
In-Reply-To: <342BAC0A5467384983B586A6B0B376710548B5AD@EXNA.corp.stratus.com>

Graham, Simon wrote:
> Just run into a (real) soft lockup running 3.0.4 - stack is at the end of this, but basically:
>
> . network_open acquires the rx spin lock with spin_lock() and then checks for
>   work on the queue and calls (I think) netif_rx_schedule with the lock still held which
>   can call into the hypervisor.
> . An interrupt is delivered to the bottom half of netfront which ends up calling netif_poll
>   which blocks attempting to acquire the rx spin lock.
>
> Oops! 
>
> I see from the unstable tree that this code was recently modified to use spin_lock_bh() instead of spin_lock() as part of a mega-merge of IA64 code - clearly we cant merge this changeset into 3.0.4.
>
> I haven't looked too closely at all of the code yet, but I'm wondering if a judicious change of spin_lock to spin_lock_bh in netfront would be the best approach?
>   

I found a few locking problems when I ran netfront with lockdep
enabled.  Fixes were committed to xen-unstable in 14844:abea8d171503 and
14851:22460cfaca71.  I was wondering if there had been any real cases of
these deadlocking.

    J

  reply	other threads:[~2007-04-21 22:14 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-21 21:45 3.0.4: Soft lockup in netfront in SMP build Graham, Simon
2007-04-21 22:14 ` Jeremy Fitzhardinge [this message]
2007-04-22  9:55 ` Keir Fraser

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=462A8CB8.4080008@goop.org \
    --to=jeremy@goop.org \
    --cc=Simon.Graham@stratus.com \
    --cc=xen-devel@lists.xensource.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.