All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dominique Martinet <asmadeus@codewreck.org>
To: Linus Torvalds <torvalds@linux-foundation.org>,
	Tingmao Wang <m@maowtm.org>
Cc: Song Liu <song@kernel.org>,
	Andrii Nakryiko <andrii.nakryiko@gmail.com>,
	Eric Van Hensbergen <ericvh@kernel.org>,
	Latchesar Ionkov <lucho@ionkov.net>,
	Christian Schoenebeck <linux_oss@crudebyte.com>,
	Alexei Starovoitov <ast@kernel.org>,
	linux-kernel@vger.kernel.org, v9fs@lists.linux.dev,
	bpf@vger.kernel.org
Subject: Re: [GIT PULL] 9p cache=mmap regression fix (for 6.18-rc3)
Date: Wed, 22 Oct 2025 14:38:14 +0900	[thread overview]
Message-ID: <aPhtxt7qEWY5FjPQ@codewreck.org> (raw)
In-Reply-To: <39116c81-1798-4cc1-945c-a05d0ac7d8d9@maowtm.org>

Tingmao Wang wrote on Wed, Oct 22, 2025 at 12:34:13AM +0100:
> On 10/22/25 00:16, Dominique Martinet wrote:
> > We had a regression with cache=mmap that impacted quite a few people so
> > I'm sending a fix less than a couple of hours after making the commit.
> > 
> > If it turns out there are other side effects I'd suggest just reverting
> > commit 290434474c33 ("fs/9p: Refresh metadata in d_revalidate for
> > uncached mode too") first, but the fix is rather minimal so I think it's
> > ok to try falling forward -- let me know if you prefer a revert and I'll
> > send one instead (there's a minor conflict)
> 
> See the reply to the original patch [1] (posted right after, and before
> seeing, this message) - there is indeed more side effects, and I wouldn't
> mind a revert for now.  0172a934747f ("fs/9p: Invalidate dentry if inode
> type change detected in cached mode") will need to be reverted too.

(yeah, and even that conflicts due to the added debug message in the
next commit, but I went the heavy-handed way and removed the conflicting
hunk so that commit's also implicitly been removed. In hindsight it
would have been cleaner to revert the three commits
290434474c33^..c667c54c5875 -- ohwell)

> [1]: https://lore.kernel.org/v9fs/6c74ad63-3afc-4549-9ac6-494b9a63e839@maowtm.org/

OK, so let's go with the revert for now as I don't have time to look for
more corner cases immediately.

Linus, here's the new PR:
---------
The following changes since commit 211ddde0823f1442e4ad052a2f30f050145ccada:

  Linux 6.18-rc2 (2025-10-19 15:19:16 -1000)

are available in the Git repository at:

  https://github.com/martinetd/linux tags/9p-for-6.18-rc3-v2

for you to fetch changes up to 43c36a56ccf6d9b07b4b3f4f614756e687dcdc01:

  Revert "fs/9p: Refresh metadata in d_revalidate for uncached mode too" (2025-10-22 14:25:27 +0900)

----------------------------------------------------------------
Fix 9p cache=mmap regression by revert

This reverts the problematic commit instead of trying to fix it in a
rush

----------------------------------------------------------------
Dominique Martinet (1):
      Revert "fs/9p: Refresh metadata in d_revalidate for uncached mode too"

 fs/9p/vfs_dentry.c     | 10 ++--------
 fs/9p/vfs_inode.c      |  8 +-------
 fs/9p/vfs_inode_dotl.c |  8 +-------
 3 files changed, 4 insertions(+), 22 deletions(-)

-- 
Dominique Martinet | Asmadeus

  reply	other threads:[~2025-10-22  5:38 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-21 22:09 [PATCH] fs/9p: don't use cached metadata in revalidate for cache=mmap Dominique Martinet via B4 Relay
2025-10-21 22:09 ` Dominique Martinet
2025-10-21 22:46 ` Song Liu
2025-10-21 23:16   ` [GIT PULL] 9p cache=mmap regression fix (for 6.18-rc3) Dominique Martinet
2025-10-21 23:34     ` Tingmao Wang
2025-10-22  5:38       ` Dominique Martinet [this message]
2025-10-22 15:17         ` pr-tracker-bot
2025-10-21 23:18 ` [PATCH] fs/9p: don't use cached metadata in revalidate for cache=mmap 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=aPhtxt7qEWY5FjPQ@codewreck.org \
    --to=asmadeus@codewreck.org \
    --cc=andrii.nakryiko@gmail.com \
    --cc=ast@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=ericvh@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux_oss@crudebyte.com \
    --cc=lucho@ionkov.net \
    --cc=m@maowtm.org \
    --cc=song@kernel.org \
    --cc=torvalds@linux-foundation.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 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.