From: viric@viric.name (Lluís Batlle i Rossell)
To: linux-arm-kernel@lists.infradead.org
Subject: Bad traps for unaligned access in STM instruction
Date: Tue, 18 Sep 2012 17:46:27 +0200 [thread overview]
Message-ID: <20120918154627.GD8632@vicerveza.homeunix.net> (raw)
In-Reply-To: <alpine.LFD.2.02.1209181140450.28681@xanadu.home>
On Tue, Sep 18, 2012 at 11:44:02AM -0400, Nicolas Pitre wrote:
> On Tue, 18 Sep 2012, Llu?s Batlle i Rossell wrote:
>
> > In an ideal userland software world, the counters of the traps would be zero.
> > But they are not. And without fixup, the mkfs.btrfs fails to run properly, and
> > creates a broken filesystem that crashes the kernel.
>
> If a broken btrfs filesystem crashes the kernel, you should definitively
> report it as a bug to the btrfs developers. Filesystem code must be
> immune to any kind of corruptions and gracefully cope with them.
Yes I know; I did report that.
Thank you
next prev parent reply other threads:[~2012-09-18 15:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-15 10:46 Bad traps for unaligned access in STM instruction Lluís Batlle i Rossell
2012-09-15 10:51 ` Lluís Batlle i Rossell
2012-09-18 15:25 ` Dave Martin
2012-09-18 15:31 ` Lluís Batlle i Rossell
2012-09-18 15:44 ` Nicolas Pitre
2012-09-18 15:46 ` Lluís Batlle i Rossell [this message]
2012-09-18 19:07 ` Dave Martin
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=20120918154627.GD8632@vicerveza.homeunix.net \
--to=viric@viric.name \
--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).