[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#839590: marked as done (Bus error when accessing MBR partition records)

Your message dated Wed, 31 Jul 2019 07:04:32 -0700
with message-id <CAFHYt573FKqjZNG4Q_4p0CsKTJjOhL822wT+Bdc-U9+SG=V31g@mail.gmail.com>
and subject line Fixed in recent versions in Debian
has caused the Debian Bug report #839590,
regarding Bus error when accessing MBR partition records
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
839590: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=839590
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: mdadm
Version: 3.4-4
Tags: patch
Control: -1 forwarded http://marc.info/?l=linux-raid&m=147515212602202
X-Debbugs-Cc: debian-sparc@lists.debian.org
User: debian-sparc@lists.debian.org
Usertags: sparc64

Hi,
When mdadm tries to examine MBR partition records (such as when creating
an array using already-formatted disks), it does so with an unaligned
pointer, which leads to a bus error (SIGBUS) on sparc64. Please see the
patch I have submitted upstream, which makes sure the accesses always go
through boot_sect, since it is of type `struct MBR', which is the packed
containing struct, and so the compiler will generate the correct code to
perform the unaligned accesses when needed.

Regards,
James

Attachment: signature.asc
Description: PGP signature


--- End Message ---
--- Begin Message --- 
Hi,

Upstream adopted your patch with commit 8e2bca51 in October 2016. The
fix entered Debian with mdadm version 4.0 in June 2017.

https://git.kernel.org/pub/scm/utils/mdadm/mdadm.git/commit/?id=8e2bca513efc5deccb11cb90bad3c0891c4929e3

This bug was fixed upstream, and the fix is in Debian. Closing.

Kind regards,
Felix Lechner

--- End Message ---
Reply to: