From: Andrew Ruder <andy@aeruder.net>
To: linux-mtd@lists.infradead.org
Subject: Re: [HACK] fs/super.c: sync ro remount after blocking writers
Date: Mon, 3 Mar 2014 15:12:05 -0600 [thread overview]
Message-ID: <20140303211205.GA7311@gmail.com> (raw)
In-Reply-To: <53105604.4050501@nod.at>
On Fri, Feb 28, 2014 at 10:25:24AM +0100, Richard Weinberger wrote:
> Is it possible to create such a test case? I don't know whether it is
> possible to trigger the issue on a regular filesystem. But as hch
> noted, it would be nice to have. :)
I've given this some thought after initially receiving the email and it
would not be easily recreated. As best as I can tell, the test case
would be something along the line of:
1. # Start up a filesystem writer
2. mount -o remount,ro /testfilesystem
3. # Immediately mark block device as read only
4. # Reboot, show that the filesystem is dirty next time around.
Step 3 I'm not sure how to do, Step 4 makes for the world's most painful
test case. The thread from Leon Pollak is probably the easiest way to
recreate these issues (remount,ro followed by a hardware-enabled
read-only) and I'm just not sure it belongs in a test case.
- Andy
prev parent reply other threads:[~2014-03-03 21:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-30 15:26 [HACK] fs/super.c: sync ro remount after blocking writers Andrew Ruder
2014-01-30 15:26 ` Andrew Ruder
2014-01-31 8:20 ` Richard Weinberger
2014-01-31 8:20 ` Richard Weinberger
2014-02-03 10:23 ` Christoph Hellwig
2014-02-03 10:23 ` Christoph Hellwig
2014-02-28 9:25 ` Richard Weinberger
2014-02-28 9:25 ` Richard Weinberger
2014-03-03 21:12 ` Andrew Ruder [this message]
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=20140303211205.GA7311@gmail.com \
--to=andy@aeruder.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.