From: Michal Piotrowski <michal.k.k.piotrowski@gmail.com>
To: "Serge E. Hallyn" <serue@us.ibm.com>
Cc: Michal Piotrowski <michal.k.k.piotrowski@gmail.com>,
linux-kernel@vger.kernel.org, Andrew Morton <akpm@osdl.org>,
Herbert Poetzl <herbert@13thfloor.at>,
Oleg Nesterov <oleg@tv-sign.ru>,
Cedric Le Goater <clg@fr.ibm.com>,
Daniel Hokka Zakrisson <daniel@hozac.com>
Subject: Re: mm snapshot broken-out-2007-01-26-00-36.tar.gz uploaded
Date: Fri, 26 Jan 2007 17:06:59 +0100 [thread overview]
Message-ID: <45BA2723.3000306@googlemail.com> (raw)
In-Reply-To: <20070126153832.GB12550@sergelap.austin.ibm.com>
Serge E. Hallyn napisał(a):
> Quoting Serge E. Hallyn (serue@us.ibm.com):
>> Quoting Michal Piotrowski (michal.k.k.piotrowski@gmail.com):
>>> Hi Serge,
>>>
>>> akpm@osdl.org napisa?(a):
>>>> The mm snapshot broken-out-2007-01-26-00-36.tar.gz has been uploaded to
>>>>
>>>> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/mm/broken-out-2007-01-26-00-36.tar.gz
>>>>
>>>> It contains the following patches against 2.6.20-rc6:
>>>>
>>>> origin.patch
>>> [..]
>>>> namespaces-fix-exit-race-by-splitting-exit.patch
>>> [..]
>>>
>>> I'm receiving an error
>>>
>>> In file included from /mnt/md0/devel/linux-work5/include/linux/sched.h:87,
>>> from /mnt/md0/devel/linux-work5/include/linux/utsname.h:35,
>>> from include2/asm/elf.h:12,
>>> from /mnt/md0/devel/linux-work5/include/linux/elf.h:7,
>>> from /mnt/md0/devel/linux-work5/include/linux/module.h:15,
>>> from /mnt/md0/devel/linux-work5/include/linux/crypto.h:21,
>>> from /mnt/md0/devel/linux-work5/arch/i386/kernel/asm-offsets.c:7:
>>> /mnt/md0/devel/linux-work5/include/linux/nsproxy.h: In function 'preexit_task_namespaces':
>>> /mnt/md0/devel/linux-work5/include/linux/nsproxy.h:56: error: dereferencing pointer to incomplete type
>>> make[2]: *** [arch/i386/kernel/asm-offsets.s] Error 1
>>> make[1]: *** [prepare0] Error 2
>>> make: *** [_all] Error 2
>>>
>>> Regards,
>>> Michal
>> Sorry, I don't know where to get a series file for this patchset?
>>
>> It sounds like your tree doesn't #include <linux/sched.h> at the top of
>> include/linux/nsproxy.h. That was added by a separate patch I think
>> last week - a few architectures (which i was testing) had a #include chain
>> which ended up in sched.h being included free, but some arches had a
>> different chain.
>>
>> Anyway please try #include <linux/sched.h> at the top of
>> include/linux/nsproxy.h and let me know if that doesn't fix the problem.
>
> No, I just found Cedric's patch removing the include.
>
> So moving preexit_task_namespaces() into nsproxy.c is the right way to
> go.
>
> thanks,
> -serge
>
Thanks!
Regards,
Michal
--
Michal K. K. Piotrowski
LTG - Linux Testers Group
(http://www.stardust.webpages.pl/ltg/)
Build fix.
Signed-off-by: Michal Piotrowski <michal.k.k.piotrowski@gmail.com>
diff -uprN linux-work-clean/include/linux/nsproxy.h linux-work/include/linux/nsproxy.h
--- linux-work-clean/include/linux/nsproxy.h 2007-01-26 16:47:55.000000000 +0100
+++ linux-work/include/linux/nsproxy.h 2007-01-26 17:00:54.000000000 +0100
@@ -51,11 +51,6 @@ static inline void put_and_finalize_nspr
finalize_put_nsproxy(put_nsproxy(ns));
}
-static inline struct nsproxy *preexit_task_namespaces(struct task_struct *p)
-{
- return put_nsproxy(p->nsproxy);
-}
-
extern void exit_task_namespaces(struct task_struct *p);
#endif
diff -uprN linux-work-clean/kernel/nsproxy.c linux-work/kernel/nsproxy.c
--- linux-work-clean/kernel/nsproxy.c 2007-01-26 16:53:49.000000000 +0100
+++ linux-work/kernel/nsproxy.c 2007-01-26 17:01:14.000000000 +0100
@@ -196,3 +196,8 @@ struct mnt_namespace *get_task_mnt_ns(st
return mnt_ns;
}
+
+static inline struct nsproxy *preexit_task_namespaces(struct task_struct *p)
+{
+ return put_nsproxy(p->nsproxy);
+}
next prev parent reply other threads:[~2007-01-26 16:07 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200701260837.l0Q8blBr011622@shell0.pdx.osdl.net>
2007-01-26 15:04 ` mm snapshot broken-out-2007-01-26-00-36.tar.gz uploaded Michal Piotrowski
2007-01-26 15:33 ` Serge E. Hallyn
2007-01-26 15:38 ` Serge E. Hallyn
2007-01-26 16:06 ` Michal Piotrowski [this message]
2007-01-26 16:37 ` Michal Piotrowski
2007-01-26 16:46 ` Michal Piotrowski
2007-01-26 16:57 ` Michal Piotrowski
2007-01-26 17:29 ` Michal Piotrowski
2007-01-26 18:14 ` Serge E. Hallyn
2007-01-26 18:22 ` Michal Piotrowski
2007-01-26 18:58 ` Serge E. Hallyn
2007-01-26 17:48 ` Michal Piotrowski
2007-01-26 18:04 ` Michal Piotrowski
[not found] ` <6bffcb0e0701261008u2fd5a7d9va16d7fd9f250e14b@mail.gmail.com>
2007-01-26 18:38 ` Christoph Lameter
2007-01-26 18:43 ` Pavel Machek
2007-01-26 18:45 ` Michal Piotrowski
2007-01-26 19:07 ` Christoph Lameter
2007-01-26 19:20 ` Michal Piotrowski
2007-01-26 19:45 ` Michal Piotrowski
[not found] ` <6bffcb0e0701261523j3a84a357lad93260b5865c99d@mail.gmail.com>
2007-01-27 0:33 ` Andrew Morton
2007-01-27 0:41 ` Michal Piotrowski
2007-01-27 0:29 ` Michal Piotrowski
2007-01-27 15:05 ` Michal Piotrowski
2007-01-27 20:38 ` Herbert Xu
2007-01-27 16:03 ` Michal Piotrowski
2007-01-30 1:05 ` Tejun Heo
2007-01-27 16:14 ` Michal Piotrowski
2007-01-27 17:20 ` Michal Piotrowski
[not found] ` <6bffcb0e0701270837i1ec40560l6e61e8876177e9da@mail.gmail.com>
2007-01-27 21:29 ` Tilman Schmidt
2007-01-27 21:41 ` Andrew Morton
2007-01-27 22:12 ` Michal Piotrowski
2007-01-27 23:25 ` Tilman Schmidt
2007-01-27 23:27 ` Michal Piotrowski
2007-01-28 2:41 ` Valdis.Kletnieks
2007-01-28 3:37 ` Michal Piotrowski
2007-01-29 2:49 ` Valdis.Kletnieks
2007-01-29 6:08 ` Eric W. Biederman
2007-01-29 6:45 ` Valdis.Kletnieks
2007-01-29 8:24 ` Eric W. Biederman
2007-01-29 2:58 ` Valdis.Kletnieks
2007-01-29 5:14 ` Randy Dunlap
2007-01-29 5:46 ` Valdis.Kletnieks
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=45BA2723.3000306@googlemail.com \
--to=michal.k.k.piotrowski@gmail.com \
--cc=akpm@osdl.org \
--cc=clg@fr.ibm.com \
--cc=daniel@hozac.com \
--cc=herbert@13thfloor.at \
--cc=linux-kernel@vger.kernel.org \
--cc=oleg@tv-sign.ru \
--cc=serue@us.ibm.com \
/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