linux-kernel - Re: [PATCH] selftests/livepatch: introduce tests

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <alpine.LSU.2.21.1804101625090.8026@pobox.suse.cz>
Date:   Tue, 10 Apr 2018 16:31:05 +0200 (CEST)
From:   Miroslav Benes <mbenes@...e.cz>
To:     Petr Mladek <pmladek@...e.com>
cc:     Joe Lawrence <joe.lawrence@...hat.com>,
        Josh Poimboeuf <jpoimboe@...hat.com>,
        live-patching@...r.kernel.org, linux-kernel@...r.kernel.org,
        lpechacek@...e.com, nstange@...e.de
Subject: Re: [PATCH] selftests/livepatch: introduce tests


> > > I love this.  Nice work!

Yes, it looks really good.

> > > As you and Petr discussed, it would be nice to get rid of some of the
> > > delays, and also the callback tests will be very important.
> > 
> > I've got v2 WIP that minimizes the delays, cleans up build flags, and
> > adds a basic shadow variable test.
> 
> Sounds great.
> 
> > Since these tests are based on top of Petr's current patchsets for
> > atomic replace and shadow variables, it probably makes sense for those
> > to merge first.  I can post test results to his patchsets if that helps.
> 
> Sounds good to me. We could synchronize the merge. But I think that it
> will not be a big deal if we would merge the atomic replace slightly
> earlier if the tests needed some more love.

Well, it depends. Josh wants the patch first and then atomic replace. So 
we can merge selftests for all features we currently have and tests for 
atomic replace could go with it.

> > These tests are basically a mash up of some of the tedious callback
> > Documentation and shadow variable sample livepatches.  Since there will
> > be a lot of duplication, should we just remove redundant doc/samples in
> > favor of these tests?
> 
> Yup, it does not make sense to maintain two copies of basically
> the same modules.

Yes, but I'd leave a basic sample module there (that is, the first sample 
we had should stay).

Libor and Nicolai from SUSE CCed. We have some internal tests as well and 
it would be great to join forces.

Regards,
Miroslav