linux-kernel - Re: [PATCH 0/3] exec: Make do_coredump more robust and safer when using pipes in core

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Wed, 1 Jul 2009 11:26:40 -0400
From:	Neil Horman <nhorman@...driver.com>
To:	linux-kernel@...r.kernel.org
Cc:	oleg@...hat.com, alan@...rguk.ukuu.org.uk, andi@...stfloor.org,
	akpm@...ux-foundation.org, earl_chew@...lent.com,
	nhorman@...driver.com
Subject: Re: [PATCH 0/3] exec: Make do_coredump more robust and safer when
	using pipes in core_pattern (v5)

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@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/