BPF List
 help / color / mirror / Atom feed
From: Tingmao Wang <m@maowtm.org>
To: Song Liu <song@kernel.org>, v9fs@lists.linux.dev
Cc: "Eric Van Hensbergen" <ericvh@kernel.org>,
	"Dominique Martinet" <asmadeus@codewreck.org>,
	"Latchesar Ionkov" <lucho@ionkov.net>,
	"Christian Schoenebeck" <linux_oss@crudebyte.com>,
	"Mickaël Salaün" <mic@digikod.net>, bpf <bpf@vger.kernel.org>
Subject: Re: 9P change breaks bpftrace running in qemu+9p?
Date: Mon, 20 Oct 2025 19:40:21 +0100	[thread overview]
Message-ID: <e0c7cd4e-4183-40a8-b90d-12e9e29e9890@maowtm.org> (raw)
In-Reply-To: <CAHzjS_u_SYdt5=2gYO_dxzMKXzGMt-TfdE_ueowg-Hq5tRCAiw@mail.gmail.com>

Hi Song,

On 10/20/25 18:40, Song Liu wrote:
> Hi,
> 
> I noticed a new error in the upstream kernel when I run bpftrace with
> vmtest [2]:
> 
> $ vmtest -k arch/x86/boot/bzImage "bpftrace.real -e
> 'fexit:cmdline_proc_show {exit();}'"
> => bzImage
> ===> Booting
> ===> Setting up VM
> ===> Running command
> [    5.610741] id (178) used greatest stack depth: 11592 bytes left
> Parse error: Input/output error
> Command failed with exit code: 2
> [root@(none) /]#
> 
> git bisect points to patch 1/3 of this set [1].
> 
> Any idea what is happening here?

I have attempted to reproduce this but couldn't yet:

	> git log --format=short -1
	commit 211ddde0823f1442e4ad052a2f30f050145ccada (HEAD, tag: v6.18-rc2, origin/master, origin/HEAD)
	Author: Linus Torvalds <torvalds@linux-foundation.org>
	
	    Linux 6.18-rc2
	(0.067s) linux-devbox-2 (mao; ; ?) ~/9pfs
	> vmtest -k arch/x86/boot/bzImage "bpftrace -e 'fexit:cmdline_proc_show {exit();}'"
	=> bzImage
	===> Booting
	===> Setting up VM
	===> Running command
	Attached 1 probe
	^C⏎
	 (130) (14.421s) linux-devbox-2 (mao; ; ?) ~/9pfs
	> vmtest -k arch/x86/boot/bzImage "(sleep 2; cat /proc/cmdline) & bpftrace -e 'fexit:cmdline_proc_show {exit();}'"
	=> bzImage
	===> Booting
	===> Setting up VM
	===> Running command
	Attached 1 probe
	rootfstype=9p rootflags=trans=virtio,cache=mmap,msize=1048576 rw earlyprintk=serial,0,115200 printk.devkmsg=on console=0,115200 loglevel=7 ra...
	
	(5.29s) linux-devbox-2 (mao; ; ?) ~/9pfs
	> qemu-system-x86_64 -version
	QEMU emulator version 10.1.1
	Copyright (c) 2003-2025 Fabrice Bellard and the QEMU Project developers
	(0.011s) linux-devbox-2 (mao; ; ?) ~/9pfs
	> bpftrace --version
	bpftrace v0.24.1

I'm happy to take a further look - is there anything special about your
setup, what version of QEMU / bpftrace are you running?

> 
> Thanks,
> Song
> 
> [1] https://lore.kernel.org/v9fs/cover.1743956147.git.m@maowtm.org/
> [2] https://github.com/danobi/vmtest


  reply	other threads:[~2025-10-20 18:40 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-20 17:40 9P change breaks bpftrace running in qemu+9p? Song Liu
2025-10-20 18:40 ` Tingmao Wang [this message]
2025-10-20 19:40   ` Song Liu
2025-10-20 21:32     ` Dominique Martinet
2025-10-20 21:52       ` Song Liu
2025-10-21  0:54         ` Tingmao Wang
2025-10-21  6:49           ` Song Liu
2025-10-21 16:56             ` Alexei Starovoitov
2025-10-21 22:12               ` Dominique Martinet

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=e0c7cd4e-4183-40a8-b90d-12e9e29e9890@maowtm.org \
    --to=m@maowtm.org \
    --cc=asmadeus@codewreck.org \
    --cc=bpf@vger.kernel.org \
    --cc=ericvh@kernel.org \
    --cc=linux_oss@crudebyte.com \
    --cc=lucho@ionkov.net \
    --cc=mic@digikod.net \
    --cc=song@kernel.org \
    --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