-
Notifications
You must be signed in to change notification settings - Fork 44
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
loadkeys triggers all mounts in the cwd #101
Comments
See systemd/systemd#28677 for details where people ran into this. |
This is a very old behavior that appeared before I joined this project: Line 568 in 7fbc262
I totally agree that this is extremely counter-intuitive behavior. I'm going to remove the current directory and search list. |
excellent! thanks! |
Now loadkeys first tries to look for a keymap in the current directory. This behavior is not intuitive and leads to problems. It appears that loadskeys triggers all inodes in the current cwd. This might lead to deadlocks during boot, because the system might not be ready to trigger an autofs this early. To solve this I exclude the current directory from the keymaps search paths. We still have ways to specify a different directory to search for keymaps than the one specified on build time. The user can set the LOADKEYS_KEYMAP_PATH environment variable to specify a different search path. Link: #101 Signed-off-by: Alexey Gladkov <[email protected]>
Should be fixed in kbd-2.6.2. |
Excellent! thanks! |
@legionus It seems like loadkeys still probes all directories in the cwd for some reason. This is from loadkeys 2.6.3 on Arch Linux:
|
Fixes the same issue as a770f39 but for include files. Link: legionus#101
Fixes the same issue as a770f39 but for include files. Link: legionus#101 Signed-off-by: Daan De Meyer <[email protected]>
Another fix that corrects the search for keymaps in the current directory. Link: #101 Link: #105 Signed-off-by: Alexey Gladkov <[email protected]>
It appears that loadskeys triggers all inodes in the current cwd. It really shouldn#t do that, as this might lead to deadlocks during boot, because the system might not be ready to trigger an autofs this early.
it's also a security hole of sorts (i.e. compare with the fact that on linux execvp() does not bother with the cwd either by default, and people generally frown upon it).
I think loadkeys should never look in the cwd for keymaps. If you want to keep it, at least don#t trigger the inodes anymore. i.e. use AT_NO_AUTOMOUNT
The text was updated successfully, but these errors were encountered: