DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=rogers.com;
	b=l/zn6i0OJLbWGd5Xa8mRyXCOvLd/0OfId9IRW0zrDOAx2vUR8IxUozdLEpONam5jNcOZyhrTyIwSroRay6tg8c4Mg7INiEMkLnVnW505u+vRVs7oEPm15Exg5gHmynrsf98Pv5pG2n3s9K1XtqyIbkMcHcwUN9T9TdJd1JbP/Og=;
From: Shawn Starr <shawn.starr@rogers.com>
To: Kernel development list <linux-kernel@vger.kernel.org>
Subject: [3.18-rc1] Regression in userspace - Google Chrome
Date: Mon, 27 Oct 2014 10:08:02 -0400
Message-ID: <4344395.V0onCpLkaI@segfault>
Organization: sh0n.net
User-Agent: KMail/4.14.2 (Linux/3.17.1-303.fc21.x86_64; KDE/4.14.2; x86_64; ; )
MIME-Version: 1.0
Content-Transfer-Encoding: 7Bit
Content-Type: text/plain; charset="us-ascii"
Sender: linux-kernel-owner@vger.kernel.org

Hello kernel folks,

In -rc1, I had problems running Google Chrome with sandbox enabled by default. 
Chrome would start once, sometimes not run at all, setuid binary would be 
stuck in 'D' state.

Using my current kernel (kernel-3.17.1-303.fc21.x86_64) no such problems 
exist.  I know 3.18 is early in it's -rc cycle but this is a heads up if 
nobody else noticed.

Now that -rc2 is out and soon Fedora will have a -rc2 kernel for me to play 
with, I'll will see if this was just noise in the merge window.

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