From: Richard Fuchs <richard.fuchs@inode.info>
To: linux-kernel@vger.kernel.org
Subject: /proc/$pid/mem
Date: Sat, 19 Mar 2005 10:08:30 +0100 [thread overview]
Message-ID: <423BEC0E.300@inode.info> (raw)
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
reply other threads:[~2005-03-19 9:08 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=423BEC0E.300@inode.info \
--to=richard.fuchs@inode.info \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.