From: Daeho Jeong <daeho.jeong@samsung.com>
To: Jan Kara <jack@suse.cz>
Cc: "tytso@mit.edu" <tytso@mit.edu>,
"linux-ext4@vger.kernel.org" <linux-ext4@vger.kernel.org>,
정대호 <daeho.jeong@samsung.com>, 이기태 <kitae87.lee@samsung.com>
Subject: Re: [PATCH] ext4: guarantee already started handles to successfully finish while ro remounting
Date: Fri, 06 May 2016 05:35:56 +0000 (GMT) [thread overview]
Message-ID: <1656879517.452811462512954933.JavaMail.weblogic@ep2mlwas08c> (raw)
> So can you share a reproducer for this issue? Because my initial thinking
> is that checks during remount should fail the remount with EBUSY if there
> is any modification outstanding... If they don't we have a racy remount and
> fs-freezing code, which is a bug.
Hi Jan,
Sorry to make you confused. My patch description was little wrong.
I meant only the emergency read-only remount case, not the normal read-only
remount case. Android is currently using emergency ro remount for the device
shutdown procedure.
We can easily reproduce this problem, but we didn't make a TC for xfstest yet.
If we did that, I will let you know.
next reply other threads:[~2016-05-06 5:35 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-06 5:35 Daeho Jeong [this message]
-- strict thread matches above, loose matches on Subject: below --
2016-05-07 13:05 [PATCH] ext4: guarantee already started handles to successfully finish while ro remounting Daeho Jeong
2016-05-07 17:47 ` Theodore Ts'o
2016-05-06 6:01 Daeho Jeong
2016-05-06 13:00 ` Theodore Ts'o
2016-05-06 20:01 ` Andreas Dilger
2016-05-06 23:36 ` tytso
2016-05-09 8:40 ` Jan Kara
2016-05-02 0:50 Daeho Jeong
2016-05-05 13:45 ` Jan Kara
2016-05-05 15:44 ` Theodore Ts'o
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=1656879517.452811462512954933.JavaMail.weblogic@ep2mlwas08c \
--to=daeho.jeong@samsung.com \
--cc=jack@suse.cz \
--cc=kitae87.lee@samsung.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).