From: Petr Vorel <pvorel@suse.cz>
To: Cyril Hrubis <chrubis@suse.cz>
Cc: Yael Tzur <yaelt@google.com>,
linux-integrity@vger.kernel.org, ltp@lists.linux.it
Subject: Re: [LTP] [PATCH v4] syscalls/keyctl09: test encrypted keys with provided decrypted data.
Date: Thu, 3 Mar 2022 07:14:34 +0100 [thread overview]
Message-ID: <YiBcyvtqTX1CerM4@pevik> (raw)
In-Reply-To: <Yh+S7JD2q8oalRoM@yuki>
Hi Cyril, Yael,
> Hi!
> The test looks good to me now.
> Reviewed-by: Cyril Hrubis <chrubis@suse.cz>
> Looking at the kernel counterpart it is still in the next tree. We
> usually wait until the kernel functionality is part of a kernel release
> in order to make sure that there are no changes done to the
> kernel-userspace API.
Good (last time I checked it wasn't there).
For my record:
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?h=next-20220302&id=cd3bc044af483422cc81a93f23c78c20c978b17c
> I this case I guess that in this case the change is so minimal that we
> can add this test into LTP once it reaches Linus tree.
Cyril, maybe we could finally merge our policy (waiting ack for you):
https://patchwork.ozlabs.org/project/ltp/patch/20220203101803.10204-1-rpalethorpe@suse.com/
and put keyctl09 into runtest/staging now.
Kind regards,
Petr
next prev parent reply other threads:[~2022-03-03 6:14 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-23 20:07 [PATCH v4] syscalls/keyctl09: test encrypted keys with provided decrypted data Yael Tzur
2022-03-02 15:53 ` [LTP] " Cyril Hrubis
2022-03-02 20:16 ` Yael Tzur
2022-03-03 6:14 ` Petr Vorel [this message]
2022-03-03 12:44 ` Cyril Hrubis
2022-03-03 13:26 ` Petr Vorel
2022-03-03 13:46 ` Cyril Hrubis
2022-03-03 14:07 ` Petr Vorel
2022-03-16 20:10 ` Yael Tzur
2022-03-17 20:38 ` Petr Vorel
2022-03-23 19:13 ` Petr Vorel
2022-03-24 13:35 ` Cyril Hrubis
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=YiBcyvtqTX1CerM4@pevik \
--to=pvorel@suse.cz \
--cc=chrubis@suse.cz \
--cc=linux-integrity@vger.kernel.org \
--cc=ltp@lists.linux.it \
--cc=yaelt@google.com \
/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;
as well as URLs for NNTP newsgroup(s).