From: Ian Kent <raven@themaw.net>
To: Miklos Szeredi <miklos@szeredi.hu>
Cc: autofs@vger.kernel.org, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org, sukadev@linux.vnet.ibm.com,
serge.hallyn@canonical.com, ebiederm@xmission.com
Subject: Re: [PATCH 0/2] struct pid-ify autofs4
Date: Tue, 25 Sep 2012 09:46:44 +0800 [thread overview]
Message-ID: <1348537604.2307.8.camel@perseus.themaw.net> (raw)
In-Reply-To: <87d31bczo7.fsf@tucsk.pomaz.szeredi.hu>
On Mon, 2012-09-24 at 15:34 +0200, Miklos Szeredi wrote:
> Ian Kent <raven@themaw.net> writes:
>
> > On Fri, 2012-09-21 at 17:44 +0200, Miklos Szeredi wrote:
> >> Miklos Szeredi <miklos@szeredi.hu> writes:
> >>
> >> > These two patches change autofs4 to store struct pid pointers instead of pid_t
> >> > values.
> >> >
> >> > Fixed various issues with the previous post. Not tested, handle with
> >> > care!
> >>
> >> Customer gave positive test results.
> >
> > For what exactly, there's no problem description in these patches?
>
> From what I understand (and I'm not an expert by any means) is that
> autofs doesn't work if containers are used. The first patch fixes this.
Yeah, the problem with that is that "autofs doesn't work if containers
are used" is ill defined since there are use cases where it does, I
believe. At the very least, ill defined in my view of things.
But I can't even sensibly discuss it because of the lack of specified
use cases and requirements for each. So, there's a chance this will
break another case that does work.
All I can do is ask annoying questions each time time I see related
patches.
>
> Both the patches replace pid_t with a refcounted struct pid object,
> which has better lifetime properties: you don't know whether a pid_t is
> valid, because pid numbers are reused, while pid objects remain valid
> until there are no more references to them.
Yep, at least I got that.
>
> Thanks,
> Miklos
next prev parent reply other threads:[~2012-09-25 1:46 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-19 15:29 Miklos Szeredi
2012-09-19 15:29 ` [PATCH 1/2] Replace pid_t in autofs4 with struct pid reference Miklos Szeredi
2012-09-19 15:29 ` [PATCH 2/2] autofs4: store struct pids in autofs_waitqs Miklos Szeredi
2012-09-21 15:44 ` [PATCH 0/2] struct pid-ify autofs4 Miklos Szeredi
2012-09-24 0:38 ` Ian Kent
2012-09-24 13:34 ` Miklos Szeredi
2012-09-25 1:46 ` Ian Kent [this message]
2012-09-25 2:56 ` Eric W. Biederman
2012-10-11 3:34 ` Ian Kent
2012-10-24 14:59 ` Miklos Szeredi
2012-10-25 0:25 ` Ian Kent
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=1348537604.2307.8.camel@perseus.themaw.net \
--to=raven@themaw.net \
--cc=autofs@vger.kernel.org \
--cc=ebiederm@xmission.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=miklos@szeredi.hu \
--cc=serge.hallyn@canonical.com \
--cc=sukadev@linux.vnet.ibm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®