linux-kernel - Re: [PATCH] tracing: Choose static tp_printk buffer by explicit nesting count

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <CALCETrX9jQMiQb0U0PUH5hDe0Cjf3CsqQVDXUYO3oMLTtVmjHA@mail.gmail.com>
Date:	Wed, 25 May 2016 13:18:25 -0700
From:	Andy Lutomirski <luto@...capital.net>
To:	Namhyung Kim <namhyung@...il.com>
Cc:	Andy Lutomirski <luto@...nel.org>,
	Peter Zijlstra <peterz@...radead.org>,
	LKML <linux-kernel@...r.kernel.org>,
	Steven Rostedt <rostedt@...dmis.org>,
	Ingo Molnar <mingo@...hat.com>
Subject: Re: [PATCH] tracing: Choose static tp_printk buffer by explicit
 nesting count

On Wed, May 25, 2016 at 6:20 AM, Namhyung Kim <namhyung@...il.com> wrote:
> Hi Andy,

>> - out:
>> +
>> +out_nobuffer:
>> +       put_trace_buf();
>> +
>> +out:
>
> Shouldn't the labels be reversed like below?
>
> out:
>         put_trace_buf();
>
> out_nobuffer:

Yes.  I'll send a new version.

--Andy