public inbox for v9fs@lists.linux.dev
 help / color / mirror / Atom feed
From: Dominique Martinet <asmadeus@codewreck.org>
To: Tingmao Wang <m@maowtm.org>
Cc: "Eric Van Hensbergen" <ericvh@kernel.org>,
	"Latchesar Ionkov" <lucho@ionkov.net>,
	"Christian Schoenebeck" <linux_oss@crudebyte.com>,
	v9fs@lists.linux.dev, "Mickaël Salaün" <mic@digikod.net>
Subject: Re: [PATCH 0/3] fs/9p: d_revalidate changes and using it for uncached mode
Date: Tue, 15 Apr 2025 06:01:11 +0900	[thread overview]
Message-ID: <Z_13l9hPolrDrEnj@codewreck.org> (raw)
In-Reply-To: <cover.1743956147.git.m@maowtm.org>

Hi,

Thanks for the patches; I think it makes sense overall. We've had
problems with files modifiede on host while guest was looking at it
semi-recently and I thought it was fixed but it either came back or I
missed something...

Just a note so you don't wonder what's happening that I won't be able to
give them a proper look for ~a month with real life getting in the way.

If someone else gives it a fair review I can probably pick up this
thread up for 6.16 but otherwise it probably won't make it, the landlock
part will probably come even later...

Sorry for the delay,
-- 
Dominique

  parent reply	other threads:[~2025-04-14 21:10 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-06 16:18 [PATCH 0/3] fs/9p: d_revalidate changes and using it for uncached mode Tingmao Wang
2025-04-06 16:18 ` [PATCH 1/3] fs/9p: Refresh metadata in d_revalidate for uncached mode too Tingmao Wang
2025-04-06 16:18 ` [PATCH 2/3] fs/9p: Invalidate dentry if inode type change detected in cached mode Tingmao Wang
2025-04-06 16:18 ` [PATCH 3/3] fs/9p: Add p9_debug(VFS) in d_revalidate Tingmao Wang
2025-04-14 21:01 ` Dominique Martinet [this message]
2025-08-15  4:12   ` [PATCH 0/3] fs/9p: d_revalidate changes and using it for uncached mode Dominique Martinet
2025-08-19 12:57     ` Mickaël Salaün

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=Z_13l9hPolrDrEnj@codewreck.org \
    --to=asmadeus@codewreck.org \
    --cc=ericvh@kernel.org \
    --cc=linux_oss@crudebyte.com \
    --cc=lucho@ionkov.net \
    --cc=m@maowtm.org \
    --cc=mic@digikod.net \
    --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