linux-kernel - [PATCH -mm] Disable core ulimit for user core process

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>] [day] [month] [year] [list]

Date:	Fri, 25 Aug 2006 11:01:35 +0200
From:	Andi Kleen <ak@...e.de>
To:	akpm@...l.org
Cc:	linux-kernel@...r.kernel.org
Subject: [PATCH -mm] Disable core ulimit for user core process

[I can't remember if I already sent this one off or not. If yes
please ignore the dup.]
[This is an incremental patch for the user-core patch series which
is in -mm]

Disable core files for pipe user helpers

This addresses one of the review comments earlier for the user core
patchkit: when the core dump handler is executed make sure there
is no potential for recursion in case it crashes again.

This currently does it for all pipe user mode helpers. In theory
it could be done only for core dump user helpers, but there are
currently no other users of this function.

Signed-off-by: Andi Kleen <ak@...e.de>

Index: linux/kernel/kmod.c
===================================================================
--- linux.orig/kernel/kmod.c
+++ linux/kernel/kmod.c
@@ -35,6 +35,7 @@
 #include <linux/mount.h>
 #include <linux/kernel.h>
 #include <linux/init.h>
+#include <linux/resource.h>
 #include <asm/uaccess.h>

 extern int max_threads;
@@ -158,6 +159,9 @@ static int ____call_usermodehelper(void 
 		FD_SET(0, fdt->open_fds);
 		FD_CLR(0, fdt->close_on_exec);
 		spin_unlock(&f->file_lock);
+
+		/* and disallow core files too */
+		current->signal->rlim[RLIMIT_CORE] = (struct rlimit){0, 0};
 	}

 	/* We can run anywhere, unlike our parent keventd(). */
-
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/