linux-kernel - Re: [PATCH] posix_types.h: make _

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: <CA+55aFxYe64cNUNc5Xsz3R34nLynhWri=7konGGgM9iNHFVuFg@mail.gmail.com>
Date:	Tue, 24 Jul 2012 12:59:40 -0700
From:	Linus Torvalds <torvalds@...ux-foundation.org>
To:	Josh Boyer <jwboyer@...hat.com>
Cc:	Jeff Law <law@...hat.com>,
	Andrew Morton <akpm@...ux-foundation.org>,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] posix_types.h: make __NFDBITS match glibc definition

On Tue, Jul 24, 2012 at 12:41 PM, Josh Boyer <jwboyer@...hat.com> wrote:
>
> I'd be happy to come up with a patch that drops them, but since they're
> in a user visible header file I was concerned somebody might be using
> them explicitly from posix_types.h.  People do weird crap like not use
> glibc all the time.

Yeah, I agree that somebody could possibly use them.

But the odd thing is, we don't actually export anything *useful*. It's
not like we export the define for __FD_ISSET() etc, which would be
something somebody really wants. No, that kernel header only exports
the (unused by the kernel) building blocks for creating __FD_ISSET().

And I suspect (but it must be before even the old bitkeeper tree) that
we *used* to implement __FD_ISSET() long ago. We removed it, and
nobody used it, so nobody even noticed that we removed it - but left
some now unused stuff behind.

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