linux-kernel - Re: 2.6.18-rc6-mm1 'uio_read' redefined, breaks allyesconfig on i386

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, 11 Sep 2006 15:53:11 -0700
From:	Andrew Morton <akpm@...l.org>
To:	Judith Lebzelter <judith@...l.org>
Cc:	tglx@...utronix.de, linux-kernel@...r.kernel.org,
	Greg KH <greg@...ah.com>, linux-xfs@....sgi.com
Subject: Re: 2.6.18-rc6-mm1 'uio_read' redefined, breaks allyesconfig on
 i386

On Mon, 11 Sep 2006 15:45:20 -0700
Judith Lebzelter <judith@...l.org> wrote:

> Hello, 
> 
> I noticed in the 'allyesconfig' build for i386 is not working for 2.6.18-rc6-mm1.
> The function 'uio_read' in gregkh-driver-uio.patch has the same name as a 
> function in fs/xfs/support/move.c.  Here is the error message:
> 
>   LD      drivers/w1/built-in.o
>   LD      drivers/built-in.o
>   GEN     .version
>   CHK     include/linux/compile.h
>   UPD     include/linux/compile.h
>   CC      init/version.o
>   LD      init/built-in.o
>   LD      .tmp_vmlinux1
> drivers/built-in.o(.text+0x6eb597): In function `uio_read':
> drivers/uio/uio_dev.c:59: multiple definition of `uio_read'
> fs/built-in.o(.text+0x2f4ee8):fs/xfs/support/move.c:26: first defined here
> i686-unknown-linux-gnu-ld: Warning: size of symbol `uio_read' changed from 123 in fs/built-in.o to 397 in drivers/built-in.o
> make: [.tmp_vmlinux1] Error 1 (ignored)
>   KSYM    .tmp_kallsyms1.S
> i686-unknown-linux-gnu-nm: '.tmp_vmlinux1': No such file
> No valid symbol.
> make: [.tmp_kallsyms1.S] Error 1 (ignored)
> 

Thanks.   I'd suggest that XFS is being poorly behaved here.  "uio_read" isn't
an appropriately named symbol for a filesystem to be exposing.
-
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/