From: David Miller <davem@davemloft.net>
To: netdev@vger.kernel.org
Cc: dborkman@redhat.com, ast@plumgrid.com, torvalds@vger.kernel.org
Subject: audit regression on x86 32-bit
Date: Sun, 13 Apr 2014 15:00:02 -0400 (EDT) [thread overview]
Message-ID: <20140413.150002.2000370566602899725.davem@davemloft.net> (raw)
Linus reported to me that Chrome stopped working on x86 32-bit for
him, and he gets a bunch of audit errors in his log:
audit: type=1326 audit(1397359304.356:28108): auid=500 uid=500
gid=500 ses=2 subj=unconfined_u:unconfined_r:chrome_sandbox_t:s0-s0:c0.c1023
pid=3677 comm="chrome" exe="/opt/google/chrome/chrome" sig=0
syscall=172 compat=0 ip=0xb2dd9852 code=0x30000
audit: type=1326 audit(1397359304.356:28109): auid=500 uid=500
gid=500 ses=2 subj=unconfined_u:unconfined_r:chrome_sandbox_t:s0-s0:c0.c1023
pid=3677 comm="chrome" exe="/opt/google/chrome/chrome" sig=0 syscall=5
compat=0 ip=0xb2dd9852 code=0x50000
He hasn't finished bisecting but it is starting to look like it's
the BPF changes that went into this merge window.
Daniel and Alexei can you guys look into this?
Thanks.
next reply other threads:[~2014-04-13 19:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-13 19:00 David Miller [this message]
2014-04-13 21:46 ` audit regression on x86 32-bit Daniel Borkmann
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=20140413.150002.2000370566602899725.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=ast@plumgrid.com \
--cc=dborkman@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=torvalds@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;
as well as URLs for NNTP newsgroup(s).