linux-kernel - Re: [PATCH] blackfin: Makefile: Skip reloc overflow issue when COMPILE

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: <BLU437-SMTP70BC4F801A077F7292466DB9FB0@phx.gbl>
Date:	Fri, 10 Apr 2015 07:14:20 +0800
From:	Chen Gang <xili_gchen_5257@...mail.com>
To:	Richard Weinberger <richard@....at>, realmz6@...il.com
CC:	adi-buildroot-devel@...ts.sourceforge.net,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] blackfin: Makefile: Skip reloc overflow issue when COMPILE_TEST
 enabled

On 4/9/15 21:38, Richard Weinberger wrote:
> Am 09.04.2015 um 15:28 schrieb Chen Gang:
>> On 4/9/15 05:12, Richard Weinberger wrote:
>>> Am 08.04.2015 um 23:10 schrieb Chen Gang:
>>>>
>>>> After this patch, blackfin can pass allmodconfig building (if we treat
>>>> it as allmodconfig). And next, I shall try to:
>>>>
>>>>  - Send all related patches v2 for blackfin kernel within this month.
>>>>
>>>>  - Fix blackfin gcc/binutils related issues within this month.
>>>
>>> All you do is randomly papering over issues to make the allmodconfig build
>>> somehow proceed.
>>> This is not the correct way to deal with problems.
>>>
>>
>> Still, for me, it is not a good idea to make a conclusion in discussing.
>>
>> For gcc/binutils issues, they are real world issue, they need to be
>> fixed, next (I shall try to fix them within this month).
> 
> I leave that up to the blackfin maintainer.

OK, thanks.

> IMHO this is wrong, you're not fixing a real world issue, all you do is
> making allmodconfig somehow proceed by papering over possible real issues
> which you cannot test as you don't have blackfin hardware.
> 

For me, it is not a real world issue, the user should not let it happen.
It is only about building test (COMPILE_TEST).

And for me, the root cause is:

 - init section is the last section which can be dropped easily.

 - but init section includes l1 section (which may also include sched
   section).

 - l1 section has fixed address. If the kernel is too big, l1 section
   will be overwrite, so ld report "reloc overflow".

Welcome any other ideas, discussions or completions.


Thanks.
-- 
Chen Gang

Open, share, and attitude like air, water, and life which God blessed
--
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/