linux-kernel - Re: [PATCH 2/3] exporting capability name/code pairs (final)

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <47BE99BC.2060707@ak.jp.nec.com>
Date:	Fri, 22 Feb 2008 18:45:32 +0900
From:	Kohei KaiGai <kaigai@...jp.nec.com>
To:	"Andrew G. Morgan" <morgan@...nel.org>
CC:	greg@...ah.com, serue@...ibm.com,
	linux-security-module@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 2/3] exporting capability name/code pairs (final)

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@...jp.nec.com>
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/