Re: [git pull] apparmor fix for __d_path() misuse

[Linus Torvalds]

On Tue, Dec 6, 2011 at 5:23 PM, Al Viro <viro@xxxxxxxxxxxxxxxxxx> wrote:
>
> Damnit, it may very well be NOT ANY KIND OF ROOT AT ALL.  Which is what
> I'd been trying to tell you all along.  You can race with umount -l.
> In that case that thing might have been *INSIDE* your chroot jail.
> Anywhere in it.

AND NOBODY CARES.

That's the deeper point here. IT DOES NOT MATTER.

Why do you try to convince people that it does. Nobody uses the
information that you claim is so magically important.

You are the only one who seems to think that it matters. No code
agrees with you except for the clearly broken AppArmor code that
everybody agrees should just go the f*ck away.

> See what I'm talking about?  I'm fine with giving the pathname to global
> root.  It's doing that to *random* just-unmounted vfsmount that is not
> a good thing.

It *never* matters. The pathname should never be used at all.

We want to *see* what the pathname is, but no code should ever use it.

The *only* valid use for the broken pathname is for a "show user debug
information". That's all I've ever claimed. The "where it was mounted
- or *if* it was mounted" part is pointless.

Why do you keep on harping on this totally useless issue? Seriously?

                 Linus
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/