| 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
| ||
|
Date: Tue, 05 Feb 2008 10:00:25 -0800 From: Dave Hansen <haveblue@...ibm.com> To: Oren Laadan <orenl@...columbia.edu> Cc: Pierre Peiffer <pierre.peiffer@...l.net>, linux-kernel@...r.kernel.org, containers@...ts.linux-foundation.org, Alexey Dobriyan <adobriyan@...il.com> Subject: Re: [PATCH 2.6.24-rc8-mm1 09/15] (RFC) IPC: new kernel API to change an ID On Tue, 2008-02-05 at 04:51 -0500, Oren Laadan wrote: > That said, I suggest the following method instead (this is the method > we use in Zap to determine the desired resource identifier when a new > resource is allocated; I recall that we had discussed it in the past, > perhaps the mini-summit in september ?): > > 1) The process/thread tells the kernel that it wishes to pre-determine > the resource identifier of a subsequent call (this can be done via a > new syscall, or by writing to /proc/self/...). > > 2) Each system call that allocates a resource and assigns an > identifier > is modified to check this per-thread field first; if it is set then > it will attempt to allocate that particular value (if already taken, > return an error, eg. EBUSY). Otherwise it will proceed as it is today. You forgot to attach the patch to your mail. ;) -- Dave -- 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/
Powered by blists - more mailing lists