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: <4810A46B.1090809@redhat.com>
Date:	Thu, 24 Apr 2008 08:16:59 -0700
From:	Ulrich Drepper <drepper@...hat.com>
To:	Alan Cox <alan@...rguk.ukuu.org.uk>
CC:	linux-kernel@...r.kernel.org, netdev@...r.kernel.org,
	akpm@...ux-foundation.org, torvalds@...ux-foundation.org
Subject: Re: [PATCH] alternative to sys_indirect, part 1

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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ