From: David Sterba <dsterba@suse.cz>
To: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>
Cc: Anatoly Pugachev <matorola@gmail.com>,
debian-sparc <debian-sparc@lists.debian.org>,
Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: [sparc64] mkfs.btrfs bus error / align issue?
Date: Thu, 28 Jul 2016 20:04:13 +0200 [thread overview]
Message-ID: <20160728180413.GY30795@suse.cz> (raw)
In-Reply-To: <b2ac0d76-f2e3-81d7-0ab1-35960426d412@physik.fu-berlin.de>
On Thu, Jul 28, 2016 at 04:28:41PM +0200, John Paul Adrian Glaubitz wrote:
> On 07/28/2016 04:25 PM, John Paul Adrian Glaubitz wrote:
> > On 07/28/2016 04:01 PM, Anatoly Pugachev wrote:
> >> Program received signal SIGBUS, Bus error.
> >> 0x0000000000177dfc in raid6_gen_syndrome (disks=4, bytes=65536,
> >> ptrs=0x2c4510) at raid6.c:87
> >> 87 wq0 = wp0 = *(unative_t *)&dptr[z0][d+0*NSIZE];
> >
> > That should be easy to fix. Just make the R values aligned with the
> > appropriate get_aligned functions, see David's previous commit [1]:
>
> Argh, those are called get_UNaligned_*, not get_aligned_*.
>
> > There are more lines in raid6.c which need the same fix, basically everything
> > with * (unative_t *).
>
> Oh, and you will somehow need to guard this with #if BITS_PER_LONG == 64 ...
> #else ... #endif respectively since you need to use different versions
> (64 vs. 32) of get_unaligned_* depending on the size of unative_t.
And I've fixed it that way, now pushed to devel ("btrfs-progs: fix
unaligned access in raid6 calculations" [1]). Would be great if you or
Anatoly can test it so I can add it to the 4.7 release (ETA tomorrow).
[1] https://github.com/kdave/btrfs-progs/commit/44b35e94facf820d2c2d8e1be631bf40d68dff8d
next prev parent reply other threads:[~2016-07-28 18:04 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-27 13:59 [sparc64] mkfs.btrfs bus error / align issue? Anatoly Pugachev
2016-07-27 19:56 ` David Sterba
2016-07-28 9:44 ` David Sterba
2016-07-28 11:58 ` Anatoly Pugachev
2016-07-28 12:02 ` John Paul Adrian Glaubitz
2016-07-28 12:09 ` John Paul Adrian Glaubitz
2016-07-28 12:24 ` David Sterba
2016-07-28 14:01 ` Anatoly Pugachev
2016-07-28 14:25 ` John Paul Adrian Glaubitz
2016-07-28 14:28 ` John Paul Adrian Glaubitz
2016-07-28 14:32 ` Patrick Baggett
2016-07-28 18:04 ` David Sterba [this message]
2016-07-28 20:34 ` Anatoly Pugachev
2016-07-29 9:40 ` Anatoly Pugachev
2016-07-29 12:41 ` David Sterba
2016-07-29 15:03 ` Anatoly Pugachev
2016-07-29 10:20 ` John Paul Adrian Glaubitz
2016-07-27 20:39 ` Patrick Baggett
2016-07-27 20:41 ` Patrick Baggett
2016-07-27 20:40 ` John Paul Adrian Glaubitz
2016-07-27 20:48 ` Patrick Baggett
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=20160728180413.GY30795@suse.cz \
--to=dsterba@suse.cz \
--cc=debian-sparc@lists.debian.org \
--cc=glaubitz@physik.fu-berlin.de \
--cc=linux-btrfs@vger.kernel.org \
--cc=matorola@gmail.com \
/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.