Unable to access directory after chmod (unless 777)

[helltraitor]

WslLogs-2024-12-18_16-26-29.zip

Windows Version

Microsoft Windows [Version 10.0.26100.2605]

WSL Version

2.3.26.0

Are you using WSL 1 or WSL 2?

• WSL 2
• WSL 1

Kernel Version

5.15.167.4-1

Distro Version

Ubuntu 24.04

Other Software

GNU bash, version 5.2.21(1)-release (x86_64-pc-linux-gnu)

Repro Steps

/etc/wsl.conf (same with just options=metadata, or options="metadata")

[boot]
systemd=true

[automount]
enabled=true
options=metadata,umask=22,fmask=11
mountFsTab=false

helltraitor@Helltraitor-PC:/mnt/c/Users/Helltraitor$ sudo chmod -R 0664 test/
helltraitor@Helltraitor-PC:/mnt/c/Users/Helltraitor$ cd test/

Expected Behavior

Directory is changed as supposed by cd command

Actual Behavior

Output: -bash: cd: test/: Permission denied

Diagnostic Logs

journalctl -r

Dec 18 16:16:57 Helltraitor-PC sudo[975]: pam_unix(sudo:session): session closed for user root
Dec 18 16:16:57 Helltraitor-PC sudo[975]: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=1000)
Dec 18 16:16:57 Helltraitor-PC sudo[975]: helltraitor : TTY=pts/2 ; PWD=/mnt/c/Users/Helltraitor ; USER=root ; COMMAND=/usr/bin/chmod -R 0777 test/
Dec 18 16:16:50 Helltraitor-PC sudo[972]: pam_unix(sudo:session): session closed for user root
Dec 18 16:16:50 Helltraitor-PC sudo[972]: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=1000)
Dec 18 16:16:50 Helltraitor-PC sudo[972]: helltraitor : TTY=pts/2 ; PWD=/mnt/c/Users/Helltraitor ; USER=root ; COMMAND=/usr/bin/chmod -R 0444 test/

[github-actions]

Logs are required for review from WSL team

If this a feature request, please reply with '/feature'. If this is a question, reply with '/question'.
Otherwise please attach logs by following the instructions below, your issue will not be reviewed unless they are added. These logs will help us understand what is going on in your machine.

How to collect WSL logs

Download and execute collect-wsl-logs.ps1 in an administrative powershell prompt:

Invoke-WebRequest -UseBasicParsing "https://raw.githubusercontent.com/microsoft/WSL/master/diagnostics/collect-wsl-logs.ps1" -OutFile collect-wsl-logs.ps1
Set-ExecutionPolicy Bypass -Scope Process -Force
.\collect-wsl-logs.ps1

The script will output the path of the log file once done.

If this is a networking issue, please use collect-networking-logs.ps1, following the instructions here

Once completed please upload the output files to this Github issue.

Click here for more info on logging
If you choose to email these logs instead of attaching to the bug, please send them to [email protected] with the number of the github issue in the subject, and in the message a link to your comment in the github issue and reply with '/emailed-logs'.

[helltraitor]

UPD: Upload logs

I need to run ansible, so I need to change permission, if I as user want to make process simple for myself

[github-actions]

The log file doesn't contain any WSL traces. Please make sure that you reproduced the issue while the log collection was running.

Diagnostic information

Issue was edited and new log file was found: https://github.com/user-attachments/files/18183226/WslLogs-2024-12-18_16-26-29.zip
Detected appx version: 2.3.26.0
Found no WSL traces in the logs

[helltraitor]

Logs were acquired after executing same cd test/ command, so I'm not sure how much logs can be there, or even if they will be there