All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Hannes Reinecke <hare@kernel.org>
Cc: oe-kbuild-all@lists.linux.dev
Subject: [hare-scsi-devel:configfs-ns.v6 1/26] drivers/nvme/target/bpf_ops.c:108:33: sparse: sparse: restricted __le16 degrades to integer
Date: Tue, 23 Jun 2026 10:15:24 +0800	[thread overview]
Message-ID: <202606231024.hfkoLKdf-lkp@intel.com> (raw)

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/hare/scsi-devel.git configfs-ns.v6
head:   22642e5d1c63efa6b484188105d45886f637d2be
commit: 95eeb6714114cd17d9c4c494a28cc11d86059eef [1/26] nvmet-bpf: eBPF struct_ops support for log pages
config: riscv-randconfig-r121-20260623 (https://download.01.org/0day-ci/archive/20260623/202606231024.hfkoLKdf-lkp@intel.com/config)
compiler: riscv64-linux-gcc (GCC) 8.5.0
sparse: v0.6.5-rc1
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260623/202606231024.hfkoLKdf-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/202606231024.hfkoLKdf-lkp@intel.com/

sparse warnings: (new ones prefixed by >>)
>> drivers/nvme/target/bpf_ops.c:108:33: sparse: sparse: restricted __le16 degrades to integer

vim +108 drivers/nvme/target/bpf_ops.c

    97	
    98	static int nvmet_bpf_reg(void *kdata, struct bpf_link *link)
    99	{
   100		struct nvmet_bpf_ops *ops = kdata;
   101		struct nvmet_port *p, *port = NULL;
   102		struct nvmet_subsys_link *s;
   103	
   104		pr_debug("%s: register %s port id %d\n",
   105			 __func__, ops->subsysnqn, ops->portid);
   106	
   107		list_for_each_entry(p, nvmet_ports, global_entry) {
 > 108			if (p->disc_addr.portid == ops->portid) {
   109				port = p;
   110				break;
   111			}
   112		}
   113		if (!port)
   114			return -EINVAL;
   115	
   116		down_write(&nvmet_config_sem);
   117		list_for_each_entry(s, &port->subsystems, entry) {
   118			if (!strncmp(s->subsys->subsysnqn, ops->subsysnqn,
   119				     NVMF_NQN_SIZE)) {
   120				s->bpf_ops = ops;
   121				ops->subsys_link = s;
   122				break;
   123			}
   124		}
   125		up_write(&nvmet_config_sem);
   126		if (ops->subsys_link) {
   127			pr_debug("%s: attached %pUb to %s\n",
   128				 __func__, &ops->uuid,
   129				 ops->subsys_link->subsys->serial);
   130			/* Raise a discovery log page changed AEN if log page is present */
   131			if (ops->log_page_supported(ops, NVME_LOG_DISC))
   132				nvmet_port_disc_changed(port, ops->subsys_link->subsys);
   133		}
   134		return ops->subsys_link ? 0 : -EINVAL;
   135	}
   136	

--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki

                 reply	other threads:[~2026-06-23  2:16 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=202606231024.hfkoLKdf-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=hare@kernel.org \
    --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.