From: Kurt Garloff <garloff@suse.de>
To: Andreas Gruenbacher <agruen@suse.de>
Cc: Kurt Garloff <garloff@suse.de>,
Linux kernel list <linux-kernel@vger.kernel.org>,
James Morris <jmorris@redhat.com>, Chris Wright <chrisw@osdl.org>
Subject: Re: [PATCH] 2/5: LSM hooks rework
Date: Mon, 14 Feb 2005 19:30:04 +0100 [thread overview]
Message-ID: <20050214183004.GB9866@tpkurt.garloff.de> (raw)
In-Reply-To: <1108391432.2974.6.camel@winden.suse.de>
[-- Attachment #1: Type: text/plain, Size: 769 bytes --]
Hi Andreas,
On Mon, Feb 14, 2005 at 03:30:33PM +0100, Andreas Gruenbacher wrote:
> On Sun, 2005-02-13 at 22:11, Kurt Garloff wrote:
> > Rather than having every LSM hook twice, once for the case with
> > CONFIG_SECURITY enabled and once for the disabled case, put
> > everything in one inline function.
>
> The attached patch fixes compilation if CONFIG_SECURITY_NETWORK is
> turned off.
>
> > This reduces the chance of the two to go out of sync immensely.
>
> ... as it already happened with security_sk_free(). Also fixed in the
> attached patch.
Indeed. Though harmless fortunately ...
Thanks for fixing this up, I had overlooked the CONFIG_SECURITY_NETWORK
disabled case :(
Regards,
--
Kurt Garloff, Director SUSE Labs, Novell Inc.
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2005-02-14 18:30 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-13 21:05 [PATCH] 0/5: " Kurt Garloff
2005-02-13 21:10 ` [PATCH] 1/5: " Kurt Garloff
2005-02-13 21:11 ` [PATCH] 2/5: " Kurt Garloff
2005-02-13 21:11 ` [PATCH] 3/5: " Kurt Garloff
2005-02-13 21:12 ` [PATCH] 4/5: " Kurt Garloff
2005-02-13 21:12 ` [PATCH] 5/5: " Kurt Garloff
2005-02-14 16:50 ` James Morris
2005-02-14 23:23 ` Kurt Garloff
2005-02-14 16:54 ` [PATCH] 4/5: " Rik van Riel
2005-02-14 23:27 ` Kurt Garloff
2005-02-14 23:35 ` Rik van Riel
2005-02-14 14:30 ` [PATCH] 2/5: " Andreas Gruenbacher
2005-02-14 18:30 ` Kurt Garloff [this message]
2005-02-15 5:45 ` [PATCH] New " Kurt Garloff
2005-02-15 4:50 ` [PATCH] 0/5: " Chris Wright
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=20050214183004.GB9866@tpkurt.garloff.de \
--to=garloff@suse.de \
--cc=agruen@suse.de \
--cc=chrisw@osdl.org \
--cc=jmorris@redhat.com \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®