struct tee_param: revc -> recv.
TEE_IOC_SUPPL_SEND: typo introduced by copy-pasting, replace invalid
description with description from the according argument struct.
Signed-off-by: Elvira Khabirova <e.khabirova(a)omprussia.ru>
---
include/linux/tee_drv.h | 2 +-
include/uapi/linux/tee.h | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/include/linux/tee_drv.h b/include/linux/tee_drv.h
index d074302989dd..61557bc0e29f 100644
--- a/include/linux/tee_drv.h
+++ b/include/linux/tee_drv.h
@@ -85,7 +85,7 @@ struct tee_param {
* @close_session: close a session
* @invoke_func: invoke a trusted function
* @cancel_req: request cancel of an ongoing invoke or open
- * @supp_revc: called for supplicant to get a command
+ * @supp_recv: called for supplicant to get a command
* @supp_send: called for supplicant to send a response
* @shm_register: register shared memory buffer in TEE
* @shm_unregister: unregister shared memory buffer in TEE
diff --git a/include/uapi/linux/tee.h b/include/uapi/linux/tee.h
index b619f37ee03e..7546be5ed4f8 100644
--- a/include/uapi/linux/tee.h
+++ b/include/uapi/linux/tee.h
@@ -342,7 +342,7 @@ struct tee_iocl_supp_send_arg {
};
/**
- * TEE_IOC_SUPPL_SEND - Receive a request for a supplicant function
+ * TEE_IOC_SUPPL_SEND - Send a response to a received request
*
* Takes a struct tee_ioctl_buf_data which contains a struct
* tee_iocl_supp_send_arg followed by any array of struct tee_param
--
2.28.0
Since the addition of session's client UUID generation via commit [1],
login via REE kernel method was disallowed. So fix that via passing
nill UUID in case of TEE_IOCTL_LOGIN_REE_KERNEL method as well.
Fixes: e33bcbab16d1 ("tee: add support for session's client UUID generation") [1]
Signed-off-by: Sumit Garg <sumit.garg(a)linaro.org>
---
drivers/tee/tee_core.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/drivers/tee/tee_core.c b/drivers/tee/tee_core.c
index 64637e0..2f6199e 100644
--- a/drivers/tee/tee_core.c
+++ b/drivers/tee/tee_core.c
@@ -200,7 +200,8 @@ int tee_session_calc_client_uuid(uuid_t *uuid, u32 connection_method,
int name_len;
int rc;
- if (connection_method == TEE_IOCTL_LOGIN_PUBLIC) {
+ if (connection_method == TEE_IOCTL_LOGIN_PUBLIC ||
+ connection_method == TEE_IOCTL_LOGIN_REE_KERNEL) {
/* Nil UUID to be passed to TEE environment */
uuid_copy(uuid, &uuid_null);
return 0;
--
2.7.4
[BCC all OP-TEE maintainers]
Hi OP-TEE maintainers & contributors,
OP-TEE 3.11.0 is scheduled to be released on Friday, October 16th. So,
now is a good time to start testing the master branch on the various
platforms and report/fix any bugs.
The GitHub pull request for collecting Tested-by tags or any other
comment is https://github.com/OP-TEE/optee_os/pull/4101.
As usual, I will create a release candidate tag one week before the
release date for final testing.
Thanks!
Regards,
--
Jerome
Hi Joakim,
On Tue, Sep 29, 2020 at 12:00 PM Joakim Bech via OP-TEE <
op-tee(a)lists.trustedfirmware.org> wrote:
> Hi Jorge,
>
> On Tue, 29 Sep 2020 at 11:49, Jorge Ramirez <jorge(a)foundries.io> wrote:
>
> > Hi Joakim
> >
> > Shall we discuss how we want to extend the criptodriver API were
> different
> > algorithms can be taken from different ciphers?
> > And maybe also how to communicate other than using the github frontend? I
> > think this is useful in the case of relatively complex PR.
> >
> Sounds good to me, I'm adding that to the agenda. This concludes that there
> _will_ be a LOC meeting tomorrow Wednesday 30th Sept @ 16.00 (UTC+2).
>
> Again, connection details etc can be found in the meeting notes document:
> http://bit.ly/loc-notes
Apologies for not joining, I had a calendar issue (my fault!).
Since the date for the next release is confirmed and coming soon, I will
create the release PR and send the notification email shortly.
Thanks,
--
Jerome
Hi Joakim
Shall we discuss how we want to extend the criptodriver API were different
algorithms can be taken from different ciphers?
And maybe also how to communicate other than using the github frontend? I
think this is useful in the case of relatively complex PR.
thanks
Jorge
On Mon, Sep 28, 2020 at 1:08 PM Joakim Bech via OP-TEE <
op-tee(a)lists.trustedfirmware.org> wrote:
> Hi,
>
> Just a reminder, I have seen no suggestions for topics and if I hear
> nothing until noon tomorrow 29/9 (UTC), then I'll cancel the September
> meeting.
>
> Regards,
> Joakim
>
>
> On Thu, 17 Sep 2020 at 11:19, Joakim Bech <joakim.bech(a)linaro.org> wrote:
>
> > Hi,
> >
> > LOC monthly meeting is planned to take place Sept 30 @ 16.00 (UTC+2).
> > Connection details can be found in the meeting notes document (link
> below).
> >
> > This email is a request to gather topics to discuss. If there are no
> > suggestions, then there will be no meeting (announced in this email
> thread,
> > if that's the case). To suggest a topic, either reply to this email
> thread
> > or add your topic directly into the meeting notes (or do both).
> >
> > Meeting details:
> > ---------------
> > Date/time: Wednesday Sept 30th(a)16.00 (UTC+2)
> > https://everytimezone.com/s/92bd296e
> > Invitation/connection details: In the meeting notes
> > Meeting notes: http://bit.ly/loc-notes
> > Project page: https://www.linaro.org/projects/#LOC
> >
> > Regards,
> > Joakim on behalf of the Linaro OP-TEE team
> >
>
Hi,
LOC monthly meeting is planned to take place Sept 30 @ 16.00 (UTC+2).
Connection details can be found in the meeting notes document (link below).
This email is a request to gather topics to discuss. If there are no
suggestions, then there will be no meeting (announced in this email thread,
if that's the case). To suggest a topic, either reply to this email thread
or add your topic directly into the meeting notes (or do both).
Meeting details:
---------------
Date/time: Wednesday Sept 30th(a)16.00 (UTC+2)
https://everytimezone.com/s/92bd296e
Invitation/connection details: In the meeting notes
Meeting notes: http://bit.ly/loc-notes
Project page: https://www.linaro.org/projects/#LOC
Regards,
Joakim on behalf of the Linaro OP-TEE team