add new host injection variant symlinks for 2025.06#263
add new host injection variant symlinks for 2025.06#263bedroge wants to merge 9 commits intoEESSI:mainfrom
Conversation
bedroge
force-pushed
the
new_hostinjection_symlinks
branch
from
003ac66 to
96c108e
Compare
| #versions/2025.06/compat/linux/aarch64/lib/amd: '$(EESSI_202506_AMD_OVERRIDE:-/cvmfs/software.eessi.io/defaults/amd)' | ||
| #versions/2025.06/compat/linux/riscv64/lib/amd: '$(EESSI_202506_AMD_OVERRIDE:-/cvmfs/software.eessi.io/defaults/amd)' | ||
| #versions/2025.06/compat/linux/x86_64/lib/amd: '$(EESSI_202506_AMD_OVERRIDE:-/cvmfs/software.eessi.io/defaults/amd)' |
There was a problem hiding this comment.
I've commented these out for now, as we won't be using them yet. On the other hand, it doesn't do any harm to already create them?
| # defaults/amd: '$(EESSI_AMD_OVERRIDE_DEFAULT:-/dev/null)' | ||
| defaults/nvidia: '$(EESSI_NVIDIA_OVERRIDE_DEFAULT:-/dev/null)' | ||
| defaults/override: '$(EESSI_LIB_OVERRIDE_DEFAULT:-/dev/null)' | ||
| host_injections: '$(EESSI_HOST_INJECTIONS:-/opt/eessi)' |
There was a problem hiding this comment.
Not to muddy things too much here, but I wonder if this too should also be pointing to /dev/null by default? It is a bit of a security hole as you can inject into MPI binaries via locations in there and this is not explicitly obvious (the default doesn't appear in your local configuration so you would need to actively know that you should be monitoring that).
There was a problem hiding this comment.
Granted, for it to be a problem you have to manually create /opt/eessi and lose control of that directory, but if you did that, there's no real record in your CVMFS setup about that.
2 participants
See EESSI/software-layer-scripts#158.