From: Luis Henriques <luis@igalia.com>
To: Sam Lewis via fuse-devel <fuse-devel@lists.sourceforge.net>
Cc: miklos@szeredi.hu, Sam Lewis <samclewis@google.com>,
bernd.schubert@fastmail.fm, linux-fsdevel@vger.kernel.org
Subject: Re: [fuse-devel] Symlink caching: Updating the target can result in corrupted symlinks - kernel issue?
Date: Thu, 20 Feb 2025 09:37:07 +0000 [thread overview]
Message-ID: <87h64p7y9o.fsf@igalia.com> (raw)
In-Reply-To: <20250219195400.1700787-1-samclewis@google.com> (Sam Lewis via fuse-devel's message of "Wed, 19 Feb 2025 19:54:00 +0000")
On Wed, Feb 19 2025, Sam Lewis via fuse-devel wrote:
> Hi Miklos.
>
> I work at Google on the Android team, and we have a build system that would
> benefit greatly from the kernel symlink cache. In my testing, I can easily
> reproduce the truncation using the steps outlined by Laura. I tested your patch
> and have confirmed it fixes the bug.
Oh, wow! I've tried to reproduce the issue myself and I've been failing
miserably. Are you using CVMFS as well, or can you reproduce it with some
synthetic fuse server? I've tried both approaches but no luck so far.
Cheers,
--
Luís
> What steps need to be taken to merge your fix? Can I help in any way?
>
> Thanks,
> Sam Lewis
>
>
> --
> fuse-devel mailing list
> To unsubscribe or subscribe, visit https://lists.sourceforge.net/lists/listinfo/fuse-devel
prev parent reply other threads:[~2025-02-20 9:37 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <GV0P278MB07187F9B0E7B576AD0B362B485802@GV0P278MB0718.CHEP278.PROD.OUTLOOK.COM>
2024-08-19 16:04 ` [fuse-devel] Symlink caching: Updating the target can result in corrupted symlinks - kernel issue? Bernd Schubert
2024-08-22 12:41 ` Miklos Szeredi
2024-09-25 12:20 ` Miklos Szeredi
2024-09-25 14:07 ` Bernd Schubert
2024-09-25 14:25 ` Miklos Szeredi
2024-09-25 21:42 ` Bernd Schubert
2025-02-19 19:54 ` Sam Lewis
2025-02-19 20:22 ` Bernd Schubert
2025-02-20 9:57 ` Miklos Szeredi
2025-02-20 10:00 ` Bernd Schubert
2025-02-20 15:50 ` Sam Lewis
2025-02-20 9:37 ` 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=87h64p7y9o.fsf@igalia.com \
--to=luis@igalia.com \
--cc=bernd.schubert@fastmail.fm \
--cc=fuse-devel@lists.sourceforge.net \
--cc=linux-fsdevel@vger.kernel.org \
--cc=miklos@szeredi.hu \
--cc=samclewis@google.com \
/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.