[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <3805f5f4-34c3-4c29-a03f-80ac2563cef3@infotecs.ru>
Date: Fri, 24 May 2024 10:59:03 +0000
From: Khannanov Lenar <Lenar.Khannanov@...otecs.ru>
To: "naresh.kamboju@...aro.org" <naresh.kamboju@...aro.org>
CC: "brauner@...nel.org" <brauner@...nel.org>, "fweimer@...hat.com"
<fweimer@...hat.com>, "linux-kernel@...r.kernel.org"
<linux-kernel@...r.kernel.org>, "linux-kselftest@...r.kernel.org"
<linux-kselftest@...r.kernel.org>, "lkft-triage@...ts.linaro.org"
<lkft-triage@...ts.linaro.org>, "shuah@...nel.org" <shuah@...nel.org>,
Gavrilov Ilia <Ilia.Gavrilov@...otecs.ru>
Subject: Re: selftests: clone3: clone3_cap_checkpoint_restore fails - Could
not set CAP_CHECKPOINT_RESTORE
I presume that test fails because of the difference between definition of struct _cap_struct (struct libcap in test). Commit aca076443591 (Make cap_t operations thread safe.) introduces mutex field at the beginning of the structure. Test uses own definition to set CAP_CHECKPOINT_RESTORE. As data member of these two versions of structures is at the different offsets, CAP_CHECKPOINT_RESTORE is lost and that's why cap_set_proc returns EPERM.
С уважением,
Ленар Ханнанов
Программист
Отдел разработки
АО "ИнфоТеКС" в г. Санкт-Петербург
190000, г. Санкт-Петербург, ул. Артиллерийская, д. 1, литер А, БЦ «Европа Хаус»
T: +7 495 737-61-92 ( доб. 7196)
Ф: +7 495 737-72-78
Lenar.Khannanov@...otecs.ru
www.infotecs.ru
Powered by blists - more mailing lists