linux-kernel - Re: spinlock BUG in qdisc

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <89cb5ede0803240434s7fad3d09y7a422213407f1e90@mail.gmail.com>
Date:	Mon, 24 Mar 2008 14:34:28 +0300
From:	"Khaled Al-Hamwi" <khaled.linux@...il.com>
To:	"David Miller" <davem@...emloft.net>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: spinlock BUG in qdisc_restart

On Sun, Mar 23, 2008 at 1:10 PM, David Miller <davem@...emloft.net> wrote:
> From: "Khaled Al-Hamwi" <khaled.linux@...il.com>
> Date: Sun, 23 Mar 2008 10:23:20 +0300
>
> > [<c02845af>] netif_receive_skb+0x1fc/0x23e
> > [<e033b560>] MM_IndicateRxPackets+0x2be/0x379 [bcm5700]
> > [<e0342c26>] LM_ServiceInterrupts+0xac/0xc5 [bcm5700]
> > [<e0337768>] bcm5700_interrupt+0x13c/0x2bd [bcm5700]
>
> This backtrace is not from a driver that is in the upstream kernel
> sources.
>
> Please use the supported and upstream "tg3" driver for this hardware.
>
> Thank you.
>

Thank you for your reply.

I need to use the bcm5700 driver. Otherwise, I have to reimplemented
the changes that has been already implemented.

By the way, I found the reason for this bug and fixed it. It was
caused by the scheduling of NET_TX_SOFTIRQ. The conflict happens when
tx softirq is run.
I have already disabled rx softirq as I am processing the packets at
the interrupt level.


Thanks,
Khaled
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/