| 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 PHC | |
|
Open Source and information security mailing list archives
| ||
|
Date: Tue, 20 Nov 2007 17:47:32 -0700 From: ebiederm@...ssion.com (Eric W. Biederman) To: Roland McGrath <roland@...hat.com> Cc: Ingo Molnar <mingo@...e.hu>, Ulrich Drepper <drepper@...hat.com>, Guillaume Chazarain <guichaz@...oo.fr>, Pavel Emelyanov <xemul@...nvz.org>, "Rafael J. Wysocki" <rjw@...k.pl>, Pavel Machek <pavel@....cz>, kernel list <linux-kernel@...r.kernel.org>, netdev <netdev@...r.kernel.org> Subject: Re: 2.6.24-rc3: find complains about /proc/net Roland McGrath <roland@...hat.com> writes: >> can you see any danger to providing a /proc/self_task/ link? (or can you >> think of a better name/API/approach) > > That is a poor name to choose given /proc/self/task exists as something > else (just try writing a sentence comparing them and then read it aloud). > Probably /proc/self/task/self is what makes the most sense structurally. > I don't know if it matters to whatever use you are concerned with to have > two more steps in the lookup. Well the only case it could matter is if you aren't allowed to access /proc/<tgid> which I think may actually be the current selinux behavior. So if we can't fix /proc/self we need to introduce /proc/task-self at the top level, just to be certain we don't run into weird cases like that. Otherwise /proc/self/task/self sounds like a wonderful suggestion. Eric - To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists