From: hooanon05@yahoo.co.jp
To: Al Viro <viro@ZenIV.linux.org.uk>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
linux-kernel@vger.kernel.org
Subject: Re: [git pull] vfs patches, part 1
Date: Wed, 17 Jun 2009 01:19:09 +0900 [thread overview]
Message-ID: <11056.1245169149@jrobl> (raw)
In-Reply-To: <20090612014507.GA8633@ZenIV.linux.org.uk>
Al Viro:
> * more pushing of lock_super() and BKL down into fs (by now only ->get_sb()
> has the latter held by caller and nothing in VFS touches the former) (me,
> hch, Alessio Igor Bogani)
:::
> Al Viro (36):
:::
> Push BKL down into do_remount_sb()
:::
> Alessio Igor Bogani (1):
> Push BKL down into ->remount_fs()
These two patches conflict, or are unmatched.
Al's patch adds one lock_kernel() call and several unlock_kernel() into
do_remount_sb(), and then Alessio's patch removes only single pair of
lock/unlock_kernel().
Finally a few unlock_kernel() are left in do_remount_sb().
I guess Alessio's base was different from Al's.
J. R. Okajima
commit 8219ce0904f57cd0893092369fbde39471cfb5a7
Author: J. R. Okajima <hooanon05@yahoo.co.jp>
Date: Wed Jun 17 01:16:50 2009 +0900
remove unlock_kernel() left accidentally
commit 337eb00a2c3a421999c39c94ce7e33545ee8baa7
Push BKL down into ->remount_fs()
and
commit 4aa98cf768b6f2ea4b204620d949a665959214f6
Push BKL down into do_remount_sb()
were uncorrectly merged.
The former removes one pair of lock/unlock_kernel(), but the latter adds
several unlock_kernel(). Finally a few unlock_kernel() calls left.
Signed-off-by: J. R. Okajima <hooanon05@yahoo.co.jp>
diff --git a/fs/super.c b/fs/super.c
index 83b4741..d40d53a 100644
--- a/fs/super.c
+++ b/fs/super.c
@@ -545,24 +545,18 @@ int do_remount_sb(struct super_block *sb, int flags, void *data, int force)
if ((flags & MS_RDONLY) && !(sb->s_flags & MS_RDONLY)) {
if (force)
mark_files_ro(sb);
- else if (!fs_may_remount_ro(sb)) {
- unlock_kernel();
+ else if (!fs_may_remount_ro(sb))
return -EBUSY;
- }
retval = vfs_dq_off(sb, 1);
- if (retval < 0 && retval != -ENOSYS) {
- unlock_kernel();
+ if (retval < 0 && retval != -ENOSYS)
return -EBUSY;
- }
}
remount_rw = !(flags & MS_RDONLY) && (sb->s_flags & MS_RDONLY);
if (sb->s_op->remount_fs) {
retval = sb->s_op->remount_fs(sb, &flags, data);
- if (retval) {
- unlock_kernel();
+ if (retval)
return retval;
- }
}
sb->s_flags = (sb->s_flags & ~MS_RMT_MASK) | (flags & MS_RMT_MASK);
if (remount_rw)
next prev parent reply other threads:[~2009-06-16 16:19 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-12 1:45 [git pull] vfs patches, part 1 Al Viro
2009-06-12 3:13 ` Linus Torvalds
2009-06-12 3:38 ` Al Viro
2009-06-16 16:19 ` hooanon05 [this message]
2009-06-16 17:31 ` Al Viro
2009-06-18 14:30 ` hooanon05
2009-06-20 0:29 ` Linus Torvalds
-- strict thread matches above, loose matches on Subject: below --
2008-12-31 7:43 Al Viro
2008-12-31 17:21 ` Linus Torvalds
2008-12-31 17:31 ` Linus Torvalds
2008-12-31 17:41 ` Linus Torvalds
2008-12-31 20:43 ` Junio C Hamano
2008-12-31 23:10 ` Al Viro
2009-01-01 0:05 ` Linus Torvalds
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=11056.1245169149@jrobl \
--to=hooanon05@yahoo.co.jp \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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