From: aq <aquynh@gmail.com>
To: Keir Fraser <Keir.Fraser@cl.cam.ac.uk>
Cc: xen-devel <xen-devel@lists.xensource.com>,
Stefan Berger <stefanb@us.ibm.com>
Subject: Re: [PATCH] fix broken ACM
Date: Fri, 24 Jun 2005 00:22:04 +0900 [thread overview]
Message-ID: <9cde8bff05062308227dfd471e@mail.gmail.com> (raw)
In-Reply-To: <7ae02d710529059790220f4430ef0fae@cl.cam.ac.uk>
On 6/24/05, Keir Fraser <Keir.Fraser@cl.cam.ac.uk> wrote:
>
> On 23 Jun 2005, at 15:57, Stefan Berger wrote:
>
> >> ok, i see the point. the problem is because i moved some codes
> >> (acm_init() and acm_init_binary_policy()) to acm_hooks.h. now it seems
> >> better to move them back. but it is weird that i got no problem with
> >> gcc 3.3.5
> >>
> >> could you please try again with the new patch below?
> >
> > I tried it with your attached patch. There was an unused function when
> > trying out the NULL policy. The attached patch on top of yours and
> > things
> > compile fine.
>
> I'm still confused what these patches are aiming to fix. If we are
> building 'NULL' security policy then all the hooks should compile away
> to nothing and acm core files do not get built. So why do they need
> patching with ifdef's conditional on whether or not the policy is
> 'NULL'?
>
> Currently, if you re-enable building of acm/ directory in the Xen root
> Makefile, yet the ACM_USE_SECURITY_POLICY is NULL_POLICY, the build
> will certainly fail. But I don;t see why we would want to support that.
> :-)
Keir, certainly i understand your point. but this patch doesnt harm, anyway ;-)
one annoying problem at the moment is that if we want to compile ACM
in, we should modify the value of ACM_USE_SECURITY_POLICY, since the
current default value is ACM_NULL_POLICY( which is meaningless as Keir
pointed out )
any clean way to overcome this problem?
regards,
aq
next prev parent reply other threads:[~2005-06-23 15:22 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-22 17:40 [PATCH] fix broken ACM aq
2005-06-22 17:51 ` Keir Fraser
2005-06-22 17:52 ` aq
2005-06-23 7:48 ` Keir Fraser
2005-06-23 8:04 ` aq
2005-06-23 8:14 ` Keir Fraser
2005-06-23 8:19 ` aq
2005-06-22 18:22 ` aq
2005-06-23 3:42 ` Stefan Berger
2005-06-23 3:56 ` aq
2005-06-23 4:18 ` Stefan Berger
2005-06-23 7:56 ` aq
2005-06-23 14:57 ` Stefan Berger
2005-06-23 15:16 ` Keir Fraser
2005-06-23 15:22 ` aq [this message]
2005-06-23 15:52 ` Keir Fraser
2005-06-23 22:06 ` aq
2005-06-23 15:56 ` Stefan Berger
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=9cde8bff05062308227dfd471e@mail.gmail.com \
--to=aquynh@gmail.com \
--cc=Keir.Fraser@cl.cam.ac.uk \
--cc=stefanb@us.ibm.com \
--cc=xen-devel@lists.xensource.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 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.