From: Jan Blunck <jblunck@suse.de>
To: Jan Kara <jack@suse.cz>, tytso@mit.edu
Cc: Linux-Kernel Mailinglist <linux-kernel@vger.kernel.org>,
linux-ext4@vger.kernel.org,
Frederic Weisbecker <fweisbec@gmail.com>,
Arnd Bergmann <arnd@arndb.de>, Jan Blunck <jblunck@suse.de>
Subject: [PATCH 1/5] ext2: Use ext2_clear_super_error() in ext2_sync_fs()
Date: Mon, 12 Apr 2010 22:41:41 +0200 [thread overview]
Message-ID: <1271104905-8804-2-git-send-email-jblunck@suse.de> (raw)
In-Reply-To: <1271104905-8804-1-git-send-email-jblunck@suse.de>
ext2_sync_fs() used to duplicate the code from ext2_clear_super_error().
Signed-off-by: Jan Blunck <jblunck@suse.de>
---
fs/ext2/super.c | 19 +++----------------
1 files changed, 3 insertions(+), 16 deletions(-)
diff --git a/fs/ext2/super.c b/fs/ext2/super.c
index 42e4a30..dbebbf0 100644
--- a/fs/ext2/super.c
+++ b/fs/ext2/super.c
@@ -1120,8 +1120,8 @@ static void ext2_clear_super_error(struct super_block *sb)
* be remapped. Nothing we can do but to retry the
* write and hope for the best.
*/
- printk(KERN_ERR "EXT2-fs: %s previous I/O error to "
- "superblock detected", sb->s_id);
+ ext2_msg(sb, KERN_ERR,
+ "previous I/O error to superblock detected\n");
clear_buffer_write_io_error(sbh);
set_buffer_uptodate(sbh);
}
@@ -1164,20 +1164,7 @@ static int ext2_sync_fs(struct super_block *sb, int wait)
struct buffer_head *sbh = EXT2_SB(sb)->s_sbh;
lock_kernel();
- if (buffer_write_io_error(sbh)) {
- /*
- * Oh, dear. A previous attempt to write the
- * superblock failed. This could happen because the
- * USB device was yanked out. Or it could happen to
- * be a transient write error and maybe the block will
- * be remapped. Nothing we can do but to retry the
- * write and hope for the best.
- */
- ext2_msg(sb, KERN_ERR,
- "previous I/O error to superblock detected\n");
- clear_buffer_write_io_error(sbh);
- set_buffer_uptodate(sbh);
- }
+ ext2_clear_super_error(sb);
if (es->s_state & cpu_to_le16(EXT2_VALID_FS)) {
ext2_debug("setting valid to 0\n");
--
1.6.4.2
next prev parent reply other threads:[~2010-04-12 20:42 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-12 20:41 [PATCH 0/5] ext2: Preparation to remove BKL Jan Blunck
2010-04-12 20:41 ` Jan Blunck [this message]
2010-04-12 20:41 ` [PATCH 2/5] ext2: Set the write time in ext2_sync_fs() Jan Blunck
2010-04-12 20:41 ` [PATCH 3/5] ext2: Remove duplicate code from ext2_sync_fs() Jan Blunck
2010-04-12 20:41 ` [PATCH 4/5] ext2: Move ext2_write_super() out of ext2_setup_super() Jan Blunck
2010-04-13 17:53 ` Jan Kara
2010-04-14 7:55 ` Jan Blunck
2010-04-12 20:41 ` [PATCH 5/5] ext2: Add ext2_sb_info s_lock spinlock Jan Blunck
2010-04-13 19:09 ` Jan Kara
2010-04-14 8:19 ` Jan Blunck
2010-04-14 7:10 ` Jaswinder Singh Rajput
2010-04-14 8:00 ` Jan Blunck
2010-04-12 21:01 ` [PATCH 0/5] ext2: Preparation to remove BKL Frederic Weisbecker
2010-04-13 9:31 ` Arnd Bergmann
2010-04-13 20:12 ` Frederic Weisbecker
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=1271104905-8804-2-git-send-email-jblunck@suse.de \
--to=jblunck@suse.de \
--cc=arnd@arndb.de \
--cc=fweisbec@gmail.com \
--cc=jack@suse.cz \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tytso@mit.edu \
/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).