From: Shuah Khan <shuahkh@osg.samsung.com>
To: David Herrmann <dh.herrmann@gmail.com>,
Pranith Kumar <bobby.prani@gmail.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Hugh Dickins <hughd@google.com>,
Phong Tran <tranmanphong@gmail.com>,
"open list:KERNEL SELFTEST F..." <linux-api@vger.kernel.org>,
open list <linux-kernel@vger.kernel.org>,
Shuah Khan <shuahkh@osg.samsung.com>
Subject: Re: [PATCH] selftests/memfd: Run test on all architectures
Date: Wed, 17 Sep 2014 09:36:17 -0600 [thread overview]
Message-ID: <5419AA71.4020506@osg.samsung.com> (raw)
In-Reply-To: <CANq1E4Q_KfDamkCMatGFYCQ0VPfc6tbd7sWT_z_qDeboiNzgNw@mail.gmail.com>
On 09/17/2014 06:28 AM, David Herrmann wrote:
> Hi
>
> On Tue, Sep 16, 2014 at 12:59 AM, Pranith Kumar <bobby.prani@gmail.com> wrote:
>> Remove the dependence on x86 to run the memfd test. Verfied on 32-bit powerpc.
>>
>> Signed-off-by: Pranith Kumar <bobby.prani@gmail.com>
>
> Now that most archs have __NR_memfd_create, this is:
>
> Reviewed-by: David Herrmann <dh.herrmann@gmail.com>
>
Hmm. I am seeing failures on x86_64 on top of Linus's tree
(without this patch)
make -C tools/testing/selftests/memfd/make: Entering directory
`/lkml/linus_git_3.14/tools/testing/selftests/memfd'
gcc -D_FILE_OFFSET_BITS=64
-I../../../../arch/x86/include/generated/uapi/
-I../../../../arch/x86/include/uapi/ -I../../../../include/uapi/
-I../../../../include/ memfd_test.c -o memfd_test
memfd_test.c: In function ‘sys_memfd_create’:
memfd_test.c:26:17: error: ‘__NR_memfd_create’ undeclared (first use in
this function)
return syscall(__NR_memfd_create, name, flags);
^
memfd_test.c:26:17: note: each undeclared identifier is reported only
once for each function it appears in
Could you please look into this?? It appears __NR_memfd_create isn't
defined on x86_64???
thanks,
-- Shuah
--
Shuah Khan
Sr. Linux Kernel Developer
Samsung Research America (Silicon Valley)
shuahkh@osg.samsung.com | (970) 217-8978
next prev parent reply other threads:[~2014-09-17 15:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-15 22:59 [PATCH] selftests/memfd: Run test on all architectures Pranith Kumar
2014-09-17 12:28 ` David Herrmann
2014-09-17 15:36 ` Shuah Khan [this message]
2014-09-17 15:39 ` Pranith Kumar
2014-09-17 15:39 ` David Herrmann
2014-09-17 15:41 ` Shuah Khan
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=5419AA71.4020506@osg.samsung.com \
--to=shuahkh@osg.samsung.com \
--cc=akpm@linux-foundation.org \
--cc=bobby.prani@gmail.com \
--cc=dh.herrmann@gmail.com \
--cc=hughd@google.com \
--cc=linux-api@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tranmanphong@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