linux-kernel - Re: SELinux change in 3.13 causes sync hang

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Tue, 10 Dec 2013 15:11:31 -0500
From:	Eric Paris <eparis@...hat.com>
To:	Josh Boyer <jwboyer@...oraproject.org>
Cc:	Anand Avati <avati@...hat.com>, James Morris <jmorris@...ei.org>,
	Eric Sandeen <sandeen@...hat.com>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	"Linux-Kernel@...r. Kernel. Org" <linux-kernel@...r.kernel.org>
Subject: Re: SELinux change in 3.13 causes sync hang

On Tue, 2013-12-10 at 15:06 -0500, Josh Boyer wrote:
> We've had a report[1] in Fedora of sync(1) hanging after logging into
> GNOME and running the command in a terminal.  I was able to recreate
> this on my local system and did a git bisect.  The bisect blames:
> 
> commit 102aefdda4d8275ce7d7100bc16c88c74272b260
> Author: Anand Avati <avati@...hat.com>
> Date:   Tue Apr 16 18:56:19 2013 -0400
> 
>     selinux: consider filesystem subtype in policies
> 

I think this should revert cleanly (and if so is what we should do).
Josh is testing that right now...

Anand, I know policy ships with:
fs_use_xattr fuse.glusterfs gen_context(system_u:object_r:fs_t,s0);
So we must have a bug where other fuse filesystems are tripping on this
rule.  Since we are trying to use xattrs on a gvfs filesystem.

/me still grows that fuse refuses to respond to xattr requests until
mount(8) (that's right mount(8) not even mount(3) completes)

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/