From: Peter Zijlstra <peterz@infradead.org>
To: Jim Cromie <jim.cromie@gmail.com>
Cc: linux-kernel@vger.kernel.org, Ingo Molnar <mingo@redhat.com>,
Will Deacon <will@kernel.org>,
Mark Rutland <mark.rutland@arm.com>
Subject: Re: [PATCH] locking-selftest: add option to proceed through unexpected failures
Date: Tue, 17 Nov 2020 11:02:56 +0100 [thread overview]
Message-ID: <20201117100256.GC3121406@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <20201113230048.1200162-1-jim.cromie@gmail.com>
On Fri, Nov 13, 2020 at 04:00:48PM -0700, Jim Cromie wrote:
> Locking selftest is currently (v.5.10-rc3) seeing 14 unexpected failures.
> Add option to not disable debug_locks, so as to let it reveal any
> locking flaws in new unrelated work.
I'm assuming this is the arm64 fallout? Mark anything I can do to help
you there?
The reasoning doesn't make sense though; if it can't pass the selftest,
then why would you trust any further reports?
next prev parent reply other threads:[~2020-11-17 10:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-13 23:00 Jim Cromie
2020-11-17 10:02 ` Peter Zijlstra [this message]
2020-11-24 21:27 ` jim.cromie
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=20201117100256.GC3121406@hirez.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=jim.cromie@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mingo@redhat.com \
--cc=will@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
all inboxes | Powered by JetHome®