Hi John,
Agree, let me send another patch, this one can be considered obsolete
On Mon, Feb 24, 2025 at 10:02 AM John Johansen
wrote:
> On 2/13/25 07:57, Hector Cao wrote:
> > For executables dynamically linked to libnuma, the runtimer linker
> > invokes libnuma functions (num_init) that try to a
On 2/13/25 07:57, Hector Cao wrote:
For executables dynamically linked to libnuma, the runtimer linker
invokes libnuma functions (num_init) that try to access
/sys/devices/system/node/ and if the application's apparmor
profile does not allow this access, this access will be denied
by apparmor wit
On Thu, Feb 13, 2025 at 7:57 PM Ryan Lee wrote:
> On Thu, Feb 13, 2025 at 7:58 AM Hector Cao
> wrote:
> >
> > For executables dynamically linked to libnuma, the runtimer linker
> > invokes libnuma functions (num_init) that try to access
> > /sys/devices/system/node/ and if the application's appa
On Thu, Feb 13, 2025 at 7:58 AM Hector Cao wrote:
>
> For executables dynamically linked to libnuma, the runtimer linker
> invokes libnuma functions (num_init) that try to access
> /sys/devices/system/node/ and if the application's apparmor
> profile does not allow this access, this access will be
For executables dynamically linked to libnuma, the runtimer linker
invokes libnuma functions (num_init) that try to access
/sys/devices/system/node/ and if the application's apparmor
profile does not allow this access, this access will be denied
by apparmor with following error message:
apparmor
