Re: [REGRESSION] 5.8-rc3: seccomp crash with Chromium, QtWebEngine and related browsers: seccomp-bpf failure in syscall 0072

2020-06-29 Thread Kees Cook
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.ca...@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


[REGRESSION] 5.8-rc3: seccomp crash with Chromium, QtWebEngine and related browsers: seccomp-bpf failure in syscall 0072

2020-06-29 Thread Martin Steigerwald
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




Re: [REGRESSION] 5.8-rc3: seccomp crash with Chromium, QtWebEngine and related browsers: seccomp-bpf failure in syscall 0072

2020-06-29 Thread Kees Cook
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.ca...@redhat.com/#r

-- 
Kees Cook


Re: [REGRESSION] 5.8-rc3: seccomp crash with Chromium, QtWebEngine and related browsers: seccomp-bpf failure in syscall 0072

2020-06-29 Thread Mel Gorman
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.ca...@redhat.com/#r
> 

It's a definite problem. I've sent a revert but it hasn't hit lkml yet
for whatever reason.

-- 
Mel Gorman
SUSE Labs