From: Zach Brown <zab@zabbo.net>
To: Sage Weil <sweil@redhat.com>,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-api@vger.kernel.org
Subject: [PATCH RFC v2 0/2] O_NOCMTIME protected by generic mount option
Date: Fri, 15 May 2015 14:23:46 -0700 [thread overview]
Message-ID: <1431725028-24071-1-git-send-email-zab@zabbo.net> (raw)
Here's a current draft of what is now the O_NOCMTIME series. It
implements the frequent suggestion to gate unprivileged O_NOCMTIME use
with a mount option.
This method has the advantage of being entirely runtime. There's no
persistence that'd require updating all the tools that deal with each
file system's format. It's also requested by writers as they open.
Writes to the file that know nothing of O_NOCMTIME will behave as
usual.
Another suggested method is to use inode attributes: require root to
set +nocmtime on a dir and inherit it down subdirs to new files. This
nicely solves the unprivilieged use problem without having to fiddle
with mount options but it requires touching all systems that support
it and would prevent cmtime updates on all writes to the inode. I
have a patch series that starts on this but haven't taken it very far.
Sage is working on spinning up some hardware to test the various dirty
inode avoidance methods at load and should have numbers soon. That'll
tell us if lazytime isn't good enough and if any of this is worth the
trouble.
- z
next reply other threads:[~2015-05-15 21:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-15 21:23 Zach Brown [this message]
2015-05-15 21:23 ` [PATCH RFC v2 1/2] vfs: add generic nocmtime mount flag Zach Brown
[not found] ` <1431725028-24071-1-git-send-email-zab-ugsP4Wv/S6ZeoWH0uzbU5w@public.gmane.org>
2015-05-15 21:23 ` [PATCH RFC v2 2/2] vfs: add O_NOCMTIME Zach Brown
[not found] ` <1431725028-24071-3-git-send-email-zab-ugsP4Wv/S6ZeoWH0uzbU5w@public.gmane.org>
2015-05-16 21:50 ` Azat Khuzhin
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=1431725028-24071-1-git-send-email-zab@zabbo.net \
--to=zab@zabbo.net \
--cc=linux-api@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sweil@redhat.com \
/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).