From: Ingo Molnar <mingo@elte.hu>
To: Eduard - Gabriel Munteanu <eduard.munteanu@linux360.ro>
Cc: Pekka Enberg <penberg@cs.helsinki.fi>,
"Paul E. McKenney" <paulmck@linux.vnet.ibm.com>,
Mathieu Desnoyers <mathieu.desnoyers@polymtl.ca>,
Dipankar Sarma <dipankar@in.ibm.com>,
Alexey Dobriyan <adobriyan@gmail.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] RCU: Don't include unnecessary headers, allow kmemtrace w/ tracepoints.
Date: Tue, 30 Dec 2008 09:21:53 +0100 [thread overview]
Message-ID: <20081230082153.GB17629@elte.hu> (raw)
In-Reply-To: <20081230081445.GC10635@localhost>
* Eduard - Gabriel Munteanu <eduard.munteanu@linux360.ro> wrote:
> On Tue, Dec 30, 2008 at 08:53:37AM +0100, Ingo Molnar wrote:
> > hm, there are quite a few such dependencies it appears, for example:
> >
> > In file included from init/do_mounts_initrd.c:4:
> > include/linux/fs.h: In function 'alloc_secdata':
> > include/linux/fs.h:2214: error: implicit declaration of function 'get_zeroed_page'
> > include/linux/fs.h:2214: error: 'GFP_KERNEL' undeclared (first use in this function)
> > include/linux/fs.h:2214: error: (Each undeclared identifier is reported only once
> > include/linux/fs.h:2214: error: for each function it appears in.)
> > include/linux/fs.h: In function 'free_secdata':
> > include/linux/fs.h:2219: error: implicit declaration of function
> > 'free_page'
> > In file included from include/linux/slab.h:13,
> > from include/linux/percpu.h:6,
> > from include/linux/percpu_counter.h:14,
> > from include/linux/ext2_fs_sb.h:21,
> > from include/linux/ext2_fs.h:70,
> > from init/do_mounts_initrd.c:6:
> >
> > config attached.
> >
> > Ingo
>
> Hm, that's weird, I was also testing on a 2.6.28-based tree. And I don't
> see any reference to RCU headers in this error message. My guess is some
> code assumes a certain header provides some definitions it isn't
> required to.
>
> I'll checkout your tree and have a look.
note: you'll need to apply your patch ontop of tip/master, i moved it out
of tip/master for now due to the build breakage. Let me know if you cannot
reproduce the problem, i'll then figure out what's going on.
Ingo
next prev parent reply other threads:[~2008-12-30 8:22 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-30 7:41 [PATCH 0/2] kmemtrace over tracepoints (resubmit) Eduard - Gabriel Munteanu
2008-12-30 7:41 ` [PATCH 1/2] RCU: Don't include unnecessary headers, allow kmemtrace w/ tracepoints Eduard - Gabriel Munteanu
2008-12-30 7:41 ` [PATCH 2/2] kmemtrace: Use tracepoints instead of markers Eduard - Gabriel Munteanu
2008-12-30 7:50 ` Pekka Enberg
2008-12-30 12:40 ` Arnaldo Carvalho de Melo
2008-12-30 14:02 ` Eduard - Gabriel Munteanu
2009-01-02 21:48 ` Mathieu Desnoyers
2009-01-02 22:38 ` Eduard - Gabriel Munteanu
2009-01-02 23:32 ` Mathieu Desnoyers
2008-12-30 7:49 ` [PATCH 1/2] RCU: Don't include unnecessary headers, allow kmemtrace w/ tracepoints Ingo Molnar
2008-12-30 7:53 ` Ingo Molnar
2008-12-30 8:14 ` Eduard - Gabriel Munteanu
2008-12-30 8:21 ` Ingo Molnar [this message]
2008-12-31 3:56 ` [PATCH 0/2] kmemtrace over tracepoints (resubmit) Paul E. McKenney
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=20081230082153.GB17629@elte.hu \
--to=mingo@elte.hu \
--cc=adobriyan@gmail.com \
--cc=dipankar@in.ibm.com \
--cc=eduard.munteanu@linux360.ro \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@polymtl.ca \
--cc=paulmck@linux.vnet.ibm.com \
--cc=penberg@cs.helsinki.fi \
/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
all inboxes | Powered by JetHome®