From: Kohei KaiGai <kaigai@ak.jp.nec.com>
To: "Andrew G. Morgan" <morgan@kernel.org>
Cc: greg@kroah.com, serue@us.ibm.com,
linux-security-module@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/3] exporting capability name/code pairs (final)
Date: Fri, 22 Feb 2008 18:45:32 +0900 [thread overview]
Message-ID: <47BE99BC.2060707@ak.jp.nec.com> (raw)
In-Reply-To: <47BE8A10.3080103@kernel.org>
Andrew G. Morgan wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> KaiGai,
>
> I've just tried to build this with a separate obj tree: make O=/path.../
> ~ the build failed as follows:
>
> ~ CC security/dummy.o
> ~ CC security/inode.o
> ~ CAPS security/cap_names.h
> /bin/sh: security/../scripts/mkcapnames.sh: No such file or directory
> make[3]: *** [security/cap_names.h] Error 127
> make[2]: *** [security] Error 2
> make[1]: *** [sub-make] Error 2
> make: *** [all] Error 2
>
> when I replace $(src)/../scripts/... with $(srctree)/scripts/... I get
> it to compile, but (x86_64) see this warning fly by:
Thanks for your pointed out.
I didn't know the macro, but it is suitable for my purpose.
I'll replace it on the next submitting.
> ~ CC security/commoncap.o
> /home/morgan/gits/linux-2.6/security/commoncap.c: In function
> `capability_name_show':
> /home/morgan/gits/linux-2.6/security/commoncap.c:652: warning: cast from
> pointer to integer of different size
The entries under capability/names have its private data as integer value,
stored in kobj_attribute->data declared as void *.
One idea is casting it to 'unsigned long' and using "%ld" as the format.
I believe it is correct assumption that long type and pointers have
same width in the linux kernel. Please tell me, if it is wrong.
Thanks,
--
OSS Platform Development Division, NEC
KaiGai Kohei <kaigai@ak.jp.nec.com>
next prev parent reply other threads:[~2008-02-22 9:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-22 1:49 [PATCH 2/3] exporting capability name/code pairs (final) Kohei KaiGai
2008-02-22 8:38 ` Andrew G. Morgan
2008-02-22 9:45 ` Kohei KaiGai [this message]
2008-02-22 15:30 ` Greg KH
2008-02-22 9:51 ` Li Zefan
2008-02-25 4:30 ` Kohei KaiGai
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=47BE99BC.2060707@ak.jp.nec.com \
--to=kaigai@ak.jp.nec.com \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=morgan@kernel.org \
--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