public inbox for linux-rt-users@vger.kernel.org
 help / color / mirror / Atom feed
From: Darcy Watkins <dwatkins@tranzeo.com>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: linux-rt-users <linux-rt-users@vger.kernel.org>
Subject: Re: rtmutex grabbed twice by same context in network code
Date: Tue, 15 Nov 2011 09:01:08 -0800	[thread overview]
Message-ID: <1321376468.27762.47.camel@tr-pentomino> (raw)
In-Reply-To: <alpine.LFD.2.02.1111150010200.4902@ionos>

On Mon, 2011-11-14 at 15:12 -0800, Thomas Gleixner wrote:
> On Mon, 14 Nov 2011, Darcy Watkins wrote:
> 
> > Hi,
> >
> > Anyone have insight into the kernel crash below?
> 
> Can you please enable CONFIG_PROVE_LOCKING ? That should tell us all
> the details.

Hi Thomas,

I tried that but couldn't fit the resulting system into the memory on
the device.  oops!   But I think I determined the cause.

The function header comments for netif_receive_skb() mentions it should
only be used under softirqd context.  I guess earlier kernel versions I
used didn't really care.  But the newest ones do.

To invoke it under the thread context, I used the technique described
in...

http://kerneltrap.org/mailarchive/linux-netdev/2010/5/19/6277601

...and it seems to avoid the crash.  Essentially the trick is to suspend
bottom half, then invoke netif_receive_skb(), then allow it.

When I looked at dev.c in netif_rx_ni() I notice functions like
migate_disable/enable(), are those related to SMP support?


Thanks,

Darcy
> 
> Thanks,
> 
>         tglx
> 
> 



      reply	other threads:[~2011-11-15 17:01 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-14 22:41 rtmutex grabbed twice by same context in network code Darcy Watkins
2011-11-14 23:12 ` Thomas Gleixner
2011-11-15 17:01   ` Darcy Watkins [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=1321376468.27762.47.camel@tr-pentomino \
    --to=dwatkins@tranzeo.com \
    --cc=linux-rt-users@vger.kernel.org \
    --cc=tglx@linutronix.de \
    /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