linux-kernel - Re: [PATCH 2/2] selftests/userfaultfd: improve syscall number definition

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: Windows password security audit tool. GUI, reports in PDF.

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

Message-ID: <5602A505.8090804@arm.com>
Date:	Wed, 23 Sep 2015 14:11:33 +0100
From:	Andre Przywara <andre.przywara@....com>
To:	Michael Ellerman <mpe@...erman.id.au>
Cc:	Andrea Arcangeli <aarcange@...hat.com>,
	Shuah Khan <shuahkh@....samsung.com>,
	Andrew Morton <akpm@...ux-foundation.org>,
	"linux-api@...r.kernel.org" <linux-api@...r.kernel.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	Pavel Emelyanov <xemul@...allels.com>,
	Will Deacon <Will.Deacon@....com>
Subject: Re: [PATCH 2/2] selftests/userfaultfd: improve syscall number
 definition

Hi Michael,

On 23/09/15 10:55, Michael Ellerman wrote:
> On Tue, 2015-09-22 at 18:15 +0100, Andre Przywara wrote:
>> On 22/09/15 15:06, Andrea Arcangeli wrote:
>>> Andre, could you see if linux-next (which includes -mm) works for you
>>> by just running "cd tools/testing/selftests/vm/ && make"? If there's
>>> any further change required could you diff it against linux-next?
>>
>> This doesn't compile now for me, because it looks into
>> /usr/include/asm/unistd.h, which I keep to the distribution copy of it.
>> Also linux/userfaultfd.h is missing, because it's brand new.
> ...
>> I guess the right solution would be to hack the Makefile to set the
>> include path to the kernel's copy of include/uapi, though I am not sure
>> this works cleanly for different architectures and separate build
>> directories. I will give this a try ...
> 
> Not that's not the right solution.
> 
> The right solution is to export the kernel headers, the Makefile will pick them
> up (at least in linux-next):

Actually that was I was hoping for, I just missed the possibility of
headers_install to put the files back into the kernel tree (I usually
use it with INSTALL_HDR_PATH for packaging).

> 
>   $ cd linux
>   $ make headers_install
>   $ ls usr/include/
>   asm/  asm-generic/  drm/  linux/  misc/  mtd/  rdma/  scsi/  sound/  uapi/  video/  xen/
>   $ make -C tools/testing/selftests TARGETS=vm
>   ...
>   $ ls tools/testing/selftests/vm/userfaultfd
>   tools/testing/selftests/vm/userfaultfd*

Yes, that works. Now I have just to figure out how to arrange this with
out-of-tree build directories.

Cheers,
Andre.
--
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/