From: Peter Zijlstra <peterz@infradead.org>
To: Uriel Guajardo <urielguajardo@google.com>
Cc: Brendan Higgins <brendanhiggins@google.com>,
mingo@redhat.com, will@kernel.org,
Uriel Guajardo <urielguajardojr@gmail.com>,
"open list:KERNEL SELFTEST FRAMEWORK"
<linux-kselftest@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] kunit: added lockdep support
Date: Mon, 10 Aug 2020 23:25:06 +0200 [thread overview]
Message-ID: <20200810212506.GH3982@worktop.programming.kicks-ass.net> (raw)
In-Reply-To: <CAG30EefjgzOMePHA2tQ-UmAw5_mnLDoS2hJH6z3nidNC8n8+Lg@mail.gmail.com>
On Mon, Aug 10, 2020 at 04:17:42PM -0500, Uriel Guajardo wrote:
> On Mon, Aug 10, 2020 at 3:35 PM Brendan Higgins
> <brendanhiggins@google.com> wrote:
> >
> > On Thu, Aug 6, 2020 at 1:43 PM Uriel Guajardo <urielguajardo@google.com> wrote:
> > >
> > > On Thu, Aug 6, 2020 at 3:37 PM Uriel Guajardo <urielguajardojr@gmail.com> wrote:
> > > >
> > > > From: Uriel Guajardo <urielguajardo@google.com>
> > > >
> > > > KUnit tests will now fail if lockdep detects an error during a test
> > > > case.
> > > >
> > > > The idea comes from how lib/locking-selftest [1] checks for lock errors: we
> > > > first if lock debugging is turned on. If not, an error must have
> > > > occurred, so we fail the test and restart lockdep for the next test case.
> > > >
> > > > Like the locking selftests, we also fix possible preemption count
> > > > corruption from lock bugs.
> >
> > Sorry, just noticed: You probably want to send this to some of the
> > lockdep maintainers or the maintainers of the kselftest for lockdep.
> >
>
> Thanks for the reminder. CC'ed lockdep maintainers.
Please resend as a whole, this is an unreadable mess.
next prev parent reply other threads:[~2020-08-10 21:25 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-06 20:37 [PATCH] kunit: added lockdep support Uriel Guajardo
2020-08-06 20:43 ` Uriel Guajardo
2020-08-10 20:35 ` Brendan Higgins
2020-08-10 21:17 ` Uriel Guajardo
2020-08-10 21:25 ` Peter Zijlstra [this message]
2020-08-10 20:34 ` Brendan Higgins
-- strict thread matches above, loose matches on Subject: below --
2020-08-10 21:32 Uriel Guajardo
2020-08-10 21:43 ` Peter Zijlstra
2020-08-11 17:03 ` Uriel Guajardo
2020-08-11 19:05 ` peterz
2020-08-11 22:22 ` Uriel Guajardo
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=20200810212506.GH3982@worktop.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=brendanhiggins@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=urielguajardo@google.com \
--cc=urielguajardojr@gmail.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 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.