seccomp update (next)
Hi,
Please pull these seccomp changes for next.
Thanks!
-Kees
The following changes since commit 5d01410fe4d92081f349b013a2e7a95429e4f2c9:
Linux 3.18-rc6 (2014-11-23 15:25:20 -0800)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/kees/linux.git tags/seccomp-next
for you to fetch changes up to cb24de187b9a0717246f05afc0f2be070e075d80:
seccomp: Replace smp_read_barrier_depends() with lockless_dereference() (2014-11-25 11:40:24 -0800)
----------------------------------------------------------------
Improves SMP dereferencing with new macro.
----------------------------------------------------------------
Pranith Kumar (1):
seccomp: Replace smp_read_barrier_depends() with lockless_dereference()
kernel/seccomp.c | 7 +++---- 1 file changed, 3 insertions(+), 4 deletions(-)
Signature · 2 lines
Kees Cook Chrome OS Security
Quoted 23 lines · Kees Cook
Hi,
Please pull these seccomp changes for next.
Thanks!
-Kees
The following changes since commit
5d01410fe4d92081f349b013a2e7a95429e4f2c9:Linux 3.18-rc6 (2014-11-23 15:25:20 -0800)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/kees/linux.gittags/seccomp-nextfor you to fetch changes up to
cb24de187b9a0717246f05afc0f2be070e075d80:seccomp: Replace
smp_read_barrier_depends()withlockless_dereference()(2014-11-25 11:40:24 -0800)----------------------------------------------------------------
Improves SMP dereferencing with new macro.
Quoted 7 lines
----------------------------------------------------------------
Pranith Kumar (1):
seccomp: Replacesmp_read_barrier_depends()withlockless_dereference()kernel/seccomp.c | 7 +++---- 1 file changed, 3 insertions(+), 4 deletions(-)
This is what I get when pulling to my next branch:
9128 files changed, 468773 insertions(+), 340317 deletions(-)
Signature · 2 lines
James Morris <[email protected]>
Hi James,
Quoted 28 lines · On Thu, 27 Nov 2014 00:23:06 +1100 (AEDT) James Morris <[email protected]>…
Quoted 25 lines · Kees Cook
Please pull these seccomp changes for next.
Thanks!
-Kees
The following changes since commit
5d01410fe4d92081f349b013a2e7a95429e4f2c9:Linux 3.18-rc6 (2014-11-23 15:25:20 -0800)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/kees/linux.gittags/seccomp-nextfor you to fetch changes up to
cb24de187b9a0717246f05afc0f2be070e075d80:seccomp: Replace
smp_read_barrier_depends()withlockless_dereference()(2014-11-25 11:40:24 -0800)----------------------------------------------------------------
Improves SMP dereferencing with new macro.----------------------------------------------------------------
Pranith Kumar (1):
seccomp: Replacesmp_read_barrier_depends()withlockless_dereference()
Quoted 7 lines
Quoted 3 lines
kernel/seccomp.c | 7 +++---- 1 file changed, 3 insertions(+), 4 deletions(-)This is what I get when pulling to my next branch:
9128 files changed, 468773 insertions(+), 340317 deletions(-)
That would be because your tree is based on v3.17 and Kees' is based on v3.18-rc6 ...
Signature · 2 lines
Cheers, Stephen Rothwell [email protected]
Quoted 35 lines · Stephen Rothwell
Hi James,
Quoted 32 lines · On Thu, 27 Nov 2014 00:23:06 +1100 (AEDT) James Morris <[email protected]>…
Quoted 28 lines · Kees Cook
Please pull these seccomp changes for next.
Thanks!
-Kees
The following changes since commit
5d01410fe4d92081f349b013a2e7a95429e4f2c9:Linux 3.18-rc6 (2014-11-23 15:25:20 -0800)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/kees/linux.gittags/seccomp-nextfor you to fetch changes up to
cb24de187b9a0717246f05afc0f2be070e075d80:seccomp: Replace
smp_read_barrier_depends()withlockless_dereference()(2014-11-25 11:40:24 -0800)----------------------------------------------------------------
Improves SMP dereferencing with new macro.----------------------------------------------------------------
Pranith Kumar (1):
seccomp: Replacesmp_read_barrier_depends()withlockless_dereference()kernel/seccomp.c | 7 +++---- 1 file changed, 3 insertions(+), 4 deletions(-)
Quoted 6 lines
Quoted 3 lines
This is what I get when pulling to my next branch:
9128 files changed, 468773 insertions(+), 340317 deletions(-)That would be because your tree is based on v3.17 and Kees' is based on v3.18-rc6 ...
James, I can base on whatever you like. I can do v3.17, or even against your security-next. It seems everyone uses something different. :)
Thanks!
-Kees
Signature · 2 lines
Kees Cook Chrome OS Security
Quoted 6 lines · Kees Cook
Quoted 2 lines
That would be because your tree is based on v3.17 and Kees' is based on v3.18-rc6 ...
James, I can base on whatever you like. I can do v3.17, or even against your security-next. It seems everyone uses something different. :)
It's best to track my next branch as your upstream.
Signature · 2 lines
James Morris <[email protected]>
Quoted 10 lines · James Morris
Quoted 6 lines · Kees Cook
Quoted 2 lines
That would be because your tree is based on v3.17 and Kees' is based on v3.18-rc6 ...
James, I can base on whatever you like. I can do v3.17, or even against your security-next. It seems everyone uses something different. :)
It's best to track my next branch as your upstream.
It'll trigger collisions with what's the x86 -next from luto's changes. Should I just let Stephen sort that out?
-Kees
Signature · 2 lines
Kees Cook Chrome OS Security
Quoted 6 lines · Kees Cook
Quoted 5 lines · James Morris
Quoted 3 lines · Kees Cook
Quoted 2 lines
That would be because your tree is based on v3.17 and Kees' is based on v3.18-rc6 ...
Quoted 8 lines
Quoted 5 lines
Quoted 3 lines
James, I can base on whatever you like. I can do v3.17, or even against your security-next. It seems everyone uses something different. :)
It's best to track my next branch as your upstream.
It'll trigger collisions with what's the x86 -next from luto's changes. Should I just let Stephen sort that out?
Yep.
Signature · 2 lines
James Morris <[email protected]>
Quoted 12 lines · James Morris
Quoted 10 lines · Kees Cook
Quoted 9 lines · James Morris
Quoted 6 lines · Kees Cook
Quoted 2 lines
That would be because your tree is based on v3.17 and Kees' is based on v3.18-rc6 ...
James, I can base on whatever you like. I can do v3.17, or even against your security-next. It seems everyone uses something different. :)
Quoted 6 lines
Quoted 4 lines
Quoted 1 line
It's best to track my next branch as your upstream.
It'll trigger collisions with what's the x86 -next from luto's changes. Should I just let Stephen sort that out?
Yep.
Hm, it depends on 54ef6df3f3f1353d99c80c437259d317b2cd1cbd, so basing against security-next would make the tree unbuildable. Perhaps I should just wait for -rc1 to land first?
-Kees
Signature · 2 lines
Kees Cook Chrome OS Security
Quoted 15 lines · Kees Cook
Quoted 14 lines · James Morris
Quoted 12 lines · Kees Cook
Quoted 10 lines · James Morris
Quoted 6 lines · Kees Cook
Quoted 2 lines
That would be because your tree is based on v3.17 and Kees' is based on v3.18-rc6 ...
James, I can base on whatever you like. I can do v3.17, or even against your security-next. It seems everyone uses something different. :)
It's best to track my next branch as your upstream.
Quoted 8 lines
Quoted 4 lines
Quoted 2 lines
It'll trigger collisions with what's the x86 -next from luto's changes. Should I just let Stephen sort that out?
Yep.
Hm, it depends on
54ef6df3f3f1353d99c80c437259d317b2cd1cbd, so basing against security-next would make the tree unbuildable. Perhaps I should just wait for -rc1 to land first?
Yep, that will work.
Signature · 2 lines
James Morris <[email protected]>