From: Greg KH <greg@kroah.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>,
Roman Zippel <zippel@linux-m68k.org>,
linux-kernel@vger.kernel.org, linux-security-module@wirex.com
Subject: Re: [BK PATCH] LSM changes for 2.5.27
Date: Wed, 24 Jul 2002 12:56:17 -0700 [thread overview]
Message-ID: <20020724195617.GD11384@kroah.com> (raw)
In-Reply-To: <1027430194.31782.125.camel@irongate.swansea.linux.org.uk>
On Tue, Jul 23, 2002 at 02:16:34PM +0100, Alan Cox wrote:
> On Tue, 2002-07-23 at 09:16, Roman Zippel wrote:
> > Hi,
> >
> > On Mon, 22 Jul 2002, Greg KH wrote:
> >
> > > + error = security_ops->inode_setattr(dentry, attr);
> >
> > Am I the only one who'd like to see this as an inline function?
> > 1. It can be optimized away.
> > 2. It's easier to read.
Yes, I've considered it. I might still wrap them in a inline function
if people _really_ don't like the look of them.
> You are not the only one. At the kernel summit there were discussions
> about both wrapping the few performance impacting ones in ifdefs, and/or
> using dynamic patching.
Yes, for the hooks that might affect performance (like the network ones)
they will probably be wrapped in inline functions, and controlled by a
config option.
thanks,
greg k-h
prev parent reply other threads:[~2002-07-24 19:53 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-23 0:37 [BK PATCH] LSM changes for 2.5.27 Greg KH
2002-07-23 0:38 ` Greg KH
2002-07-23 0:39 ` Greg KH
2002-07-23 0:39 ` Greg KH
2002-07-23 0:39 ` Greg KH
2002-07-23 0:40 ` Greg KH
2002-07-23 0:40 ` Greg KH
2002-07-23 0:40 ` Greg KH
2002-07-23 0:43 ` Greg KH
2002-07-23 0:44 ` Greg KH
2002-07-23 8:16 ` Roman Zippel
2002-07-23 13:16 ` Alan Cox
2002-07-24 19:56 ` Greg KH [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=20020724195617.GD11384@kroah.com \
--to=greg@kroah.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@wirex.com \
--cc=zippel@linux-m68k.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox