From: Cyril Hrubis <chrubis@suse.cz>
To: Petr Vorel <pvorel@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 13:44:46 +0100 [thread overview]
Message-ID: <YiC4Pj1sH8UIHY7k@yuki> (raw)
In-Reply-To: <YiBcyvtqTX1CerM4@pevik>
Hi!
> > 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.
I guess that we still did not agree on exactly how this should be
handled or did we?
--
Cyril Hrubis
chrubis@suse.cz
WARNING: multiple messages have this Message-ID (diff)
From: Cyril Hrubis <chrubis@suse.cz>
To: Petr Vorel <pvorel@suse.cz>
Cc: linux-integrity@vger.kernel.org, Yael Tzur <yaelt@google.com>,
ltp@lists.linux.it
Subject: Re: [LTP] [PATCH v4] syscalls/keyctl09: test encrypted keys with provided decrypted data.
Date: Thu, 3 Mar 2022 13:44:46 +0100 [thread overview]
Message-ID: <YiC4Pj1sH8UIHY7k@yuki> (raw)
In-Reply-To: <YiBcyvtqTX1CerM4@pevik>
Hi!
> > 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.
I guess that we still did not agree on exactly how this should be
handled or did we?
--
Cyril Hrubis
chrubis@suse.cz
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2022-03-03 12:42 UTC|newest]
Thread overview: 24+ 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-02-23 20:07 ` [LTP] " Yael Tzur via ltp
2022-03-02 15:53 ` Cyril Hrubis
2022-03-02 15:53 ` Cyril Hrubis
2022-03-02 20:16 ` Yael Tzur
2022-03-02 20:16 ` Yael Tzur via ltp
2022-03-03 6:14 ` Petr Vorel
2022-03-03 6:14 ` Petr Vorel
2022-03-03 12:44 ` Cyril Hrubis [this message]
2022-03-03 12:44 ` Cyril Hrubis
2022-03-03 13:26 ` Petr Vorel
2022-03-03 13:26 ` Petr Vorel
2022-03-03 13:46 ` Cyril Hrubis
2022-03-03 13:46 ` Cyril Hrubis
2022-03-03 14:07 ` Petr Vorel
2022-03-03 14:07 ` Petr Vorel
2022-03-16 20:10 ` Yael Tzur
2022-03-16 20:10 ` Yael Tzur via ltp
2022-03-17 20:38 ` Petr Vorel
2022-03-17 20:38 ` Petr Vorel
2022-03-23 19:13 ` Petr Vorel
2022-03-23 19:13 ` Petr Vorel
2022-03-24 13:35 ` Cyril Hrubis
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=YiC4Pj1sH8UIHY7k@yuki \
--to=chrubis@suse.cz \
--cc=linux-integrity@vger.kernel.org \
--cc=ltp@lists.linux.it \
--cc=pvorel@suse.cz \
--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 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.