From: Mateusz Guzik <mguzik@redhat.com>
To: Florian Margaine <florian@margaine.com>
Cc: Alexander Viro <viro@zeniv.linux.org.uk>,
Jeff Layton <jlayton@poochiereds.net>,
"J. Bruce Fields" <bfields@fieldses.org>,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] fs: add the FIGETFROZEN ioctl call
Date: Fri, 15 Apr 2016 02:50:54 +0200 [thread overview]
Message-ID: <20160415005052.6734gfnt7kjpwxyc@mguzik> (raw)
In-Reply-To: <CABRjmp_FK8PYyAhBjAqE3Er8gfPo+EkJA5+yzVg7SdBYEwjJeA@mail.gmail.com>
On Thu, Apr 14, 2016 at 09:57:07AM +0200, Florian Margaine wrote:
> This lets userland get the filesystem freezing status, aka whether the
> filesystem is frozen or not. This is so that an application can know if
> it should freeze the filesystem or if it isn't necessary when taking a
> snapshot.
The feature may be useful in general, I don't know.
However, I'm confused why programs would depend on it. If you froze
a particular subsystem, you don't have to check. If you did not, what
prevents whoever originaly froze it from unfreezing as you access it?
As such, maybe the feature you are looking for would count how many
times the fs is frozen.
--
Mateusz Guzik
next prev parent reply other threads:[~2016-04-15 0:51 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-14 7:57 Florian Margaine
2016-04-14 8:10 ` Florian Margaine
2016-04-15 0:50 ` Mateusz Guzik [this message]
2016-04-15 2:17 ` Dave Chinner
2016-04-16 12:18 ` Florian Margaine
2016-04-17 15:05 ` Jan Kara
2016-04-18 15:20 ` Eric Sandeen
2016-04-18 17:20 ` Florian Margaine
2016-04-18 17:47 ` Eric Sandeen
2016-04-18 23:06 ` Dave Chinner
2016-04-22 21:53 ` Florian Margaine
2016-04-22 23:14 ` Dave Chinner
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=20160415005052.6734gfnt7kjpwxyc@mguzik \
--to=mguzik@redhat.com \
--cc=bfields@fieldses.org \
--cc=florian@margaine.com \
--cc=jlayton@poochiereds.net \
--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
all inboxes | Powered by JetHome®