From: kernel test robot <lkp@intel.com>
To: Chao Peng <chao.p.peng@linux.intel.com>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org,
Isaku Yamahata <isaku.yamahata@intel.com>
Subject: [intel-tdx:kvm-upstream-workaround 135/314] memfd_test.c:1025:34: error: 'F_SEAL_AUTO_ALLOCATE' undeclared
Date: Mon, 19 Sep 2022 21:24:51 +0800 [thread overview]
Message-ID: <202209192142.TsjtmilL-lkp@intel.com> (raw)
tree: https://github.com/intel/tdx.git kvm-upstream-workaround
head: 552dd80c48f67ca01bcdd10667e0c11efd375177
commit: 6fc2c0d90c42ad750192a03cdf03d78befd0d8ce [135/314] selftests/memfd: Add tests for F_SEAL_AUTO_ALLOCATE
compiler: gcc-11 (Debian 11.3.0-5) 11.3.0
reproduce:
# https://github.com/intel/tdx/commit/6fc2c0d90c42ad750192a03cdf03d78befd0d8ce
git remote add intel-tdx https://github.com/intel/tdx.git
git fetch --no-tags intel-tdx kvm-upstream-workaround
git checkout 6fc2c0d90c42ad750192a03cdf03d78befd0d8ce
make O=/tmp/kselftest headers
make O=/tmp/kselftest -C tools/testing/selftests
If you fix the issue, kindly add following tag where applicable
Reported-by: kernel test robot <lkp@intel.com>
All errors (new ones prefixed by >>):
memfd_test.c: In function 'test_seal_auto_allocate':
>> memfd_test.c:1025:34: error: 'F_SEAL_AUTO_ALLOCATE' undeclared (first use in this function)
1025 | mfd_assert_add_seals(fd, F_SEAL_AUTO_ALLOCATE);
| ^~~~~~~~~~~~~~~~~~~~
memfd_test.c:1025:34: note: each undeclared identifier is reported only once for each function it appears in
--
0-DAY CI Kernel Test Service
https://01.org/lkp
reply other threads:[~2022-09-19 13:25 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=202209192142.TsjtmilL-lkp@intel.com \
--to=lkp@intel.com \
--cc=chao.p.peng@linux.intel.com \
--cc=isaku.yamahata@intel.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.