From: Petr Mladek <pmladek@suse.com>
To: Miroslav Benes <mbenes@suse.cz>
Cc: "Joe Lawrence" <joe.lawrence@redhat.com>,
live-patching@vger.kernel.org, linux-kselftest@vger.kernel.org,
linux-kernel@vger.kernel.org, "Jiri Kosina" <jikos@kernel.org>,
"Josh Poimboeuf" <jpoimboe@redhat.com>,
"Libor Pecháček" <lpechacek@suse.com>,
"Nicolai Stange" <nstange@suse.de>,
"Artem Savkov" <asavkov@redhat.com>
Subject: Re: [PATCH v3] selftests/livepatch: introduce tests
Date: Mon, 16 Apr 2018 17:02:30 +0200 [thread overview]
Message-ID: <20180416150230.6ys6ya7alpodxp3d@pathway.suse.cz> (raw)
In-Reply-To: <alpine.LSU.2.21.1804161329040.23118@pobox.suse.cz>
On Mon 2018-04-16 13:33:55, Miroslav Benes wrote:
> On Fri, 13 Apr 2018, Joe Lawrence wrote:
> > Thanks for reviewing. I'll hold off on posting v4 until Petr (and
> > others) get a chance to comment. Perhaps there are other tests that
> > would be helpful?
> I think it would be useful to have tests for a stack checking and a
> consistency. Nicolai has written some lately for our internal testing, but
> it would take some time to transform them appropriately, I think.
The future of the stack handling is not clear at the moment. We should
wait how the discussion goes before spending time on test cases for
the current behavior.
Best Regards,
Petr
next prev parent reply other threads:[~2018-04-16 15:02 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-12 14:54 [PATCH v3] Add livepatch kselftests Joe Lawrence
2018-04-12 14:54 ` [PATCH v3] selftests/livepatch: introduce tests Joe Lawrence
2018-04-12 21:36 ` Josh Poimboeuf
2018-04-13 11:20 ` Miroslav Benes
2018-04-13 20:52 ` Joe Lawrence
2018-04-16 11:33 ` Miroslav Benes
2018-04-16 15:02 ` Petr Mladek [this message]
2018-04-17 8:06 ` Miroslav Benes
2018-04-17 13:25 ` Joe Lawrence
2018-04-16 12:49 ` Petr Mladek
2018-04-20 12:56 ` Libor Pechacek
2018-04-23 14:43 ` Joe Lawrence
2018-04-24 15:50 ` Joe Lawrence
2018-04-24 17:19 ` Libor Pechacek
2018-04-24 17:35 ` Libor Pechacek
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=20180416150230.6ys6ya7alpodxp3d@pathway.suse.cz \
--to=pmladek@suse.com \
--cc=asavkov@redhat.com \
--cc=jikos@kernel.org \
--cc=joe.lawrence@redhat.com \
--cc=jpoimboe@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=live-patching@vger.kernel.org \
--cc=lpechacek@suse.com \
--cc=mbenes@suse.cz \
--cc=nstange@suse.de \
/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®