mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Ingo Oeser <ioe-lkml@rameria.de>
To: David Howells <dhowells@redhat.com>
Cc: sfr@canb.auug.org.au, jmorris@namei.org, hch@infradead.org,
	davem@davemloft.net, sfrench@us.ibm.com,
	linux-kernel@vger.kernel.org,
	linux-security-module@vger.kernel.org
Subject: Re: [PATCH 2/2] CRED: Introduce credential access wrappers
Date: Wed, 13 Aug 2008 00:59:19 +0200	[thread overview]
Message-ID: <200808130059.21049.ioe-lkml@rameria.de> (raw)
In-Reply-To: <9503.1218572852@redhat.com>

Hi David,

On Tuesday 12 August 2008, David Howells wrote:
> Ingo Oeser <ioe-lkml@rameria.de> wrote:
> 
> > Why macros? When introducing APIs using trivial inlines makes sure that 
> > the conversion is correct, type correct and side effect free for the callers.
> > Macros cannot ensure this without pain.
> 
> But macros don't care that you can't access current at this point.

Ok, if that is the only reason, please mention this in the commit message.
That would be enough for me to not wonder about this issue.

But I wonder how you solve this issue if the amount of code behinde your wrappers
grows.

If you have to take them out of line, it would give me a good indication
of the costs involved in the later bodies of these now trivial wrappers,
if you do it right away. 

That way you'll find missing includes and whatnot while converting existing code
to the trivial wrappers.


Best Regards

Ingo Oeser

      reply	other threads:[~2008-08-12 23:05 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-12 13:28 [PATCH 0/2] Introduce credentials API David Howells
2008-08-12 13:28 ` [PATCH 1/2] CRED: Alter XFS so as to avoid namespace collisions with upcoming COW creds David Howells
2008-08-12 22:55   ` James Morris
2008-08-12 23:01   ` Christoph Hellwig
2008-08-12 13:28 ` [PATCH 2/2] CRED: Introduce credential access wrappers David Howells
2008-08-12 19:02   ` Ingo Oeser
2008-08-12 20:27   ` David Howells
2008-08-12 22:59     ` Ingo Oeser [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=200808130059.21049.ioe-lkml@rameria.de \
    --to=ioe-lkml@rameria.de \
    --cc=davem@davemloft.net \
    --cc=dhowells@redhat.com \
    --cc=hch@infradead.org \
    --cc=jmorris@namei.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-security-module@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    --cc=sfrench@us.ibm.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®