netdev - Socket options for different architectures (a short question)

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>] [day] [month] [year] [list]

Date:	Thu, 25 Jun 2009 15:42:54 +0300
From:	Kevin Wilson <wkevils@...il.com>
To:	netdev@...r.kernel.org
Subject: Socket options for different architectures (a short question)

Hello, netdev list,

I have a short question about socket options:
why does each architecture has a list of the socket options
it supports in a separate socket.h header ? it seems to me that the list
of these options is identical (I did not verified this though)
Is there a case when some specific platform/platforms define socket
options in a different way ?
Is there a case when some platform supports only part of the socket
options ?
For example, for

SO_DEBUG,SO_REUSEADDR, SO_SNDBUF, etc, we have the same definitions in

 arch/ia64/include/asm/socket.h, arch/xtensa/include/asm/socket.h,
 arch/x86/include/asm/socket.h ,arch/powerpc/include/asm/socket.h and so on.

Regards,
 Kevin
--
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