From: Bernd Schubert <bernd@bsbernd.com>
To: "Darrick J. Wong" <djwong@kernel.org>
Cc: fuse-devel@lists.linux.dev
Subject: Re: [PATCH 03/10] mount_service: refuse OPEN after the MNTPT request
Date: Mon, 28 Sep 2026 11:21:11 +0200 [thread overview]
Message-ID: <479220fa-ad50-4ab8-af10-fe3cb947a07e@bsbernd.com> (raw)
In-Reply-To: <20260925220714.GS6253@frogsfrogsfrogs>
On 9/26/26 00:07, Darrick J. Wong wrote:
> On Fri, Sep 25, 2026 at 12:23:31AM +0200, Bernd Schubert via B4 Relay wrote:
>> From: Bernd Schubert <bernd@bsbernd.com>
>>
>> The fuse server sends fuservicemount3 a series of requests: OPEN for
>> its backing file, MNTPT to name the mount point, then MOUNT. The server
>> chooses the order. For a directory mount point, attach_to_mountpoint()
>> changes the working directory of the helper to the mount point. The
>> helper then mounts on ".", so a rename of the path cannot redirect the
>> mount.
>>
>> A relative path in an OPEN request after MNTPT resolved inside the
>> mount point. For "fuservicemount3 disk.img /mnt -t fuse.service_ll",
>> an OPEN of "disk.img" matched the command line argument, but the helper
>> opened /mnt/disk.img, not disk.img in the user's working directory. The
>> helper now refuses OPEN once the mount point is set. No in-tree server
>> sends OPEN after MNTPT.
>
> How about absolute paths? The resolution of those remain the same after
> the cwd changes.
Next version switches to openat and should handle all of that.
Thanks,
Bernd
next prev parent reply other threads:[~2026-09-28 9:21 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-24 22:23 [PATCH 00/10] libfuse: Add mount service safety checks and tests Bernd Schubert via B4 Relay
2026-09-24 22:23 ` [PATCH 01/10] mount_service: move the command line check into arg_in_cmdline() Bernd Schubert via B4 Relay
2026-09-25 21:40 ` Darrick J. Wong
2026-09-24 22:23 ` [PATCH 02/10] mount_service: open only paths named on the command line Bernd Schubert via B4 Relay
2026-09-25 22:05 ` Darrick J. Wong
2026-09-28 9:19 ` Bernd Schubert
2026-09-24 22:23 ` [PATCH 03/10] mount_service: refuse OPEN after the MNTPT request Bernd Schubert via B4 Relay
2026-09-25 22:07 ` Darrick J. Wong
2026-09-28 9:21 ` Bernd Schubert [this message]
2026-09-24 22:23 ` [PATCH 04/10] util: give fuservicemount3 an absolute build-tree runpath Bernd Schubert via B4 Relay
2026-09-25 22:09 ` Darrick J. Wong
2026-09-24 22:23 ` [PATCH 05/10] mount.fuse: free the options on the service mount return path Bernd Schubert via B4 Relay
2026-09-25 22:10 ` Darrick J. Wong
2026-09-24 22:23 ` [PATCH 06/10] example/single_file: take no sector size from a regular backing file Bernd Schubert via B4 Relay
2026-09-25 22:13 ` Darrick J. Wong
2026-09-24 22:23 ` [PATCH 07/10] test: check which files fuservicemount3 opens for the server Bernd Schubert via B4 Relay
2026-09-24 22:23 ` [PATCH 08/10] test: check what fuservicemount3 refuses Bernd Schubert via B4 Relay
2026-09-24 22:23 ` [PATCH 09/10] test: mount the service examples through fuservicemount3 Bernd Schubert via B4 Relay
2026-09-25 22:25 ` Darrick J. Wong
2026-09-28 9:27 ` Bernd Schubert
2026-09-24 22:23 ` [PATCH 10/10] test: run mkfs.ext4 through the service examples Bernd Schubert via B4 Relay
2026-09-25 22:27 ` Darrick J. Wong
2026-09-28 9:30 ` Bernd Schubert
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=479220fa-ad50-4ab8-af10-fe3cb947a07e@bsbernd.com \
--to=bernd@bsbernd.com \
--cc=djwong@kernel.org \
--cc=fuse-devel@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