linux-kernel - Re: Lots of unexpected non-allocatable section warnings

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:	Mon, 4 May 2009 12:05:42 +0200
From:	Manuel Lauss <mano@...rinelk.homelinux.net>
To:	Sam Ravnborg <sam@...nborg.org>
Cc:	Anders Kaseorg <andersk@....edu>,
	LKML <linux-kernel@...r.kernel.org>,
	Linux-MIPS <linux-mips@...ux-mips.org>
Subject: Re: Lots of unexpected non-allocatable section warnings

Hi Sam,

On Mon, May 04, 2009 at 11:49:28AM +0200, Sam Ravnborg wrote:
> On Mon, May 04, 2009 at 10:28:16AM +0200, Manuel Lauss wrote:
> > Hi Sam,
> > 
> > On Sun, May 03, 2009 at 10:29:39PM +0200, Sam Ravnborg wrote:
> > > This is due to the SUSE specific section as you expected.
> > > We ignore sections named ".comment" but not ".comment" sections
> > > with something appended to the name.
> > 
> > 
> > On a related note, I see tons of the following warnings cross-building for
> > MIPS:
> > 
> > WARNING: init/mounts.o (.mdebug.abi32): unexpected non-allocatable section.
> > Did you forget to use "ax"/"aw" in a .S file?                              
> > Note that for example <linux/init.h> contains                              
> > section definitions for use in .S files.                                   
> > 
> > WARNING: init/mounts.o (.pdr): unexpected non-allocatable section.
> > Did you forget to use "ax"/"aw" in a .S file?                     
> > Note that for example <linux/init.h> contains                     
> > section definitions for use in .S files. 
> > 
> > 
> > I added ".pdr" and ".mdebug*" to the whitelist;  the resulting kernels still
> > work.  (gcc-4.3.3, binutils-2.19.1)
> 
> Hi Manuel - thanks for reporting!
> 
> Is your mips target little or big endian?
> If it is a big-endian target (which I expect) then the right fix
> is the patch posted by Anders.

No, it's little-endian.  Cross-compiling on x86_64 to mipsel.

 
> In other words - what happens if you back out your change
> and apply the appended patch.

no change.

(Did you attach the wrong patch?  It does indentation fixes and adds a few
more entries)

Thanks!
	Manuel Lauss
--
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/