linux-kernel - Re: [PATCH 1/2] r8169: Rx FIFO overflow fixes.

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: <20120220232219.GB13960@electric-eye.fr.zoreil.com>
Date:	Tue, 21 Feb 2012 00:22:19 +0100
From:	Francois Romieu <romieu@...zoreil.com>
To:	Jonathan Nieder <jrnieder@...il.com>
Cc:	booster@...ke7.net, hayeswang <hayeswang@...ltek.com>,
	"'Eric Dumazet'" <eric.dumazet@...il.com>, netdev@...r.kernel.org,
	"'nic_swsd'" <nic_swsd@...ltek.com>, linux-kernel@...r.kernel.org,
	"'Armin Kazmi'" <armin.kazmi@...dortmund.de>,
	Lucas Stach <dev@...xeye.de>
Subject: Re: [PATCH 1/2] r8169: Rx FIFO overflow fixes.

Jonathan Nieder <jrnieder@...il.com> :
[...]
> What do you think?  Is there any way I can help?  (E.g., given rough
> guidelines about what approach is acceptable I'd be happy to work with
> Gerd to produce a tested patch that does (1) and (2) but not (3) for
> 3.0.y.)

Few guidelines are needed: go for it.

I would trust the manufacturer for (3) though.

If you still have time to help, you should really try to break davem-next
branch. I won't claim it's bug-free but the IRQ / napi / Tx processing in
the r8169 driver should now be easier to read and maintain.

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