[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <2d4f3bfa-22c7-a18c-3902-fe1b6ac401f7@infradead.org>
Date: Sun, 24 Mar 2019 19:31:16 -0700
From: Randy Dunlap <rdunlap@...radead.org>
To: Linus Torvalds <torvalds@...ux-foundation.org>,
Linux List Kernel Mailing <linux-kernel@...r.kernel.org>
Cc: linux-security-module <linux-security-module@...r.kernel.org>,
Kees Cook <keescook@...omium.org>,
Tetsuo Handa <penguin-kernel@...ove.SAKURA.ne.jp>,
James Morris <jmorris@...ei.org>
Subject: Re: Linux 5.1-rc2
On 3/24/19 2:26 PM, Linus Torvalds wrote:
> Well, we're a week away from the merge window close, and here's rc2.
> Things look fairly normal, but honestly, rc2 is usually too early to
> tell. People haven't necessarily had time to notice problems yet.
> Which is just another way of saying "please test harder".
>
> Nothing particularly stands out. Yes, we had some fixes for the new
> io_ring code for issues that were discussed when merging it. Other
> than that, worth noting is that the bulk of the patches are for
> tooling, not the core kernel. In fact, about two thirds of the patch
> is just for the tools/ subdirectory, most of it due to some late perf
> tool updates. The people involved promise they're done.
Hmph. I'm still looking for the patch that restores the various
CONFIG_DEFAULT_<security> kconfig options to be merged.
https://lore.kernel.org/linux-security-module/2bf23acd-22c4-a260-7648-845887a409d5@i-love.sakura.ne.jp/
since commit 70b62c25665f636c9f6c700b26af7df296b0887e dropped them somehow.
--
~Randy
Powered by blists - more mailing lists