netdev - Re: [PATCH] [BACKPORT] [3.14.56] bnx2x: Don't notify about scratchpad parities

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 for Android: free password hash cracker in your pocket

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

Date:	Fri, 06 Nov 2015 18:40:42 +0100
From:	Patrick Schaaf <netdev@....de>
To:	Greg KH <gregkh@...uxfoundation.org>
Cc:	netdev@...r.kernel.org, Yuval Mintz <Yuval.Mintz@...gic.com>
Subject: Re: [PATCH] [BACKPORT] [3.14.56] bnx2x: Don't notify about scratchpad parities

On Friday 06 November 2015 09:32:46 Greg KH wrote:
> On Thu, Nov 05, 2015 at 11:18:37AM +0100, Patrick Schaaf wrote:
> > bnx2x: Don't notify about scratchpad parities
> > 
> > This is a (trivial) "backport" of ad6afbe9578d1fa26680faf78c846bd8c00d1d6e
> > to stable kernel 3.14.56.
> 
> This patch isn't in 4.1 either, do you want it there as well?

Personally I'll probably stay on 3.14 until 4.4 comes out, but the patch seems 
to make huge sense generally, given the 1 million in 8 second printk's I 
experienced :)

My 3 servers with the patch applied to 3.14.56 run rock solid so far (but the 
issue I had manifested only after 22 days of uptime, on one of them)

The cited commit from mainline applied nicely with some offset to 3.14.56, so 
I think you could just pull it down to all stable kernels.

best regards
  Patrick
--
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