Message-ID: <423BEC0E.300@inode.info>
Date: Sat, 19 Mar 2005 10:08:30 +0100
From: Richard Fuchs <richard.fuchs@inode.info>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.5) Gecko/20050105 Debian/1.7.5-1
MIME-Version: 1.0
To: linux-kernel@vger.kernel.org
Subject: /proc/$pid/mem
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 938
Lines: 22

Aloha!

I know it has been discussed before, but I must express my feelings 
about this issue nonetheless. I find it a major pain in the back that 
/proc/$pid/mem isn't readable by an unrelated process without doing a 
PTRACE_ATTACH first.

I mainly want to ask: is there a good reason to not drop this restriction?

I can read all the machine's physical memory and all of the kernel's 
address space (/dev/mem, /proc/kcore) non-intrusively, but I can't do 
the same on a single process. It seems to me that /proc/$pid/mem should 
work analogous to /dev/mem or /proc/kcore, but currently in practice it 
doesn't, and I don't see a good reason why it is supposed to be that way.

Cheers
Richard
-
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/