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  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:	Mon, 9 Nov 2009 19:00:17 -0500
From:	Bryan Donlan <>
To:	Andrew Morton <>
Cc:	KOSAKI Motohiro <>,
	Americo Wang <>,
	Timo Sirainen <>,
	Ulrich Drepper <>,
	LKML <>,
Subject: Re: [PATCH v5] Added PR_SET_PROCTITLE_AREA option for prctl()

On Mon, Nov 9, 2009 at 5:47 PM, Andrew Morton <> wrote:

> What happens if userspace unmaps the memory after telling the kernel to
> use it?
> Will processes which try to read the command line get an error reading
> /proc?  If so, do all the commandline-reading programs in the world
> handle this in an appropriate fashion?

This case can already occur in the current code; the userspace process
would have to munmap() the top of its stack, but it certainly can do
so if it tries. In any case, access_process_vm() then returns 0
because of the fault, and thus /proc/pid/cmdline is seen to have zero
length. Since a zero-length /proc/pid/cmdline occurs with kernel
threads as well, we know this isn't a problem.
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

Powered by blists - more mailing lists