Re: [PATCH v3 0/6] fs: Add 9P filesystem support over virtio

[Tom Rini <trini@konsulko.com>]

[-- Attachment #1: Type: text/plain, Size: 3349 bytes --]

On Thu, Oct 08, 2026 at 04:30:12AM +0800, Kuan-Wei Chiu wrote:
> Hi Tom,
> 
> On Thu, Oct 08, 2026 at 04:13:33AM +0800, Kuan-Wei Chiu wrote:
> > Hi Tom,
> > 
> > On Wed, Oct 07, 2026 at 01:59:51PM -0600, Tom Rini wrote:
> > > On Wed, Oct 07, 2026 at 12:42:03PM -0600, Tom Rini wrote:
> > > > On Wed, 23 Sep 2026 21:29:56 +0000, Kuan-Wei Chiu wrote:
> > > > 
> > > > > Add 9P network filesystem support to U-Boot.
> > > > > 
> > > > > It allows U-Boot to directly mount host directories in virtualization
> > > > > environments via virtio. This is useful for loading kernel and
> > > > > initramfs images directly from the host into the VM during development
> > > > > and testing without having to rebuild disk images or set up a TFTP
> > > > > server.
> > > > > 
> > > > > [...]
> > > > 
> > > > Applied to u-boot/main, thanks!
> > > > 
> > > > [1/6] net: 9p: Add 9P2000.L protocol support
> > > >       commit: 48bb83195682d189273bdba813fa67f7f2760d59
> > > > [2/6] fs: 9p: Add 9P filesystem support
> > > >       commit: 9e14f904f8f12cd9df07e99a679453c8782e523b
> > > > [3/6] virtio: 9p: Add 9P transport driver
> > > >       commit: 09e668e32b4c14ce5c929d6cebfac75d2aefb90d
> > > > [4/6] doc: 9p: Add 9P filesystem documentation
> > > >       commit: 7d963df1bc38f5ae070ea8b96e03afc1ef7e23ed
> > > > [5/6] test: 9p: Add test for 9P filesystem
> > > >       commit: d446ef40b87d53ef7ac59ac9b1d79a16f0a065b0
> > > > [6/6] MAINTAINERS: Add entry for 9PFS
> > > >       commit: f6002d5e8018714ca80dcf1835c230c99c5090b3
> > > 
> > > Are there special permissions required for 9p to run? This works in
> > > Gitlab, but in Azure:
> > > test/py/tests/test_9p.py:46: in test_fs_9p
> > >     assert test_file_name in output
> > > E   assert '9p_test_small.txt' in "9P Error: No matching 9P transport device found for '-'"
> > > 
> > That's weird.  In theory, no special permissions should be required.
> > That error messag indicates that u-boot didn't detect any 9p transport
> > device. I'll take a look at it.
> > 
> Azure currently points to the github mirror of u-boot-test-hooks,
> which does not include my previous u-boot-test-hooks patch that adds
> the 9p device to arm64 qemu.
> 
> The following change should fix it, although I haven't tested it yet. I
> can submit it separately as a formal patch.
> 
> Regards,
> Kuan-Wei
> 
> diff --git a/.azure-pipelines.yml b/.azure-pipelines.yml
> index 015fc15d5c2..93bdbf4a4cf 100644
> --- a/.azure-pipelines.yml
> +++ b/.azure-pipelines.yml
> @@ -251,7 +251,7 @@ stages:
>            # the below corresponds to .gitlab-ci.yml "before_script"
>            cd \${WORK_DIR}
>            git config --global --add safe.directory \${WORK_DIR}
> -          git clone --depth=1 https://github.com/u-boot/u-boot-test-hooks /tmp/uboot-test-hooks
> +          git clone --depth=1 https://git.u-boot-project.org/u-boot/u-boot-test-hooks /tmp/uboot-test-hooks
>            # qemu_arm64_lwip_defconfig is the same as qemu_arm64 but with NET_LWIP enabled.
>            # The test config and the boardenv file from qemu_arm64 can be re-used so create symlinks
>            ln -s conf.qemu_arm64 /tmp/uboot-test-hooks/bin/travis-ci/conf.qemu_arm64_lwip_na

Ah! Thanks! Yes, please post a proper patch and I'll grab and push it
out.

-- 
Tom

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]