All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jiri Slaby <jirislaby@gmail.com>
To: Horst von Brand <vonbrand@inf.utfsm.cl>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	sds@tycho.nsa.gov, jmorris@namei.org, selinux@tycho.nsa.gov
Subject: Re: 2.6.17-rc1 compile failure
Date: Mon, 03 Apr 2006 17:15:56 +0159	[thread overview]
Message-ID: <44313C43.7070701@gmail.com> (raw)
In-Reply-To: <200604030521.k335LRu4018913@laptop11.inf.utfsm.cl>

[-- Attachment #1: Type: text/plain, Size: 935 bytes --]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Horst von Brand napsal(a):
> It ends with:
> 
>   CC      security/selinux/xfrm.o
>   security/selinux/xfrm.c: In function â??selinux_socket_getpeer_dgramâ??:
>   security/selinux/xfrm.c:284: error: â??struct sec_pathâ?? has no member named â??xâ??
>   security/selinux/xfrm.c: In function â??selinux_xfrm_sock_rcv_skbâ??:
>   security/selinux/xfrm.c:317: error: â??struct sec_pathâ?? has no member named â??xâ??
>   make[2]: *** [security/selinux/xfrm.o] Error 1
Could you test attached patch?

thanks,
- --
Jiri Slaby         www.fi.muni.cz/~xslaby
\_.-^-._   jirislaby@gmail.com   _.-^-._/
B67499670407CE62ACC8 22A032CC55C339D47A7E
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2.2 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org

iD8DBQFEMTxDMsxVwznUen4RAgLCAJ9WEAU018cecP1emeMZKfCTrttVeQCgric6
g9Cq+yh5IvmVJGHqlVsIEXs=
=9MLb
-----END PGP SIGNATURE-----

[-- Attachment #2: selinux-xfrm.txt --]
[-- Type: text/plain, Size: 1317 bytes --]

SELinux-xfrm-compilation-fix

sec_path struct no longer contains sec_decap_state struct, but only
xfrm_state.

Signed-off-by: Jiri Slaby <jirislaby@gmail.com>

---
commit 87b9e5f728ab1f5f805f1db9d96d569b1218b611
tree 60d080432a06f8bdddb8665a89dd825a33b2b01f
parent 9e4a4f43bab1268fc459295a673d00470d5e150d
author Jiri Slaby <ku@bellona.localdomain> Mon, 03 Apr 2006 17:11:07 +0159
committer Jiri Slaby <ku@bellona.localdomain> Mon, 03 Apr 2006 17:11:07 +0159

 security/selinux/xfrm.c |    4 ++--
 1 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/security/selinux/xfrm.c b/security/selinux/xfrm.c
index dfab6c8..abe99d8 100644
--- a/security/selinux/xfrm.c
+++ b/security/selinux/xfrm.c
@@ -281,7 +281,7 @@ u32 selinux_socket_getpeer_dgram(struct 
 		int i;
 
 		for (i = sp->len-1; i >= 0; i--) {
-			struct xfrm_state *x = sp->x[i].xvec;
+			struct xfrm_state *x = sp->xvec[i];
 			if (selinux_authorizable_xfrm(x)) {
 				struct xfrm_sec_ctx *ctx = x->security;
 				return ctx->ctx_sid;
@@ -314,7 +314,7 @@ int selinux_xfrm_sock_rcv_skb(u32 isec_s
 		 *  Only need to verify the existence of an authorizable sp.
 		 */
 		for (i = 0; i < sp->len; i++) {
-			struct xfrm_state *x = sp->x[i].xvec;
+			struct xfrm_state *x = sp->xvec[i];
 
 			if (x && selinux_authorizable_xfrm(x))
 				goto accept;

  reply	other threads:[~2006-04-03 15:16 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-03  5:21 2.6.17-rc1 compile failure Horst von Brand
2006-04-03 15:16 ` Jiri Slaby [this message]
2006-04-03 18:09   ` Horst von Brand
  -- strict thread matches above, loose matches on Subject: below --
2006-04-11 11:06 Jan Engelhardt

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=44313C43.7070701@gmail.com \
    --to=jirislaby@gmail.com \
    --cc=jmorris@namei.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sds@tycho.nsa.gov \
    --cc=selinux@tycho.nsa.gov \
    --cc=vonbrand@inf.utfsm.cl \
    /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.