From: "Theodore Ts'o" <tytso@mit.edu>
To: Karel Zak <kzak@redhat.com>
Cc: Harald Dunkel <harald.dunkel@aixigo.com>, util-linux@vger.kernel.org
Subject: Re: careful with that umount options, Eugene
Date: Fri, 7 Jun 2019 09:26:37 -0400 [thread overview]
Message-ID: <20190607132636.GA19820@mit.edu> (raw)
In-Reply-To: <20190607072003.ykquv57n3bpf2yf2@ws.net.home>
On Fri, Jun 07, 2019 at 09:20:03AM +0200, Karel Zak wrote:
> > Hmm... Should we also prevent a lazy unmount of the root file system?
>
> Not sure if we want to maintain extra rule/restriction in userspace.
> Is there any reason why this feature is supported by kernel?
I certainly can't think of one. I'll raise on linux-fsdevel; if
there's no good reason ever, I agree that it's probably better to
restrict in the kernel.
- Ted
prev parent reply other threads:[~2019-06-07 13:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-04 11:51 careful with that umount options, Eugene Harald Dunkel
2019-06-04 13:55 ` Václav Doležal
2019-06-06 12:59 ` Karel Zak
2019-06-06 23:31 ` Theodore Ts'o
2019-06-07 7:20 ` Karel Zak
2019-06-07 13:26 ` Theodore Ts'o [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=20190607132636.GA19820@mit.edu \
--to=tytso@mit.edu \
--cc=harald.dunkel@aixigo.com \
--cc=kzak@redhat.com \
--cc=util-linux@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.