From: kernel test robot <lkp@intel.com>
To: Ranganath V N <vnranganath.20@gmail.com>,
davem@davemloft.net, edumazet@google.com, horms@kernel.org,
jhs@mojatatu.com, jiri@resnulli.us, kuba@kernel.org,
pabeni@redhat.com, xiyou.wangcong@gmail.com
Cc: oe-kbuild-all@lists.linux.dev, vnranganath.20@gmail.com,
david.hunter.linux@gmail.com, khalid@kernel.org,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
skhan@linuxfoundation.org,
syzbot+0c85cae3350b7d486aee@syzkaller.appspotmail.com
Subject: Re: [PATCH v3 2/2] net: sched: act_ife: initialize struct tc_ife to fix KMSAN kernel-infoleak
Date: Sat, 8 Nov 2025 09:26:49 +0800 [thread overview]
Message-ID: <202511080909.0OWvBSbY-lkp@intel.com> (raw)
In-Reply-To: <20251106195635.2438-3-vnranganath.20@gmail.com>
Hi Ranganath,
kernel test robot noticed the following build errors:
[auto build test ERROR on net-next/main]
[also build test ERROR on net/main linus/master v6.18-rc4 next-20251107]
[cannot apply to horms-ipvs/master]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch#_base_tree_information]
url: https://github.com/intel-lab-lkp/linux/commits/Ranganath-V-N/net-sched-act_connmark-initialize-struct-tc_ife-to-fix-kernel-leak/20251107-035911
base: net-next/main
patch link: https://lore.kernel.org/r/20251106195635.2438-3-vnranganath.20%40gmail.com
patch subject: [PATCH v3 2/2] net: sched: act_ife: initialize struct tc_ife to fix KMSAN kernel-infoleak
config: i386-buildonly-randconfig-003-20251108 (https://download.01.org/0day-ci/archive/20251108/202511080909.0OWvBSbY-lkp@intel.com/config)
compiler: gcc-14 (Debian 14.2.0-19) 14.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20251108/202511080909.0OWvBSbY-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/202511080909.0OWvBSbY-lkp@intel.com/
All errors (new ones prefixed by >>):
net/sched/act_ife.c: In function 'tcf_ife_dump':
>> net/sched/act_ife.c:652:9: error: 'index' undeclared (first use in this function)
652 | index = ife->tcf_index;
| ^~~~~
net/sched/act_ife.c:652:9: note: each undeclared identifier is reported only once for each function it appears in
>> net/sched/act_ife.c:653:9: error: 'refcnt' undeclared (first use in this function)
653 | refcnt = refcount_read(&ife->tcf_refcnt) - ref;
| ^~~~~~
>> net/sched/act_ife.c:654:9: error: 'bindcnt' undeclared (first use in this function); did you mean 'bind'?
654 | bindcnt = atomic_read(&ife->tcf_bindcnt) - bind;
| ^~~~~~~
| bind
vim +/index +652 net/sched/act_ife.c
640
641 static int tcf_ife_dump(struct sk_buff *skb, struct tc_action *a, int bind,
642 int ref)
643 {
644 unsigned char *b = skb_tail_pointer(skb);
645 struct tcf_ife_info *ife = to_ife(a);
646 struct tcf_ife_params *p;
647 struct tc_ife opt;
648 struct tcf_t t;
649
650 memset(&opt, 0, sizeof(opt));
651
> 652 index = ife->tcf_index;
> 653 refcnt = refcount_read(&ife->tcf_refcnt) - ref;
> 654 bindcnt = atomic_read(&ife->tcf_bindcnt) - bind;
655
656 spin_lock_bh(&ife->tcf_lock);
657 opt.action = ife->tcf_action;
658 p = rcu_dereference_protected(ife->params,
659 lockdep_is_held(&ife->tcf_lock));
660 opt.flags = p->flags;
661
662 if (nla_put(skb, TCA_IFE_PARMS, sizeof(opt), &opt))
663 goto nla_put_failure;
664
665 tcf_tm_dump(&t, &ife->tcf_tm);
666 if (nla_put_64bit(skb, TCA_IFE_TM, sizeof(t), &t, TCA_IFE_PAD))
667 goto nla_put_failure;
668
669 if (!is_zero_ether_addr(p->eth_dst)) {
670 if (nla_put(skb, TCA_IFE_DMAC, ETH_ALEN, p->eth_dst))
671 goto nla_put_failure;
672 }
673
674 if (!is_zero_ether_addr(p->eth_src)) {
675 if (nla_put(skb, TCA_IFE_SMAC, ETH_ALEN, p->eth_src))
676 goto nla_put_failure;
677 }
678
679 if (nla_put(skb, TCA_IFE_TYPE, 2, &p->eth_type))
680 goto nla_put_failure;
681
682 if (dump_metalist(skb, ife)) {
683 /*ignore failure to dump metalist */
684 pr_info("Failed to dump metalist\n");
685 }
686
687 spin_unlock_bh(&ife->tcf_lock);
688 return skb->len;
689
690 nla_put_failure:
691 spin_unlock_bh(&ife->tcf_lock);
692 nlmsg_trim(skb, b);
693 return -1;
694 }
695
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
prev parent reply other threads:[~2025-11-08 1:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-06 19:56 [PATCH v3 0/2] net: sched: initialize struct tc_ife to fix kernel-infoleak Ranganath V N
2025-11-06 19:56 ` [PATCH v3 1/2] net: sched: act_connmark: initialize struct tc_ife to fix kernel leak Ranganath V N
2025-11-07 10:38 ` Simon Horman
2025-11-08 1:26 ` kernel test robot
2025-11-06 19:56 ` [PATCH v3 2/2] net: sched: act_ife: initialize struct tc_ife to fix KMSAN kernel-infoleak Ranganath V N
2025-11-08 1:15 ` kernel test robot
2025-11-08 1:26 ` kernel test robot [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=202511080909.0OWvBSbY-lkp@intel.com \
--to=lkp@intel.com \
--cc=davem@davemloft.net \
--cc=david.hunter.linux@gmail.com \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=jhs@mojatatu.com \
--cc=jiri@resnulli.us \
--cc=khalid@kernel.org \
--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 \
--cc=skhan@linuxfoundation.org \
--cc=syzbot+0c85cae3350b7d486aee@syzkaller.appspotmail.com \
--cc=vnranganath.20@gmail.com \
--cc=xiyou.wangcong@gmail.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.