| 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
| ||
|
Message-ID: <20141118141817.GG23958@pathway.suse.cz> Date: Tue, 18 Nov 2014 15:18:17 +0100 From: Petr Mladek <pmladek@...e.cz> To: Steven Rostedt <rostedt@...dmis.org> Cc: linux-kernel@...r.kernel.org, Ingo Molnar <mingo@...nel.org>, Andrew Morton <akpm@...ux-foundation.org>, Jiri Kosina <jkosina@...e.cz> Subject: Re: [PATCH 12/26 v5] tracing: Remove return values of most trace_seq_*() functions On Fri 2014-11-14 23:58:59, Steven Rostedt wrote: > From: "Steven Rostedt (Red Hat)" <rostedt@...dmis.org> > > The trace_seq_printf() and friends are used to store strings into a buffer > that can be passed around from function to function. If the trace_seq buffer > fills up, it will not print any more. The return values were somewhat > inconsistant and using trace_seq_has_overflowed() was a better way to know > if the write to the trace_seq buffer succeeded or not. > > Now that all users have removed reading the return value of the printf() > type functions, they can safely return void and keep future users of them > from reading the inconsistent values as well. > > Link: http://lkml.kernel.org/r/20141114011411.992510720@goodmis.org > > Signed-off-by: Steven Rostedt <rostedt@...dmis.org> Reviewed-by: Petr Mladek <pmladek@...e.cz> Best Regards, Petr -- 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/
Powered by blists - more mailing lists