linux-kernel - Re: R_SPARC

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <4D34ECBC.2030304@oldelvet.org.uk>
Date:	Tue, 18 Jan 2011 01:28:28 +0000
From:	Richard Mortimer <richm@...elvet.org.uk>
To:	David Miller <davem@...emloft.net>
CC:	609371@...s.debian.org, ben@...adent.org.uk,
	sparclinux@...r.kernel.org, linux-kernel@...r.kernel.org,
	rostedt@...dmis.org, fweisbec@...il.com, mingo@...hat.com,
	Jesper.Nilsson@...s.com, jeffm@...e.com
Subject: Re: R_SPARC_13



On 18/01/2011 00:37, David Miller wrote:
> From: Richard Mortimer<richm@...elvet.org.uk>
> Date: Mon, 17 Jan 2011 23:34:03 +0000
>
>> I guess that points towards the binutils linker not doing the correct
>> thing.
>
> Ok, it is in fact doing the correct thing.
>
> I'm really surprised we never hit this before in all of these years
> :-) I guess we've simply never hit this kind of expression in a module
> before.
>
> The issue is that modules aren't a "final link", it's really more like
> an intermediate partial link.
>
> So we do end up seeing the R_SPARC_LO10 + R_SPARC_13 sequences in the
> final module object.
>
> Therefore, we really should handle R_SPARC_13 in the sparc module loader.
>
> Richard, I want you to get full credit for this since you did all of
> the dirty work :-) Would you please cons up a formal patch with commit
> message and signoff for this and I'll push it around?
>
> Thanks a lot!

Will do tomorrow. I'll dust off my git tree.

Regards

Richard
--
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/