From 9260319e7411ff8281700a532caa436f40120ec4 Mon Sep 17 00:00:00 2001 From: Christian Krinitsin Date: Fri, 30 May 2025 16:52:07 +0200 Subject: gitlab scraper: download in toml and text format --- .../target_missing/host_missing/accel_missing/1066 | 32 ++++++++++++++++++++++ 1 file changed, 32 insertions(+) create mode 100644 gitlab/issues_text/target_missing/host_missing/accel_missing/1066 (limited to 'gitlab/issues_text/target_missing/host_missing/accel_missing/1066') diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1066 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1066 new file mode 100644 index 000000000..366dcf0ed --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1066 @@ -0,0 +1,32 @@ +virtfs fails to access contents of non-readable directories +Description of problem: +Attempting to access a directory inside a non-readable directory via virtfs fails. +Steps to reproduce: +On host: +1. `mkdir -p test/foo/bar` +2. `echo hello world >test/foo/bar/baz.txt` +3. `chmod -r test/foo` + +The following works on host: + +``` +$ ls test +foo +$ ls test/foo +ls: cannot open directory 'test/foo': Permission denied +$ ls test/foo/bar +baz.txt +``` + +However on guest: + +``` +bash-5.1# ls /test/ +foo +bash-5.1# ls /test/foo/ +ls: cannot open directory '/test/foo/': Permission denied +bash-5.1# ls /test/foo/bar/ +ls: cannot access '/test/foo/bar/': Permission denied +``` +Additional information: +I am guessing virtfs attempts to check rights (via access?) on the directory itself when obtaining an inode to give to the guest, however not having read access doesn't mean something can't be executed, especially for directories. -- cgit 1.4.1