Date: Wed, 1 Jul 2009 11:26:40 -0400
From: Neil Horman <nhorman@tuxdriver.com>
To: linux-kernel@vger.kernel.org
Cc: oleg@redhat.com, alan@lxorguk.ukuu.org.uk, andi@firstfloor.org,
       akpm@linux-foundation.org, earl_chew@agilent.com, nhorman@tuxdriver.com
Subject: Re: [PATCH 0/3] exec: Make do_coredump more robust and safer when
	using pipes in core_pattern (v5)
Message-ID: <20090701152640.GD29601@hmsreliant.think-freely.org>
References: <20090622172818.GB14673@hmsreliant.think-freely.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20090622172818.GB14673@hmsreliant.think-freely.org>
User-Agent: Mutt/1.5.18 (2008-05-17)
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 931
Lines: 24

Ok, version 5 of this patchset.  The frist two patches are identical.  The
second two have some minor cleanups

Change notes:

1) Patch 3 has the wait_for_dump_helper modified a bit to remove the ISFIFO
check.  Instead, we use the ispipe test in do_coredump.

2) wait_for_dump_helpers is modified slightly to move the readers/writers
modification outside of the while loop, so we don't have to constantly churn
those values.

3) Augment the test to call wait_for_dump_helpers to include a non-zero check on
core_pipe_limit.  This restores the documented sysctl behavior that I intended,
which only allows for waiting on processes when core_pipe_limit is non-zero.

Patches Follow
Neil

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/