linux-kernel - Re: [PATCH] init/Kconfig: Add ENDIAN attributes for all architectures using

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: <54176B0E.7080208@gmail.com>
Date:	Tue, 16 Sep 2014 06:41:18 +0800
From:	Chen Gang <gang.chen.5i5j@...il.com>
To:	Arnd Bergmann <arnd@...db.de>
CC:	Paul Gortmaker <paul.gortmaker@...driver.com>,
	"H. Peter Anvin" <hpa@...or.com>, eparis@...hat.com,
	paulmck@...ux.vnet.ibm.com,
	Geert Uytterhoeven <geert@...ux-m68k.org>,
	zhenglong.cai@...c.com.cn, khilman@...aro.org, ak@...ux.intel.com,
	mcgrof@...e.com, fabf@...net.be,
	"dhowells@...hat.com" <dhowells@...hat.com>, pefoley2@...oley.com,
	mgorman@...e.de, biederm@...ssion.com,
	"akpm@...ux-foundation.org" <akpm@...ux-foundation.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	Jean Delvare <jdelvare@...e.de>
Subject: Re: [PATCH] init/Kconfig: Add ENDIAN attributes for all architectures
 using

On 09/15/2014 09:55 PM, Arnd Bergmann wrote:
> On Sunday 14 September 2014, Chen Gang wrote:
>> Hello Maintainers:
>>
>> Is this patch worthy enough to be applied?
>>
>> Welcome any ideas, suggestions or completions.
> 
> I find it hard to judge whether it's worth it or not. You gave one example
> for a driver that needs this, but what would be your estimate on how
> many other drivers have the same problem, either producing a #warning
> or misbehaving if neither symbol is set?
> 

For me, it is also hard to judge, so at present, we can assume it is not
worthy enough for other individual modules.

> Having all architectures consistently report the endianess would be nice,
> but we have to weigh the advantages (currently broken code, potential
> simplifications) against the regression risk.
> 

Yeah, so our 'goal' is OK, but we need focus on 'how'.

At present, firstly need modify 'init/Kconfig', and then scan all
architectures one by one, let each related patch pass checking by the
related maintainers (which can avoid the risk).


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/