From: Stephen Rothwell <sfr@canb•auug.org.au>
To: sedat.dilek@gmail•com
Cc: Jens Axboe <jaxboe@fusionio•com>,
Sedat Dilek <sedat.dilek@googlemail•com>,
dedekind1@gmail•com, 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]s
Date: Sat, 2 Apr 2011 11:20:37 +1100 [thread overview]
Message-ID: <20110402112037.ca288d7b.sfr@canb.auug.org.au> (raw)
In-Reply-To: <AANLkTimhD_cu46Bhtt9v8MjKMVCnVMT6Es+Ys9RNPOp1@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2855 bytes --]
cc'ing Jens ...
On Fri, 1 Apr 2011 20:22:41 +0200 Sedat Dilek <sedat.dilek@googlemail•com> wrote:
>
> On Fri, Apr 1, 2011 at 7:02 PM, Artem Bityutskiy <dedekind1@gmail•com> wrote:
> > 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 (Артём Битюцкий)
> >
> >
>
> You are right, I pulled linux-2.6-block.git#for-linus into linux-next.
> Looks like linux-2.6-block-for-linus/0007-fs-export-empty_aops.patch
> is causing this [1].
>
> - Sedat -
>
> [1] http://git.kernel.org/?p=linux/kernel/git/axboe/linux-2.6-block.git;a=commit;h=2c9214b7b72cf440024d8b91523eea25bbc76040
>
--
Cheers,
Stephen Rothwell sfr@canb•auug.org.au
http://www.canb.auug.org.au/~sfr/
[-- Attachment #2: Type: application/pgp-signature, Size: 490 bytes --]
next prev parent reply other threads:[~2011-04-02 0:20 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-01 18:22 linux-next: Tree for April 1 [BROKEN ubifs when CONFIG_DEBUG_SECTION_MISMATCH=y]s Sedat Dilek
2011-04-02 0:20 ` Stephen Rothwell [this message]
2011-04-02 10:14 ` Sedat Dilek
2011-04-02 11:02 ` Sedat Dilek
2011-04-03 22:16 ` Jens Axboe
2011-04-03 22:19 ` Sedat Dilek
2011-04-03 22:21 ` Jens Axboe
2011-04-03 22:33 ` Sedat Dilek
2011-04-03 22:36 ` Jens Axboe
2011-04-03 22:38 ` Sedat Dilek
2011-04-03 22:47 ` Jens Axboe
2011-04-03 23:14 ` Sedat Dilek
2011-04-03 23:07 ` Sedat Dilek
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=20110402112037.ca288d7b.sfr@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=dedekind1@gmail$(echo .)com \
--cc=jaxboe@fusionio$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=sedat.dilek@gmail$(echo .)com \
--cc=sedat.dilek@googlemail$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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