From: Ian Kent <raven@themaw.net>
To: Steve Thompson <smt@vgersoft.com>
Cc: autofs@linux.kernel.org
Subject: Re: Wrong network
Date: Thu, 17 Feb 2011 09:58:08 +0800 [thread overview]
Message-ID: <1297907888.2893.21.camel@perseus> (raw)
In-Reply-To: <alpine.LRH.0.9999.1102161657250.24619@helios.vgersoft.com>
On Wed, 2011-02-16 at 17:00 -0500, Steve Thompson wrote:
> On Tue, 15 Feb 2011, Ian Kent wrote:
>
> > As far as the hang you have seen, I don't know why that's happening, the
> > patches were added between el5_5.4 and el5_5.6 have been around for
> > quite a while, upstream and in Fedora and tested by more than one
> > customer, so I didn't expect to hear of a problem.
>
> While thinking about this I noticed that the automount hangs all occurred
> on systems that had SElinux set to enforcing mode; there were no hangs on
> systems with SElinux either disabled or in permissive mode. So for now I
> have disabled SElinux on most of the systems on which a hang was observed.
> So far, so good: no more hangs. But it's only been a couple of days, so I
> will keep an eye on it.
Right, but to help me a gdb backtrace (the "thr a a bt") of a hung
automount process would be useful.
Also, an avc log from a system with selinux in permissive mode is needed
to find out what is happening. I don't think the changes to the package
caused this breakage and QA testing is always done with selinux in
enforcing mode. So maybe there has been an selinux policy change too.
Ian
prev parent reply other threads:[~2011-02-17 1:58 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-12 14:29 Wrong network Steve Thompson
2011-02-12 15:38 ` Frank Thommen
2011-02-12 19:28 ` Steve Thompson
2011-02-12 20:21 ` Steve Thompson
2011-02-14 2:06 ` Ian Kent
2011-02-14 19:22 ` Steve Thompson
2011-02-15 3:06 ` Ian Kent
2011-02-15 12:04 ` Steve Thompson
2011-02-15 12:15 ` Ian Kent
2011-02-15 12:40 ` Steve Thompson
2011-02-15 13:03 ` Ian Kent
2011-02-16 22:00 ` Steve Thompson
2011-02-17 1:58 ` Ian Kent [this message]
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=1297907888.2893.21.camel@perseus \
--to=raven@themaw.net \
--cc=autofs@linux.kernel.org \
--cc=smt@vgersoft.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 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.