Quoting Andrew Morton ([EMAIL PROTECTED]): > On Wed, 07 Nov 2007 23:44:49 -0800 > Andrew Morgan <[EMAIL PROTECTED]> wrote: > > > The attached patch (e3d27bcb07485a6c8927c8e4f5483d35a99680c3) adds > > 64-bit capability support to the kernel. This version of the patch is > > designed to apply against the 2.6.23-mm1 tree. > > > > FWIW libcap-2.00 supports this change (and earlier capability formats) > > > > http://www.kernel.org/pub/linux/libs/security/linux-privs/kernel-2.6/ > > > > Cheers > > > > Andrew > > > > Note: to apply this patch against Linus' upstream kernel, you will first > > have to undo this other patch from Serge: > > > > From b68680e4731abbd78863063aaa0dca2a6d8cc723 Mon Sep 17 00:00:00 2001 > > From: Serge E. Hallyn <[EMAIL PROTECTED]> > > Date: Sun, 21 Oct 2007 16:41:38 -0700 > > Subject: [PATCH] capabilities: clean up file capability reading > > > > It seems that this patch has made it into 2.6.24-rc1, but it is not > > Well I did that reversion, but I don't understand why. Was that patch > wrong, or did it make this new patch impractical, or...?
Andrew wanted to keep the vfs_cap_data.data[] structure, using two 'data's for 64-bit caps (and later three for 96-bit caps), whereas my patch had gotten rid of the 'data' struct made its members inline. His 64-bit caps patch keeps the stack abuse fix at get_file_caps(), which was the more important part of that patch. thanks, -serge - To unsubscribe from this list: send the line "unsubscribe linux-security-module" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
