From: Arvid Brodin <Arvid.Brodin@xdin.com>
To: "Eric W. Biederman" <ebiederm@xmission.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Al Viro <viro@zeniv.linux.org.uk>,
"Cyrill Gorcunov" <gorcunov@openvz.org>,
David Rientjes <rientjes@google.com>
Subject: Re: [PATCH] fs/proc: Add process text segment md5-summing
Date: Wed, 14 Nov 2012 01:45:46 +0000 [thread overview]
Message-ID: <50A2F7C9.2030006@xdin.com> (raw)
In-Reply-To: <871ufyjli4.fsf@xmission.com>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset="utf-8", Size: 780 bytes --]
On 2012-11-13 03:16, Eric W. Biederman wrote:
> To add another nail in the coffin.
>
> You can do this with ptrace or with /proc/<pid>/mem without a kernel
> patch.
>
> To make this safe would need a ptrace_may_acces(PTRACE_MODE_READ)
> permission check. At which point not doing this with ptrace just adds
> up to extra kernel maintenance for no real point.
If my client still wants to run text segment checks, even after the
criticism of the idea behind the patch, the above should prove very
handy. Thanks!
--
Arvid Brodin | Consultant (Linux)
XDIN AB | Knarrarnäsgatan 7 | SE-164 40 Kista | Sweden | xdin.comÿôèº{.nÇ+‰·Ÿ®‰†+%ŠËÿ±éݶ\x17¥Šwÿº{.nÇ+‰·¥Š{±þG«éÿŠ{ayº\x1dʇڙë,j\a¢f£¢·hšïêÿ‘êçz_è®\x03(階ŠÝ¢j"ú\x1a¶^[m§ÿÿ¾\a«þG«éÿ¢¸?™¨èÚ&£ø§~á¶iO•æ¬z·švØ^\x14\x04\x1a¶^[m§ÿÿÃ\fÿ¶ìÿ¢¸?–I¥
next prev parent reply other threads:[~2012-11-14 1:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-12 21:36 [PATCH] fs/proc: Add process text segment md5-summing Arvid Brodin
2012-11-12 23:03 ` Andrew Morton
2012-11-13 2:16 ` Eric W. Biederman
2012-11-14 1:45 ` Arvid Brodin [this message]
2012-11-14 0:11 ` Arvid Brodin
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=50A2F7C9.2030006@xdin.com \
--to=arvid.brodin@xdin.com \
--cc=akpm@linux-foundation.org \
--cc=ebiederm@xmission.com \
--cc=gorcunov@openvz.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rientjes@google.com \
--cc=viro@zeniv.linux.org.uk \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox