From: Vyacheslav Dubeyko <slava@dubeyko.com>
To: "Timo Schlüßler" <timo@schluessler.org>
Cc: linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH 2/2] HFS: clear dirty flags on remount read-only
Date: Sun, 29 Nov 2015 15:03:36 -0800 [thread overview]
Message-ID: <1448838216.4582.12.camel@ubuntu-slavad-14.04> (raw)
In-Reply-To: <565B12E5.3090600@schluessler.org>
Hi Timo,
On Sun, 2015-11-29 at 15:59 +0100, Timo Schlüßler wrote:
> Remounting a HFS filesystem read-only doesn't clear the "DIRTY"-flags (not
> HFS_SB_ATTRIB_UNMNT and HFS_SB_ATTRIB_INCNSTNT) correctly. Subsequent
> mounts then report a dirty filesystem and enforce a check before willing to
> mount it read-write again.
> Signed-off-by: Timo Schlüßler <timo@schluessler.org>
> ---
>
> --- linux/fs/hfs/super.c.orig 2015-11-29 14:42:22.000000000 +0100
> +++ linux/fs/hfs/super.c 2015-11-29 15:22:03.000000000 +0100
> @@ -113,11 +113,13 @@ static int hfs_statfs(struct dentry *den
>
> static int hfs_remount(struct super_block *sb, int *flags, char *data)
> {
> - sync_filesystem(sb);
I think that this is the right placement for sync_filesystem() call.
It's much better to have such call in one place. Anyway, you need to set
HFS_SB_ATTRIB_UNMNT and to clear HFS_SB_ATTRIB_INCNSTNT for remount from
READ-WRITE to READ-ONLY state. And vou need to do opposite operation for
remount from READ-ONLY to READ-WRITE state. So, it's much better ti
leave sync_filesystem() call in the same place but to add additional
logic before this call.
Thanks,
Vyacheslav Dubeyko.
> *flags |= MS_NODIRATIME;
> - if ((*flags & MS_RDONLY) == (sb->s_flags & MS_RDONLY))
> + if ((*flags & MS_RDONLY) == (sb->s_flags & MS_RDONLY)) {
> + sync_filesystem(sb);
> return 0;
> + }
> if (!(*flags & MS_RDONLY)) {
> + sync_filesystem(sb);
> if (!(HFS_SB(sb)->mdb->drAtrb & cpu_to_be16(HFS_SB_ATTRIB_UNMNT))) {
> pr_warn("filesystem was not cleanly unmounted, running fsck.hfs is recommended. leaving read-only.\n");
> sb->s_flags |= MS_RDONLY;
> @@ -127,6 +129,9 @@ static int hfs_remount(struct super_bloc
> sb->s_flags |= MS_RDONLY;
> *flags |= MS_RDONLY;
> }
> + } else {
> + hfs_mdb_close(sb);
> + sync_filesystem(sb);
> }
> return 0;
> }
>
>
> --
> 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 prev parent reply other threads:[~2015-11-29 23:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-29 14:59 [PATCH 2/2] HFS: clear dirty flags on remount read-only Timo Schlüßler
2015-11-29 23:03 ` Vyacheslav Dubeyko [this message]
2015-12-03 18:42 ` Timo Schlüßler
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=1448838216.4582.12.camel@ubuntu-slavad-14.04 \
--to=slava@dubeyko.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=timo@schluessler.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).