From: Kurt Garloff <garloff@suse.de>
To: James Morris <jmorris@redhat.com>
Cc: Tony Jones <tonyj@immunix.com>,
Linux kernel list <linux-kernel@vger.kernel.org>,
Chris Wright <chrisw@osdl.org>,
Stephen Smalley <sds@epoch.ncsc.mil>,
Greg Kroah-Hartman <gregkh@suse.de>,
Steve Beattie <smb@wirex.com>,
Linux LSM list <linux-security-module@wirex.com>
Subject: Re: [PATCH 1/3] Make cap default
Date: Tue, 5 Jul 2005 18:26:49 +0200 [thread overview]
Message-ID: <20050705162649.GB12583@tpkurt.garloff.de> (raw)
In-Reply-To: <Xine.LNX.4.44.0507051139470.3247-100000@thoron.boston.redhat.com>
[-- Attachment #1: Type: text/plain, Size: 794 bytes --]
Hi James,
On Tue, Jul 05, 2005 at 11:40:40AM -0400, James Morris wrote:
> On Tue, 5 Jul 2005, Kurt Garloff wrote:
>
> > # define COND_SECURITY(seop, def) \
> > (security_opt->seop == NULL) || \
> > security_ops == &capability_security_ops)? \
> > def: security_ops->seop
>
> Why is this a macro and not a static inline?
Good question ...
The number and type of parameters is variable, so we can't
easily do it with ONE static inline function.
seop is the function call including parameters, as is def.
Which means that the idea won't work the way I suggested in
the email. We'd need a three arg version, one for the security_ops
function name, one for the cap version and one for the arguments.
Best,
--
Kurt Garloff, Director SUSE Labs, Novell Inc.
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
prev parent reply other threads:[~2005-07-05 16:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-03 15:43 Kurt Garloff
2005-07-03 22:51 ` Tony Jones
2005-07-05 7:21 ` Kurt Garloff
2005-07-05 15:40 ` James Morris
2005-07-05 16:26 ` Kurt Garloff [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=20050705162649.GB12583@tpkurt.garloff.de \
--to=garloff@suse.de \
--cc=chrisw@osdl.org \
--cc=gregkh@suse.de \
--cc=jmorris@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@wirex.com \
--cc=sds@epoch.ncsc.mil \
--cc=smb@wirex.com \
--cc=tonyj@immunix.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®