From: kernel test robot <lkp@intel.com>
To: Aruna Ramakrishna <aruna.ramakrishna@oracle.com>
Cc: oe-kbuild-all@lists.linux.dev
Subject: Re: [RFC PATCH v2 1/1] x86/pkeys: update PKRU to enable pkey 0 before XSAVE
Date: Wed, 27 Mar 2024 07:47:18 +0800 [thread overview]
Message-ID: <202403270713.CDQA9ROT-lkp@intel.com> (raw)
In-Reply-To: <20240321215622.3396410-2-aruna.ramakrishna@oracle.com>
Hi Aruna,
[This is a private test report for your RFC patch.]
kernel test robot noticed the following build warnings:
[auto build test WARNING on tip/x86/core]
[also build test WARNING on tip/master tip/auto-latest linus/master v6.9-rc1 next-20240326]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch#_base_tree_information]
url: https://github.com/intel-lab-lkp/linux/commits/Aruna-Ramakrishna/x86-pkeys-update-PKRU-to-enable-pkey-0-before-XSAVE/20240322-055950
base: tip/x86/core
patch link: https://lore.kernel.org/r/20240321215622.3396410-2-aruna.ramakrishna%40oracle.com
patch subject: [RFC PATCH v2 1/1] x86/pkeys: update PKRU to enable pkey 0 before XSAVE
config: x86_64-randconfig-123-20240326 (https://download.01.org/0day-ci/archive/20240327/202403270713.CDQA9ROT-lkp@intel.com/config)
compiler: gcc-9 (Debian 9.3.0-22) 9.3.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240327/202403270713.CDQA9ROT-lkp@intel.com/reproduce)
If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202403270713.CDQA9ROT-lkp@intel.com/
sparse warnings: (new ones prefixed by >>)
arch/x86/kernel/fpu/signal.c: note: in included file (through arch/x86/include/asm/uaccess.h, include/linux/uaccess.h, include/linux/sched/task.h, ...):
arch/x86/include/asm/uaccess_64.h:85:24: sparse: sparse: cast removes address space '__user' of expression
>> arch/x86/kernel/fpu/signal.c:80:34: sparse: sparse: incorrect type in argument 1 (different address spaces) @@ expected struct xregs_state *xsave @@ got struct xregs_state [noderef] __user *buf @@
arch/x86/kernel/fpu/signal.c:80:34: sparse: expected struct xregs_state *xsave
arch/x86/kernel/fpu/signal.c:80:34: sparse: got struct xregs_state [noderef] __user *buf
arch/x86/include/asm/uaccess_64.h:85:24: sparse: sparse: cast removes address space '__user' of expression
arch/x86/include/asm/uaccess_64.h:85:24: sparse: sparse: cast removes address space '__user' of expression
vim +80 arch/x86/kernel/fpu/signal.c
65
66 /*
67 * Update the value of PKRU register that was already pushed
68 * onto the signal frame.
69 */
70 static inline int
71 __update_pkru_in_sigframe(struct xregs_state __user *buf, u32 pkru)
72 {
73 int err = -EFAULT;
74 struct _fpx_sw_bytes fx_sw;
75 struct pkru_state *pk = NULL;
76
77 if (unlikely(!check_xstate_in_sigframe((void __user *) buf, &fx_sw)))
78 goto out;
79
> 80 pk = get_xsave_addr_user(buf, XFEATURE_PKRU);
81 if (!pk || !user_write_access_begin(buf, sizeof(struct xregs_state)))
82 goto out;
83 unsafe_put_user(pkru, (unsigned int __user *) pk, uaccess_end);
84
85 err = 0;
86 uaccess_end:
87 user_access_end();
88 out:
89 return err;
90 }
91
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2024-03-26 23:48 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-21 21:56 [RFC PATCH v2 0/1] x86/pkeys: update PKRU to enable pkey 0 Aruna Ramakrishna
2024-03-21 21:56 ` [RFC PATCH v2 1/1] x86/pkeys: update PKRU to enable pkey 0 before XSAVE Aruna Ramakrishna
2024-03-22 9:46 ` Ingo Molnar
2024-03-22 18:30 ` Aruna Ramakrishna
2024-04-25 22:03 ` jeffxu
2024-03-22 15:40 ` Dave Hansen
2024-03-22 18:28 ` Aruna Ramakrishna
2024-03-26 23:47 ` kernel test robot [this message]
2024-04-25 21:05 ` jeffxu
2024-04-25 22:49 ` Aruna Ramakrishna
2024-04-26 0:12 ` Jeff Xu
2024-04-26 16:13 ` Jeff Xu
2024-04-26 16:33 ` Edgecombe, Rick P
2024-04-26 17:13 ` Jeff Xu
2024-04-25 21:58 ` jeffxu
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=202403270713.CDQA9ROT-lkp@intel.com \
--to=lkp@intel.com \
--cc=aruna.ramakrishna@oracle.com \
--cc=oe-kbuild-all@lists.linux.dev \
/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.