From: "Marion, Mike" <mmarion@qualcomm.com>
To: "autofs@vger.kernel.org" <autofs@vger.kernel.org>
Subject: Re: [PATCH] autofs: fix contained_in_local_fs and improve scalability
Date: Tue, 22 Mar 2016 01:24:46 +0000 [thread overview]
Message-ID: <20160322012444.GE28078@qualcomm.com> (raw)
In-Reply-To: <56F070F6.7030802@suse.com>
On Mon, Mar 21, 2016 at 06:08:54PM -0400, Jeff Mahoney wrote:
> > I thought that was bad so this really needs to be fixed.
> >
> > I am puzzled why I haven't seen other bug reports.
>
> Yeah, I usually see all of the autofs bugs reported against our products
> and it's the first time I've seen it too.
Probably because enterprise customers tend to be behind the curve
already. I know the engineers we support are even further behind
because the tools they're using are behind even where we'd like to be.
When the first moves to bring out "Enterprise Linux" distros started, the
big EDA ISVs we work with (Synopsys, Cadence, etc) thought the 18 month
time-frames being discussed then were too fast. If you can believe it.
The SLE12 (and RH7.x) stuff is another special case though because our
internal CM systems needed to be updated to handle the big change that
systemd was, but still work on the older stuff as well. We didn't get
that to the point where we could test with our namespaces until SP1
had come out.
We're the/a customer that raised this issue BTW. We have pretty huge
direct maps that have been working fine for quite a few years, until the
/etc/mtab symlink. Our large maps and heavy autofs usage has led us
into breaking it in many... "interesting" ways over the years that
helped the Suse guys get patches upstream that benefit everyone though,
so there's that.
--
Mike Marion-Unix SysAdmin/Sr. Staff IT Engineer-http://www.qualcomm.com
Homer: "Oh.. I hate having parties. The toilet always gets backed up!"
==> Simpsons--
To unsubscribe from this list: send the line "unsubscribe autofs" in
next prev parent reply other threads:[~2016-03-22 1:24 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-18 20:44 [BUG] contained_in_local_fs will *always* return true Jeff Mahoney
2016-03-18 21:25 ` [PATCH] autofs: fix contained_in_local_fs and improve scalability Jeff Mahoney
2016-03-19 20:58 ` Jeff Mahoney
2016-03-21 3:44 ` Ian Kent
2016-03-21 22:08 ` Jeff Mahoney
2016-03-22 0:24 ` Ian Kent
2016-03-22 3:50 ` Jeff Mahoney
2016-03-22 14:13 ` [PATCH] autofs: improve scalability of direct mount path component creation Jeff Mahoney
2016-03-22 14:38 ` Jeff Mahoney
2016-03-24 1:23 ` Ian Kent
2016-03-22 1:24 ` Marion, Mike [this message]
2016-03-20 13:05 ` [BUG] contained_in_local_fs will *always* return true 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=20160322012444.GE28078@qualcomm.com \
--to=mmarion@qualcomm.com \
--cc=autofs@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 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.