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

2019-01-08 Thread Mimi Zohar
On Tue, 2019-01-08 at 08:45 +1100, James Morris wrote: > > 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. > > If you see changes doing this, please call them out. Any changes to LSM >

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

2019-01-07 Thread James Morris
On Sat, 29 Dec 2018, Mimi Zohar wrote: > On Sat, 2018-12-29 at 10:34 -0800, Casey Schaufler wrote: > > On 12/28/2018 8:15 PM, Linus Torvalds wrote: > > > On Fri, Dec 28, 2018 at 8:09 PM James Morris wrote: > > >> Yep, I understand what you mean. I can't find the discussion from several > > >>

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

2018-12-29 Thread Mimi Zohar
On Sat, 2018-12-29 at 10:34 -0800, Casey Schaufler wrote: > On 12/28/2018 8:15 PM, Linus Torvalds wrote: > > On Fri, Dec 28, 2018 at 8:09 PM James Morris wrote: > >> Yep, I understand what you mean. I can't find the discussion from several > >> years ago, but developers asked to be able to work

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

2018-12-29 Thread Casey Schaufler
On 12/28/2018 8:15 PM, Linus Torvalds wrote: > On Fri, Dec 28, 2018 at 8:09 PM James Morris wrote: >> 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

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

2018-12-28 Thread James Morris
On Fri, 28 Dec 2018, Linus Torvalds wrote: > On Fri, Dec 28, 2018 at 7:11 PM James Morris wrote: > > > > I do this every development cycle, after requests from security subsystem > > maintainers to sync to -rc kernels. > > Why? > > A merge should have a *reason*. Yep, I understand what you

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

2018-12-28 Thread Linus Torvalds
On Fri, Dec 28, 2018 at 7:11 PM James Morris wrote: > > I do this every development cycle, after requests from security subsystem > maintainers to sync to -rc kernels. Why? A merge should have a *reason*. Linus

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

2018-12-28 Thread Linus Torvalds
On Fri, Dec 28, 2018 at 8:09 PM James Morris wrote: > > 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

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

2018-12-28 Thread James Morris
On Thu, 27 Dec 2018, Linus Torvalds wrote: > On Mon, Dec 24, 2018 at 11:55 AM James Morris wrote: > > > > The main changes here are Paul Gortmaker's removal of unneccesary module.h > > infrastructure. > > I will point out a merge with a horrible commit message: > > "Sync to Linux 4.20-rc2

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

2018-12-27 Thread pr-tracker-bot
The pull request you sent on Tue, 25 Dec 2018 06:55:00 +1100 (AEDT): > git://git.kernel.org/pub/scm/linux/kernel/git/jmorris/linux-security.git > next-general has been merged into torvalds/linux.git: https://git.kernel.org/torvalds/c/3f03bf93947fa2a2b84fac56e93c65d4fffed7f1 Thank you! --

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

2018-12-27 Thread Linus Torvalds
On Mon, Dec 24, 2018 at 11:55 AM James Morris wrote: > > The main changes here are Paul Gortmaker's removal of unneccesary module.h > infrastructure. I will point out a merge with a horrible commit message: "Sync to Linux 4.20-rc2 for downstream developers" that tells nobody anything. Why

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

2018-12-24 Thread James Morris
Hi Linus, Please pull these general updates for the security subsystem for v4.21. The main changes here are Paul Gortmaker's removal of unneccesary module.h infrastructure. The following changes since commit 7566ec393f4161572ba6f11ad5171fd5d59b0fbd: Linux 4.20-rc7 (2018-12-16 15:46:55