linux-kernel - Re: scsi: Implement per-cpu logging buffer

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] [day] [month] [year] [list]

Message-ID: <alpine.LRH.2.00.1502171359340.2547@twin.jikos.cz>
Date:	Tue, 17 Feb 2015 14:01:18 +0100 (CET)
From:	Jiri Kosina <jkosina@...e.cz>
To:	Hannes Reinecke <hare@...e.de>
cc:	Josh Triplett <josh@...htriplett.org>,
	Geert Uytterhoeven <geert@...ux-m68k.org>,
	Christoph Hellwig <hch@....de>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	scsi <linux-scsi@...r.kernel.org>
Subject: Re: scsi: Implement per-cpu logging buffer

On Fri, 13 Feb 2015, Hannes Reinecke wrote:

> Thing is, if we were to use per-CPU buffers for printk() out of 
> necessity we have to queue these buffers for writing out. So there is a 
> time window during which the message already is in the per-CPU buffer 
> but still not printed out as printk() is currently writing out one of 
> the other per-CPU buffers.

Please also take a look at per-CPU printk() function redirection mechanism 
that got added because of printk()-from-NMI madness ('printk_func' 
pointer). It might be useful for your purposes as well.

-- 
Jiri Kosina
SUSE Labs

--
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/