From: Randy Dunlap <randy.dunlap@oracle.com>
To: Helmut Grohne <helmut@subdivi.de>
Cc: linux-kernel@vger.kernel.org, andrea@qumranet.com
Subject: Re: PROBLEM: SECCOMP documentation outdated in some arch/*/Kconfig
Date: Tue, 22 Jan 2008 16:21:56 -0800 [thread overview]
Message-ID: <20080122162156.e62e4285.randy.dunlap@oracle.com> (raw)
In-Reply-To: <20080122144156.GA29993@alf.mars>
On Tue, 22 Jan 2008 15:41:58 +0100 Helmut Grohne wrote:
> Hi,
>
> I didn't find out whom to report this bug to and thus report to
> linux-kernel@vger.kernel.org as described in
> http://kernel.org/pub/linux/docs/lkml/reporting-bugs.html.
Andrea cc-ed.
Helmut, would you care to make a patch that you think should be
applied to the current kernel source tree?
> I'm posting from outside, so please CC me.
>
> [1] The description about seccomp is outdated in some arch/*/Kconfig
> files.
>
> [2] According to the source (2.6.23.14) seccomp is to be activated using
> pcrtl. It was previously activated using a file /proc/<pid>/seccomp.
> The Kconfig documentation (also displayed in menuconfig) does not
> reflect this change and is thus wrong.
>
> [3] seccomp documentation Kconfig
>
> [4] 2.6.23.14, seems to also apply to git head:
> http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=blob;f=arch/x86/Kconfig;h=80b7ba4056dbbb566841c1e1cbef9475730fe199;hb=HEAD
>
> [5] no oops
>
> [6] less arch/x86_64/Kconfig
> /SECCOMP
>
> [7] Ask me again if you really think you need information about the
> environment for a documentation bug.
---
~Randy
next prev parent reply other threads:[~2008-01-23 0:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-22 14:41 PROBLEM: SECCOMP documentation outdated in some arch/*/Kconfig Helmut Grohne
2008-01-23 0:21 ` Randy Dunlap [this message]
2008-01-24 17:19 ` Andrea Arcangeli
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=20080122162156.e62e4285.randy.dunlap@oracle.com \
--to=randy.dunlap@oracle.com \
--cc=andrea@qumranet.com \
--cc=helmut@subdivi.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).