From: kd6lvw@yahoo.com
To: "Eric W. Biederman" <ebiederm@xmission.com>,
Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org,
Vasiliy Kulikov <segoon@openwall.com>,
Arkadiusz Miskiewicz <a.miskiewicz@gmail.com>,
Alexey Dobriyan <adobriyan@gmail.com>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: Regression Mounting /proc w/ kernel 3.4.0 - "uid" parameter no longer ignored.
Date: Fri, 25 May 2012 17:26:49 -0700 (PDT) [thread overview]
Message-ID: <1337992009.23813.YahooMailClassic@web84502.mail.ne1.yahoo.com> (raw)
Ignoring "uid=#" is the documented behavior from the "mount(8)" man page for procfs. That implies that the proposed patch should be [temporarily] installed.
I personally don't care if the option is restored or not. My issue was that this side effect was not documented in any way in the change that occurred -- which affected documented behavior.
I mount my /proc file system in a "mount -at nonfs" statement in an initialization script. The "uid" optional parameter was in /etc/fstab. I have removed "uid" in my "at home" copy of the configuration but haven't visited the remote server to fix it there (I can't log in from remote as a result of this issue).
--- On Fri, 5/25/12, Linus Torvalds <torvalds@linux-foundation.org> wrote:
> If it is *only* uid, maybe we should just expressly ignore it. Like
> the (completely untested) attached patch.
next reply other threads:[~2012-05-26 0:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-26 0:26 kd6lvw [this message]
2012-05-26 0:30 ` Linus Torvalds
-- strict thread matches above, loose matches on Subject: below --
2012-05-24 19:52 Mounting /proc w/ kernel 3.4.0 - "uid" parameter no longer valid? kd6lvw
2012-05-25 20:19 ` Regression Mounting /proc w/ kernel 3.4.0 - "uid" parameter no longer ignored Eric W. Biederman
2012-05-25 21:42 ` Linus Torvalds
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=1337992009.23813.YahooMailClassic@web84502.mail.ne1.yahoo.com \
--to=kd6lvw@yahoo.com \
--cc=a.miskiewicz@gmail.com \
--cc=adobriyan@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=ebiederm@xmission.com \
--cc=linux-kernel@vger.kernel.org \
--cc=segoon@openwall.com \
--cc=torvalds@linux-foundation.org \
/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
all inboxes | Powered by JetHome®