Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
Subject: Re: kernel 4.14.x crash around fsnotify_mark_connector
To:     Jan Kara <jack@suse.cz>
Cc:     mszeredi@redhat.com, amir73il@gmail.com,
        linux-kernel@vger.kernel.org, stable@vger.kernel.org
References: <e7323798-3175-3d27-fdd1-349f1422cb26@gmail.com>
 <20180417140231.75fi4ek2q77qilta@quack2.suse.cz>
From:   Pavlos Parissis <pavlos.parissis@gmail.com>
Message-ID: <3016af7f-97f0-e28d-96cd-e49fada3e88d@gmail.com>
Date:   Tue, 17 Apr 2018 16:15:07 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101
 Thunderbird/52.6.0
MIME-Version: 1.0
In-Reply-To: <20180417140231.75fi4ek2q77qilta@quack2.suse.cz>
Content-Type: multipart/signed; micalg=pgp-sha256;
 protocol="application/pgp-signature";
 boundary="U4xveoVe93KwCD4ioJf56f49MGuONfZfq"
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--U4xveoVe93KwCD4ioJf56f49MGuONfZfq
Content-Type: multipart/mixed; boundary="pliiOaWIfp47bu4mmtRCZwtgX9dBeXHV4";
 protected-headers="v1"
From: Pavlos Parissis <pavlos.parissis@gmail.com>
To: Jan Kara <jack@suse.cz>
Cc: mszeredi@redhat.com, amir73il@gmail.com, linux-kernel@vger.kernel.org,
 stable@vger.kernel.org
Message-ID: <3016af7f-97f0-e28d-96cd-e49fada3e88d@gmail.com>
Subject: Re: kernel 4.14.x crash around fsnotify_mark_connector
References: <e7323798-3175-3d27-fdd1-349f1422cb26@gmail.com>
 <20180417140231.75fi4ek2q77qilta@quack2.suse.cz>
In-Reply-To: <20180417140231.75fi4ek2q77qilta@quack2.suse.cz>

--pliiOaWIfp47bu4mmtRCZwtgX9dBeXHV4
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: quoted-printable

On 17/04/2018 04:02 =CE=BC=CE=BC, Jan Kara wrote:
> On Tue 17-04-18 12:39:32, Pavlos Parissis wrote:
>> In one of our production servers where we run kernel version 4.14.32, =
I noticed
>> the following:
>=20
> OK, I was looking into this for some time and couldn't find a problem i=
n
> 4.14.32 code. Can you try running a kernel with CONFIG_DEBUG_SLAB and
> CONFIG_DEBUG_PAGEALLOC enabled to hopefully catch the problem earlier?
> Thanks!
>=20

I can certainly do that, but I can't reproduce that specific crash. So, i=
t may
take days before we get a similar crash. Having said that, the soft locku=
p issue,
which I mentioned in another thread, happens once per day, so I hope runn=
ing a
kernel with those debug settings will help you.

Cheers,
Pavlos


--pliiOaWIfp47bu4mmtRCZwtgX9dBeXHV4--

--U4xveoVe93KwCD4ioJf56f49MGuONfZfq
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQIcBAEBCAAGBQJa1gFsAAoJEIP8ktofcXa5NyAP/2TLllQtoWDeIM42THZwHmEB
KxqiXxA4mnDCUvnMxcxNxTpoZBfqDzEU3qTZ5Bjsp2N9MFKWf+IjxSuTb1hEGp9o
kumkUoNS3ZaB/WjV5kHvOGsmcOUK+XV0yzMQEh5XwOPr9L7o00QBk6TS4RJvQWv8
zbGZabigMQVgfWWXwJJShMPrOPcKfaRAL7xwzfAp0BcVwmQa2kXSgBGOlYuYWveW
UhrWsWERU3BOR+f7UROdQsE1pX3m6/Tye1YREPkoYk+HHA9yHWoMtc1QNU+qxSeq
ow89Un1odPhKOMRB5PgsK8hgg5VWZ5w6P9T8/3fIs2KLK28a3iiXFcz96lfY8jY1
N4rERLjPN8F/pSTZC+3UKezyGhADZuNd9vuKxs7CHC9ooiv9CqcvaMUE9E4J+qPA
gxG1FgzVjhwg8l9RsnrMbe6khHWuFlu/YmkfkvBb/Q+zZanEP0f9Xt+qx13IZ0IF
MariVX2GsfWR+v5EEno0XmEGHowxWuuCd6ZAn26ouW6NDLK92YgWN+W8evO1cvK9
87hZELxhGKI4xkzgUrbQDbmsMydRyMxbifqZqzGdNQFd+21HPgOk+ZpL5wCccalB
hPyPl3M3NPwAxDQfufjNj2qg8er4VRkzLBI8m4QDMwSABviNniy1j8w1wK9U0uCE
mjVkgGLdZPD9iRzxw9VB
=61O7
-----END PGP SIGNATURE-----

--U4xveoVe93KwCD4ioJf56f49MGuONfZfq--