Skip to content

Third service in an SNF partition causes panic when executed. #48

@slawomirpiotrowski

Description

@slawomirpiotrowski

Hello,

Calling third not connection based service in an SNF partition causes panic when executed.

Steps to reproduce:

  • compile TF-M using IPC mode
  • add an SFN partition application RoT
  • add three (or more) not connection based services to this partition (doesn't matter what they do, simple return PSA_SUCCESS in _sfn is enough)
  • call any command in third service (causes panic in TF-M before actually calling _sfn function)

I'm not very good understanding TF-M internals but it looks like third service's message flag collides with ASYNC_MSG_REPLY which leads to TF-M panic as soon as anything is called inside this service.

Workaround is simple: just add dummy service as third and never call it. Calling 4th service, 5th and so on works without problems.

I have spotted it using stm32u585, but I think it's not specific to the platform.

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions