linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Pasha Tatashin <pasha.tatashin@soleen.com>
To: kernel test robot <lkp@intel.com>
Cc: oe-kbuild-all@lists.linux.dev,
	Andrew Morton <akpm@linux-foundation.org>,
	 Linux Memory Management List <linux-mm@kvack.org>
Subject: Re: [linux-next:master 9912/10599] kernel/liveupdate/luo_session.c:392:86: sparse: sparse: Using plain integer as NULL pointer
Date: Thu, 20 Nov 2025 17:06:48 -0500	[thread overview]
Message-ID: <CA+CK2bDOxj14O2kuvn+BNnXJ+R7rb0CK+ZS_hoiUBX5YhDfaHw@mail.gmail.com> (raw)
In-Reply-To: <202511210513.ywQeN1k6-lkp@intel.com>

On Thu, Nov 20, 2025 at 4:36 PM kernel test robot <lkp@intel.com> wrote:
>
> tree:   https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
> head:   88cbd8ac379cf5ce68b7efcfd4d1484a6871ee0b
> commit: f485f57c35af5b8c2a243dfc39ee171673484915 [9912/10599] liveupdate: luo_session: add sessions support
> config: x86_64-randconfig-121-20251120 (https://download.01.org/0day-ci/archive/20251121/202511210513.ywQeN1k6-lkp@intel.com/config)
> compiler: clang version 20.1.8 (https://github.com/llvm/llvm-project 87f0227cb60147a26a1eeb4fb06e3b505e9c7261)
> reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20251121/202511210513.ywQeN1k6-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/202511210513.ywQeN1k6-lkp@intel.com/
>
> sparse warnings: (new ones prefixed by >>)
> >> kernel/liveupdate/luo_session.c:392:86: sparse: sparse: Using plain integer as NULL pointer
>
> vim +392 kernel/liveupdate/luo_session.c
>
>    357
>    358  int luo_session_deserialize(void)
>    359  {
>    360          struct luo_session_header *sh = &luo_session_global.incoming;
>    361          int err;
>    362
>    363          if (luo_session_is_deserialized())
>    364                  return 0;
>    365
>    366          luo_session_global.deserialized = true;
>    367          if (!sh->active) {
>    368                  INIT_LIST_HEAD(&sh->list);
>    369                  init_rwsem(&sh->rwsem);
>    370                  return 0;
>    371          }
>    372
>    373          for (int i = 0; i < sh->header_ser->count; i++) {
>    374                  struct luo_session *session;
>    375
>    376                  session = luo_session_alloc(sh->ser[i].name);
>    377                  if (IS_ERR(session)) {
>    378                          pr_warn("Failed to allocate session [%s] during deserialization %pe\n",
>    379                                  sh->ser[i].name, session);
>    380                          return PTR_ERR(session);
>    381                  }
>    382
>    383                  err = luo_session_insert(sh, session);
>    384                  if (err) {
>    385                          luo_session_free(session);
>    386                          pr_warn("Failed to insert session [%s] %pe\n",
>    387                                  session->name, ERR_PTR(err));
>    388                          return err;
>    389                  }
>    390
>    391                  session->count = sh->ser[i].count;
>  > 392                  session->files = sh->ser[i].files ? phys_to_virt(sh->ser[i].files) : 0;

Should be: session->files = sh->ser[i].files ?
phys_to_virt(sh->ser[i].files) : NULL;

Will fix it in the next version.

Pasha


      reply	other threads:[~2025-11-20 22:07 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-20 21:35 kernel test robot
2025-11-20 22:06 ` Pasha Tatashin [this message]

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=CA+CK2bDOxj14O2kuvn+BNnXJ+R7rb0CK+ZS_hoiUBX5YhDfaHw@mail.gmail.com \
    --to=pasha.tatashin@soleen.com \
    --cc=akpm@linux-foundation.org \
    --cc=linux-mm@kvack.org \
    --cc=lkp@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox