linux-kernel - Re: [patch 7/8] fdmap v2

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: <20070606.160817.70217859.davem@davemloft.net>
Date:	Wed, 06 Jun 2007 16:08:17 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	davidel@...ilserver.org
Cc:	alan@...rguk.ukuu.org.uk, linux-kernel@...r.kernel.org,
	torvalds@...ux-foundation.org, akpm@...ux-foundation.org,
	drepper@...hat.com, mingo@...e.hu, dada1@...mosbay.com
Subject: Re: [patch 7/8] fdmap v2 - implement sys_socket2

From: Davide Libenzi <davidel@...ilserver.org>
Date: Wed, 6 Jun 2007 16:04:40 -0700 (PDT)

> On Wed, 6 Jun 2007, Alan Cox wrote:
> 
> > > The sys_accept() system call has been modified to return a file
> > > descriptor inside the non-sequential area, if the listening fd is.
> > > The sys_socketcall() system call has been also changed to support
> > > a new SYS_SOCKET2 indentifier.
> > 
> > This still all seems really really ugly. Is there anything wrong with
> > throwing all these extra cases out and replacing the entire lot with
> > 
> > 	prctl(PR_SPARSEFD, 1);
> > 
> > to turn on sparse fd allocation for a process ?
> 
> There was a little discussion where I tried to whisper something similar, 
> but Linus and Uli shot me :) - with good reasons IMO.
> You may link to runtimes that are not non-sequentialfd aware, and will 
> break them.

Thanks for explaining this issue clearly instead of telling people
to "go read the archives" in a condescending manner like someone
else did.
-
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/