linux-kernel - Re: UML build issue with v2.6.26-rc2-129-g9604006

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Wed, 14 May 2008 10:52:10 -0400
From:	Jeff Dike <jdike@...toit.com>
To:	Toralf Förster <toralf.foerster@....de>
Cc:	WANG Cong <xiyou.wangcong@...il.com>, linux-kernel@...r.kernel.org,
	"Kirill A. Shutemov" <k.shutemov@...il.com>
Subject: Re: UML build issue with v2.6.26-rc2-129-g9604006

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@...il.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
--
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/