Thread (11 messages) 11 messages, 5 authors, 2019-01-08

Re: [GIT PULL] security: general updates for v4.21

From: Mimi Zohar <zohar@linux.ibm.com>
Date: 2018-12-30 02:44:41
Also in: lkml

On Sat, 2018-12-29 at 10:34 -0800, Casey Schaufler wrote:
On 12/28/2018 8:15 PM, Linus Torvalds wrote:
quoted
On Fri, Dec 28, 2018 at 8:09 PM James Morris [off-list ref] wrote:
quoted
Yep, I understand what you mean. I can't find the discussion from several
years ago, but developers asked to be able to work with more current
kernels, and I recall you saying that if you want to do this, merge to a
specific -rc tag at least.
If people really want it, maybe the merge can state that explicit
thing, as it is I'm trying to push back on empty merges that don't
explain why they even exist.

                  Linus
The security tree tends to get changed from multiple directions,
most of which aren't based out of the security sub-system. The mount
rework from David is an excellent example. It gets hit just about
any time there's a significant VFS or networking change. Keeping
it current has helped find issues much earlier in the process.
Agreed, the security subsystem is different than other subsystems.  In
addition to VFS changes, are key changes.  Changes in other subsystems
do affect the LSMs/integrity.

Included in this open window are a number of LSM changes, which were
not posted on the LSM mailing list and are not being upstreamed via
the LSMs.

Mimi
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help