linux-kernel - Re: [patch 7/8] fdmap v2

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]

Date:	Wed, 06 Jun 2007 15:44:34 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	davidel@...ilserver.org
Cc:	linux-kernel@...r.kernel.org, torvalds@...ux-foundation.org,
	akpm@...ux-foundation.org, drepper@...hat.com, mingo@...e.hu,
	dada1@...mosbay.com
Subject: Re: [patch 7/8] fdmap v2 - implement sys_socket2

From: Davide Libenzi <davidel@...ilserver.org>
Date: Wed, 06 Jun 2007 15:30:31 -0700

> This patch implement a new syscall sys_socket2(), that accepts an
> extra "flags" parameter:
> 
> int socket2(int domain, int type, int protocol, int flags);
> 
> The flags parameter is used to pass extra flags to the kernel, and is
> at the moment used to select the file descriptor allocations inside
> the non-sequential area (O_NONSEQFD). The remaining parameters are
> exactly the same as the ones of sys_socket().
> The sys_accept() system call has been modified to return a file
> descriptor inside the non-sequential area, if the listening fd is.
> The sys_socketcall() system call has been also changed to support
> a new SYS_SOCKET2 indentifier.
> 
> Signed-off-by: Davide Libenzi <davidel@...ilserver.org>

Since the valid range of "domain" values is quite small,
we could avoid the new system call by cribbing some of the
upper bits of the 'domain' argument.

Valid existing programs pass in valid 'domain' values and
thus will not set any of the new flags.

Just an idea.
-
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/