linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Benjamin Marzinski" <bmarzins@redhat.com>
To: linux-fsdevel <linux-fsdevel@vger.kernel.org>
Cc: Jan Kara <jack@suse.cz>
Subject: [PATCH 0/2] renamed freeze/thaw hooks.
Date: Mon,  6 Oct 2014 15:12:07 -0500	[thread overview]
Message-ID: <1412626329-16867-1-git-send-email-bmarzins@redhat.com> (raw)

These are the freeze/thaw patches with the names Honza suggested. The only
other name ideas that I can think of that seem to work would involve just
using synonyms like suspend_fs/resume_fs.  While they aren't perfect, I like
freeze_super/thaw_super better.

Benjamin Marzinski (2):
  fs: add freeze_super/thaw_super fs hooks
  gfs2: update freeze code to use freeze/thaw_super on all nodes

 fs/block_dev.c       |  10 ++++-
 fs/gfs2/glops.c      |  26 ++++++-------
 fs/gfs2/glops.h      |   2 +
 fs/gfs2/incore.h     |  15 +++++---
 fs/gfs2/inode.c      |  40 +++++---------------
 fs/gfs2/log.c        |  29 ++++++---------
 fs/gfs2/main.c       |  11 +++++-
 fs/gfs2/ops_fstype.c |  16 ++------
 fs/gfs2/super.c      | 101 ++++++++++++++++++++++++++++++++++-----------------
 fs/gfs2/super.h      |   1 +
 fs/gfs2/trans.c      |  17 +++++++--
 fs/ioctl.c           |   6 ++-
 include/linux/fs.h   |   2 +
 13 files changed, 154 insertions(+), 122 deletions(-)

-- 
1.8.3.1


             reply	other threads:[~2014-10-06 21:17 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-06 20:12 Benjamin Marzinski [this message]
2014-10-06 20:12 ` [PATCH 1/2] fs: add freeze_super/thaw_super fs hooks Benjamin Marzinski
2014-10-07  9:26   ` Jan Kara
2014-10-06 20:12 ` [PATCH 2/2] gfs2: update freeze code to use freeze/thaw_super on all nodes Benjamin Marzinski

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=1412626329-16867-1-git-send-email-bmarzins@redhat.com \
    --to=bmarzins@redhat.com \
    --cc=jack@suse.cz \
    --cc=linux-fsdevel@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 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).