On 11.11.21 11:58, Ando Yuta wrote:
> Hello
>
>> Sandbox enabled:
>> stat("/sys/fs/cgroup/cpuset/chrome", 0x7f9068a987c0) = -1 ENOSYS (Function
>> not implemented)
>> Sandbox disabled:
>> stat("/sys/fs/cgroup/cpuset/chrome", 0x7f9e3a03a7c0) = -1 ENOENT (No such
>> file or directory)
>> You have updated the kernel, but did you update your libseccomp security
>> profile as well? (IOW: Have you updated your userspace as well?)
>> I know about some problems in the past where similar affects were observed
>> when using syscalls that were not known to the security profile in use. The
>> stat call is not new, but ENOSYS is unexpected.
>
> Yes I checked. My seccomp version is 2.5.1-1ubuntu1~18.04.1.
> Is there anything else I need to do to update the security profile of
> libseccomp?
>
I'm starting to reproduce, and there is some behavioral difference on
5.10 with vs. without Dovetail/Xenomai. I'm now trying to narrow this
down, will keep you posted.
Thanks so far,
Jan
--
Siemens AG, T RDA IOT
Corporate Competence Center Embedded Linux
