From: Artem Bityutskiy <dedekind1@gmail.com>
To: sedat.dilek@gmail.com
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: Tree for April 1 [BROKEN ubifs when CONFIG_DEBUG_SECTION_MISMATCH=y]
Date: Fri, 01 Apr 2011 20:02:29 +0300 [thread overview]
Message-ID: <1301677349.2789.120.camel@localhost> (raw)
In-Reply-To: <AANLkTin6dXV1bvgzwGuKKq_o08Wnz6Ddm38vFP4us4fC@mail.gmail.com>
On Fri, 2011-04-01 at 18:10 +0200, Sedat Dilek wrote:
> On Fri, Apr 1, 2011 at 6:06 PM, Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> > Cc'ing Artem,
> >
> > On Fri, 1 Apr 2011 17:55:52 +0200 Sedat Dilek <sedat.dilek@googlemail.com> wrote:
> >>
> >> With CONFIG_DEBUG_SECTION_MISMATCH=y set, I see in my build.log:
> >> ...
> >> MODPOST 2742 modules
> >> ...
> >> ERROR: "empty_aops" [fs/ubifs/ubifs.ko] undefined!
> >> make[5]: *** [__modpost] Error 1
> >> make[4]: *** [modules] Error 2
> >> make[3]: *** [sub-make] Error 2
> >> make[2]: *** [all] Error 2
> >> make[2]: Leaving directory
> >> `/home/sd/src/linux-2.6/linux-2.6.39-rc1/debian/build/build_i386_none_686-iniza'
> >>
> >> - Sedat -
> >>
> >
> >
> > --
> > Cheers,
> > Stephen Rothwell sfr@canb.auug.org.au
> > http://www.canb.auug.org.au/~sfr/
> >
>
> Speculative patch (untested).
>
> - Sedat -
>
> $ diff -uprN fs/ubifs/xattr.c.orig fs/ubifs/xattr.c
> --- fs/ubifs/xattr.c.orig 2011-04-01 15:56:08.471082117 +0200
> +++ fs/ubifs/xattr.c 2011-04-01 18:08:27.355276827 +0200
> @@ -81,6 +81,7 @@ enum {
>
> static const struct inode_operations none_inode_operations;
> static const struct file_operations none_file_operations;
> +static const struct address_space_operations empty_aops;
>
> /**
> * create_xattr - create an extended attribute.
ubifs doess not have 'empty_aops' symbol and does not use such symbol. I
do not understand how you got that build issue, but this must be
something to do with your local setup.
Also:
[dedekind@eru linux-next (master)]$ grep -r 'empty_aops' *
fs/nilfs2/page.c: static const struct address_space_operations empty_aops;
fs/nilfs2/page.c: mapping->a_ops = &empty_aops;
fs/inode.c: static const struct address_space_operations empty_aops;
fs/inode.c: mapping->a_ops = &empty_aops;
in the current linux-next.
--
Best Regards,
Artem Bityutskiy (Артём Битюцкий)
prev parent reply other threads:[~2011-04-01 17:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-01 15:55 linux-next: Tree for April 1 [BROKEN ubifs when CONFIG_DEBUG_SECTION_MISMATCH=y] Sedat Dilek
2011-04-01 16:06 ` Stephen Rothwell
2011-04-01 16:10 ` Sedat Dilek
2011-04-01 17:02 ` Artem Bityutskiy [this message]
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=1301677349.2789.120.camel@localhost \
--to=dedekind1@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sedat.dilek@gmail.com \
--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;
as well as URLs for NNTP newsgroup(s).