From: Randy Dunlap <rdunlap@infradead.org>
To: Linus Torvalds <torvalds@linux-foundation.org>,
Linux List Kernel Mailing <linux-kernel@vger.kernel.org>
Cc: linux-security-module <linux-security-module@vger.kernel.org>,
Kees Cook <keescook@chromium.org>,
Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>,
James Morris <jmorris@namei.org>
Subject: Re: Linux 5.1-rc2
Date: Sun, 24 Mar 2019 19:31:16 -0700 [thread overview]
Message-ID: <2d4f3bfa-22c7-a18c-3902-fe1b6ac401f7@infradead.org> (raw)
In-Reply-To: <CAHk-=wgg_PRWs3a6u2gnFLQjhxOJcrFkqqWVnLw60eQAwD-DNw@mail.gmail.com>
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
next prev parent reply other threads:[~2019-03-25 2:31 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-24 21:26 Linux 5.1-rc2 Linus Torvalds
2019-03-25 2:31 ` Randy Dunlap [this message]
2019-03-25 19:08 ` James Morris
2019-03-25 21:05 ` Tetsuo Handa
2019-03-27 19:16 ` Kees Cook
2019-03-27 20:30 ` Tetsuo Handa
2019-03-27 20:45 ` Kees Cook
2019-03-27 21:05 ` Tetsuo Handa
2019-03-27 21:43 ` Kees Cook
2019-03-27 22:05 ` Tetsuo Handa
2019-03-27 22:23 ` Casey Schaufler
2019-03-27 22:55 ` Randy Dunlap
2019-03-27 23:22 ` Casey Schaufler
2019-03-29 18:07 ` James Morris
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=2d4f3bfa-22c7-a18c-3902-fe1b6ac401f7@infradead.org \
--to=rdunlap@infradead.org \
--cc=jmorris@namei.org \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=penguin-kernel@I-love.SAKURA.ne.jp \
--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).