linux-kernel - Re: [patch 14/22] pollfs: pollable futex

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: <a36005b50705021049k44881c5er1b9e61d64618ae1e@mail.gmail.com>
Date:	Wed, 2 May 2007 10:49:36 -0700
From:	"Ulrich Drepper" <drepper@...il.com>
To:	"Davi Arnaut" <davi@...ent.com.br>
Cc:	"Eric Dumazet" <dada1@...mosbay.com>,
	"Andrew Morton" <akpm@...ux-foundation.org>,
	"Davide Libenzi" <davidel@...ilserver.org>,
	"Linus Torvalds" <torvalds@...ux-foundation.org>,
	"Linux Kernel Mailing List" <linux-kernel@...r.kernel.org>
Subject: Re: [patch 14/22] pollfs: pollable futex

On 5/2/07, Davi Arnaut <davi@...ent.com.br> wrote:
> NO! Every single waiter of the _file descriptor_ is waked, not of the futex.

And how is this better?  In this world of yours a program must have
one file descriptor for each single futex which is used like this *per
thread*.  There can be hundreds, thousands of threads.  And there can
be large numbers of futexes, too.

This is not going to fly.  You reach the file descriptor limit just
with this.  And this in many processes on the system.

> davi@...mic:~/git/linux-2.6$ find patches/ -name *.patch |grep -v
> syscall | wc -l
> 10
>
> davi@...mic:~/git/linux-2.6$ find patches/ -name *.patch |grep -v
> syscall |grep futex
> patches/pollfs-futex-async-wait.patch
> patches/pollfs-futex.patch

I don't know what  you want to show here.  You 10 new syscalls?  You
have two patches alone modifying futexes?  And 22 patches in total.
That's not "a lot"?
-
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/