linux-kernel - Re: [PATCH] printk(): add KERN

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]

Message-ID: <CAPXgP11MBdqc3BiDLA1q5gW4BZy2q4PoLtD20oRXfKY+C-HOgw@mail.gmail.com>
Date:	Tue, 3 Apr 2012 18:11:44 +0200
From:	Kay Sievers <kay@...y.org>
To:	Joe Perches <joe@...ches.com>
Cc:	linux-kernel@...r.kernel.org,
	Andrew Morton <akpm@...ux-foundation.org>,
	Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
	Len Brown <lenb@...nel.org>
Subject: Re: [PATCH] printk(): add KERN_CONT where needed

On Tue, Apr 3, 2012 at 18:05, Joe Perches <joe@...ches.com> wrote:
> On Tue, 2012-04-03 at 17:50 +0200, Kay Sievers wrote:
>> I did not claim to address the problem of concurrent continuation line
>> writers, and this patch has absolutely nothing to do with that
>> problem. It _does_ fix encountered problems,
>
> No it doesn't.  It fixes problems _you_ encounter
> with an unpublished modification of the printk
> subsystem.

Exactly. And that is what is written in the changelog of the patch.
But all that does not matter, the change results in more correct code
than the current one is; and that is all that matters.

Sure, I see your point, and support your effort, but I don't think
your arguments are related to this patch and you are hijacking
something unrelated, which should be discussed in a separate mail
thread, that's all.

Thanks,
Kay
--
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/