From: Christoph Hellwig <hch@lst.de>
To: axboe@kernel.dk
Cc: viro@zeniv.linux.org.uk, linux-fsdevel@vger.kernel.org
Subject: [PATCH] writeback: fix pin_sb_for_writeback
Date: Wed, 9 Jun 2010 15:31:01 +0200 [thread overview]
Message-ID: <20100609133101.GA25876@lst.de> (raw)
We need to check for s_instances to make sure we don't bother working
against a filesystem that is beeing unmounted, and we need to call
put_super to make sure a superblock is freed when we race against
umount. Also no need to keep sb_lock after we got a reference on it.
Signed-off-by: Christoph Hellwig <hch@lst.de>
---
Note: this is against Jens' tree with the writeback changes applied.
The logic in mainline is the same, but the context is slightl different.
Index: linux-2.6/fs/fs-writeback.c
===================================================================
--- linux-2.6.orig/fs/fs-writeback.c 2010-06-09 13:15:29.152004893 +0200
+++ linux-2.6/fs/fs-writeback.c 2010-06-09 13:15:29.946253462 +0200
@@ -534,19 +534,21 @@ select_queue:
static bool pin_sb_for_writeback(struct super_block *sb)
{
spin_lock(&sb_lock);
+ if (list_empty(&sb->s_instances)) {
+ spin_unlock(&sb_lock);
+ return false;
+ }
+
sb->s_count++;
+ spin_unlock(&sb_lock);
+
if (down_read_trylock(&sb->s_umount)) {
- if (sb->s_root) {
- spin_unlock(&sb_lock);
+ if (sb->s_root)
return true;
- }
- /*
- * umounted, drop rwsem again and fall through to failure
- */
up_read(&sb->s_umount);
}
- sb->s_count--;
- spin_unlock(&sb_lock);
+
+ put_super(sb);
return false;
}
reply other threads:[~2010-06-09 13:31 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20100609133101.GA25876@lst.de \
--to=hch@lst.de \
--cc=axboe@kernel.dk \
--cc=linux-fsdevel@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).