From: Luis Henriques <luis@igalia.com>
To: Miklos Szeredi <miklos@szeredi.hu>
Cc: Laura Promberger <laura.promberger@cern.ch>,
Bernd Schubert <bschubert@ddn.com>,
Dave Chinner <david@fromorbit.com>,
Matt Harvey <mharvey@jumptrading.com>,
"linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v8] fuse: add more control over cache invalidation behaviour
Date: Tue, 15 Apr 2025 11:49:54 +0100 [thread overview]
Message-ID: <87mschn1gt.fsf@igalia.com> (raw)
In-Reply-To: <CAJfpegu-x88d+DGa=x_EfvWWCjnkZYjO8MwjAc4bGQky8kBi3g@mail.gmail.com> (Miklos Szeredi's message of "Tue, 15 Apr 2025 12:41:40 +0200")
On Tue, Apr 15 2025, Miklos Szeredi wrote:
> On Tue, 15 Apr 2025 at 12:34, Luis Henriques <luis@igalia.com> wrote:
>>
>> Hi Laura,
>>
>> On Fri, Apr 11 2025, Laura Promberger wrote:
>>
>> > Hello Miklos, Luis,
>> >
>> > I tested Luis NOTIFY_INC_EPOCH patch (kernel, libfuse, cvmfs) on RHEL9 and can
>> > confirm that in combination with your fix to the symlink truncate it solves all
>> > the problem we had with cvmfs when applying a new revision and at the same time
>> > hammering a symlink with readlink() that would change its target. (
>> > https://github.com/cvmfs/cvmfs/issues/3626 )
>> >
>> > With those two patches we no longer end up with corrupted symlinks or get stuck on an old revision.
>> > (old revision was possible because the kernel started caching the old one again during the update due to the high access rate and the asynchronous evict of inodes)
>> >
>> > As such we would be very happy if this patch could be accepted.
>>
>> Even though this patch and the one that fixed the symlinks corruption [1]
>> aren't really related, it's always good to have extra testing. Thanks a
>> lot for your help, Laura.
>>
>> In the meantime, I hope to send a refreshed v9 of this patch soon (maybe
>> today) as it doesn't apply cleanly to current master anymore. And I also
>> plan to send v2 of the (RFC) patch that adds the workqueue to clean-up
>> expired cache entries.
>
> Don't bother, I just applied the patch with the conflicts fixed up.
Oh, awesome! Thanks a lot, Miklos. I'll focus on the other patch and try
to send v2 later today.
Cheers,
--
Luís
prev parent reply other threads:[~2025-04-15 10:50 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-26 9:14 [PATCH v8] fuse: add more control over cache invalidation behaviour Luis Henriques
2025-03-07 15:30 ` Luis Henriques
2025-03-10 16:42 ` Miklos Szeredi
2025-03-10 20:11 ` Bernd Schubert
2025-03-13 10:24 ` Miklos Szeredi
2025-03-11 11:08 ` Luis Henriques
2025-03-13 10:32 ` Miklos Szeredi
2025-03-13 11:25 ` Luis Henriques
2025-03-13 11:39 ` Miklos Szeredi
2025-03-13 12:11 ` Luis Henriques
2025-03-17 11:28 ` Luis Henriques
2025-04-11 15:14 ` Laura Promberger
2025-04-11 15:16 ` Laura Promberger
2025-04-15 10:34 ` Luis Henriques
2025-04-15 10:41 ` Miklos Szeredi
2025-04-15 10:49 ` Luis Henriques [this message]
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=87mschn1gt.fsf@igalia.com \
--to=luis@igalia.com \
--cc=bschubert@ddn.com \
--cc=david@fromorbit.com \
--cc=laura.promberger@cern.ch \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mharvey@jumptrading.com \
--cc=miklos@szeredi.hu \
/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.