linux-kernel - Re: [RFC][PATCH] printk: Fixup the nmi printk mess

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:	Wed, 10 Jun 2015 21:36:12 +0200
From:	Peter Zijlstra <peterz@...radead.org>
To:	Petr Mladek <pmladek@...e.cz>
Cc:	Steven Rostedt <rostedt@...dmis.org>, linux-kernel@...r.kernel.org,
	jkosina@...e.cz, paulmck@...ux.vnet.ibm.com,
	Ingo Molnar <mingo@...nel.org>,
	Thomas Gleixner <tglx@...utronix.de>
Subject: Re: [RFC][PATCH] printk: Fixup the nmi printk mess

On Wed, Jun 10, 2015 at 09:23:04PM +0200, Peter Zijlstra wrote:
> +static int vprintk_nmi(const char *fmt, va_list args)
> +{
> +	struct nmi_seq_buf *s = this_cpu_ptr(&nmi_print_seq);
> +	int add = -1, len;
> +
> +	irq_work_queue(&s->work);
> +
> +	/*
> +	 * head > tail; indicates someone is writing.
> +	 * avoids the buffer being truncated.
> +	 *
> +	 * we rely on the memory barrier to ensure the increment
> +	 * is visible before we start writing to the buffer.
> +	 */
> +	len = atomic_inc_return(&s->head);

That wants to be:

	len = atomic_inc_return(&s->head) - 1;

we need the value before the increment, not after it.

> +
> +	if (len < sizeof(s->buffer)) {
> +		add = vsnprintf(s->buffer + len, sizeof(s->buffer) - len, fmt, args);
> +		/*
> +		 * Fwd head to the right location; NMIs do not nest, therefore
> +		 * we can use regular stores.
> +		 */
> +		atomic_set(&s->head, len + add);
> +		/*
> +		 * Once the data is written and head is correct, update tail to
> +		 * match; indicating we're complete.
> +		 */
> +		smp_wmb();
> +		atomic_set(&s->tail, len + add);
> +	}
> +
> +	return add;
> +}
--
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/