From: Oleg Nesterov <oleg@redhat.com>
To: Al Viro <viro@zeniv.linux.org.uk>,
Dave Chinner <david@fromorbit.com>,
Dave Hansen <dave.hansen@linux.intel.com>,
Jan Kara <jack@suse.cz>
Cc: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH 0/4] sb_write: lockdep fixes/cleanups
Date: Mon, 20 Jul 2015 19:00:44 +0200 [thread overview]
Message-ID: <20150720170044.GA3868@redhat.com> (raw)
So this is the preparation for percpu_rw_semaphore conversion. But let
me repeat, imo these changes make sense in any case, so I'd like to send
them separately.
2/4 fixes 2 bugs and cleanups the "trylock" hack. Although this hack can
be probably removed, see the changelog.
3/4 and 4/4 try to make the lockdep annotations more consistent. If we
want to use lockdep we should not hide the "write" locks we hold when we
call freeze_fs(sb) and unfreeze_fs(sb).
Please review.
Oleg.
fs/btrfs/transaction.c | 8 +---
fs/super.c | 101 +++++++++++++++++++++++++++++------------------
fs/xfs/xfs_aops.c | 6 +--
include/linux/fs.h | 5 ++
4 files changed, 71 insertions(+), 49 deletions(-)
next reply other threads:[~2015-07-20 17:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-20 17:00 Oleg Nesterov [this message]
2015-07-20 17:01 ` [PATCH 1/4] introduce __sb_{acquire,release}_write() helpers Oleg Nesterov
2015-07-21 8:23 ` Jan Kara
2015-07-20 17:01 ` [PATCH 2/4] fix the broken lockdep logic in __sb_start_write() Oleg Nesterov
2015-07-21 8:38 ` Jan Kara
2015-07-22 21:13 ` Oleg Nesterov
2015-07-20 17:01 ` [PATCH 3/4] move rwsem_release() from sb_wait_write() to freeze_super() Oleg Nesterov
2015-07-21 8:40 ` Jan Kara
2015-07-20 17:01 ` [PATCH 4/4] change thaw_super() to re-acquire s_writers.lock_map Oleg Nesterov
2015-07-21 8:48 ` Jan Kara
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=20150720170044.GA3868@redhat.com \
--to=oleg@redhat.com \
--cc=dave.hansen@linux.intel.com \
--cc=david@fromorbit.com \
--cc=jack@suse.cz \
--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;
as well as URLs for NNTP newsgroup(s).