From: Steve McIntyre <steve@einval.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: Jann Horn <jannh@google.com>,
John Johansen <john.johansen@canonical.com>,
Sasha Levin <sashal@kernel.org>,
stable@vger.kernel.org, 963493@bugs.debian.org
Subject: Re: Repeatable hard lockup running strace testsuite on 4.19.98+ onwards
Date: Fri, 26 Jun 2020 16:20:34 +0100 [thread overview]
Message-ID: <20200626152034.GA2950@unset.einval.com> (raw)
In-Reply-To: <20200626134518.GB32542@unset.einval.com>
On Fri, Jun 26, 2020 at 02:45:18PM +0100, Steve McIntyre wrote:
>Hey Greg,
>
>On Fri, Jun 26, 2020 at 03:41:32PM +0200, Greg KH wrote:
>>On Fri, Jun 26, 2020 at 12:35:58PM +0100, Steve McIntyre wrote:
>>>
>>> e58f543fc7c0926f31a49619c1a3648e49e8d233 is the first bad commit
>>> commit e58f543fc7c0926f31a49619c1a3648e49e8d233
>>> Author: Jann Horn <jannh@google.com>
>>> Date: Thu Sep 13 18:12:09 2018 +0200
>
>...
>
>>> Annoyingly, I can't reproduce this on my disparate other machines
>>> here, suggesting it's maybe(?) timing related.
>>>
>>> Hope this helps - happy to give more information, test things, etc.
>>
>>So if you just revert this one patch, all works well?
>
>Correct.
>
>>I've added the authors of the patch to the cc: list...
>>
>>Also, does this problem happen on Linus's tree?
>
>Just building to check that now...
Current head here (3e08a95294a4fb3702bb3d35ed08028433c37fe6) works fine.
--
Steve McIntyre, Cambridge, UK. steve@einval.com
The two hard things in computing:
* naming things
* cache invalidation
* off-by-one errors -- Stig Sandbeck Mathisen
next prev parent reply other threads:[~2020-06-26 15:21 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-26 11:35 Repeatable hard lockup running strace testsuite on 4.19.98+ onwards Steve McIntyre
2020-06-26 13:41 ` Greg KH
2020-06-26 13:45 ` Steve McIntyre
2020-06-26 15:20 ` Steve McIntyre [this message]
2020-06-26 14:25 ` Jann Horn
2020-06-26 16:50 ` Steve McIntyre
2020-06-26 17:29 ` John Johansen
2020-06-26 19:01 ` Steve McIntyre
2020-06-26 19:57 ` Sasha Levin
2020-06-26 17:52 ` Steve McIntyre
2020-06-26 18:27 ` Jann Horn
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=20200626152034.GA2950@unset.einval.com \
--to=steve@einval.com \
--cc=963493@bugs.debian.org \
--cc=gregkh@linuxfoundation.org \
--cc=jannh@google.com \
--cc=john.johansen@canonical.com \
--cc=sashal@kernel.org \
--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.