On Fri, Jun 20, 2014 at 07:10:46PM +0100, Kees Cook wrote: > On Fri, Jun 20, 2014 at 10:36 AM, Kees Cook <keesc...@chromium.org> wrote: > > On Fri, Jun 20, 2014 at 10:23 AM, Will Deacon <will.dea...@arm.com> wrote: > >> Right, gotcha. Thanks for the explanation. I was confused, because > >> tracehook_report_syscall does the right thing (returns > >> current_thread_info()->syscall), but if we don't have TIF_SYSCALL_TRACE > >> set, > >> then updates during the secure_computing callback will be ignored. > >> > >> However, my fix to this is significantly smaller than your patch, so I fear > >> I'm still missing something. > > > > Oh, yes, that's much smaller. Nice! I will test this and report back. > > Yup, I can confirm this works. Thanks! > > Tested-by: Kees Cook <keesc...@chromium.org>
Thanks, Kees. I'll post a patch shortly. I'll try and remember to keep an eye out for this when seccomp lands for arm64 too. Will -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
