From: "Theodore Y. Ts'o" <tytso@mit.edu>
To: Jaegeuk Kim <jaegeuk@kernel.org>
Cc: linux-kernel@vger.kernel.org, Jaegeuk Kim <jaegeuk@google.com>,
Andreas Dilger <adilger.kernel@dilger.ca>,
linux-ext4@vger.kernel.org
Subject: Re: [PATCH v3] ext4: handle errors on ext4_commit_super
Date: Sun, 13 May 2018 23:46:52 -0400 [thread overview]
Message-ID: <20180514034652.GM14763@thunk.org> (raw)
In-Reply-To: <20180423144626.GA31757@jaegeuk-macbookpro.roam.corp.google.com>
On Mon, Apr 23, 2018 at 08:46:26AM -0600, Jaegeuk Kim wrote:
> When remounting ext4 from ro to rw, currently it allows its transition,
> even if ext4_commit_super() returns EIO. Even worse thing is, after that,
> fs/buffer complains buffer dirty bits like:
>
> Call trace:
> [<ffffff9750c259dc>] mark_buffer_dirty+0x184/0x1a4
> [<ffffff9750cb398c>] __ext4_handle_dirty_super+0x4c/0xfc
> [<ffffff9750c7a9fc>] ext4_file_open+0x154/0x1c0
> [<ffffff9750bea51c>] do_dentry_open+0x114/0x2d0
> [<ffffff9750bea75c>] vfs_open+0x5c/0x94
> [<ffffff9750bf879c>] path_openat+0x668/0xfe8
> [<ffffff9750bf8088>] do_filp_open+0x74/0x120
> [<ffffff9750beac98>] do_sys_open+0x148/0x254
> [<ffffff9750beade0>] SyS_openat+0x10/0x18
> [<ffffff9750a83ab0>] el0_svc_naked+0x24/0x28
> EXT4-fs (dm-1): previous I/O error to superblock detected
> Buffer I/O error on dev dm-1, logical block 0, lost sync page write
> EXT4-fs (dm-1): re-mounted. Opts: (null)
> Buffer I/O error on dev dm-1, logical block 80, lost async page write
>
> Cc: "Theodore Ts'o" <tytso@mit.edu>
> Cc: Andreas Dilger <adilger.kernel@dilger.ca>
> Cc: linux-ext4@vger.kernel.org
> Cc: Jaegeuk Kim <jaegeuk@kernel.org>
> Signed-off-by: Jaegeuk Kim <jaegeuk@google.com>
Applied with a fix up to ext4_fill_super() when it calls
ext4_setup_super() with the changed error return semantics.
- Ted
diff --git a/fs/ext4/super.c b/fs/ext4/super.c
index aac33c155363..1388e56bb3f5 100644
--- a/fs/ext4/super.c
+++ b/fs/ext4/super.c
@@ -4254,8 +4254,12 @@ static int ext4_fill_super(struct super_block *sb, void *data, int silent)
goto failed_mount4;
}
- if (ext4_setup_super(sb, es, sb_rdonly(sb)))
+ ret = ext4_setup_super(sb, es, sb_rdonly(sb));
+ if (ret == -EROFS) {
sb->s_flags |= SB_RDONLY;
+ ret = 0;
+ } else if (ret)
+ goto failed_mount4a;
/* determine the minimum size of new large inodes, if present */
if (sbi->s_inode_size > EXT4_GOOD_OLD_INODE_SIZE &&
prev parent reply other threads:[~2018-05-14 3:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-30 1:44 [PATCH] ext4: handle errors on ext4_commit_super Jaegeuk Kim
2018-04-19 15:18 ` Jan Kara
2018-04-19 15:58 ` Jaegeuk Kim
2018-04-19 15:59 ` [PATCH v2] " Jaegeuk Kim
2018-04-21 13:12 ` Jan Kara
2018-04-23 14:46 ` [PATCH v3] " Jaegeuk Kim
2018-05-14 3:46 ` Theodore Y. Ts'o [this message]
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=20180514034652.GM14763@thunk.org \
--to=tytso@mit.edu \
--cc=adilger.kernel@dilger.ca \
--cc=jaegeuk@google.com \
--cc=jaegeuk@kernel.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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).