From: asmadeus@codewreck.org
To: Christian Schoenebeck <linux_oss@crudebyte.com>
Cc: Eric Van Hensbergen <ericvh@kernel.org>,
Latchesar Ionkov <lucho@ionkov.net>,
Chris Arges <carges@cloudflare.com>,
v9fs@lists.linux.dev, linux-kernel@vger.kernel.org,
David Howells <dhowells@redhat.com>,
Matthew Wilcox <willy@infradead.org>,
linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH] 9p/virtio: restrict page pinning to user_backed_iter() iovec
Date: Fri, 19 Dec 2025 08:14:58 +0900 [thread overview]
Message-ID: <aUSK8vrhPLAGdQlv@codewreck.org> (raw)
In-Reply-To: <8622834.T7Z3S40VBb@weasel>
Christian Schoenebeck wrote on Thu, Dec 18, 2025 at 04:14:45PM +0100:
> > Won't be the first time I can't reproduce, but what kind of workload are
> > you testing?
> > Anything that might help me try to reproduce (like VM cpu count/memory)
> > will be appreciated, corruptions are Bad...
>
> Debian Trixie guest running as 9p rootfs in QEMU, 4 cores, 16 GB.
>
> Compiling a bunch of projects with GCC works fine without errors, but with
> clang it's very simple for me to reproduce. E.g. just a very short C++ file
> that pulls in some system headers:
>
> #include <utility>
> #include <sys/cdefs.h>
> #include <limits>
>
> Then running 3 times: clang++ -c foo.cpp -std=c++17
>
> The first 2 clang runs succeed, the 3rd clang run then always blows up for
> anything else than cache=none, various spurious clang errors on those system
> headers like
Thanks, I can't reproduce with this example, but building linux with
`make LLVM=1` does blow up on debian... even with cache=none actually?
I couldn't reproduce running the same rootfs directory in a container so
I don't think I corrupted my image, it appears to be reading junk? short
reads perhaps?...
(Interestingly, it doesn't seem to blow up on an alpine rootfs, I wonder
what's different...)
I'm now getting late for work but at least there's something I can
reproduce, I'll have a closer look ASAP, thank you.
--
Dominique Martinet | Asmadeus
next prev parent reply other threads:[~2025-12-18 23:15 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-09 21:04 [PATCH] 9p/virtio: restrict page pinning to user_backed_iter() iovec Dominique Martinet
2025-12-09 21:04 ` Dominique Martinet via B4 Relay
2025-12-10 4:21 ` Matthew Wilcox
2025-12-10 6:04 ` Christoph Hellwig
2025-12-10 7:38 ` asmadeus
2025-12-10 8:32 ` Christoph Hellwig
2025-12-13 13:28 ` asmadeus
2025-12-15 5:55 ` Christoph Hellwig
2025-12-15 7:34 ` Dominique Martinet
2025-12-15 11:16 ` Christian Schoenebeck
2025-12-15 14:37 ` Christoph Hellwig
2025-12-19 12:03 ` David Howells
2025-12-19 12:00 ` David Howells
2025-12-19 11:26 ` David Howells
2025-12-10 13:33 ` Christian Schoenebeck
2025-12-17 13:41 ` Christian Schoenebeck
2025-12-17 21:49 ` asmadeus
2025-12-18 14:21 ` asmadeus
2025-12-18 15:14 ` Christian Schoenebeck
2025-12-18 23:14 ` asmadeus [this message]
2025-12-19 4:09 ` 9p read corruption of mmaped content (Was: [PATCH] 9p/virtio: restrict page pinning to user_backed_iter() iovec) Dominique Martinet
2025-12-19 11:53 ` Dominique Martinet
2025-12-19 13:46 ` Dominique Martinet
2025-12-19 14:01 ` David Howells
2025-12-19 12:06 ` [PATCH] 9p/virtio: restrict page pinning to user_backed_iter() iovec David Howells
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=aUSK8vrhPLAGdQlv@codewreck.org \
--to=asmadeus@codewreck.org \
--cc=carges@cloudflare.com \
--cc=dhowells@redhat.com \
--cc=ericvh@kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux_oss@crudebyte.com \
--cc=lucho@ionkov.net \
--cc=v9fs@lists.linux.dev \
--cc=willy@infradead.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.