TEXTREL in shared lib

[xkszltl__xkszltl]

Hi!

We got someone complaining about using MKL in a SELinux-enabled docker due to TEXTREL in shared lib.

And seems IMPI also has this issue.

Any idea why? Is this a bug during the build process of Intel's libraries?

> find /opt/intel -name *.so* | xargs scanelf -qt
TEXTREL  /opt/intel/compilers_and_libraries_2019.4.243/linux/mpi/intel64/lib/debug_mt/libmpi.so
TEXTREL  /opt/intel/compilers_and_libraries_2019.4.243/linux/mpi/intel64/lib/debug_mt/libmpi.so.12.0
TEXTREL  /opt/intel/compilers_and_libraries_2019.4.243/linux/mpi/intel64/lib/debug_mt/libmpi.so.12.0.0
TEXTREL  /opt/intel/compilers_and_libraries_2019.4.243/linux/mpi/intel64/lib/debug_mt/libmpi.so.12
TEXTREL  /opt/intel/compilers_and_libraries_2019.4.243/linux/mpi/intel64/lib/debug/libmpi.so
TEXTREL  /opt/intel/compilers_and_libraries_2019.4.243/linux/mpi/intel64/lib/debug/libmpi.so.12.0
TEXTREL  /opt/intel/compilers_and_libraries_2019.4.243/linux/mpi/intel64/lib/debug/libmpi.so.12.0.0
TEXTREL  /opt/intel/compilers_and_libraries_2019.4.243/linux/mpi/intel64/lib/debug/libmpi.so.12
TEXTREL  /opt/intel/compilers_and_libraries_2019.4.243/linux/mkl/lib/intel64_lin/libmkl_tbb_thread.so
TEXTREL  /opt/intel/compilers_and_libraries_2019.4.243/linux/mkl/lib/intel64_lin/libmkl_avx2.so
TEXTREL  /opt/intel/compilers_and_libraries_2019.4.243/linux/mkl/lib/intel64_lin/libmkl_core.so
TEXTREL  /opt/intel/compilers_and_libraries_2019.4.243/linux/mkl/lib/intel64_lin/libmkl_avx512.so
TEXTREL  /opt/intel/compilers_and_libraries_2019.4.243/linux/mkl/lib/intel64_lin/libmkl_avx512_mic.so
TEXTREL  /opt/intel/compilers_and_libraries_2019.4.243/linux/mkl/lib/ia32_lin/libmkl_tbb_thread.so
TEXTREL  /opt/intel/compilers_and_libraries_2019.4.243/linux/mkl/lib/ia32_lin/libmkl_core.so

[Gennady_F_Intel]

Here is the first time we hear about this case. BTW we never check this OS. you may check the MKL System Requirements. Recently, not exactly the same, but a similar issue has been discussed at the IPP forum - https://software.intel.com/en-us/forums/intel-integrated-performance-primitives/topic/841949.

How does this problem prevent to use mkl with your application? 

[xkszltl__xkszltl]

What do you mean by "this OS"? It's on both Ubuntu/CentOS.

Just in case, SELinux is a rule-based whitelist library for security, which comes with most of the popular Linux distros these days. 

By default (i.e. stock selinux policy provided by distro/docker's repo), when use in docker with selinux enabled, libraries under /usr (where we ship our library and embedded mkl to) is forced to a "selinux context" different than host filesystem, and under this context TEXTREL is not allowed for security consideration. SELinux will give application a "permission denied" error. 

[xkszltl__xkszltl]

Hi Gennady! Hope you have a great holiday season.

Any update regarding this issue?

[Gennady_F_Intel]

We confirmed the problem on the mkl side and will investigate the cause of this issue.

[Gennady_F_Intel]

Please check the latest version of MKL 2020 update 4 which has been released the last Friday and let us know the results.

[Gennady_F_Intel]

This issue has been resolved and we will no longer respond to this thread. If you require additional assistance from Intel, please start a new thread. Any further interaction in this thread will be considered community only.