linux-kernel - Re: Linux 4.4.110

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: <20180108092949.GC32642@kroah.com>
Date:   Mon, 8 Jan 2018 10:29:49 +0100
From:   Greg KH <gregkh@...uxfoundation.org>
To:     Willy Tarreau <w@....eu>
Cc:     linux-kernel@...r.kernel.org,
        Andrew Morton <akpm@...ux-foundation.org>,
        torvalds@...ux-foundation.org, stable@...r.kernel.org, lwn@....net,
        Jiri Slaby <jslaby@...e.cz>
Subject: Re: Linux 4.4.110

On Mon, Jan 08, 2018 at 10:16:35AM +0100, Willy Tarreau wrote:
> On Fri, Jan 05, 2018 at 07:02:35PM +0100, Greg KH wrote:
> > On Fri, Jan 05, 2018 at 04:55:07PM +0100, Willy Tarreau wrote:
> > > On Fri, Jan 05, 2018 at 03:54:33PM +0100, Greg KH wrote:
> > > > I'm announcing the release of the 4.4.110 kernel.
> > > > 
> > > > All users of the 4.4 kernel series must upgrade.
> > > > 
> > > > But be careful, there have been some reports of problems with this
> > > > release during the -rc review cycle.  Hopefully all of those issues are
> > > > now resolved.
> > > > 
> > > > So please test, as of right now, it should be "bug compatible" with the
> > > > "enterprise" kernel releases with regards to the Meltdown bug and proper
> > > > support on all virtual platforms (meaning there is still a vdso issue
> > > > that might trip up some old binaries, again, please test!)
> > > > 
> > > > If anyone has any problems, please let me know.
> > > 
> > > FWIW I've just booted one of our LBs on it and am hammering it at full
> > > load with pti enabled and will let it run for the week-end. It takes
> > > 860k irq/s and about 1.7M syscalls/s. For now it works well (but slowly).
> > > Hopefully if there are any rare race conditions left it has a chance to
> > > trigger them.
> > 
> > Thanks for the testing, let me know if you see anything.  And "slowly",
> > does that mean it is noticable?  I have some querys from the virtual
> > networking people that are getting worried about all of this.  I told
> > them to go test, but they were having a hard time finding a kernel to
> > test with.  Hopefully we hear back from them now that these are out...
> 
> So at least the good news is that after 2.5 days, it has flawlessly
> forwarded 21 billion connections, 3 TB of TCP payload and processed ~180
> billion interrupts. No single error in dmesg nor in the test. Thus I'm
> now quite confident with this kernel's stability.

Wow, impressive.  Thanks for the testing and letting me know.

greg k-h