Skip to content

virtio/fs: report actual bytes written in used ring len#701

Open
cathay4t wants to merge 1 commit into
containers:mainfrom
cathay4t:main
Open

virtio/fs: report actual bytes written in used ring len#701
cathay4t wants to merge 1 commit into
containers:mainfrom
cathay4t:main

Conversation

@cathay4t
Copy link
Copy Markdown

The virtio used ring's len field must reflect the number of bytes the
device wrote into the writable descriptor chain. libkrun was hard-coding
0, which broke FUSE protocol validation added in Linux kernel commit
68b69fa0edb (virtiofs: add FUSE protocol validation).

Resolves: #695

The virtio used ring's len field must reflect the number of bytes the
device wrote into the writable descriptor chain. libkrun was hard-coding
0, which broke FUSE protocol validation added in Linux kernel commit
68b69fa0edb (virtiofs: add FUSE protocol validation).

Resolves: containers#695

Signed-off-by: Gris Ge <cnfourt@gmail.com>
@cathay4t
Copy link
Copy Markdown
Author

cathay4t commented May 30, 2026

Manually tested by and confirmed podman krun works well with kernel 7.1 rc5.

make BLK=1 NET=1 
sudo cp target/release/libkrun.so.1.18.0  /usr/lib/libkrun.so.1.18.0 -f

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

linux 7.1-rc5 virtiofs not working

1 participant