netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Patrick McHardy <kaber@trash.net>
To: Jarek Poplawski <jarkao2@gmail.com>
Cc: Jay Cliburn <jcliburn@gmail.com>, netdev@vger.kernel.org
Subject: Re: atl1 warn_on_slowpath help
Date: Wed, 29 Oct 2008 09:12:20 +0100	[thread overview]
Message-ID: <49081AE4.9040301@trash.net> (raw)
In-Reply-To: <20081029071549.GA4861@ff.dom.local>

Jarek Poplawski wrote:
> On 29-10-2008 01:08, Jay Cliburn wrote:
>> I'm pretty fuzzy on the mechanics of warn_on_slowpath, so I'd like to
>> ask for help from more experienced netdev developers.
>>
>> An atl1 user reports the following warning when receiving a VLAN tagged
>> packet.
>>
>> [   27.779463] ------------[ cut here ]------------
>> [   27.779509] WARNING: at kernel/softirq.c:136 local_bh_enable+0x37/0x81()
> ...
>> [   27.782520]  [<c0264755>] netif_nit_deliver+0x5b/0x75
>> [   27.782590]  [<c02bba83>] __vlan_hwaccel_rx+0x79/0x162
>> [   27.782664]  [<f8851c1d>] atl1_intr+0x9a9/0xa7c [atl1]
>> [   27.782738]  [<c0155b17>] handle_IRQ_event+0x23/0x51
>> [   27.782808]  [<c015692e>] handle_edge_irq+0xc2/0x102
>> [   27.782878]  [<c0105fd5>] do_IRQ+0x4d/0x64
>> [   27.782947]  [<c010434f>] common_interrupt+0x23/0x28
>> [   27.783017]  [<c0108df6>] mwait_idle+0x2f/0x3b
>> [   27.783085]  [<c0102a75>] cpu_idle+0xde/0x101
>> [   27.783154]  =======================
>> [   27.783195] ---[ end trace 744634f3da93b46a ]---
>>
>> I've flailed around trying to find the bug, but haven't been
>> successful -- primarily because I don't understand the
>> warn_on_slowpath stuff well enough to know what to look for. Can someone
>> please take a quick look at drivers/net/atlx/atl1.c around line 2017
>> and see if there's an obvious error?  I'd really appreciate it.
> 
> It looks to me like vlan_hwaccel_rx() is to blame: I doubt we can do
> netif_nit_deliver() in hard irq context. (Patrick Cc-ed.)

Crap, I didn't think of that, all drivers I tested with support
NAPI. I can't think of a clean way to fix it right now, but I'll
look into it.

  reply	other threads:[~2008-10-29  8:12 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-29  0:08 atl1 warn_on_slowpath help Jay Cliburn
2008-10-29  7:15 ` Jarek Poplawski
2008-10-29  8:12   ` Patrick McHardy [this message]
2008-10-29 10:17     ` Patrick McHardy
2008-10-29 12:51       ` J. K. Cliburn
2008-10-29 12:54         ` Patrick McHardy
2008-10-29 14:15         ` Ramon Casellas
2008-10-29 16:47           ` Patrick McHardy
2008-10-29 13:03       ` Jarek Poplawski
2008-10-29 13:09         ` Patrick McHardy
2008-10-29 13:22           ` Jarek Poplawski
2008-10-29 13:26             ` Patrick McHardy
2008-10-29 14:04               ` Jarek Poplawski
2008-10-29 16:40                 ` Patrick McHardy

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=49081AE4.9040301@trash.net \
    --to=kaber@trash.net \
    --cc=jarkao2@gmail.com \
    --cc=jcliburn@gmail.com \
    --cc=netdev@vger.kernel.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).