util-linux.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Karel Zak <kzak@redhat.com>
To: Linus Heckemann <git@sphalerite.org>
Cc: util-linux@vger.kernel.org
Subject: Re: [PATCH] libmount: provide tree fd even when a mount helper is used
Date: Fri, 31 May 2024 11:41:25 +0200	[thread overview]
Message-ID: <20240531094125.r2nvmio47itrtzep@ws.net.home> (raw)
In-Reply-To: <20240530180041.3447273-1-git@sphalerite.org>

On Thu, May 30, 2024 at 08:00:34PM +0200, Linus Heckemann wrote:
> Previously, the X-mount.subdir option would fail (mount exited with
> code 0, but the target was not mounted) when a helper was used.

Do you have any examples that can easily reproduce it?

> In addition to fixing X-mount.subdir, this allows dropping the
> fallback behaviour previously implemented specifically by the
> set_vfsflags and set_propagation hooks.
> 
> I realise this patch is not acceptable as is, since I just exported
> the previously private open_mount_tree symbol from hook_mount.c

Perhaps it is unnecessary to only keep the API file descriptors in
hook_mount.c. It is a generic feature and we may see more use
cases where it would make sense to use it in other places.

I can imagine having the file descriptors in the libmnt_context
structure and initializing them through functions in context.c (which
would involve renaming open_mount_tree() to something more
appropriate). It could potentially be a public library function so
that libmount applications can also utilize it.

I will think about it :-)

    Karel

-- 
 Karel Zak  <kzak@redhat.com>
 http://karelzak.blogspot.com


  reply	other threads:[~2024-05-31  9:41 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-30 18:00 [PATCH] libmount: provide tree fd even when a mount helper is used Linus Heckemann
2024-05-31  9:41 ` Karel Zak [this message]
2024-05-31 14:32   ` Linus Heckemann
2024-06-03 11:20   ` Karel Zak

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=20240531094125.r2nvmio47itrtzep@ws.net.home \
    --to=kzak@redhat.com \
    --cc=git@sphalerite.org \
    --cc=util-linux@vger.kernel.org \
    /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;
as well as URLs for NNTP newsgroup(s).