From: kernel test robot <lkp@intel.com>
To: Justin Iurman <justin.iurman@uliege.be>, netdev@vger.kernel.org
Cc: oe-kbuild-all@lists.linux.dev, davem@davemloft.net,
dsahern@kernel.org, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, linux-kernel@vger.kernel.org,
justin.iurman@uliege.be
Subject: Re: [PATCH net-next 2/3] ioam6: multicast event
Date: Wed, 21 Feb 2024 22:18:06 +0800 [thread overview]
Message-ID: <202402212253.mfysd5E1-lkp@intel.com> (raw)
In-Reply-To: <20240220194444.36127-3-justin.iurman@uliege.be>
Hi Justin,
kernel test robot noticed the following build warnings:
[auto build test WARNING on a6e0cb150c514efba4aaba4069927de43d80bb59]
url: https://github.com/intel-lab-lkp/linux/commits/Justin-Iurman/uapi-ioam6-API-for-netlink-multicast-events/20240221-034623
base: a6e0cb150c514efba4aaba4069927de43d80bb59
patch link: https://lore.kernel.org/r/20240220194444.36127-3-justin.iurman%40uliege.be
patch subject: [PATCH net-next 2/3] ioam6: multicast event
config: parisc-defconfig (https://download.01.org/0day-ci/archive/20240221/202402212253.mfysd5E1-lkp@intel.com/config)
compiler: hppa-linux-gcc (GCC) 13.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240221/202402212253.mfysd5E1-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/202402212253.mfysd5E1-lkp@intel.com/
All warnings (new ones prefixed by >>):
net/ipv6/ioam6.c: In function 'ioam6_event':
>> net/ipv6/ioam6.c:657:9: warning: enumeration value 'IOAM6_EVENT_UNSPEC' not handled in switch [-Wswitch]
657 | switch (type) {
| ^~~~~~
vim +/IOAM6_EVENT_UNSPEC +657 net/ipv6/ioam6.c
638
639 void ioam6_event(enum ioam6_event_type type, struct net *net, gfp_t gfp,
640 void *opt, unsigned int opt_len)
641 {
642 struct nlmsghdr *nlh;
643 struct sk_buff *skb;
644
645 if (!genl_has_listeners(&ioam6_genl_family, net,
646 IOAM6_GENL_EV_GRP_OFFSET))
647 return;
648
649 skb = nlmsg_new(NLMSG_DEFAULT_SIZE, gfp);
650 if (!skb)
651 return;
652
653 nlh = genlmsg_put(skb, 0, 0, &ioam6_genl_family, 0, type);
654 if (!nlh)
655 goto nla_put_failure;
656
> 657 switch (type) {
658 case IOAM6_EVENT_TRACE:
659 if (ioam6_event_put_trace(skb, (struct ioam6_trace_hdr *)opt,
660 opt_len))
661 goto nla_put_failure;
662 break;
663 }
664
665 genlmsg_end(skb, nlh);
666 genlmsg_multicast_netns(&ioam6_genl_family, net, skb, 0,
667 IOAM6_GENL_EV_GRP_OFFSET, gfp);
668 return;
669
670 nla_put_failure:
671 nlmsg_free(skb);
672 }
673
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2024-02-21 14:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-20 19:44 [PATCH net-next 0/3] multicast event support for ioam6 Justin Iurman
2024-02-20 19:44 ` [PATCH net-next 1/3] uapi: ioam6: API for netlink multicast events Justin Iurman
2024-02-20 19:44 ` [PATCH net-next 2/3] ioam6: multicast event Justin Iurman
2024-02-21 14:18 ` kernel test robot [this message]
2024-02-20 19:44 ` [PATCH net-next 3/3] net: exthdrs: ioam6: send trace event Justin Iurman
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=202402212253.mfysd5E1-lkp@intel.com \
--to=lkp@intel.com \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=justin.iurman@uliege.be \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=pabeni@redhat.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;
as well as URLs for NNTP newsgroup(s).