From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751155AbcFVVvD (ORCPT ); Wed, 22 Jun 2016 17:51:03 -0400 Received: from mx1.redhat.com ([209.132.183.28]:37539 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750718AbcFVVvB (ORCPT ); Wed, 22 Jun 2016 17:51:01 -0400 Date: Wed, 22 Jun 2016 23:51:42 +0200 From: Oleg Nesterov To: "Eric W. Biederman" Cc: "Michael Kerrisk (man-pages)" , Jann Horn , James Morris , linux-man , Stephen Smalley , lkml , Kees Cook , linux-security-module , Linux API Subject: Re: Documenting ptrace access mode checking Message-ID: <20160622215142.GA14751@redhat.com> References: <87ziqewc3r.fsf@x220.int.ebiederm.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <87ziqewc3r.fsf@x220.int.ebiederm.org> User-Agent: Mutt/1.5.18 (2008-05-17) X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.5.110.25]); Wed, 22 Jun 2016 21:51:00 +0000 (UTC) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 06/21, Eric W. Biederman wrote: > > Adding Oleg just because he seems to do most of the ptrace related > maintenance these days. so I have to admit that I never even tried to actually understand ptrace_may_access ;) > We certainly need something that gives a high level view so people > reading the man page can know what to expect. If you get down into the > weeds we run the danger of people beginning to think they can depend > upon bugs in the implementation. Personally I agree. I think "man ptrace" shouldn't not tell too much about kernel internals. Perhaps Documentation/security/ makes more sense? Oleg.