From: "Paweł Sikora" <pluto@pld-linux.org>
To: James Morris <jmorris@redhat.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] security/selinux/hooks.c:1898: error: `PER_CLEAR_ON_SETID' undeclared
Date: Sun, 18 Jul 2004 22:58:37 +0200 [thread overview]
Message-ID: <200407182258.41581.pluto@pld-linux.org> (raw)
In-Reply-To: <Pine.LNX.4.58.0407181647590.7127@devserv.devel.redhat.com>
On Sunday 18 of July 2004 22:51, James Morris wrote:
> On Sun, 18 Jul 2004, [iso-8859-2] Pawe³ Sikora wrote:
> > CC security/selinux/hooks.o
> > security/selinux/hooks.c: In function `selinux_bprm_apply_creds':
> > security/selinux/hooks.c:1898: error: `PER_CLEAR_ON_SETID' undeclared
>
> I can't find this symbol anywhere in the kernel. Is this stock
> 2.6.8-rc2?
# grep PER_CLEAR /usr/src/linux/include/linux/personality.h
#define PER_CLEAR_ON_SETID (READ_IMPLIES_EXEC)
--
/* Copyright (C) 2003, SCO, Inc. This is valuable Intellectual Property. */
#define say(x) lie(x)
prev parent reply other threads:[~2004-07-18 20:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-18 12:25 [PATCH] security/selinux/hooks.c:1898: error: `PER_CLEAR_ON_SETID' undeclared Paweł Sikora
2004-07-18 20:51 ` James Morris
2004-07-18 20:58 ` Paweł Sikora [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=200407182258.41581.pluto@pld-linux.org \
--to=pluto@pld-linux.org \
--cc=jmorris@redhat.com \
--cc=linux-kernel@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.