linux-kernel - Re: [RFC PATCH for-next 2/4] epoll: epoll() syscall declaration

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: <20140224053232.GB7056@dcvr.yhbt.net>
Date:	Mon, 24 Feb 2014 05:32:32 +0000
From:	Eric Wong <normalperson@...t.net>
To:	Nathaniel Yazdani <n1ght.4nd.d4y@...il.com>
Cc:	viro@...iv.linux.org.uk, linux-fsdevel@...r.kernel.org,
	linux-kernel@...r.kernel.org
Subject: Re: [RFC PATCH for-next 2/4] epoll: epoll() syscall declaration

Nathaniel Yazdani <n1ght.4nd.d4y@...il.com> wrote:
> +asmlinkage long sys_epoll(int ep, struct epoll __user *in,
> +			  unsigned int inc, struct epoll __user *out,
> +			  unsigned int outc, int timeout);

I can understand using the new struct for 'in', but 'out' could just be
"struct epoll_event *" like sys_epoll_wait, right?

>  asmlinkage long sys_epoll_wait(int epfd, struct epoll_event __user *events,
--
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/