linux-kernel - Re: [PATCH] cleanup paccept

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: <20081028191531.GA1007@infradead.org>
Date:	Tue, 28 Oct 2008 15:15:31 -0400
From:	Christoph Hellwig <hch@...radead.org>
To:	Ulrich Drepper <drepper@...hat.com>
Cc:	linux-kernel@...r.kernel.org, akpm@...ux-foundation.org,
	linux-api@...r.kernel.org, torvalds@...ux-foundation.org
Subject: Re: [PATCH] cleanup paccept

On Tue, Oct 28, 2008 at 03:09:51PM -0400, Ulrich Drepper wrote:
> This patch doesn't change *any* functionality from what is currently
> in the upstream kernel.  There is no reason to start arguing again and
> for me to explain everything the way I did it months ago.  This is just
> a *cleanup patch*, nothing else.  If you want to know why this cleanup
> is needed read the discussions of

Umm, it does enabled functionality that wasn't enabled before.  And that
functionality includes a syscall.  So any chance you could write a
proper changelog that describes what you actually do instead of lots of
ranting and references to old posts?

And no "[PATCH] cleanup paccept" isn't really a good subject for adding
a new syscalls either.

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