linux-kernel - Re: [GIT]: Sparc

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]

Date:	Mon, 21 Apr 2008 17:16:19 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	viro@...IV.linux.org.uk
Cc:	torvalds@...ux-foundation.org, akpm@...ux-foundation.org,
	sparclinux@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [GIT]: Sparc

From: Al Viro <viro@...IV.linux.org.uk>
Date: Tue, 22 Apr 2008 00:25:34 +0100

> On Tue, Apr 22, 2008 at 12:18:15AM +0100, Al Viro wrote:
> 
> > FWIW, two things I _really_ want dead and gone are
> > 	* timod (or full rewrite of that animal; current one is badly racy
> > and plays fast and loose with way too many place in VFS guts)
> > 	* altroot (use chroot, damnit, and bind whatever you need in there)
> 
> BTW, the part about altroot goes for other architectures too; it's badly
> broken and it's one hell of an obstacle to fs/namei.c work of any kind.
> 
> As absolute minimum we _must_ lose the "if we hadn't found what we wanted
> in that subtree, repeat lookup starting at real root"; that's causing
> nightmares in pathname resolution and there's no excuse whatsoever for
> that since we have bindings.

The only platforms defining a non-NOP __emul_prefix() after this
sparc changeset are:

1) IA-64 for PER_LINUX32 --> /emul/ia32-linux/
2) MIPS for riscos and IRIX compat support
3) ARM for ARM_BSD_EMUL --> "usr/gnemul/bsd", yikes no leading slash
   in that path!

I bet if we really tried we could get rid of these things.
--
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/