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
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Mon, 29 Feb 2016 11:21:11 -0300
From:	Arnaldo Carvalho de Melo <acme@...nel.org>
To:	Peter Zijlstra <peterz@...radead.org>
Cc:	Steven Rostedt <rostedt@...dmis.org>,
	Ingo Molnar <mingo@...nel.org>,
	Taeung Song <treeze.taeung@...il.com>,
	linux-kernel@...r.kernel.org, Jiri Olsa <jolsa@...nel.org>,
	Namhyung Kim <namhyung@...nel.org>,
	Thomas Gleixner <tglx@...utronix.de>,
	Lai Jiangshan <jiangshanlai@...il.com>
Subject: Re: [RFC] Re: [PATCH v3 1/2] tracing/syscalls: Rename variable 'nr'
 to '__syscall_nr'

Em Sat, Feb 27, 2016 at 04:13:57PM +0100, Peter Zijlstra escreveu:
> On Fri, Feb 26, 2016 at 10:57:13AM -0300, Arnaldo Carvalho de Melo wrote:
> 
> > Ingo, Peter, have you guys followed this case?
> > 
> > Summary: Some tracepoint have multiple fields with the same name, 'nr',
> >          the first one is a unique syscall ID, the other is a syscall
> >          argument:
> 
> I'm all for pushing the limits on tracepoint ABI. I'm all for making it
> less rigid. So if we can get away with changing this under the promise
> of helping fixup fallout, I'm all for it.
> 
> That means we can always just change tracepoints, and they're not really
> ABI at all.

I'll take that as an Acked-by, and will apply Taeung/Steven's patch for
the kernel + the builtin-trace.c change, Ok everybody?

- Arnaldo

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ