netdev - Re: pull request: wireless-2.6 2008-06-03

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: <20080603.141652.245225529.davem@davemloft.net>
Date:	Tue, 03 Jun 2008 14:16:52 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	linville@...driver.com
Cc:	netdev@...r.kernel.org, linux-wireless@...r.kernel.org
Subject: Re: pull request: wireless-2.6 2008-06-03

From: "John W. Linville" <linville@...driver.com>
Date: Tue, 3 Jun 2008 15:09:43 -0400

> Kirill A. Shutemov (1):
>       wireless.h: improve userland include-ability

I'm not pulling this into my tree.  I've already replied
to that patch posting saying why I don't like this.

Even if I found this change as the only way to go and therefore
had to take it in, the commit log is way too terse about what
the problem is.  And it must describe the horrifics that are
now necessary to include this file in userspace after the change.

It needs to describe in detail what the conflicting types and
definitions in the kernel headers are that cause problems with
userspace, and the exact sequence of includes userland has to make in
order to get this right.

And I require such enormously scary details in order to make it clear
how bogus this change is.

There is zero point in us sanitizing kernel headers for userspace
usage if this kind of crap is still necessary.  I mean tell me, why
should we even bother in that case?  And this is why I'm not taking in
this changeset.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html