From: Pavlos Parissis <pavlos.parissis@gmail.com>
To: Jan Kara <jack@suse.cz>
Cc: Guillaume Morin <guillaume@morinfr.org>,
stable@vger.kernel.org, decui@microsoft.com, jack@suse.com,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
mszeredi@redhat.com, Robert Kolchmeyer <rkolchmeyer@google.com>
Subject: Re: kernel panics with 4.14.X versions
Date: Thu, 19 Apr 2018 23:16:55 +0200 [thread overview]
Message-ID: <13d1dfff-e0dc-38a5-e2c5-87e8e1f2fb9d@gmail.com> (raw)
In-Reply-To: <20180419202302.vj2eu43hy77g5mv7@quack2.suse.cz>
[-- Attachment #1.1: Type: text/plain, Size: 1174 bytes --]
On 19/04/2018 10:23 μμ, Jan Kara wrote:
> On Wed 18-04-18 10:32:21, Pavlos Parissis wrote:
>> On 17/04/2018 02:12 μμ, Jan Kara wrote:
>>> On Tue 17-04-18 01:31:24, Pavlos Parissis wrote:
>>>> On 16/04/2018 04:40 μμ, Jan Kara wrote:
>>>
>>> <snip>
>>>
>>>>> How easily can you hit this?
>>>>
>>>> Very easily, I only need to wait 1-2 days for a crash to occur.
>>>
>>> I wouldn't call that very easily but opinions may differ :). Anyway it's
>>> good (at least for debugging) that it's reproducible.
>>>
>>
>> Unfortunately, I can't reproduce it, so waiting 1-2 days is the only
>> option I have.
>
> Good news guys, Robert has just spotted a bug which looks like what I'd
> expect can cause your lockups / crashes. I've merged his patch to my tree
> and will push it to Linus for -rc3 so eventually it should land in
> appropriate stable trees as well. If you are too eager to test it out, it
> is attached for you to try.
>
> Honza
>
Can I apply it on top of 4.14.32?
I am on vacation for the coming 11 days, so I can only provide feedback when I am back.
Thanks a lot for your support on this issue.
Cheers,
Pavlos
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2018-04-19 21:16 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-16 13:25 Guillaume Morin
2018-04-16 14:40 ` kernel panics with 4.14.X versions Jan Kara
2018-04-16 16:06 ` Guillaume Morin
2018-04-16 21:10 ` Dexuan Cui
2018-04-17 10:33 ` Greg KH
2018-04-17 11:48 ` Amir Goldstein
2018-04-17 12:03 ` Jan Kara
2018-04-17 17:42 ` Dexuan Cui
2018-04-16 23:31 ` Pavlos Parissis
2018-04-17 11:18 ` Pavlos Parissis
2018-04-17 12:04 ` Jan Kara
2018-04-17 12:12 ` Jan Kara
2018-04-18 8:32 ` Pavlos Parissis
2018-04-19 20:23 ` Jan Kara
2018-04-19 21:16 ` Pavlos Parissis [this message]
2018-04-19 21:24 ` Robert Kolchmeyer
2018-04-19 21:37 ` Dexuan Cui
2018-04-20 10:21 ` Jan Kara
2018-04-20 17:43 ` Dexuan Cui
-- strict thread matches above, loose matches on Subject: below --
2018-04-16 11:54 Pavlos Parissis
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=13d1dfff-e0dc-38a5-e2c5-87e8e1f2fb9d@gmail.com \
--to=pavlos.parissis@gmail.com \
--cc=decui@microsoft.com \
--cc=guillaume@morinfr.org \
--cc=jack@suse.com \
--cc=jack@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mszeredi@redhat.com \
--cc=rkolchmeyer@google.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.