From: Alexey Dobriyan <adobriyan@gmail.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: Pekka Enberg <penberg@cs.helsinki.fi>,
eduard.munteanu@linux360.ro, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] kmemtrace: fix build breakage in befs
Date: Tue, 24 Mar 2009 16:09:26 +0300 [thread overview]
Message-ID: <20090324130926.GA11358@x200.localdomain> (raw)
In-Reply-To: <20090324095346.GB23208@elte.hu>
On Tue, Mar 24, 2009 at 10:53:46AM +0100, Ingo Molnar wrote:
> > -static inline char *alloc_secdata(void)
> > -{
> > - return (char *)get_zeroed_page(GFP_KERNEL);
> > -}
> > -
> > -static inline void free_secdata(void *secdata)
> > -{
> > - free_page((unsigned long)secdata);
> > -}
> > +#define alloc_secdata() (char *)get_zeroed_page(GFP_KERNEL)
> > +#define free_secdata() free_page((unsigned long) secdata)
>
> yep, that would be fine - but please add a comment about why they
> are macros and what would have to be done to fix it.
Nooo!
Stick it into security.h!
> (the real fix would be to separate fs.h into fs_types.h and
> fs_apis.h - like we did it with spinlock.h. Similarly with slab.h.)
next prev parent reply other threads:[~2009-03-24 13:02 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-24 8:43 Pekka Enberg
2009-03-24 8:51 ` Ingo Molnar
2009-03-24 8:54 ` Pekka Enberg
2009-03-24 8:56 ` Ingo Molnar
2009-03-24 8:57 ` Pekka Enberg
2009-03-24 9:07 ` Ingo Molnar
2009-03-24 9:15 ` Pekka Enberg
2009-03-24 9:17 ` Ingo Molnar
2009-03-24 9:22 ` Pekka Enberg
2009-03-24 9:31 ` Ingo Molnar
2009-03-24 9:34 ` Ingo Molnar
2009-03-24 9:46 ` Ingo Molnar
2009-03-24 10:12 ` Ingo Molnar
2009-03-24 10:34 ` Ingo Molnar
2009-03-24 9:38 ` Pekka Enberg
2009-03-24 9:53 ` Ingo Molnar
2009-03-24 13:09 ` Alexey Dobriyan [this message]
2009-03-24 13:11 ` Pekka Enberg
2009-03-24 16:32 ` Eduard - Gabriel Munteanu
2009-03-24 21:02 ` Ingo Molnar
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=20090324130926.GA11358@x200.localdomain \
--to=adobriyan@gmail.com \
--cc=eduard.munteanu@linux360.ro \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--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®