Messages in this thread | | | Date | Fri, 28 Oct 2022 16:23:48 +0100 | From | Cristian Marussi <> | Subject | Re: [PATCH v4 0/11] Introduce a unified API for SCMI Server testing |
| |
On Fri, Oct 28, 2022 at 07:44:32AM -0700, Florian Fainelli wrote: > Hi Christian, > > On 10/19/2022 1:46 PM, Cristian Marussi wrote: > > Hi all, > >
Hi Florian,
> > This series aims to introduce a new SCMI unified userspace interface meant > > to ease testing an SCMI Server implementation for compliance, fuzzing etc., > > from the perspective of the OSPM agent (non-secure world only ...) > > > > It is proposed as a testing/development facility, it is NOT meant to be a > > feature to use in production, but only enabled in Kconfig for test > > deployments. > > > > Currently an SCMI Compliance Suite like the one at [1] can only work by > > injecting SCMI messages at the SCMI transport layer using the mailbox test > > driver (CONFIG_MAILBOX_TEST) via its few debugfs entries and looking at > > the related replies from the SCMI backend Server. > > I plan on giving this a try on our systems later today and will let you know > the outcome.
Great ! It would be much appreciated...
> This is very useful for making sure the SCMI implementation is > both correct and properly hardened.
... that was the plan :P
Note that the upstream SCMI ACS suite that I am using for stressing/testing this Raw thing is still WIP in term of supporting Raw mode injection (i.e. functional but ALL still to be merged)..but if you need I can give you pointers on how to use it....unless of course you have your suite or you just want to test using the shell as in the cover-letter examples...
... on my side I tried to fuzz me with a brutal
'dd bs=128 count=1 if=/dev/random of=<scmi_raw>/message'
as a poor man fuzzying tool :D ... so I was thinking if it was meaningful to think about upstreaming some common tools for fuzzying or simply pre-building bare payloads (in proper endianity) to be injected with this SCMI raw thing... (I mean something useful that could live in tools/)
...any feedbacks/hints in these regards are welcome.
Thanks, Cristian
| |