From: "J. R. Okajima" <hooanon05g@gmail.com>
To: Al Viro <viro@zeniv.linux.org.uk>
Cc: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
kolyshkin@gmail.com
Subject: Re: [PATCH] concrete /proc/mounts
Date: Mon, 27 May 2019 04:06:38 +0900 [thread overview]
Message-ID: <14954.1558897598@jrobl> (raw)
In-Reply-To: <20190526120719.GQ17978@ZenIV.linux.org.uk>
Al Viro:
> Translation: let's generate the entire contents on the first read() and keep
> it until the sucker's closed; that way userland wont' see anything changing
> under it. Oh, wait...
>
> NAK.
Do you mean that the change can hide other mountpoints which are
kept unchanged before/after read()?
J. R. Okajima
prev parent reply other threads:[~2019-05-26 19:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-26 9:11 [PATCH] concrete /proc/mounts J. R. Okajima
2019-05-26 12:07 ` Al Viro
2019-05-26 19:06 ` J. R. Okajima [this message]
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=14954.1558897598@jrobl \
--to=hooanon05g@gmail.com \
--cc=kolyshkin@gmail.com \
--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).