From: Martin Steigerwald <martin@lichtvoll.de>
To: LKML <linux-kernel@vger.kernel.org>
Cc: Andy Lutomirski <luto@amacapital.net>,
Kees Cook <keescook@chromium.org>, Will Drewry <wad@chromium.org>
Subject: [REGRESSION] 5.8-rc3: seccomp crash with Chromium, QtWebEngine and related browsers: seccomp-bpf failure in syscall 0072
Date: Mon, 29 Jun 2020 11:08:10 +0200 [thread overview]
Message-ID: <2293324.KF7j4Pszzj@merkaba> (raw)
Dear Andy, Kees, Will, dear kernel community,
With 5.8-rc3 there is a seccomp related crash which prevents Chromium and
QtWebEngine from starting:
Bug 208369 - seccomp crash with Chromium, QtWebEngine and related browsers: seccomp-bpf failure in syscall 0072
https://bugzilla.kernel.org/show_bug.cgi?id=208369
Reverting to 5.8-rc2 fixes the issue.
Best,
--
Martin
next reply other threads:[~2020-06-29 20:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-29 9:08 Martin Steigerwald [this message]
2020-06-29 14:41 ` [REGRESSION] 5.8-rc3: seccomp crash with Chromium, QtWebEngine and related browsers: seccomp-bpf failure in syscall 0072 Kees Cook
2020-06-29 15:08 ` Mel Gorman
2020-06-29 15:32 ` Kees Cook
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=2293324.KF7j4Pszzj@merkaba \
--to=martin@lichtvoll.de \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@amacapital.net \
--cc=wad@chromium.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).