From: Dominique Martinet <asmadeus@codewreck.org>
To: Tingmao Wang <m@maowtm.org>
Cc: Christian Schoenebeck <linux_oss@crudebyte.com>,
Eric Van Hensbergen <ericvh@kernel.org>,
Latchesar Ionkov <lucho@ionkov.net>,
v9fs@lists.linux.dev
Subject: Re: [PATCH v2] fs/9p: Don't open remote file with APPEND mode when writeback cache is used
Date: Mon, 3 Nov 2025 16:34:19 +0900 [thread overview]
Message-ID: <aQha--QBgwu8DoDE@codewreck.org> (raw)
In-Reply-To: <20251102235631.8724-1-m@maowtm.org>
Thanks for the v2
Tingmao Wang wrote on Sun, Nov 02, 2025 at 11:56:30PM +0000:
> I haven't done a bisect to figure out if this regression was introduced by
> a change or was this behaviour always present - 6.14 has the same problem
> and 6.13 did not compile for me due to some problem with bool / true /
> false being a keyword in c23, and it could not compile with c17 either.
Ok so you got me at the "it happens in cache=loose too", so I went ahead
with bisect... I had the same problem with newer gcc being c23 and older
kernels being silly, you'd think `KCFLAGS=-std=gnu11` is enough but some
arch makefiles ignore that so I went in heavy patching
arch/x86/boot/Makefile and arch/x86/boot/compressed/Makefile . . .
... Anyway, it certainly didn't break recently, but it's not ages ago
either: the repro you made (thank you!!) starts failing in 6.4 cache
rework: the first bad commit is actually 21e26d5e54ab ("fs/9p: Fix bit
operation logic error"), but that's just a fixup of the previous commit
so 4eb3117888a9 ("fs/9p: Rework cache modes and add new options to
Documentation") is the cluprit... and... I'm not quite sure I get why
without digging deeper...
(But at least that made me realize the commit just before, 1543b4c5071c
("fs/9p: remove writeback fid and fix per-file modes"), removed the
writeback fid I was talking about... But that commit was working (with a
sane ~P9_OWRITE mask), so it's not directly that removal that broke
things, but something else in the rework)
Anyway, I think this commit is a strict improvement over the current
situation, I'll just slap a Fixes tag and push to -next for now, and if
time allows I'll try to have a closer look...
Thanks,
--
Dominique
next prev parent reply other threads:[~2025-11-03 7:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-02 20:24 [PATCH 0/1] fs/9p: Do not open remote file with APPEND mode when writeback cache is used Tingmao Wang
2025-11-02 20:24 ` [PATCH 1/1] " Tingmao Wang
2025-11-02 23:07 ` Dominique Martinet
2025-11-02 23:56 ` [PATCH v2] fs/9p: Don't " Tingmao Wang
2025-11-03 7:34 ` Dominique Martinet [this message]
2025-11-10 13:25 ` Christian Schoenebeck
2025-11-10 14:22 ` Christian Schoenebeck
2025-11-02 23:58 ` [PATCH 1/1] fs/9p: Do not " Tingmao Wang
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=aQha--QBgwu8DoDE@codewreck.org \
--to=asmadeus@codewreck.org \
--cc=ericvh@kernel.org \
--cc=linux_oss@crudebyte.com \
--cc=lucho@ionkov.net \
--cc=m@maowtm.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