Messages in this thread | | | Date | Mon, 10 Aug 2020 23:25:06 +0200 | From | Peter Zijlstra <> | Subject | Re: [PATCH] kunit: added lockdep support |
| |
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.
| |