From: "Dmitry V. Levin" <ldv@altlinux.org>
To: Al Viro <viro@ZenIV.linux.org.uk>
Cc: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [RESEND v3 PATCH 3/3] vfs: make mounts and mountstats honor root dir like mountinfo does
Date: Tue, 30 Sep 2014 02:56:33 +0400 [thread overview]
Message-ID: <20140929225633.GA16855@altlinux.org> (raw)
In-Reply-To: <20140929212057.GN7996@ZenIV.linux.org.uk>
On Mon, Sep 29, 2014 at 10:20:57PM +0100, Al Viro wrote:
> On Tue, Sep 30, 2014 at 12:26:59AM +0400, Dmitry V. Levin wrote:
>
> > > Again, we do not break userland.
> >
> > Occasionally, we do. If you say there was no chroot prefix removal in the
> > kernel before, and there seems to be a prefix removal for at least 5 years,
> > then there must have been a break some years ago that went unnoticed.
>
> D'oh! Yes, we did. And yes, it was quite a few years ago, actually - back
> in 2000. I plead being low on sleep and lower on caffeine...
>
> For a moment I was even afraid that it was my own doing, but no - it came
> in https://lkml.org/lkml/2000/1/16/54. Werner Almesberger. IIRC, I hadn't
> realized that it was going to cause fun problems back then - basically,
> by that point 2.3 and 2.2 had already diverged a lot and quite a few things
> got written off as "oh, well - upgrade from 2.2 to 2.4 is going to be not
> far from building the system from scratch anyway, and nobody sane would be
> using 2.3 on anything other than scratch filesystem - IDE broken more often
> than not, memory corruption aplenty, etc."
Thanks, I won't be able to locate the change that fast.
It also means that the phrase "show mountpoints relative to the root
directory" I used in the commit message is irrelevant and should be
removed to avoid confusion.
> My apologies. Hmm... Filtering the out-of-root ones out is probably OK,
> but let's put that into -next after 3.18-rc1 and see if anyone yells.
BTW, the cleanup patch (vfs: cleanup show_mountinfo) could be safely
applied anytime - it's completely harmless.
--
ldv
next prev parent reply other threads:[~2014-09-29 22:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-29 18:05 [RESEND v3 PATCH 3/3] vfs: make mounts and mountstats honor root dir like mountinfo does Dmitry V. Levin
2014-09-29 18:32 ` Al Viro
2014-09-29 18:43 ` Dmitry V. Levin
2014-09-29 19:33 ` Al Viro
2014-09-29 20:26 ` Dmitry V. Levin
2014-09-29 21:20 ` Al Viro
2014-09-29 22:56 ` Dmitry V. Levin [this message]
2014-12-16 3:59 ` [RESEND v4 PATCH 1/2] vfs: cleanup show_mountinfo Dmitry V. Levin
2014-12-16 3:59 ` [RESEND v4 PATCH 2/2] vfs: make mounts and mountstats honor root dir like mountinfo does Dmitry V. Levin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20140929225633.GA16855@altlinux.org \
--to=ldv@altlinux.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=viro@ZenIV.linux.org.uk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).