linux-kernel - Re: [PATCH] atl1c: dont use highprio tx queue

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <CA+5PVA74bejZhPxUAFHaeHLB0NBd7PCRc1sQvmSY7QdmarCWEw@mail.gmail.com>
Date:	Thu, 16 Feb 2012 07:36:09 -0500
From:	Josh Boyer <jwboyer@...il.com>
To:	Eric Dumazet <eric.dumazet@...il.com>
Cc:	Thomas Meyer <thomas@...3r.de>, David Miller <davem@...emloft.net>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	"jcliburn@...il.com" <jcliburn@...il.com>,
	"chris.snook@...il.com" <chris.snook@...il.com>,
	netdev <netdev@...r.kernel.org>
Subject: Re: [PATCH] atl1c: dont use highprio tx queue

On Thu, Feb 16, 2012 at 1:43 AM, Eric Dumazet <eric.dumazet@...il.com> wrote:
> This driver attempts to use two TX rings but lacks proper support :
>
> 1) IRQ handler only takes care of TX completion on first TX ring
> 2) the stop/start logic uses the legacy functions (for non multiqueue
> drivers)
>
> This means all packets witk skb mark set to 1 are sent through high
> queue but are never cleaned and queue eventualy fills and block the
> device, triggering the infamous "NETDEV WATCHDOG" message.
>
> Lets use a single TX ring to fix the problem, this driver is not a real
> multiqueue one yet.
>
> Minimal fix for stable kernels.
>
> Reported-by: Thomas Meyer <thomas@...3r.de>
> Tested-by: Thomas Meyer <thomas@...3r.de>
> Signed-off-by: Eric Dumazet <eric.dumazet@...il.com>
> Cc: Jay Cliburn <jcliburn@...il.com>
> Cc: Chris Snook <chris.snook@...il.com>

As I think David handles netdev patches a bit differently for stable releases,
I'd like to suggest this get included in the next batch for the 3.2 kernel.
We've been seeing the bug this patch fixes in Fedora for quite a while now.

josh
--
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/