From: "Luis R. Rodriguez" <mcgrof@kernel.org>
To: viro@zeniv.linux.org.uk, linux-fsdevel@vger.kernel.org
Cc: jack@suse.cz, bart.vanassche@wdc.com, ming.lei@redhat.com,
rjw@rjwysocki.net, mguzik@redhat.com, linux-pm@vger.kernel.org,
linux-block@vger.kernel.org, linux-kernel@vger.kernel.org,
"Luis R. Rodriguez" <mcgrof@kernel.org>
Subject: [PATCH 0/3] fs: minor fs thaw fixes and adjustments
Date: Fri, 20 Apr 2018 16:59:01 -0700 [thread overview]
Message-ID: <20180420235904.27496-1-mcgrof@kernel.org> (raw)
Here's a few minor fs thaw fixes and adjustments I ran accross
as I started to refresh my development for to use freeze_fs on
suspend/hibernation [0]. These are just prep commits for the real
work, I'm still reviewing feedback and adjusting the code for
that.
I've tested the patches with generic/085 on xfs and found no regressions.
Luis R. Rodriguez (3):
fs: move documentation for thaw_super() where appropriate
fs: make thaw_super_locked() really just a helper
fs: fix corner case race on freeze_bdev() when sb disappears
fs/block_dev.c | 4 +++-
fs/super.c | 39 ++++++++++++++++++++++++++-------------
2 files changed, 29 insertions(+), 14 deletions(-)
--
2.16.3
next reply other threads:[~2018-04-20 23:59 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-20 23:59 Luis R. Rodriguez [this message]
2018-04-20 23:59 ` [PATCH 1/3] fs: move documentation for thaw_super() where appropriate Luis R. Rodriguez
2018-04-21 0:01 ` Bart Van Assche
2018-04-21 0:01 ` Bart Van Assche
2018-04-21 0:07 ` Luis R. Rodriguez
2018-04-21 0:09 ` Randy Dunlap
2018-05-03 14:53 ` Jan Kara
2018-04-20 23:59 ` [PATCH 2/3] fs: make thaw_super_locked() really just a helper Luis R. Rodriguez
2018-05-03 15:07 ` Jan Kara
2018-04-20 23:59 ` [PATCH 3/3] fs: fix corner case race on freeze_bdev() when sb disappears Luis R. Rodriguez
2018-05-03 15:02 ` Jan Kara
2018-04-21 0:02 ` [PATCH 0/3] fs: minor fs thaw fixes and adjustments Luis R. Rodriguez
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=20180420235904.27496-1-mcgrof@kernel.org \
--to=mcgrof@kernel.org \
--cc=bart.vanassche@wdc.com \
--cc=jack@suse.cz \
--cc=linux-block@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=mguzik@redhat.com \
--cc=ming.lei@redhat.com \
--cc=rjw@rjwysocki.net \
--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 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.