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

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Acked-by: Andrew G. Morgan <[EMAIL PROTECTED]> Tested-by: Andrew G. Morgan <[EMAIL PROTECTED]> Cheers Andrew Kohei KaiGai wrote: | [PATCH 2/3] exporting capability name/code pairs | | This patch enables to export code/name pairs of capabilities the

[PATCH 2/3] exporting capability name/code pairs (final#2)

[PATCH 2/3] exporting capability name/code pairs This patch enables to export code/name pairs of capabilities the running kernel supported. A newer kernel sometimes adds new capabilities, like CAP_MAC_ADMIN at 2.6.25. However, we have no interface to disclose what capabilities are supported on th

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

Li Zefan wrote: >> [2/3] Exporting capability code/name pairs >> >> This patch enables to export code/name pairs of capabilities the running >> kernel supported. >> > > supported or supports ? It seems to me "supports" is more appropriate one. The original one might mention legacy versions. :-(

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

On Fri, Feb 22, 2008 at 06:45:32PM +0900, Kohei KaiGai wrote: > 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. That is correct, it is one of the assumptions that is safe to make. But you should fix the compiler

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

Kohei KaiGai 写道: > [2/3] Exporting capability code/name pairs > > This patch enables to export code/name pairs of capabilities the running > kernel supported. > supported or supports ? > A newer kernel sometimes adds new capabilities, like CAP_MAC_ADMIN > at 2.6.25. However, we have no interfac

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 ~ CAPSsecurity/cap_names.h /bin/sh: security/../scr

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

-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 ~ CAPSsecurity/cap_names.h /bin/sh: security/../scripts/mkcapnames.sh: No su

[PATCH 2/3] exporting capability name/code pairs (final)

[2/3] Exporting capability code/name pairs This patch enables to export code/name pairs of capabilities the running kernel supported. A newer kernel sometimes adds new capabilities, like CAP_MAC_ADMIN at 2.6.25. However, we have no interface to disclose what capabilities are supported on the runn