linux-kselftest.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: rppt at linux.vnet.ibm.com (Mike Rapoport)
Subject: [PATCH] selftests:vm: add include file
Date: Sat, 14 Apr 2018 20:28:27 +0300	[thread overview]
Message-ID: <20180414172826.GA3211@rapoport-lnx> (raw)
In-Reply-To: <1523732936-42546-1-git-send-email-peng.hao2@zte.com.cn>

On Sun, Apr 15, 2018 at 03:08:56AM +0800, Peng Hao wrote:
> userfaultfd.c: In function ‘hugetlb_release_pages’:
> userfaultfd.c:145:25: error: ‘FALLOC_FL_PUNCH_HOLE’ undeclared 
> (first use in this function)
> 
> Signed-off-by: Peng Hao <peng.hao2 at zte.com.cn>
> ---
>  tools/testing/selftests/vm/userfaultfd.c | 1 +
>  1 file changed, 1 insertion(+)
> 
> diff --git a/tools/testing/selftests/vm/userfaultfd.c b/tools/testing/selftests/vm/userfaultfd.c
> index de2f9ec..d8fe447 100644
> --- a/tools/testing/selftests/vm/userfaultfd.c
> +++ b/tools/testing/selftests/vm/userfaultfd.c
> @@ -68,6 +68,7 @@
>  #include <linux/userfaultfd.h>
>  #include <setjmp.h>
>  #include <stdbool.h>
> +#include <linux/falloc.h>
  
The FALLOC_FL_PUNCH_HOLE definition should come from #include <fcntl.h>.
What are the versions of your kernel and the libc-development package?

>  #ifdef __NR_userfaultfd
>  
> -- 
> 1.8.3.1
> 

-- 
Sincerely yours,
Mike.

--
To unsubscribe from this list: send the line "unsubscribe linux-kselftest" in
the body of a message to majordomo at vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

WARNING: multiple messages have this Message-ID (diff)
From: rppt@linux.vnet.ibm.com (Mike Rapoport)
Subject: [PATCH] selftests:vm: add include file
Date: Sat, 14 Apr 2018 20:28:27 +0300	[thread overview]
Message-ID: <20180414172826.GA3211@rapoport-lnx> (raw)
Message-ID: <20180414172827.0x9tIWRIwcSe2Q2tFG12H12dWWO8hQRNaiOR7tqgWac@z> (raw)
In-Reply-To: <1523732936-42546-1-git-send-email-peng.hao2@zte.com.cn>

On Sun, Apr 15, 2018@03:08:56AM +0800, Peng Hao wrote:
> userfaultfd.c: In function ‘hugetlb_release_pages’:
> userfaultfd.c:145:25: error: ‘FALLOC_FL_PUNCH_HOLE’ undeclared 
> (first use in this function)
> 
> Signed-off-by: Peng Hao <peng.hao2 at zte.com.cn>
> ---
>  tools/testing/selftests/vm/userfaultfd.c | 1 +
>  1 file changed, 1 insertion(+)
> 
> diff --git a/tools/testing/selftests/vm/userfaultfd.c b/tools/testing/selftests/vm/userfaultfd.c
> index de2f9ec..d8fe447 100644
> --- a/tools/testing/selftests/vm/userfaultfd.c
> +++ b/tools/testing/selftests/vm/userfaultfd.c
> @@ -68,6 +68,7 @@
>  #include <linux/userfaultfd.h>
>  #include <setjmp.h>
>  #include <stdbool.h>
> +#include <linux/falloc.h>
  
The FALLOC_FL_PUNCH_HOLE definition should come from #include <fcntl.h>.
What are the versions of your kernel and the libc-development package?

>  #ifdef __NR_userfaultfd
>  
> -- 
> 1.8.3.1
> 

-- 
Sincerely yours,
Mike.

--
To unsubscribe from this list: send the line "unsubscribe linux-kselftest" in
the body of a message to majordomo at vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2018-04-14 17:28 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-14 19:08 [PATCH] selftests:vm: add include file peng.hao2
2018-04-14 17:28 ` rppt [this message]
2018-04-14 17:28   ` Mike Rapoport
2018-04-14 19:08 ` Peng Hao

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=20180414172826.GA3211@rapoport-lnx \
    --to=linux-kselftest@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).