From: kernel test robot <lkp@intel.com>
To: Eric Dumazet <edumazet@google.com>
Cc: oe-kbuild-all@lists.linux.dev,
Linux Memory Management List <linux-mm@kvack.org>,
Paolo Abeni <pabeni@redhat.com>,
Guillaume Nault <gnault@redhat.com>,
Kuniyuki Iwashima <kuniyu@amazon.com>,
Willem de Bruijn <willemb@google.com>
Subject: [linux-next:master 1200/1892] net/core/sock_diag.c:210:17: sparse: sparse: Using plain integer as NULL pointer
Date: Fri, 26 Jan 2024 00:06:16 +0800 [thread overview]
Message-ID: <202401252355.PhD9im8z-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head: 01af33cc9894b4489fb68fa35c40e9fe85df63dc
commit: 1d55a6974756cf3979efd2cc68bcece611a44053 [1200/1892] sock_diag: allow concurrent operations
config: hexagon-randconfig-r121-20240125 (https://download.01.org/0day-ci/archive/20240125/202401252355.PhD9im8z-lkp@intel.com/config)
compiler: clang version 17.0.6 (https://github.com/llvm/llvm-project 6009708b4367171ccdbf4b5905cb6a803753fe18)
reproduce: (https://download.01.org/0day-ci/archive/20240125/202401252355.PhD9im8z-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/202401252355.PhD9im8z-lkp@intel.com/
sparse warnings: (new ones prefixed by >>)
>> net/core/sock_diag.c:210:17: sparse: sparse: Using plain integer as NULL pointer
vim +210 net/core/sock_diag.c
202
203 int sock_diag_register(const struct sock_diag_handler *hndl)
204 {
205 int family = hndl->family;
206
207 if (family >= AF_MAX)
208 return -EINVAL;
209
> 210 return !cmpxchg((const struct sock_diag_handler **)
211 &sock_diag_handlers[family],
212 NULL, hndl) ? 0 : -EBUSY;
213 }
214 EXPORT_SYMBOL_GPL(sock_diag_register);
215
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2024-01-25 16:07 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=202401252355.PhD9im8z-lkp@intel.com \
--to=lkp@intel.com \
--cc=edumazet@google.com \
--cc=gnault@redhat.com \
--cc=kuniyu@amazon.com \
--cc=linux-mm@kvack.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=pabeni@redhat.com \
--cc=willemb@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