From: Will Deacon <will@kernel.org>
To: ericvh@kernel.org
Cc: lucho@ionkov.net, asmadeus@codewreck.org, oss@crudebyte.com,
v9fs@lists.linux.dev, linux-kernel@vger.kernel.org,
oleg@redhat.com, keirf@google.com
Subject: VFS regression with 9pfs ("Lookup would have caused loop")
Date: Mon, 23 Sep 2024 11:05:10 +0100 [thread overview]
Message-ID: <20240923100508.GA32066@willie-the-truck> (raw)
Hi Eric,
I'm trying to use kvmtool to run a simple guest under an Android host
but, for v6.9+ guest kernels, 'init' reliably fails to run from a 9pfs
mount because VFS emits this error:
| VFS: Lookup of 'com.android.runtime' in 9p 9p would have caused loop
The host directory being shared is a little odd, as it has symlinks out
to other mount points. In the guest, /apex is a symlink to /host/apex.
On the host, /apex/com.android.runtime is a mounted loopback device:
/dev/block/loop13 on /apex/com.android.runtime type ext4 (ro,dirsync,seclabel,nodev,noatime)
This used to work prior to 724a08450f74 ("fs/9p: simplify iget to remove
unnecessary paths") and it looks like Oleg ran into something similar
before:
https://lore.kernel.org/all/20240408141436.GA17022@redhat.com/
although he worked around it by driving QEMU with different options.
I can confirm that reverting the following commits gets mainline guests
working again for me:
724a08450f74 "fs/9p: simplify iget to remove unnecessary paths"
11763a8598f8 "fs/9p: fix uaf in in v9fs_stat2inode_dotl"
10211b4a23cf "fs/9p: remove redundant pointer v9ses"
d05dcfdf5e16 " fs/9p: mitigate inode collisions"
Do you have any better ideas? I'm happy to test anything you might have,
since this is 100% reproducible on my setup.
Cheers,
Will
next reply other threads:[~2024-09-23 10:05 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-23 10:05 Will Deacon [this message]
2024-10-09 15:34 ` Will Deacon
2024-10-15 18:07 ` Thorsten Leemhuis
2024-10-16 9:39 ` asmadeus
2024-10-22 15:01 ` Will Deacon
2024-10-22 23:00 ` Dominique Martinet
2024-10-23 7:22 ` Linux regression tracking (Thorsten Leemhuis)
2024-10-23 15:14 ` Will Deacon
2024-10-25 15:25 ` Christian Brauner
2024-10-25 15:29 ` Christian Brauner
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20240923100508.GA32066@willie-the-truck \
--to=will@kernel.org \
--cc=asmadeus@codewreck.org \
--cc=ericvh@kernel.org \
--cc=keirf@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lucho@ionkov.net \
--cc=oleg@redhat.com \
--cc=oss@crudebyte.com \
--cc=v9fs@lists.linux.dev \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®