linux-kernel - Re: epoll_ctl and const correctness

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: <49CD564E.6050101@msgid.tls.msk.ru>
Date:	Sat, 28 Mar 2009 01:42:22 +0300
From:	Michael Tokarev <mjt@....msk.ru>
To:	nicolas sitbon <nicolas.sitbon@...il.com>
CC:	linux-kernel@...r.kernel.org
Subject: Re: epoll_ctl and const correctness

nicolas sitbon wrote:
> I was looking at libevent of niels provos, and even him, is apparently
> doing a mistake :
> 
> static int
> epoll_add(void *arg, struct event *ev)
> {
> 	struct epollop *epollop = arg;
> 	struct epoll_event epev = {0, {0}};
> 
>         /* ... some code here ... */
> 	if (epoll_ctl(epollop->epfd, op, ev->ev_fd, &epev) == -1)
> 			return (-1);
> 
> 	/* Update events responsible */
> 	if (ev->ev_events & EV_READ)
> 		evep->evread = ev;
> 	if (ev->ev_events & EV_WRITE)
> 		evep->evwrite = ev;
> 
> 	return (0);
> }
> 
> the structure pointed to by &epev is allocated on the stack, so how
> the kernel could keep track of it?

I've no idea what are you talking about and what exactly
is your problem.  Both the examples (one at cplayer.org and
another above) gives correct usage of epoll.  If you don't
understand it, well, I'd suggest reading some documentation
first, maybe in kernel, maybe in glibc, maybe numerous
available on the net.  And all the numerous examples too,
which you quote as, for some reason, wrong.

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