Files
android_kernel_xiaomi_sm8450/kernel
Andy Lutomirski 5c38065e02 seccomp: check in_compat_syscall, not is_compat_task, in strict mode
Seccomp wants to know the syscall bitness, not the caller task bitness,
when it selects the syscall whitelist.

As far as I know, this makes no difference on any architecture, so it's
not a security problem.  (It generates identical code everywhere except
sparc, and, on sparc, the syscall numbering is the same for both ABIs.)

Signed-off-by: Andy Lutomirski <luto@kernel.org>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
2016-03-22 15:36:02 -07:00
..
2015-12-04 22:46:25 +01:00
2015-04-11 22:27:55 -04:00
2015-11-19 17:51:48 +01:00
2016-01-22 18:04:28 -05:00
2016-02-08 11:25:39 -05:00
2015-12-14 14:54:37 -05:00
2016-03-12 20:57:38 +01:00
2015-04-12 21:03:31 +02:00
2015-11-23 09:44:58 +01:00
2016-02-16 13:04:58 -05:00
2016-03-17 15:09:34 -07:00
2015-01-17 10:02:23 +13:00
2016-01-22 18:04:28 -05:00
2016-03-01 20:36:56 +01:00
2014-12-10 17:41:10 -08:00