linux-kernel - Re: [PATCH] percpu: use KERN_CONT in pcpu_dump_alloc

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:	Thu, 29 Mar 2012 13:06:56 -0700
From:	Joe Perches <joe@...ches.com>
To:	Tejun Heo <tj@...nel.org>
Cc:	Christoph Lameter <cl@...ux-foundation.org>,
	linux-kernel@...r.kernel.org, Kay Sievers <kay.sievers@...y.org>
Subject: Re: [PATCH] percpu: use KERN_CONT in pcpu_dump_alloc_info()

On Thu, 2012-03-29 at 12:51 -0700, Tejun Heo wrote:
> Hello, Joe.

Hello Tejun.

> On Thu, Mar 29, 2012 at 11:10 AM, Joe Perches <joe@...ches.com> wrote:
> > Perhaps it's better to try to print lines
> > in fewer printks?  Maybe use a line buffer?
> What practical difference would that make?

It'd be just for avoidance of any other possible
interleaving from other threads.

It's an __init function so that's not too likely,
but if it every happens...

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