linux-kernel - Re: [PATCH] fix modpost warnings for xtensa

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]

Date:	Thu, 19 Jul 2007 14:00:05 -0700
From:	Andrew Morton <akpm@...ux-foundation.org>
To:	Chris Zankel <czankel@...silica.com>
Cc:	torvalds@...ux-foundation.org, chris@...kel.net,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] fix modpost warnings for xtensa

On Thu, 19 Jul 2007 11:37:56 -0700
Chris Zankel <czankel@...silica.com> wrote:

> 
> 	[PATCH] fix modpost warnings for xtensa
> 
> 	The Xtensa architecture places literal pools in sections separate 
> 	from the instructions. The corresponsing text sections, therefore, 
> 	reference the .literal section, and we have to suppress those
> 	warnings. The naming convention defines the name for a literal 
> 	section as .SECTION.literal, unless .SECTION is .text. In that case
> 	the name is only .literal. Using strncmp() instead of strcmp() 
> 	to compare the from-section with .SECTION.init.refok in pattern 0
> 	should not cause any regressions for other architectures.
> 	We also need to suppress warnings for two informational 
> 	sections (.xt.lit and .xt.prop) used by the Xtensa architecture.

This generates unfixable-by-me rejects against Sam's git-kbuild tree.
Sam already had a pull request into Linus for that tree.  Could I ask
that you wait for that piece of dust to settle and then regenerate the
diff?

Thanks.
-
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/