public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jeff Dike <jdike@addtoit.com>
To: "Toralf Förster" <toralf.foerster@gmx.de>
Cc: WANG Cong <xiyou.wangcong@gmail.com>,
	linux-kernel@vger.kernel.org,
	"Kirill A. Shutemov" <k.shutemov@gmail.com>
Subject: Re: UML build issue with v2.6.26-rc2-129-g9604006
Date: Wed, 14 May 2008 10:52:10 -0400	[thread overview]
Message-ID: <20080514145210.GA8639@c2.user-mode-linux.org> (raw)
In-Reply-To: <200805141503.20065.toralf.foerster@gmx.de>

On Wed, May 14, 2008 at 03:03:17PM +0200, Toralf Förster wrote:
> > > Hmm, it seems that I can't reproduce it with your .config.
> > > And <asm/user.h> does exist.
> > 
> > I bet he's using the headers exported by the current kernel, not what
> > his distro gives him.
> > 
> > 			Jeff
> > 
> 
> Right, IIRC I ran into this some times ago under Gentoo Linux.

Commit c1445db9f72db0537c43a2eab6e1b0f6741162f5 unexported asm/user.h
(and linux/user.h):

     Author: Kirill A. Shutemov <k.shutemov@gmail.com>
     Date:   Thu Feb 7 00:15:53 2008 -0800

         Unexport asm/user.h and linux/user.h
    
        Do not export asm/user.h and linux/user.h during make
        headers_install.

As far as I can see, this renders PTRACE_[SG]ETFPREGS and
PTRACE_[SG]ETFPXREGS unusable, as userspace has no way to figure out
what size buffer to pass in.

I think we either need to make user_i387_struct and user_fxsr_struct
available someplace else, or re-export user.h.

	  	    	     Jeff

-- 
Work email - jdike at linux dot intel dot com

      reply	other threads:[~2008-05-14 14:52 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-14 11:01 UML build issue with v2.6.26-rc2-129-g9604006 Toralf Förster
2008-05-14 11:22 ` WANG Cong
2008-05-14 12:55   ` Jeff Dike
2008-05-14 13:03     ` Toralf Förster
2008-05-14 14:52       ` Jeff Dike [this message]

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=20080514145210.GA8639@c2.user-mode-linux.org \
    --to=jdike@addtoit.com \
    --cc=k.shutemov@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=toralf.foerster@gmx.de \
    --cc=xiyou.wangcong@gmail.com \
    /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