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:
pgpFpl5eNYegb.pgp
Description: PGP signature
- References:
- Re: [PATCH 1/3] Make cap default
- From: Kurt Garloff <[email protected]>
- Re: [PATCH 1/3] Make cap default
- From: James Morris <[email protected]>
- Re: [PATCH 1/3] Make cap default
- Prev by Date: A correct method to use the x86 breakpoint registers (DR0-7)
- Next by Date: Re: IBM HDAPS things are looking up (was: Re: [Hdaps-devel] Re: [ltp] IBM HDAPS Someone interested? (Accelerometer))
- Previous by thread: Re: [PATCH 1/3] Make cap default
- Next by thread: [PATCH 2a/3] Reorder the security stubs
- Index(es):