linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dominique Martinet <asmadeus@codewreck.org>
To: Arnout Engelen <arnout@bzzt.net>
Cc: ryan@lahfa.xyz, antony.antony@secunet.com, antony@phenome.org,
	brauner@kernel.org, ericvh@kernel.org,
	linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux_oss@crudebyte.com, lucho@ionkov.net, maximilian@mbosch.me,
	netfs@lists.linux.dev, regressions@lists.linux.dev,
	sedat.dilek@gmail.com, v9fs@lists.linux.dev,
	Matthew Wilcox <willy@infradead.org>,
	dhowells@redhat.com
Subject: Re: [REGRESSION] 9pfs issues on 6.12-rc1
Date: Mon, 11 Aug 2025 16:43:01 +0900	[thread overview]
Message-ID: <aJmfBTflGvAI6sBs@codewreck.org> (raw)
In-Reply-To: <aJlAD0nPcR2kvAtS@codewreck.org>

asmadeus@codewreck.org wrote on Mon, Aug 11, 2025 at 09:57:51AM +0900:
> Also I haven't been able to reproduce it with a kernel I built myself/my
> environment, but it reproduces reliably 99% of the times in the nixos
> VM, so we're missing a last piece for a "simple" (non-nix) reproducer,
> but I think it's good enough for me to dig into this;

(okay, I got this to work wedging my kernel into the nixos initrd; this
requires the iov to be built off non-contiguous pages and so having
systemd thrash around was apparently a required step...)

So that wasn't a 9p bug, I'm not sure if I should be happy or not?

I've sent "proper-ish" patches at [1] which most concerned people should
be in Cc; I'm fairly confident this will make the bug go away but any
testing is appreciated, please reply to the patches with a Tested-by if
you have time.

[1] https://lkml.kernel.org/r/20250811-iot_iter_folio-v1-0-d9c223adf93c@codewreck.org


Thank you all again, and sorry I haven't had the time to look further
into this without a clean reproducer, this really shouldn't have taken
that long...
-- 
Dominique Martinet | Asmadeus

  reply	other threads:[~2025-08-11  7:43 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-02 17:08 [REGRESSION] 9pfs issues on 6.12-rc1 Maximilian Bosch
2024-10-02 17:31 ` Linux regression tracking (Thorsten Leemhuis)
2024-10-02 21:48   ` Maximilian Bosch
2024-10-03  1:12     ` Sedat Dilek
2024-10-17 18:00       ` Antony Antony
2024-10-21 13:23         ` Christian Brauner
2024-10-23 18:35         ` Maximilian Bosch
2024-10-21 14:12       ` David Howells
2024-10-21 15:33         ` Antony Antony
2024-10-21 14:45       ` David Howells
2024-10-21 15:53         ` Antony Antony
2024-10-21 19:48         ` David Howells
2025-08-10  5:10         ` Arnout Engelen
2024-10-21 20:38       ` [PATCH] 9p: Don't revert the I/O iterator after reading David Howells
2024-10-21 23:53         ` Antony Antony
2024-10-22  8:56         ` Christian Brauner
2024-10-23 10:07       ` [REGRESSION] 9pfs issues on 6.12-rc1 David Howells
2024-10-23 19:38         ` Antony Antony
2025-06-12 22:24           ` Ryan Lahfa
2025-06-27  5:44             ` Christian Theune
2025-06-27  6:44               ` Dominique Martinet
2025-06-27  8:19                 ` Christian Theune
2025-08-10 17:57             ` Arnout Engelen
2025-08-11  0:57               ` asmadeus
2025-08-11  7:43                 ` Dominique Martinet [this message]
2025-08-11 12:43                   ` Arnout Engelen
2025-06-27 10:00           ` David Howells
2025-06-27 10:33             ` Ryan Lahfa

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=aJmfBTflGvAI6sBs@codewreck.org \
    --to=asmadeus@codewreck.org \
    --cc=antony.antony@secunet.com \
    --cc=antony@phenome.org \
    --cc=arnout@bzzt.net \
    --cc=brauner@kernel.org \
    --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=maximilian@mbosch.me \
    --cc=netfs@lists.linux.dev \
    --cc=regressions@lists.linux.dev \
    --cc=ryan@lahfa.xyz \
    --cc=sedat.dilek@gmail.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).