linux-kernel - Re: [PATCHv2 4/4] first use of sys

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:	Fri, 16 Nov 2007 03:57:59 +0100
From:	Eric Dumazet <dada1@...mosbay.com>
To:	Ulrich Drepper <drepper@...hat.com>
CC:	linux-kernel@...r.kernel.org, akpm@...ux-foundation.org,
	mingo@...e.hu, tglx@...utronix.de, torvalds@...ux-foundation.org
Subject: Re: [PATCHv2 4/4] first use of sys_indirect system call

Ulrich Drepper a écrit :
> This is a first user of sys_indirect.  Several of the socket-related system
> calls which produce a file handle now can be passed an additional parameter
> to set the FD_CLOEXEC flag.

> 
> -	retval = sock_map_fd(sock);
> +	retval = sock_map_fd_flags(sock, current->indirect_params.file_flags.flags);

Yes, we know now why you wanted sys_indirect so much :)

However, there should be a macro or something to ease reader mind...

#define INDPARAM(SUBSYSNAME,PARAMNAME) \
	(current->indirect_params.##SUBSYSNAME.##PARAMNAME)

 > +	retval = sock_map_fd_flags(sock, INDPARAM(file_flags,flags));

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