All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: oe-kbuild@lists.linux.dev
Cc: lkp@intel.com, Dan Carpenter <error27@gmail.com>
Subject: Re: [PATCH mptcp-next v2 12/14] mptcp: pm: move generic PM helpers to pm.c
Date: Sun, 2 Mar 2025 19:07:31 +0800	[thread overview]
Message-ID: <202503021814.nHwMzDOP-lkp@intel.com> (raw)

BCC: lkp@intel.com
CC: oe-kbuild-all@lists.linux.dev
In-Reply-To: <20250228-mptcp-pm-reorg-code-v2-12-fa8b2542b7a5@kernel.org>
References: <20250228-mptcp-pm-reorg-code-v2-12-fa8b2542b7a5@kernel.org>
TO: "Matthieu Baerts (NGI0)" <matttbe@kernel.org>
TO: mptcp@lists.linux.dev
CC: Geliang Tang <geliang@kernel.org>
CC: "Matthieu Baerts (NGI0)" <matttbe@kernel.org>

Hi Matthieu,

kernel test robot noticed the following build warnings:

[auto build test WARNING on 6b32949274eb9e32fe867ba9a8f8cb98587ecf36]

url:    https://github.com/intel-lab-lkp/linux/commits/Matthieu-Baerts-NGI0/mptcp-pm-remove-_nl-from-mptcp_pm_nl_addr_send_ack/20250228-213416
base:   6b32949274eb9e32fe867ba9a8f8cb98587ecf36
patch link:    https://lore.kernel.org/r/20250228-mptcp-pm-reorg-code-v2-12-fa8b2542b7a5%40kernel.org
patch subject: [PATCH mptcp-next v2 12/14] mptcp: pm: move generic PM helpers to pm.c
:::::: branch date: 2 days ago
:::::: commit date: 2 days ago
config: sparc-randconfig-r071-20250302 (https://download.01.org/0day-ci/archive/20250302/202503021814.nHwMzDOP-lkp@intel.com/config)
compiler: sparc-linux-gcc (GCC) 14.2.0

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>
| Reported-by: Dan Carpenter <error27@gmail.com>
| Closes: https://lore.kernel.org/r/202503021814.nHwMzDOP-lkp@intel.com/

smatch warnings:
net/mptcp/pm.c:156 mptcp_remove_anno_list_by_saddr() warn: returning freed memory 'entry' (line 155)

vim +/entry +156 net/mptcp/pm.c

2be048f2cf3912 Matthieu Baerts (NGI0  2025-02-28  148) 
2be048f2cf3912 Matthieu Baerts (NGI0  2025-02-28  149) bool mptcp_remove_anno_list_by_saddr(struct mptcp_sock *msk,
2be048f2cf3912 Matthieu Baerts (NGI0  2025-02-28  150) 				     const struct mptcp_addr_info *addr)
2be048f2cf3912 Matthieu Baerts (NGI0  2025-02-28  151) {
2be048f2cf3912 Matthieu Baerts (NGI0  2025-02-28  152) 	struct mptcp_pm_add_entry *entry;
2be048f2cf3912 Matthieu Baerts (NGI0  2025-02-28  153) 
2be048f2cf3912 Matthieu Baerts (NGI0  2025-02-28  154) 	entry = mptcp_pm_del_add_timer(msk, addr, false);
2be048f2cf3912 Matthieu Baerts (NGI0  2025-02-28 @155) 	kfree(entry);
2be048f2cf3912 Matthieu Baerts (NGI0  2025-02-28 @156) 	return entry;
2be048f2cf3912 Matthieu Baerts (NGI0  2025-02-28  157) }
2be048f2cf3912 Matthieu Baerts (NGI0  2025-02-28  158) 

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

             reply	other threads:[~2025-03-02 11:08 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-02 11:07 kernel test robot [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-02-28 13:31 [PATCH mptcp-next v2 00/14] mptcp: pm: code reorganisation Matthieu Baerts (NGI0)
2025-02-28 13:31 ` [PATCH mptcp-next v2 12/14] mptcp: pm: move generic PM helpers to pm.c Matthieu Baerts (NGI0)

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=202503021814.nHwMzDOP-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=error27@gmail.com \
    --cc=oe-kbuild@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.