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 Sep 2015 14:38:36 +0200 From: Petr Mladek <pmladek@...e.com> To: Steven Rostedt <rostedt@...dmis.org> Cc: Ingo Molnar <mingo@...hat.com>, Jiri Kosina <jkosina@...e.com>, linux-kernel@...r.kernel.org, Petr Mladek <pmladek@...e.com> Subject: [PATCH v3 0/2] ring_buffer: Make the benchmark slightly more safe These two patches fix potential races in the ring buffer benchmark. The first two versions were reviewed as part of the patchset that tried to convert some kthreads into the kthread worker API, see http://thread.gmane.org/gmane.linux.kernel.api/13224/focus=13821 Changes in v3: + fixed several comments (suggested by Steven) + removed duplicate memory barrier (suggested by Steven) Changes in v2: + keep the extra initialization; fix a race instead + move the setting of the current state (suggested by Steven) Petr Mladek (2): ring_buffer: Do no not complete benchmark reader too early ring_buffer: Fix more races when terminating the producer in the benchmark kernel/trace/ring_buffer_benchmark.c | 77 ++++++++++++++++++++---------------- 1 file changed, 44 insertions(+), 33 deletions(-) -- 1.8.5.6 -- 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