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 [thread overview]
Message-ID: <4344395.V0onCpLkaI@segfault> (raw)
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
reply other threads:[~2014-10-27 14:15 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4344395.V0onCpLkaI@segfault \
--to=shawn.starr@rogers.com \
--cc=linux-kernel@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox