From: Andrew Morton <akpm@osdl.org>
To: Andy Lutomirski <luto@myrealbox.com>
Cc: chrisw@osdl.org, linux-kernel@vger.kernel.org, luto@myrealbox.com
Subject: Re: [PATCH 1/2] capabilities: cleanups
Date: Wed, 12 May 2004 21:14:11 -0700 [thread overview]
Message-ID: <20040512211411.6af01084.akpm@osdl.org> (raw)
In-Reply-To: <200405112024.23834.luto@myrealbox.com>
Andy Lutomirski <luto@myrealbox.com> wrote:
>
> --- linux-2.6.6-mm1/include/linux/binfmts.h~cap_1_cleanup 2004-05-10 23:52:05.000000000 -0700
> +++ linux-2.6.6-mm1/include/linux/binfmts.h 2004-05-11 00:58:13.000000000 -0700
> @@ -20,6 +20,9 @@
> /*
> * This structure is used to hold the arguments that are used when loading binaries.
> */
> +#define BINPRM_SEC_SETUID 1
> +#define BINPRM_SEC_SETGID 2
> +#define BINPRM_SEC_SECUREEXEC 4
> struct linux_binprm{
> char buf[BINPRM_BUF_SIZE];
> struct page *page[MAX_ARG_PAGES];
> @@ -27,8 +30,9 @@
> unsigned long p; /* current top of mem */
> int sh_bang;
> struct file * file;
> - int e_uid, e_gid;
> - kernel_cap_t cap_inheritable, cap_permitted, cap_effective;
> + int set_uid, set_gid;
> + int secflags;
> + kernel_cap_t cap_inheritable, cap_permitted;
security/dummy.c: In function `dummy_bprm_apply_creds':
security/dummy.c:176: structure has no member named `e_uid'
security/dummy.c:176: structure has no member named `e_gid'
security/dummy.c:180: structure has no member named `e_uid'
security/dummy.c:181: structure has no member named `e_gid'
security/dummy.c:185: structure has no member named `e_uid'
security/dummy.c:186: structure has no member named `e_gid'
prev parent reply other threads:[~2004-05-13 4:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-12 3:24 Andy Lutomirski
2004-05-13 4:14 ` Andrew Morton [this message]
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=20040512211411.6af01084.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=chrisw@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@myrealbox.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
all inboxes | Powered by JetHome®