From: andy@aeruder.net (Andrew Ruder)
To: linux-arm-kernel@lists.infradead.org
Subject: [BUG] reproducable ubifs reboot assert and corruption
Date: Wed, 29 Jan 2014 09:39:28 -0600 [thread overview]
Message-ID: <20140129153928.GA7278@gmail.com> (raw)
In-Reply-To: <52E8AB0F.2090905@nod.at>
On Wed, Jan 29, 2014 at 08:17:35AM +0100, Richard Weinberger wrote:
> So you can trigger this by running fsstress on /mnt and then call
> mount -o remount,ro /mnt?
That's all it takes. I actually run the remount until it succeeds,
obviously with fsstress going in the background there is a pretty narrow
window where it needs to sneak in with a write between the start of the
sync_filesystem and before the remount check for writers (-EBUSY).
> Can you also trigger it on nandsim or mtdram?
Haven't tried, but I can. I just don't really have that great of
a development environment for doing this on a desktop machine.
> I did a quick test on my testbed using mtdram and was unable to trigger it.
> But I fear my box is too fast.
I think there is definitely a speed component of my 416 MHz PXA 270 that
makes this pretty easy to hit. What if you did something like (changing
the ubiattach and mount lines obviously)?
I'll see if I can do this in a qemu, but it might take me a while to get
that setup.
- Andy
next prev parent reply other threads:[~2014-01-29 15:39 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20140122051510.GB17284@gmail.com>
2014-01-24 13:31 ` [BUG] reproducable ubifs reboot assert and corruption Andrew Ruder
[not found] ` <CAFLxGvwmzftdQKSjjjwpFLS8g3EJqMrQ2gU2scBsh2MvG7Wyyw@mail.gmail.com>
2014-01-27 16:39 ` Andrew Ruder
2014-01-29 5:32 ` Andrew Ruder
2014-01-29 7:17 ` Richard Weinberger
2014-01-29 15:39 ` Andrew Ruder [this message]
2014-01-29 7:30 ` Richard Weinberger
2014-01-29 15:46 ` Andrew Ruder
2014-01-29 15:56 ` Richard Weinberger
2014-01-29 19:13 ` Andrew Ruder
2014-01-29 19:56 ` Richard Weinberger
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=20140129153928.GA7278@gmail.com \
--to=andy@aeruder.net \
--cc=linux-arm-kernel@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).