[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20200629182014.GJ26507@quack2.suse.cz>
Date: Mon, 29 Jun 2020 20:20:14 +0200
From: Jan Kara <jack@...e.cz>
To: Jörg Otte <jrg.otte@...il.com>
Cc: Mel Gorman <mgorman@...hsingularity.net>, Jan Kara <jack@...e.cz>,
Linus Torvalds <torvalds@...ux-foundation.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: segmentation faults with kernels >v5.8-rc2
Hello!
On Mon 29-06-20 15:58:50, Jörg Otte wrote:
> I frequently get segmentation faults in newer kernel >v5.8-rc2 e.g.
> Chrome_ChildIOT[1298]: segfault at 40d048 ip 000056111a41970d sp
> 00007fdced6931b0 error 6 in chrome[561115f64000+785b000]
>
> Bisection gave me the following
> first bad commit:
>
> e9c15badbb7b20ccdbadf5da14e0a68fbad51015 is the first bad commit
> commit e9c15badbb7b20ccdbadf5da14e0a68fbad51015
> Author: Mel Gorman <mgorman@...hsingularity.net>
> Date: Mon Jun 15 13:13:58 2020 +0100
>
> fs: Do not check if there is a fsnotify watcher on pseudo inodes
> ...
>
> I double checked by reverting this commit on top of v5.8-rc3 and the
> segmentation faults are gone.
We've already reverted that commit today... Thanks for report!
Honza
--
Jan Kara <jack@...e.com>
SUSE Labs, CR
Powered by blists - more mailing lists