From: Greg KH <greg@kroah.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
Andy Whitcroft <apw@shadowen.org>,
Kamalesh Babulal <kamalesh@linux.vnet.ibm.com>,
Lonnie Iverson <ldiverson@novell.com>
Subject: Re: [BUILD_FAILURE] linux-next: Tree for March 31 build fails on fs/novfs sys_flistxattr()
Date: Mon, 31 Mar 2008 08:54:17 -0700 [thread overview]
Message-ID: <20080331155417.GD3696@kroah.com> (raw)
In-Reply-To: <20080331224125.cc030176.sfr@canb.auug.org.au>
On Mon, Mar 31, 2008 at 10:41:25PM +1100, Stephen Rothwell wrote:
> On Mon, 31 Mar 2008 16:49:18 +0530 Kamalesh Babulal <kamalesh@linux.vnet.ibm.com> wrote:
> >
> > Hi Stephen,
> >
> > The next-20080331 allyesconfig, build fails on x86_64 machine
> >
> > fs/novfs/built-in.o: In function `sys_flistxattr':
> > /root/kernels/linux-2.6.25-rc7/fs/novfs/inode.c:4658: multiple definition of `sys_flistxattr'
> > fs/xattr.o:/root/kernels/linux-2.6.25-rc7/fs/xattr.c:457: first defined here
> > ld: Warning: size of symbol `sys_flistxattr' changed from 112 in fs/xattr.o to 75 in fs/novfs/built-in.o
> > fs/novfs/built-in.o: In function `sys_fsetxattr':
> > /root/kernels/linux-2.6.25-rc7/fs/novfs/inode.c:4672: multiple definition of `sys_fsetxattr'
> > fs/xattr.o:/root/kernels/linux-2.6.25-rc7/fs/xattr.c:295: first defined here
> > ld: Warning: size of symbol `sys_fsetxattr' changed from 164 in fs/xattr.o to 97 in fs/novfs/built-in.o
> > fs/novfs/built-in.o: In function `sys_fgetxattr':
> > /root/kernels/linux-2.6.25-rc7/fs/novfs/inode.c:4645: multiple definition of `sys_fgetxattr'
> > fs/xattr.o:/root/kernels/linux-2.6.25-rc7/fs/xattr.c:384: first defined here
> > ld: Warning: size of symbol `sys_fgetxattr' changed from 128 in fs/xattr.o to 91 in fs/novfs/built-in.o
> > make[1]: *** [fs/built-in.o] Error 1
> > make: *** [fs] Error 2
>
> Yes, well this from fs/novfs/inode.c was asking for it really :-)
>
> asmlinkage ssize_t sys_flistxattr(int fd, char __user * list, size_t size)
> {
> .
> .
Ugh, tha's horrible. I'll fix that up, sorry.
thanks,
greg k-h
next prev parent reply other threads:[~2008-03-31 15:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-31 7:11 linux-next: Tree for March 31 Stephen Rothwell
2008-03-31 11:19 ` [BUILD_FAILURE] linux-next: Tree for March 31 build fails on fs/novfs sys_flistxattr() Kamalesh Babulal
2008-03-31 11:41 ` Stephen Rothwell
2008-03-31 15:54 ` Greg KH [this message]
2008-03-31 16:50 ` Greg KH
2008-03-31 13:17 ` [BUILD_FAILURE] linux-next: Tree for March 31 build fails with CONFIG_SLICOSS=y Kamalesh Babulal
2008-03-31 13:31 ` Stephen Rothwell
2008-03-31 15:55 ` Greg KH
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20080331155417.GD3696@kroah.com \
--to=greg@kroah.com \
--cc=apw@shadowen.org \
--cc=kamalesh@linux.vnet.ibm.com \
--cc=ldiverson@novell.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox