lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Mon, 7 Nov 2016 15:51:32 -0800 From: Andy Lutomirski <luto@...capital.net> To: Steven Rostedt <rostedt@...dmis.org> Cc: "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>, Linus Torvalds <torvalds@...ux-foundation.org>, Ingo Molnar <mingo@...nel.org>, Andrew Morton <akpm@...ux-foundation.org>, Roland McGrath <roland@...k.frob.com>, Oleg Nesterov <oleg@...hat.com>, linux-arch <linux-arch@...r.kernel.org>, Peter Zijlstra <peterz@...radead.org> Subject: Re: [RFC][ATCH 1/3] ptrace: Remove maxargs from task_current_syscall() On Mon, Nov 7, 2016 at 1:26 PM, Steven Rostedt <rostedt@...dmis.org> wrote: > From: Steven Rostedt <rostedt@...dmis.org> > > task_current_syscall() has a single user that passes in 6 for maxargs, which > is the maximum arguments that can be used to get system calls from > syscall_get_arguments(). Instead of passing in a number of arguments to > grab, just get 6 arguments. The args argument even specifies that it's an > array of 6 items. > > This will also allow changing syscall_get_arguments() to not get a variable > number of arguments, but always grab 6. Reviewed-by: Andy Lutomirski <luto@...nel.org>
Powered by blists - more mailing lists