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
Subject: Re: kernel 4.14.x crash around fsnotify_mark_connector
Date: Tue, 17 Apr 2018 16:15:07 +0200 [thread overview]
Message-ID: <3016af7f-97f0-e28d-96cd-e49fada3e88d@gmail.com> (raw)
In-Reply-To: <20180417140231.75fi4ek2q77qilta@quack2.suse.cz>
[-- Attachment #1.1: Type: text/plain, Size: 755 bytes --]
On 17/04/2018 04:02 μμ, 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:
>
> OK, I was looking into this for some time and couldn't find a problem in
> 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!
>
I can certainly do that, but I can't reproduce that specific crash. So, it may
take days before we get a similar crash. Having said that, the soft lockup issue,
which I mentioned in another thread, happens once per day, so I hope running a
kernel with those debug settings will help you.
Cheers,
Pavlos
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2018-04-17 14:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-17 10:39 kernel 4.14.x crash around fsnotify_mark_connector Pavlos Parissis
2018-04-17 12:22 ` Jan Kara
2018-04-17 14:02 ` Jan Kara
2018-04-17 14:15 ` Pavlos Parissis [this message]
2018-04-17 15:58 ` Jan Kara
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=3016af7f-97f0-e28d-96cd-e49fada3e88d@gmail.com \
--to=pavlos.parissis@gmail.com \
--cc=amir73il@gmail.com \
--cc=jack@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=mszeredi@redhat.com \
--cc=stable@vger.kernel.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