Re: [PATCH] alternative to sys_indirect, part 1

[Ulrich Drepper <drepper@redhat.com>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Alan Cox wrote:
> There are only a small number of valid socket types recognized by POSIX
> plus a few BSD plus a few Linux ones so Linux can happily assign the
> upper bits for a different purpose.

You didn't read what I wrote.  It's about the not-yet-assigned types.
For those the implementer must ensure that during the development no
value is used which can conflict with any current and future assigned
value and not with any other development.  Hence common practice is to
use a random value over the entire range.

I don't know about a case for socket but this is definitely how (sane)
development elsewhere works.


> Every other property of a socket via accept() is inherited from the
> parent. Making one property different would be bizarre and ugly.

Implementing this would visibly change existing code and it would
actively violate POSIX.  Not a good idea.

- --
➧ Ulrich Drepper ➧ Red Hat, Inc. ➧ 444 Castro St ➧ Mountain View, CA ❖
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (GNU/Linux)

iD8DBQFIEKRr2ijCOnn/RHQRAoltAJ98g8GHGSYceIJxyddjCRI6otoVagCfeTXC
TfgaalHo6XQEzehnST+unhk=
=T272
-----END PGP SIGNATURE-----