From: Salah Triki <salah.triki@gmail.com>
To: akpm@linux-foundation.org, viro@zeniv.linux.org.uk,
luisbg@osg.samsung.com
Cc: linux-kernel@vger.kernel.org, salah.triki@gmail.com
Subject: [PATCH 2/3] fs: befs: check flags field to validate the superblock state
Date: Tue, 9 Aug 2016 13:32:55 +0100 [thread overview]
Message-ID: <03eea80e0188d9cab423cf517659280afd04d7b2.1470745951.git.salah.triki@gmail.com> (raw)
In-Reply-To: <9f647c2c2067379143fe85dfcb94842dbed0a97e.1470745951.git.salah.triki@gmail.com>
In-Reply-To: <9f647c2c2067379143fe85dfcb94842dbed0a97e.1470745951.git.salah.triki@gmail.com>
flags field records the superblock state, so check if it is equal to
BEFS_DIRTY.
Signed-off-by: Salah Triki <salah.triki@gmail.com>
---
fs/befs/super.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/fs/befs/super.c b/fs/befs/super.c
index 5ab75e8..79be409 100644
--- a/fs/befs/super.c
+++ b/fs/befs/super.c
@@ -103,7 +103,7 @@ befs_check_sb(struct super_block *sb)
return BEFS_ERR;
}
- if (befs_sb->log_start != befs_sb->log_end) {
+ if (befs_sb->log_start != befs_sb->log_end || befs_sb->flags == BEFS_DIRTY) {
befs_error(sb, "Filesystem not clean! There are blocks in the "
"journal. You must boot into BeOS and mount this volume "
"to make it clean.");
--
1.9.1
next prev parent reply other threads:[~2016-08-09 12:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-09 12:32 [PATCH 1/3] fs: befs: load flags field from disk Salah Triki
2016-08-09 12:32 ` Salah Triki [this message]
2016-08-09 12:40 ` [PATCH 2/3] fs: befs: check flags field to validate the superblock state Luis de Bethencourt
2016-08-09 12:59 ` Salah Triki
2016-08-09 13:50 ` Luis de Bethencourt
2016-08-09 12:32 ` [PATCH 3/3] fs: befs: fix typo in befs_sb_info Salah Triki
2016-08-09 12:46 ` Luis de Bethencourt
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=03eea80e0188d9cab423cf517659280afd04d7b2.1470745951.git.salah.triki@gmail.com \
--to=salah.triki@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luisbg@osg.samsung.com \
--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
all inboxes | Powered by JetHome®