All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ian Kent <raven@themaw.net>
To: Goldwyn Rodrigues <rgoldwyn@suse.de>
Cc: viro@zeniv.linux.org.uk, autofs@vger.kernel.org,
	linux-fsdevel@vger.kernel.org
Subject: Re: [RFC] Don't propagate automount
Date: Tue, 29 Oct 2019 07:57:28 +0800	[thread overview]
Message-ID: <2dcbe8a95153e43cb179733f03de7da80fbbc6b2.camel@themaw.net> (raw)
In-Reply-To: <20191028162835.dtyjwwv57xqxrpap@fiona>

On Mon, 2019-10-28 at 11:28 -0500, Goldwyn Rodrigues wrote:
> Hi Ian,
> 
> On 10:14 02/10, Ian Kent wrote:
> > On Tue, 2019-10-01 at 14:09 -0500, Goldwyn Rodrigues wrote:
> <snip>
> 
> > Anyway, it does sound like it's worth putting time into
> > your suggestion of a kernel change.
> > 
> > Unfortunately I think it's going to take a while to work
> > out what's actually going on with the propagation and I'm
> > in the middle of some other pressing work right now.
> 
> Have you have made any progress on this issue?

Sorry I haven't.
I still want to try and understand what's going on there.

> As I mentioned, I am fine with a userspace solution of defaulting
> to slave mounts all of the time instead of this kernel patch.

Oh, I thought you weren't keen on that recommendation.

That shouldn't take long to do so I should be able to get that done
and post a patch pretty soon.

I'll get back to looking at the mount propagation code when I get a
chance. Unfortunately I haven't been very successful when making
changes to that area of code in the past ...

Ian


  reply	other threads:[~2019-10-28 23:57 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-26 19:52 [RFC] Don't propagate automount Goldwyn Rodrigues
2019-09-27  1:35 ` Ian Kent
2019-09-27  7:09   ` Ian Kent
2019-09-27  7:26     ` Ian Kent
2019-09-27  7:41       ` Ian Kent
2019-09-27 10:51         ` Ian Kent
2019-09-27 16:16           ` Goldwyn Rodrigues
2019-09-28  1:47             ` Ian Kent
2019-10-01 19:09               ` Goldwyn Rodrigues
2019-10-02  2:14                 ` Ian Kent
2019-10-28 16:28                   ` Goldwyn Rodrigues
2019-10-28 23:57                     ` Ian Kent [this message]
2019-10-29  6:39                       ` Ian Kent
2019-10-29  6:40                         ` Ian Kent
2019-10-29 16:00                         ` Goldwyn Rodrigues
2019-10-30  6:01                           ` Ian Kent
2019-10-30  6:05                             ` Ian Kent
2019-10-30 12:05                           ` Ian Kent
2019-10-30 19:28                             ` Goldwyn Rodrigues

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=2dcbe8a95153e43cb179733f03de7da80fbbc6b2.camel@themaw.net \
    --to=raven@themaw.net \
    --cc=autofs@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=rgoldwyn@suse.de \
    --cc=viro@zeniv.linux.org.uk \
    /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.