linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kees Cook <keescook@chromium.org>
To: Martin Steigerwald <martin@lichtvoll.de>
Cc: LKML <linux-kernel@vger.kernel.org>,
	Andy Lutomirski <luto@amacapital.net>,
	Will Drewry <wad@chromium.org>,
	Mel Gorman <mgorman@techsingularity.net>
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 07:41:56 -0700	[thread overview]
Message-ID: <202006290739.8AB49B15@keescook> (raw)
In-Reply-To: <2293324.KF7j4Pszzj@merkaba>

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

-- 
Kees Cook

  reply	other threads:[~2020-06-29 19:28 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 [this message]
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=202006290739.8AB49B15@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 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).