From: kernel test robot <lkp@intel.com>
To: Dharanitharan R <dharanitharan725@gmail.com>,
syzbot+5dd615f890ddada54057@syzkaller.appspotmail.com
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
Dharanitharan R <dharanitharan725@gmail.com>
Subject: Re: [PATCH] net: atm: lec: add pre_send validation to avoid uninitialized
Date: Mon, 8 Dec 2025 11:04:22 +0800 [thread overview]
Message-ID: <202512081042.Zx4NasDJ-lkp@intel.com> (raw)
In-Reply-To: <20251207041453.8302-1-dharanitharan725@gmail.com>
Hi Dharanitharan,
kernel test robot noticed the following build warnings:
[auto build test WARNING on net/main]
[also build test WARNING on net-next/main linus/master horms-ipvs/master v6.18 next-20251205]
[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/Dharanitharan-R/net-atm-lec-add-pre_send-validation-to-avoid-uninitialized/20251207-121647
base: net/main
patch link: https://lore.kernel.org/r/20251207041453.8302-1-dharanitharan725%40gmail.com
patch subject: [PATCH] net: atm: lec: add pre_send validation to avoid uninitialized
config: arm64-randconfig-002-20251208 (https://download.01.org/0day-ci/archive/20251208/202512081042.Zx4NasDJ-lkp@intel.com/config)
compiler: clang version 18.1.8 (https://github.com/llvm/llvm-project 3b5b5c1ec4a3095ab096dd780e84d7ab81f3d7ff)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20251208/202512081042.Zx4NasDJ-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/202512081042.Zx4NasDJ-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> net/atm/lec.c:506:2: warning: misleading indentation; statement is not part of the previous 'if' [-Wmisleading-indentation]
506 | mesg = (struct atmlec_msg *)skb->data;
| ^
net/atm/lec.c:503:4: note: previous statement is here
503 | if (!pskb_may_pull(skb, msg_size))
| ^
1 warning generated.
vim +/if +506 net/atm/lec.c
491
492 static int lec_atm_pre_send(struct atm_vcc *vcc, struct sk_buff *skb)
493 {
494 struct atmlec_msg *mesg;
495 u32 sizeoftlvs;
496 unsigned int msg_size = sizeof(struct atmlec_msg);
497
498 /* Must contain the base message */
499 if (skb->len < msg_size)
500 return -EINVAL;
501
502 /* Must have at least msg_size bytes in linear data */
503 if (!pskb_may_pull(skb, msg_size))
504 return -EINVAL;
505
> 506 mesg = (struct atmlec_msg *)skb->data;
507 sizeoftlvs = mesg->sizeoftlvs;
508
509 /* Validate TLVs if present */
510 if (sizeoftlvs && !pskb_may_pull(skb, msg_size + sizeoftlvs))
511 return -EINVAL;
512
513 return 0;
514 }
515
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
parent reply other threads:[~2025-12-08 3:04 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20251207041453.8302-1-dharanitharan725@gmail.com>]
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=202512081042.Zx4NasDJ-lkp@intel.com \
--to=lkp@intel.com \
--cc=dharanitharan725@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=netdev@vger.kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=syzbot+5dd615f890ddada54057@syzkaller.appspotmail.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