public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: Cyrill Gorcunov <gorcunov@gmail.com>
Cc: Ingo Molnar <mingo@elte.hu>, Thomas Gleixner <tglx@linutronix.de>,
	Sam Ravnborg <sam@ravnborg.org>,
	Harvey Harrison <harvey.harrison@gmail.com>,
	LKML <linux-kernel@vger.kernel.org>,
	Jaswinder Singh Rajput <jaswinderlinux@gmail.com>
Subject: Re: [PATCH -tip] x86: headers - fix export private data to userspace
Date: Wed, 14 Jan 2009 11:42:56 -0800	[thread overview]
Message-ID: <496E4040.9080701@zytor.com> (raw)
In-Reply-To: <20090113183456.GA14470@localhost>

Cyrill Gorcunov wrote:
> Impact: cleanup
> 
> 'make headers_check' warn us about leaking of kernel private
> (mostly compile time vars) data to userspace in headers. Fix it.
> 
> More detailed report for easier reviewing:
> 
> 1) boot.h - neither BOOT_HEAP_SIZE, BOOT_STACK_SIZE refs
>    was found by searching thru net (ie in user-space area).
> 
> 2) prctl.h - sys_arch_prctl is completely removed from
>    header since frankly I don't even understand why we
>    describe it here. It is described like
>     __SYSCALL(__NR_arch_prctl, sys_arch_prctl) in unistd_64.h
>    and implemented in process_64.c. User-mode linux involved?
>    So this one in fact is suspicious.
> 
> 3) ptrace-abi.h - ptrace_bts_config struct is wrapped
>    by __KERNEL__ -- not sure if it was ever proposed for
>    userland.
> 
> 4) setup.h - COMMAND_LINE_SIZE saved for userspace, bootloaders
>    could use it.
> 
> 5) sigcontext32.h - we really need linux/types.h here
>    since we use __u... types.
> 
> Signed-off-by: Cyrill Gorcunov <gorcunov@openvz.org>

Hi Cyrill; in addition to nonexporting COMMAND_LINE_SIZE, could you 
submit this as a patchset to make post-integration bisect easier?

	-hpa

  parent reply	other threads:[~2009-01-14 19:42 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-13 18:34 [PATCH -tip] x86: headers - fix export private data to userspace Cyrill Gorcunov
2009-01-13 18:37 ` Harvey Harrison
2009-01-13 18:49   ` H. Peter Anvin
2009-01-13 18:52     ` Cyrill Gorcunov
2009-01-13 18:55       ` H. Peter Anvin
2009-01-13 19:00         ` Cyrill Gorcunov
2009-01-13 19:03           ` H. Peter Anvin
2009-01-13 19:12             ` Cyrill Gorcunov
2009-01-13 19:05     ` Harvey Harrison
2009-01-13 18:50   ` Cyrill Gorcunov
2009-01-13 18:54     ` H. Peter Anvin
2009-01-13 18:56       ` Cyrill Gorcunov
2009-01-14 19:42 ` H. Peter Anvin [this message]
2009-01-14 19:49   ` Cyrill Gorcunov
2009-01-14 20:05     ` Cyrill Gorcunov

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=496E4040.9080701@zytor.com \
    --to=hpa@zytor.com \
    --cc=gorcunov@gmail.com \
    --cc=harvey.harrison@gmail.com \
    --cc=jaswinderlinux@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=sam@ravnborg.org \
    --cc=tglx@linutronix.de \
    /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