From: Willy Tarreau <w@1wt.eu>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: linux-kernel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
torvalds@linux-foundation.org, stable@vger.kernel.org,
lwn@lwn.net, Jiri Slaby <jslaby@suse.cz>
Subject: Re: Linux 4.4.110
Date: Mon, 8 Jan 2018 10:16:35 +0100 [thread overview]
Message-ID: <20180108091634.GA10621@1wt.eu> (raw)
In-Reply-To: <20180105180235.GC30379@kroah.com>
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.
Regards
Willy
next prev parent reply other threads:[~2018-01-08 9:16 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-05 14:54 Linux 4.4.110 Greg KH
2018-01-05 14:54 ` Greg KH
2018-01-05 15:55 ` Willy Tarreau
2018-01-05 18:02 ` Greg KH
2018-01-05 18:42 ` Willy Tarreau
2018-01-05 19:58 ` Alan Cox
2018-01-05 20:24 ` Willy Tarreau
2018-01-06 13:16 ` Willy Tarreau
2018-01-08 9:16 ` Willy Tarreau [this message]
2018-01-08 9:29 ` Greg KH
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180108091634.GA10621@1wt.eu \
--to=w@1wt.eu \
--cc=akpm@linux-foundation.org \
--cc=gregkh@linuxfoundation.org \
--cc=jslaby@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=lwn@lwn.net \
--cc=stable@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).