From: kernel test robot <lkp@intel.com>
To: jeffxu@chromium.org, dave.hansen@intel.com, luto@kernel.org,
jorgelo@chromium.org, keescook@chromium.org, groeck@chromium.org,
jannh@google.com, sroettger@google.com
Cc: oe-kbuild-all@lists.linux.dev, akpm@linux-foundation.org,
jeffxu@google.com, linux-kernel@vger.kernel.org,
linux-kselftest@vger.kernel.org, linux-mm@kvack.org,
linux-hardening@vger.kernel.org
Subject: Re: [PATCH v1 4/6] PKEY:selftest pkey_enforce_api for mprotect
Date: Tue, 30 May 2023 17:32:31 +0800 [thread overview]
Message-ID: <202305301758.ddYd6um5-lkp@intel.com> (raw)
In-Reply-To: <20230519011915.846407-5-jeffxu@chromium.org>
Hi,
kernel test robot noticed the following build warnings:
[auto build test WARNING on ba0ad6ed89fd5dada3b7b65ef2b08e95d449d4ab]
url: https://github.com/intel-lab-lkp/linux/commits/jeffxu-chromium-org/PKEY-Introduce-PKEY_ENFORCE_API-flag/20230519-093355
base: ba0ad6ed89fd5dada3b7b65ef2b08e95d449d4ab
patch link: https://lore.kernel.org/r/20230519011915.846407-5-jeffxu%40chromium.org
patch subject: [PATCH v1 4/6] PKEY:selftest pkey_enforce_api for mprotect
compiler: gcc-12 (Debian 12.2.0-14) 12.2.0
reproduce:
# https://github.com/intel-lab-lkp/linux/commit/ee635a3d72bf9f400d3542d27d1df9d2813640dc
git remote add linux-review https://github.com/intel-lab-lkp/linux
git fetch --no-tags linux-review jeffxu-chromium-org/PKEY-Introduce-PKEY_ENFORCE_API-flag/20230519-093355
git checkout ee635a3d72bf9f400d3542d27d1df9d2813640dc
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>
| Closes: https://lore.kernel.org/oe-kbuild-all/202305301758.ddYd6um5-lkp@intel.com/
All warnings (new ones prefixed by >>):
In file included from pkey_enforce_api.c:72:
pkey-x86.h: In function 'expect_fault_on_read_execonly_key':
>> pkey-x86.h:165:13: warning: variable 'ptr_contents' set but not used [-Wunused-but-set-variable]
165 | int ptr_contents;
| ^~~~~~~~~~~~
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2023-05-30 9:33 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-19 1:19 [PATCH v1 0/6] Memory Mapping (VMA) protection using PKU - set 1 jeffxu
2023-05-19 1:19 ` [PATCH v1 1/6] PKEY: Introduce PKEY_ENFORCE_API flag jeffxu
2023-05-19 1:19 ` [PATCH v1 2/6] PKEY: Add arch_check_pkey_enforce_api() jeffxu
2023-05-19 1:19 ` [PATCH v1 3/6] PKEY: Apply PKEY_ENFORCE_API to mprotect jeffxu
2023-05-19 1:19 ` [PATCH v1 4/6] PKEY:selftest pkey_enforce_api for mprotect jeffxu
2023-05-30 9:32 ` kernel test robot [this message]
2023-05-19 1:19 ` [PATCH v1 5/6] PKEY: Apply PKEY_ENFORCE_API to munmap jeffxu
2023-05-19 1:19 ` [PATCH v1 6/6] PKEY:selftest pkey_enforce_api for munmap jeffxu
2023-05-19 1:21 ` [PATCH v1 0/6] Memory Mapping (VMA) protection using PKU - set 1 Jeff Xu
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=202305301758.ddYd6um5-lkp@intel.com \
--to=lkp@intel.com \
--cc=akpm@linux-foundation.org \
--cc=dave.hansen@intel.com \
--cc=groeck@chromium.org \
--cc=jannh@google.com \
--cc=jeffxu@chromium.org \
--cc=jeffxu@google.com \
--cc=jorgelo@chromium.org \
--cc=keescook@chromium.org \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=luto@kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=sroettger@google.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