From: Dave <kilroyd@googlemail.com>
To: Andrey Borzenkov <arvidjaar@mail.ru>
Cc: orinoco-devel@lists.sourceforge.net,
linux-wireless@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: 2.6.28: warn_slowpath in orinoco receive path
Date: Mon, 05 Jan 2009 20:32:13 +0000 [thread overview]
Message-ID: <49626E4D.3010705@gmail.com> (raw)
In-Reply-To: <200901052005.12428.arvidjaar@mail.ru>
Andrey Borzenkov wrote:
> I would appreciate explanation which condition triggers this
> warn_slowpath. Otherwise does it ring the bell for someone? Network was
> dead after it till I reloaded modules (orinoco and hermes).
>
> [89479.105038] WARNING: at /home/bor/src/linux-git/lib/list_debug.c:30
> __list_add+0x8f/0xa0()
> [89479.105058] list_add corruption. prev->next should be next
> (dddb3568), but was cbc28978. (prev=dddb3568).
<snip>
> [89479.106002] Pid: 15746, comm: X Not tainted 2.6.28-1avb #26
> [89479.106020] Call Trace:
> [89479.106062] [<c011d3b0>] warn_slowpath+0x60/0x80
> [89479.106104] [<c01073d0>] ? native_sched_clock+0x20/0x70
> [89479.106194] [<c013d825>] ? lock_release_holdtime+0x35/0x200
> [89479.106218] [<c018d9f0>] ? __slab_alloc+0x550/0x560
> [89479.106254] [<c02f9c9d>] ? _spin_unlock+0x1d/0x20
> [89479.106270] [<c018d9f0>] ? __slab_alloc+0x550/0x560
> [89479.106302] [<c01ff2a7>] ? delay_tsc+0x17/0x24
> [89479.106319] [<c01ff221>] ? __const_udelay+0x21/0x30
> [89479.106376] [<dfa8b1e2>] ? hermes_bap_seek+0x112/0x1e0 [hermes]
> [89479.106396] [<c013d7eb>] ? trace_hardirqs_off+0xb/0x10
> [89479.106418] [<c018e307>] ? __kmalloc_track_caller+0xb7/0x110
> [89479.106448] [<c028eefc>] ? dev_alloc_skb+0x1c/0x30
> [89479.106465] [<c028eefc>] ? dev_alloc_skb+0x1c/0x30
> [89479.106482] [<c020e13f>] __list_add+0x8f/0xa0
> [89479.106551] [<dfd0fcae>] orinoco_interrupt+0xcae/0x16c0 [orinoco]
> [89479.106574] [<c013b0e3>] ? tick_dev_program_event+0x33/0xb0
> [89479.106594] [<c01073d0>] ? native_sched_clock+0x20/0x70
> [89479.106613] [<c013d825>] ? lock_release_holdtime+0x35/0x200
> [89479.106662] [<c013d7eb>] ? trace_hardirqs_off+0xb/0x10
> [89479.106892] [<dfe7faa7>] ? usb_hcd_irq+0x97/0xa0 [usbcore]
> [89479.106926] [<c015ba79>] handle_IRQ_event+0x29/0x60
> [89479.106947] [<c015cf89>] handle_level_irq+0x69/0xe0
> [89479.106963] [<c015cf20>] ? handle_level_irq+0x0/0xe0
> [89479.106977] <IRQ> [<c02ca933>] ? tcp_v4_rcv+0x633/0x6e0
> [89479.107025] [<c0103f0c>] ? common_interrupt+0x28/0x30
> [89479.107057] [<c02a0000>] ? sk_run_filter+0x320/0x7a0
> [89479.107078] [<c020e041>] ? list_del+0x21/0x90
> [89479.107106] [<dfd0d24e>] ? orinoco_rx_isr_tasklet+0x2ce/0x480
> [orinoco]
> [89479.107131] [<c01402e0>] ? __lock_acquire+0x160/0x1650
> [89479.107151] [<c01073d0>] ? native_sched_clock+0x20/0x70
> [89479.107169] [<c013d825>] ? lock_release_holdtime+0x35/0x200
> [89479.107200] [<c012249a>] ? irq_enter+0xa/0x60
> [89479.107217] [<c0104e52>] ? do_IRQ+0xd2/0x130
> [89479.107518] [<c010342c>] ? restore_nocheck_notrace+0x0/0xe
> [89479.107542] [<c0122830>] ? __do_softirq+0x0/0x110
> [89479.107561] [<c013f7b4>] ? trace_hardirqs_on_caller+0x74/0x140
> [89479.107583] [<c01ff678>] ? trace_hardirqs_on_thunk+0xc/0x10
> [89479.107602] [<c0122087>] ? tasklet_action+0x27/0x90
> [89479.107620] [<c013f7b4>] ? trace_hardirqs_on_caller+0x74/0x140
> [89479.107638] [<c01220a3>] ? tasklet_action+0x43/0x90
> [89479.107655] [<c012289f>] ? __do_softirq+0x6f/0x110
> [89479.107674] [<c0122830>] ? __do_softirq+0x0/0x110
> [89479.107685] <IRQ> [<c015cf20>] ? handle_level_irq+0x0/0xe0
> [89479.107715] [<c012246d>] ? irq_exit+0x5d/0x80
> [89479.107732] [<c0104e52>] ? do_IRQ+0xd2/0x130
> [89479.107747] [<c0103337>] ? sysenter_exit+0xf/0x16
> [89479.107765] [<c013f83d>] ? trace_hardirqs_on_caller+0xfd/0x140
> [89479.107782] [<c0103f0c>] ? common_interrupt+0x28/0x30
> [89479.107797] ---[ end trace a1fc0a52df4a729d ]---
Looks like the RX interrupt occurred at an inconvenient point during the
list_del call in the RX tasklet (orinoco_rx_isr_tasklet).
The call needs to be protected from the RX interrupt.
Quick patch included below - I'm not sure that the local_irq_* functions
are the ones we need, but it compiles and runs.
I don't suppose you're able to reproduce the error?
Dave.
---
diff --git a/drivers/net/wireless/orinoco/orinoco.c
b/drivers/net/wireless/orinoco/orinoco.c
index b33e13f..9a2d6be 100644
--- a/drivers/net/wireless/orinoco/orinoco.c
+++ b/drivers/net/wireless/orinoco/orinoco.c
@@ -1616,9 +1616,15 @@ static void orinoco_rx_isr_tasklet(unsigned long
data)
/* extract desc and skb from queue */
list_for_each_entry_safe(rx_data, temp, &priv->rx_list, list) {
+ unsigned long flags;
+
desc = rx_data->desc;
skb = rx_data->skb;
+
+ local_irq_save(flags);
list_del(&rx_data->list);
+ local_irq_restore(flags);
+
kfree(rx_data);
orinoco_rx(dev, desc, skb);
next prev parent reply other threads:[~2009-01-05 20:32 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-05 17:05 2.6.28: warn_slowpath in orinoco receive path Andrey Borzenkov
2009-01-05 20:32 ` Dave [this message]
2009-01-05 22:27 ` Jiri Slaby
2009-01-06 0:32 ` Robert Hancock
2009-01-06 0:32 ` Robert Hancock
2009-01-06 9:51 ` Andrey Borzenkov
2009-01-06 20:02 ` Dave
2009-01-06 21:07 ` Andrey Borzenkov
2009-01-06 23:40 ` Dave
2009-01-07 2:42 ` [Orinoco-devel] " David Gibson
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=49626E4D.3010705@gmail.com \
--to=kilroyd@googlemail.com \
--cc=arvidjaar@mail.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=orinoco-devel@lists.sourceforge.net \
/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.