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:11:25 -0700
From:	Tejun Heo <tj@...nel.org>
To:	Joe Perches <joe@...ches.com>
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()

Hello,

On Thu, Mar 29, 2012 at 1:06 PM, Joe Perches <joe@...ches.com> wrote:
> 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...

Ah, okay.  Forgot about that.  Yeah, the kernel is single threaded at
that point, so it shouldn't matter. The code is rather complex so
something simpler would be nice, I agree.

Another thing is that we seem to have structured logging coming our
way and maybe userspace can deal with racing continuing printks? Not
sure how different streams could be distinguished tho. Maybe the
printing task can be used to group them? Kay, is this something
structured logging would solve?

Thanks.

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