linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Sedat Dilek <sedat.dilek@gmail.com>
To: Li Zefan <lizefan@huawei.com>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
	Andrew Morton <akpm@linux-foundation.org>,
	linux-mm <linux-mm@kvack.org>,
	Stephen Rothwell <sfr@canb.auug.org.au>
Subject: Re: linux-next: Tree for Jul 3 [ BROKEN: memcontrol.c:(.text+0x5caa6): undefined reference to `mem_cgroup_sockets_destroy' ]
Date: Wed, 3 Jul 2013 13:27:12 +0200	[thread overview]
Message-ID: <CA+icZUXPFYJAFedfq29pArsr7Wo-iAdu9NeYnr8ADYkpC6D21w@mail.gmail.com> (raw)
In-Reply-To: <CA+icZUWtvuq=KP2YsoUfWAZTzZWQymcXk72UbMquYGPCFkpnjg@mail.gmail.com>

On Wed, Jul 3, 2013 at 12:58 PM, Sedat Dilek <sedat.dilek@gmail.com> wrote:
> On Wed, Jul 3, 2013 at 11:29 AM, Sedat Dilek <sedat.dilek@gmail.com> wrote:
>> On Wed, Jul 3, 2013 at 10:06 AM, Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>>> Hi all,
>>>
>>> Changes since 20130702:
>>>
>>> The powerpc tree lost its build failure.
>>>
>>> The device-mapper tree gained a conflict against the md tree.
>>>
>>> The net-next tree gained a build failure for which I cherry-picked an
>>> upcoming fix.
>>>
>>> The trivial tree gained conflicts against the btrfs and Linus' trees.
>>>
>>> The xen-two tree gained a conflict against the tip tree.
>>>
>>> The akpm tree lost some patches that turned up elsewhere.
>>>
>>> The cpuinit tree lost a patch that turned up elsewhere.
>>>
>>> ----------------------------------------------------------------------------
>>>
>>
>> From my build-log:
>> ...
>>  CC      mm/memcontrol.o
>> ...
>>   MODPOST vmlinux.o
>> WARNING: modpost: Found 1 section mismatch(es).
>> To see full details build your kernel with:
>> 'make CONFIG_DEBUG_SECTION_MISMATCH=y'
>>   GEN     .version
>>   CHK     include/generated/compile.h
>>   UPD     include/generated/compile.h
>>   CC      init/version.o
>>   LD      init/built-in.o
>> mm/built-in.o: In function `mem_cgroup_css_free':
>> memcontrol.c:(.text+0x5caa6): undefined reference to
>> `mem_cgroup_sockets_destroy'
>> make[2]: *** [vmlinux] Error 1
>> make[1]: *** [deb-pkg] Error 2
>> make: *** [deb-pkg] Error 2
>>
>> My kernel-config is attached.
>>
>
> [ CC linux-mm and Li Zefan ]
>
> Trying with the attached patch... Building...
>

Looks like this was not a good idea:
...
  CC      mm/memcontrol.o
mm/memcontrol.c: In function 'mem_cgroup_css_free':
mm/memcontrol.c:6335:2: warning: passing argument 1 of
'mem_cgroup_css_offline' from incompatible pointer type [enabled by
default]
mm/memcontrol.c:6320:13: note: expected 'struct cgroup *' but argument
is of type 'struct mem_cgroup *'

I see I have in my kernel-config...:

# CONFIG_MEMCG_KMEM is not set

...inspired by:

[ net/core/sock.c ]
...
#ifdef CONFIG_MEMCG_KMEM
int mem_cgroup_sockets_init()
...
void mem_cgroup_sockets_destroy()
...
#endif

Not sure if...

[ include/net/sock.h ]
...
struct cgroup;
struct cgroup_subsys;
#ifdef CONFIG_NET
int mem_cgroup_sockets_init(struct mem_cgroup *memcg, struct cgroup_subsys *ss);
void mem_cgroup_sockets_destroy(struct mem_cgroup *memcg);
#else
static inline
int mem_cgroup_sockets_init(struct mem_cgroup *memcg, struct cgroup_subsys *ss)
{
        return 0;
}
static inline
void mem_cgroup_sockets_destroy(struct mem_cgroup *memcg)
{
}
#endif
...

...needs some massage.

- Sedat -

> - Sedat -
>
>
>> - Sedat -

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

      reply	other threads:[~2013-07-03 11:27 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CA+icZUUWGa0f1pKM4Vegmk3Ns8cMbQcQTR6i=XGUtpr8CkvLYA@mail.gmail.com>
2013-07-03  9:30 ` Fwd: linux-next: Tree for Jul 3 [ BROKEN: memcontrol.c:(.text+0x5caa6): undefined reference to `mem_cgroup_sockets_destroy' ] Sedat Dilek
2013-07-03 10:58 ` Sedat Dilek
2013-07-03 11:27   ` Sedat Dilek [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=CA+icZUXPFYJAFedfq29pArsr7Wo-iAdu9NeYnr8ADYkpC6D21w@mail.gmail.com \
    --to=sedat.dilek@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=linux-next@vger.kernel.org \
    --cc=lizefan@huawei.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).