From: Andrew Morton <akpm@linux-foundation.org>
To: Vasiliy Kulikov <segooon@gmail.com>
Cc: kernel-hardening@lists.openwall.com,
linux-kernel@vger.kernel.org,
Alexey Dobriyan <adobriyan@gmail.com>,
Al Viro <viro@zeniv.linux.org.uk>,
"H. Peter Anvin" <hpa@zytor.com>, Greg KH <greg@kroah.com>,
Theodore Tso <tytso@MIT.EDU>, Alan Cox <alan@lxorguk.ukuu.org.uk>,
Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: [RFC v2 1/3] procfs: parse mount options
Date: Mon, 21 Nov 2011 16:34:07 -0800 [thread overview]
Message-ID: <20111121163407.d8946ad8.akpm@linux-foundation.org> (raw)
In-Reply-To: <20111119110126.GA11468@albatros>
On Sat, 19 Nov 2011 15:01:26 +0400
Vasiliy Kulikov <segooon@gmail.com> wrote:
> This patch adds support of procfs mount options.
> Actual mount options are coming in the next patches.
The patches look sane to me.
I assume that `mount -o remount' has been tested and works as expected?
I also assume that any file which was opened prior to the remount will
remain accessible to any process which has the fd. Is this acceptable
from a security/operational POV?
next prev parent reply other threads:[~2011-11-22 0:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-19 11:01 [RFC v2 1/3] procfs: parse mount options Vasiliy Kulikov
2011-11-19 11:02 ` [RFC v2 2/3] procfs: add hidepid= and gid= " Vasiliy Kulikov
2011-12-05 22:55 ` Hugh Dickins
2011-12-08 19:21 ` Vasiliy Kulikov
2011-11-19 11:02 ` [RFC v2 3/3] procfs: add documentation for procfs " Vasiliy Kulikov
2011-11-22 0:34 ` Andrew Morton [this message]
2011-11-22 10:07 ` [RFC v2 1/3] procfs: parse " Vasiliy Kulikov
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=20111121163407.d8946ad8.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=adobriyan@gmail.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=greg@kroah.com \
--cc=hpa@zytor.com \
--cc=kernel-hardening@lists.openwall.com \
--cc=linux-kernel@vger.kernel.org \
--cc=segooon@gmail.com \
--cc=torvalds@linux-foundation.org \
--cc=tytso@MIT.EDU \
--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