linux-kernel - Re: [PATCH 03/10] ptrace: implement PTRACE

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

Date:	Wed, 1 Jun 2011 06:32:31 +0900
From:	Linus Torvalds <torvalds@...ux-foundation.org>
To:	Oleg Nesterov <oleg@...hat.com>
Cc:	Denys Vlasenko <vda.linux@...glemail.com>, indan@....nu,
	Tejun Heo <tj@...nel.org>, bdonlan@...il.com,
	linux-kernel@...r.kernel.org, jan.kratochvil@...hat.com,
	akpm@...ux-foundation.org
Subject: Re: [PATCH 03/10] ptrace: implement PTRACE_SEIZE

On Wed, Jun 1, 2011 at 4:08 AM, Oleg Nesterov <oleg@...hat.com> wrote:
>
> On a seriouse note, of course you are right, but what we should do?

Have we *ever* gotten a bug-report about these kinds of things from
actual users?

IOW, it may be an annoying issue from a theoretical standpoint, but
afaik it's not an annoying issue from a practical user standpoint.

Compare it to the _practically_ annoying issue we had with ^C and
bash, where it was fundamentally impossible to know whether the child
actually exited due to the ^C or not due to the interfaces. That one
caused actual practical issues that people hit, and that were
impossible to work around in theory, and hard to work around in
practice..

In comparison, I don't think pid-vs-namespace issues for ptrace or
some subtle interaction with execve is really all that big of a
problem in practice.

Keep the eye on the ball: look around what people actually complain
about for practical reason that they hit, rather than issues that
people say "wouldn't it be nice if.." about.

             Linus
--
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/