linux-kernel - Re: [PATCH] perf trace: Handle legacy syscalls

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]

Message-ID: <550C413A.2010301@gmail.com>
Date:	Fri, 20 Mar 2015 09:48:10 -0600
From:	David Ahern <dsahern@...il.com>
To:	Arnaldo Carvalho de Melo <arnaldo.melo@...il.com>
CC:	linux-kernel@...r.kernel.org, Steven Rostedt <rostedt@...dmis.org>,
	Namhyung Kim <namhyung@...nel.org>,
	Jiri Olsa <jolsa@...nel.org>
Subject: Re: [PATCH] perf trace: Handle legacy syscalls

On 3/20/15 9:32 AM, Arnaldo Carvalho de Melo wrote:
> But then I don't think we need to do that, i.e. we can just have a
> boolean we set at some point to tell that we need to skip the first
> entry.
>
> I'll try to cook up a patch for that.

why have a boolean that is checked every time through the loop when its 
value will always be the same for a give run? why not just remove the 
entry as I suggested?
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/