From: James Morris <jmorris@namei.org>
To: Paul Moore <paul.moore@hp.com>
Cc: linux-security-module@vger.kernel.org, netdev@vger.kernel.org,
selinux@tycho.nsa.gov
Subject: Re: [RFC PATCH v2 2/2] LSM: Make the Labeled IPsec hooks more stack friendly
Date: Fri, 11 Apr 2008 08:08:50 +1000 (EST) [thread overview]
Message-ID: <Xine.LNX.4.64.0804110808080.1313@us.intercode.com.au> (raw)
In-Reply-To: <20080409205044.26774.12364.stgit@flek.lan>
On Wed, 9 Apr 2008, Paul Moore wrote:
> The xfrm_get_policy() and xfrm_add_pol_expire() put some rather large structs
> on the stack to work around the LSM API. This patch attempts to fix that
> problem by changing the LSM API to require only the relevant "security"
> pointers instead of the entire SPD entry; we do this for all of the
> security_xfrm_policy*() functions to keep things consistent.
>
> Signed-off-by: Paul Moore <paul.moore@hp.com>
Acked-by: James Morris <jmorris@namei.org>
--
James Morris
<jmorris@namei.org>
--
This message was distributed to subscribers of the selinux mailing list.
If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov with
the words "unsubscribe selinux" without quotes as the message.
WARNING: multiple messages have this Message-ID (diff)
From: James Morris <jmorris@namei.org>
To: Paul Moore <paul.moore@hp.com>
Cc: linux-security-module@vger.kernel.org, netdev@vger.kernel.org,
selinux@tycho.nsa.gov
Subject: Re: [RFC PATCH v2 2/2] LSM: Make the Labeled IPsec hooks more stack friendly
Date: Fri, 11 Apr 2008 08:08:50 +1000 (EST) [thread overview]
Message-ID: <Xine.LNX.4.64.0804110808080.1313@us.intercode.com.au> (raw)
In-Reply-To: <20080409205044.26774.12364.stgit@flek.lan>
On Wed, 9 Apr 2008, Paul Moore wrote:
> The xfrm_get_policy() and xfrm_add_pol_expire() put some rather large structs
> on the stack to work around the LSM API. This patch attempts to fix that
> problem by changing the LSM API to require only the relevant "security"
> pointers instead of the entire SPD entry; we do this for all of the
> security_xfrm_policy*() functions to keep things consistent.
>
> Signed-off-by: Paul Moore <paul.moore@hp.com>
Acked-by: James Morris <jmorris@namei.org>
--
James Morris
<jmorris@namei.org>
next prev parent reply other threads:[~2008-04-10 22:09 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-09 20:50 [RFC PATCH v2 0/2] Labeled networking patches for 2.6.26 Paul Moore
2008-04-09 20:50 ` Paul Moore
2008-04-09 20:50 ` [RFC PATCH v2 1/2] NetLabel: Allow passing the LSM domain as a shared pointer Paul Moore
2008-04-09 20:50 ` Paul Moore
2008-04-10 22:06 ` James Morris
2008-04-10 22:06 ` James Morris
2008-04-09 20:50 ` [RFC PATCH v2 2/2] LSM: Make the Labeled IPsec hooks more stack friendly Paul Moore
2008-04-09 20:50 ` Paul Moore
2008-04-10 22:08 ` James Morris [this message]
2008-04-10 22:08 ` James Morris
2008-04-10 21:25 ` [RFC PATCH v2 0/2] Labeled networking patches for 2.6.26 Paul Moore
2008-04-10 21:25 ` Paul Moore
2008-04-10 22:04 ` James Morris
2008-04-10 22:04 ` James Morris
2008-04-10 22:12 ` Paul Moore
2008-04-10 22:12 ` Paul Moore
2008-04-10 22:47 ` David Miller
2008-04-13 2:18 ` David Miller
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=Xine.LNX.4.64.0804110808080.1313@us.intercode.com.au \
--to=jmorris@namei.org \
--cc=linux-security-module@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=paul.moore@hp.com \
--cc=selinux@tycho.nsa.gov \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.