[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20140804131249.GD6923@x2.net.home>
Date: Mon, 4 Aug 2014 15:12:49 +0200
From: Karel Zak <kzak@...hat.com>
To: Davidlohr Bueso <davidlohr@...com>
Cc: "Eric W. Biederman" <ebiederm@...ssion.com>,
Linux Containers <containers@...ts.linux-foundation.org>,
linux-api@...r.kernel.org,
"Michael Kerrisk (man-pages)" <mtk.manpages@...il.com>,
linux-fsdevel@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [REVIEW][PATCH 0/4] /proc/thread-self
On Thu, Jul 31, 2014 at 07:39:55PM -0700, Davidlohr Bueso wrote:
> On Thu, 2014-07-31 at 17:30 -0700, Eric W. Biederman wrote:
> > This is small chance changing /proc/net and /proc/mounts will cause
> > userspace regressions (although nothing has shown up in my testing) if
> > that happens we can just point the change that moves them from
> > /proc/self/... to /proc/thread-self/...
>
> Isn't breaking userspace a no no, no matter what? At least some
> util-linux programs makes use of both /proc/mounts and /proc/net.
Frankly, I don't care about /proc/mount, this file is more about backward
compatibility than about any real informations ;-)
The really important file is /proc/self/mountinfo. We use this file on
many places including shared libs and it seems (according to Eric's
suggestion), that the right think will be to update the libs to use
/proc/thread-self/mountinfo.
Note that I like the idea to have the magic symlink to access thread
specific /proc stuff. It's definitely nice thing for userspace.
Karel
--
Karel Zak <kzak@...hat.com>
http://karelzak.blogspot.com
--
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