From: kernel test robot <lkp@intel.com>
To: Casey Schaufler <casey@schaufler-ca.com>
Cc: oe-kbuild-all@lists.linux.dev, linux-kernel@vger.kernel.org,
Paul Moore <paul@paul-moore.com>,
Kees Cook <keescook@chromium.org>,
Serge Hallyn <serge@hallyn.com>,
John Johansen <john.johansen@canonical.com>
Subject: security/lsm_syscalls.c:31:1: sparse: sparse: Using plain integer as NULL pointer
Date: Tue, 26 Nov 2024 17:40:16 +0800 [thread overview]
Message-ID: <202411261712.iIifCLEW-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head: 7eef7e306d3c40a0c5b9ff6adc9b273cc894dbd5
commit: a04a1198088a1378d0389c250cc684f649bcc91e LSM: syscalls for current process attributes
date: 1 year ago
config: s390-randconfig-r132-20241126 (https://download.01.org/0day-ci/archive/20241126/202411261712.iIifCLEW-lkp@intel.com/config)
compiler: s390-linux-gcc (GCC) 14.2.0
reproduce: (https://download.01.org/0day-ci/archive/20241126/202411261712.iIifCLEW-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/202411261712.iIifCLEW-lkp@intel.com/
sparse warnings: (new ones prefixed by >>)
>> security/lsm_syscalls.c:31:1: sparse: sparse: Using plain integer as NULL pointer
>> security/lsm_syscalls.c:31:1: sparse: sparse: Using plain integer as NULL pointer
security/lsm_syscalls.c:53:1: sparse: sparse: Using plain integer as NULL pointer
security/lsm_syscalls.c:53:1: sparse: sparse: Using plain integer as NULL pointer
security/lsm_syscalls.c:53:1: sparse: sparse: Using plain integer as NULL pointer
security/lsm_syscalls.c:53:1: sparse: sparse: Using plain integer as NULL pointer
vim +31 security/lsm_syscalls.c
19
20 /**
21 * sys_lsm_set_self_attr - Set current task's security module attribute
22 * @attr: which attribute to set
23 * @ctx: the LSM contexts
24 * @size: size of @ctx
25 * @flags: reserved for future use
26 *
27 * Sets the calling task's LSM context. On success this function
28 * returns 0. If the attribute specified cannot be set a negative
29 * value indicating the reason for the error is returned.
30 */
> 31 SYSCALL_DEFINE4(lsm_set_self_attr, unsigned int, attr, struct lsm_ctx __user *,
32 ctx, size_t, size, u32, flags)
33 {
34 return security_setselfattr(attr, ctx, size, flags);
35 }
36
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next reply other threads:[~2024-11-26 9:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-26 9:40 kernel test robot [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-09-27 12:07 security/lsm_syscalls.c:31:1: sparse: sparse: Using plain integer as NULL pointer kernel test robot
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=202411261712.iIifCLEW-lkp@intel.com \
--to=lkp@intel.com \
--cc=casey@schaufler-ca.com \
--cc=john.johansen@canonical.com \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=paul@paul-moore.com \
--cc=serge@hallyn.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 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.