linux-kernel - Re: [take24 3/6] kevent: poll/select() notifications.

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <Pine.LNX.4.64.0611091207080.25481@alien.or.mcafeemobile.com>
Date:	Thu, 9 Nov 2006 12:10:42 -0800 (PST)
From:	Davide Libenzi <davidel@...ilserver.org>
To:	Evgeniy Polyakov <johnpol@....mipt.ru>
cc:	David Miller <davem@...emloft.net>,
	Ulrich Drepper <drepper@...hat.com>,
	Andrew Morton <akpm@...l.org>, netdev <netdev@...r.kernel.org>,
	Zach Brown <zach.brown@...cle.com>,
	Christoph Hellwig <hch@...radead.org>,
	Chase Venters <chase.venters@...entec.com>,
	Johann Borck <johann.borck@...sedata.com>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Jeff Garzik <jeff@...zik.org>
Subject: Re: [take24 3/6] kevent: poll/select() notifications.

On Thu, 9 Nov 2006, Davide Libenzi wrote:

> On Thu, 9 Nov 2006, Evgeniy Polyakov wrote:
> 
> > On Thu, Nov 09, 2006 at 10:51:56AM -0800, Davide Libenzi (davidel@...ilserver.org) wrote:
> > > On Thu, 9 Nov 2006, Evgeniy Polyakov wrote:
> > > 
> > > > +static int kevent_poll_callback(struct kevent *k)
> > > > +{
> > > > +	if (k->event.req_flags & KEVENT_REQ_LAST_CHECK) {
> > > > +		return 1;
> > > > +	} else {
> > > > +		struct file *file = k->st->origin;
> > > > +		unsigned int revents = file->f_op->poll(file, NULL);
> > > > +
> > > > +		k->event.ret_data[0] = revents & k->event.event;
> > > > +		
> > > > +		return (revents & k->event.event);
> > > > +	}
> > > > +}
> > > 
> > > You need to be careful that file->f_op->poll is not called inside the 
> > > spin_lock_irqsave/spin_lock_irqrestore pair, since (even this came up 
> > > during epoll developemtn days) file->f_op->poll might do a simple 
> > > spin_lock_irq/spin_unlock_irq. This unfortunate constrain forced epoll to 
> > > have a suboptimal double O(R) loop to handle LT events.
> >  
> > It is tricky - users call wake_up() from any context, which in turn ends
> > up calling kevent_storage_ready(), which calls kevent_poll_callback() with
> > KEVENT_REQ_LAST_CHECK bit set, which becomes almost empty call in fast
> > path. Since callback returns 1, kevent will be queued into ready queue,
> > which is processed on behalf of syscalls - in that case kevent will
> > check the flag and since KEVENT_REQ_LAST_CHECK is set, will call
> > callback again to check if kevent is correctly marked, but already
> > without that flag (it happens in syscall context, i.e. process context
> > without any locks held), so callback calls ->poll(), which can sleep,
> > but it is safe. If ->poll() returns 'ready' value, kevent is transfers
> > data into userspace, otherwise it is 'requeued' (just removed from
> > ready queue).
> 
> Oh, mine was only a general warn. I hadn't looked at the generic code 
> before. But now that I poke on it, I see:
> 
> void kevent_requeue(struct kevent *k)
> {
>        unsigned long flags;
> 
>        spin_lock_irqsave(&k->st->lock, flags);
>        __kevent_requeue(k, 0);
>        spin_unlock_irqrestore(&k->st->lock, flags);
> }
> 
> and then:
> 
> static int __kevent_requeue(struct kevent *k, u32 event)
> {
>        int ret, rem;
>        unsigned long flags;
> 
>        ret = k->callbacks.callback(k);
> 
> Isn't the k->callbacks.callback() possibly end up calling f_op->poll?

Ack, there the check for KEVENT_REQ_LAST_CHECK inside the callback.
The problem with f_op->poll was not that it can sleep (not excluded 
though) but that some f_op->poll can do a simple spin_lock_irq/spin_unlock_irq.
But for a quick peek your new code seems fine with that.



- Davide


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