netdev - Re: [stable request <= 3.11] net/mlx4

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: <20141103.150917.1015521239616746570.davem@davemloft.net>
Date:	Mon, 03 Nov 2014 15:09:17 -0500 (EST)
From:	David Miller <davem@...emloft.net>
To:	cwang@...pensource.com
Cc:	ben@...adent.org.uk, vlee@...pensource.com, amirv@...lanox.com,
	ogerlitz@...lanox.com, jackm@....mellanox.co.il,
	eugenia@...lanox.com, matanb@...lanox.com, netdev@...r.kernel.org
Subject: Re: [stable request <= 3.11] net/mlx4_en: Fix BlueFlame race

From: Cong Wang <cwang@...pensource.com>
Date: Mon, 3 Nov 2014 09:22:18 -0800

> On Sat, Nov 1, 2014 at 10:41 AM, David Miller <davem@...emloft.net> wrote:
>>
>> There is no documented way nor do I wish to state anything so strictly.
>> I want maximum flexibility for such a time consuming task.
>>
>> I tend to go back 3 or 4 releases at most, and it really depends upon
>> the difficulty of the backports and my own time constraints.
> 
> You should really offload to developers, otherwise too much work for you. :)

That's exactly what I am doing by having the -stable maintainers for older
releases deal with the backports and other pains.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html