From: Daeho Jeong <daeho.jeong@samsung.com>
To: "tytso@mit.edu" <tytso@mit.edu>,
"linux-ext4@vger.kernel.org" <linux-ext4@vger.kernel.org>
Cc: "daehojng@gmail.com" <daehojng@gmail.com>, 정대호 <daeho.jeong@samsung.com>
Subject: [PATCH] ext4, jbd2: ensure entering into panic after recording an error in JBD2 superblock
Date: Mon, 10 Aug 2015 05:44:49 +0000 (GMT) [thread overview]
Message-ID: <302309021.645571439185489165.JavaMail.weblogic@epmlwas07d> (raw)
If a EXT4 filesystem utilizes JBD2 journaling and an error occurs, the journaling
will be aborted first and the error number will be recorded into JBD2 superblock
and, finally, the system will enter into the panic state in "errors=panic" option.
But, in the rare case, this sequence is little twisted like the below figure and
it will happen that the system enters into panic state, which means the system
reset in mobile environment, before completion of recording an error in the
journal superblock. In this case, e2fsck cannot recognize that the filesystem
failure occured in the previous run and the corruption wouldn't be fixed.
Task A Task B
ext4_handle_error()
-> jbd2_journal_abort()
-> __journal_abort_soft()
-> __jbd2_journal_abort_hard()
| -> journal->j_flags |= JBD2_ABORT;
| __ext4_abort()
| -> jbd2_journal_abort()
| | -> __journal_abort_soft()
| | -> if (journal->j_flags & JBD2_ABORT)
| | return;
| -> panic()
-> jbd2_journal_update_sb_errno()
Tested-by: Hobin Woo <hobin.woo@samsung.com>
Signed-off-by: Daeho Jeong <daeho.jeong@samsung.com>
Signed-off-by: Youngjin Gil <youngjin.gil@samsung.com>
---
fs/jbd2/journal.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/fs/jbd2/journal.c b/fs/jbd2/journal.c
index b96bd80..b265fd8 100644
--- a/fs/jbd2/journal.c
+++ b/fs/jbd2/journal.c
@@ -2051,10 +2051,10 @@ static void __journal_abort_soft (journal_t *journal, int errno)
if (!journal->j_errno)
journal->j_errno = errno;
- __jbd2_journal_abort_hard(journal);
-
if (errno)
jbd2_journal_update_sb_errno(journal);
+
+ __jbd2_journal_abort_hard(journal);
}
/**
next reply other threads:[~2015-08-10 5:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-10 5:44 Daeho Jeong [this message]
2015-08-15 15:20 ` [PATCH] ext4, jbd2: ensure entering into panic after recording an error in JBD2 superblock Theodore Ts'o
2015-08-15 18:05 ` Theodore Ts'o
-- strict thread matches above, loose matches on Subject: below --
2015-08-16 6:33 Daeho Jeong
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=302309021.645571439185489165.JavaMail.weblogic@epmlwas07d \
--to=daeho.jeong@samsung.com \
--cc=daehojng@gmail.com \
--cc=linux-ext4@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).