From: ZhangJieJing <kzjeef@gmail.com>
To: linux-mtd@lists.infradead.org
Cc: linux-fsdevel@vger.kernel.org, Artem Bityutskiy <dedekind1@gmail.com>
Subject: [PATCH] ubifs: add update vfs super block infomation when remount to ro mode
Date: Fri, 16 Apr 2010 11:36:50 +0800 [thread overview]
Message-ID: <i2ncf7b913c1004152036t3b23af53h339b16092ecdd812@mail.gmail.com> (raw)
If some read/write error happens(eg.CRC error), ubifs make self a read
only mode,
but the vfs infomation still not update.
This patch add this also make /proc/mounts update.
Signed-off-by: Zhang Jiejing <kzjeef@gmail.com>
---
fs/ubifs/io.c | 1 +
1 files changed, 1 insertions(+), 0 deletions(-)
diff --git a/fs/ubifs/io.c b/fs/ubifs/io.c
index 0168271..d33c233 100644
--- a/fs/ubifs/io.c
+++ b/fs/ubifs/io.c
@@ -63,6 +63,7 @@ void ubifs_ro_mode(struct ubifs_info *c, int err)
if (!c->ro_media) {
c->ro_media = 1;
c->no_chk_data_crc = 0;
+ c->vfs_sb->s_flags |= MS_RDONLY;
ubifs_warn("switched to read-only mode, error %d", err);
dbg_dump_stack();
}
--
1.6.3.3
--
To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next reply other threads:[~2010-04-16 3:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-16 3:36 ZhangJieJing [this message]
2010-04-16 19:10 ` [PATCH] ubifs: add update vfs super block infomation when remount to ro mode Artem Bityutskiy
2010-04-28 7:24 ` Artem Bityutskiy
2010-04-29 2:14 ` Zhang JieJing
2010-04-29 3:46 ` Artem Bityutskiy
2010-04-29 6:36 ` Zhang JieJing
2010-04-29 6:44 ` Artem Bityutskiy
2010-04-29 6:38 ` Zhang JieJing
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=i2ncf7b913c1004152036t3b23af53h339b16092ecdd812@mail.gmail.com \
--to=kzjeef@gmail.com \
--cc=dedekind1@gmail.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.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).