[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.LRH.1.10.0812112139340.25553@tundra.namei.org>
Date: Thu, 11 Dec 2008 21:41:20 +1100 (EST)
From: James Morris <jmorris@...ei.org>
To: Stephen Smalley <sds@...ho.nsa.gov>
cc: "Eric W. Biederman" <ebiederm@...ssion.com>,
David Miller <davem@...emloft.net>, adobriyan@...il.com,
auke-jan.h.kok@...el.com, akpm@...ux-foundation.org,
e1000-devel@...ts.sourceforge.net, netdev@...r.kernel.org,
eparis@...isplace.org
Subject: Re: [E1000-devel] networking probs in next-20081203
On Fri, 5 Dec 2008, Stephen Smalley wrote:
> I suspect we need the following un-tested diff to map all of these proc/
> filesystem types to "proc" for the policy lookup at filesystem mount
> time.
I finally got a bootable linux-next, but it seems that the proc/net patch
is no longer in there.
Any idea if it's coming back? The patch below looks ok, but it needs
testing (and I'd suggest perhaps including it any future version of the
proc/net patch).
> diff --git a/security/selinux/hooks.c b/security/selinux/hooks.c
> index 9155fa9..3c3ceb7 100644
> --- a/security/selinux/hooks.c
> +++ b/security/selinux/hooks.c
> @@ -703,7 +703,7 @@ static int selinux_set_mnt_opts(struct super_block *sb,
> sbsec->proc = 1;
>
> /* Determine the labeling behavior to use for this filesystem type. */
> - rc = security_fs_use(sb->s_type->name, &sbsec->behavior, &sbsec->sid);
> + rc = security_fs_use(sbsec->proc ? "proc" : sb->s_type->name, &sbsec->behavior, &sbsec->sid);
> if (rc) {
> printk(KERN_WARNING "%s: security_fs_use(%s) returned %d\n",
> __func__, sb->s_type->name, rc);
>
> --
> Stephen Smalley
> National Security Agency
>
--
James Morris
<jmorris@...ei.org>
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists