From: Kees Cook <keescook@chromium.org>
To: Mel Gorman <mgorman@techsingularity.net>
Cc: Martin Steigerwald <martin@lichtvoll.de>,
LKML <linux-kernel@vger.kernel.org>,
Andy Lutomirski <luto@amacapital.net>,
Will Drewry <wad@chromium.org>
Subject: Re: [REGRESSION] 5.8-rc3: seccomp crash with Chromium, QtWebEngine and related browsers: seccomp-bpf failure in syscall 0072
Date: Mon, 29 Jun 2020 08:32:55 -0700 [thread overview]
Message-ID: <202006290831.E9E695450@keescook> (raw)
In-Reply-To: <20200629150807.GB3183@techsingularity.net>
On Mon, Jun 29, 2020 at 04:08:07PM +0100, Mel Gorman wrote:
> On Mon, Jun 29, 2020 at 07:41:56AM -0700, Kees Cook wrote:
> > On Mon, Jun 29, 2020 at 11:08:10AM +0200, Martin Steigerwald wrote:
> > > 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.
> >
> > Hi,
> >
> > It looks like this is from e9c15badbb7b ("fs: Do not check if there is a
> > fsnotify watcher on pseudo inodes")
> >
> > Currently being discussed here:
> > https://lore.kernel.org/lkml/7b4aa1e985007c6d582fffe5e8435f8153e28e0f.camel@redhat.com/#r
> >
>
> It's a definite problem. I've sent a revert but it hasn't hit lkml yet
> for whatever reason.
Okay, thanks! (Yeah, I think vger might be stuck?)
--
Kees Cook
prev parent reply other threads:[~2020-06-29 21:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-29 9:08 [REGRESSION] 5.8-rc3: seccomp crash with Chromium, QtWebEngine and related browsers: seccomp-bpf failure in syscall 0072 Martin Steigerwald
2020-06-29 14:41 ` Kees Cook
2020-06-29 15:08 ` Mel Gorman
2020-06-29 15:32 ` Kees Cook [this message]
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=202006290831.E9E695450@keescook \
--to=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@amacapital.net \
--cc=martin@lichtvoll.de \
--cc=mgorman@techsingularity.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.