linux-kernel - Re: [RFC PATCH 0/1] Wrong structure alignment due to compiler attribute "section"

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20150324120733.GA3579@e103592.cambridge.arm.com>
Date:	Tue, 24 Mar 2015 12:07:39 +0000
From:	Dave Martin <Dave.Martin@....com>
To:	Lino Sanfilippo <LinoSanfilippo@....de>
Cc:	Lino Sanfilippo <lsanfil@...vell.com>, linux@....linux.org.uk,
	linux-kernel@...r.kernel.org, linux-arm-kernel@...ts.infradead.org
Subject: Re: [RFC PATCH 0/1] Wrong structure alignment due to compiler
 attribute "section"

On Sun, Mar 22, 2015 at 01:56:10AM +0100, Lino Sanfilippo wrote:
> On 06.03.2015 19:20, Lino Sanfilippo wrote:
> > 
> >>>
> >> 
> >> Ok, I got a link to the source now. It can be found here:
> >> 
> >> http://tp-lab200/release/gcc/temp/internal/2010q4-113-4.4.5/marvell-gcc.src-2010q4-113.tar.bz2
> >> 
> > 
> > 
> > Sigh. Just realized that the url is not accessible. Will check that on
> > monday.
> > 
> > Lino
> > 
> 
> Hello Dave,
> 
> sorry for my late reply. But I was a few days out of office and had to
> contact some people which are not in my departement. The outcome is:
> there is no public repository in which the source code of that special
> (buggy) toolchain is available any more. There are newer versions
> already, but even for those the source code is only accessible for
> customers (thats what I was told). However the responsible developer

(GPL?)

> could confirm that the wrong alignment I initially reported is indeed a
> bug in the toolchain which now is fixed in the newer versions.
> I really would have liked to send you the source, but unfortunately I
> cant. However thanks again for all your help.

Never mind -- hopefully this issue was caused by something that got
fixed upstream meanwhile, or that never went upstream in the first
place.  Debugging legacy vendor toolchain forks isn't a very interesting
pursuit...

We can revisit the issue if it comes up again, but I've not heard
of any other instances of this type of issue so far.

Cheers
---Dave

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/