From: Steffen Klassert <steffen.klassert@secunet.com>
To: Sabrina Dubroca <sd@queasysnail.net>
Cc: <netdev@vger.kernel.org>, <oe-kbuild-all@lists.linux.dev>,
kernel test robot <lkp@intel.com>,
Alexey Dobriyan <adobriyan@gmail.com>
Subject: Re: [PATCH ipsec 6/6] xfrm: check all hash buckets for leftover states during netns deletion
Date: Tue, 21 Oct 2025 10:50:03 +0200 [thread overview]
Message-ID: <aPdJO3k9C-bhqHSQ@secunet.com> (raw)
In-Reply-To: <aPVtmloGOCQi_7ue@krikkit>
Hi Sabrina,
On Mon, Oct 20, 2025 at 01:00:42AM +0200, Sabrina Dubroca wrote:
> Hi Steffen,
>
> 2025-10-17, 23:10:36 +0800, kernel test robot wrote:
> > Hi Sabrina,
> >
> > kernel test robot noticed the following build warnings:
> >
> > [auto build test WARNING on klassert-ipsec-next/master]
> > [also build test WARNING on klassert-ipsec/master net/main net-next/main linus/master v6.18-rc1 next-20251016]
> > [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/Sabrina-Dubroca/xfrm-drop-SA-reference-in-xfrm_state_update-if-dir-doesn-t-match/20251016-184507
> > base: https://git.kernel.org/pub/scm/linux/kernel/git/klassert/ipsec-next.git master
> > patch link: https://lore.kernel.org/r/2a743a05bbad7ebdc36c2c86a5fcbb9e99071c7b.1760610268.git.sd%40queasysnail.net
> > patch subject: [PATCH ipsec 6/6] xfrm: check all hash buckets for leftover states during netns deletion
> > config: x86_64-randconfig-r123-20251017 (https://download.01.org/0day-ci/archive/20251017/202510172159.iLR9bfcc-lkp@intel.com/config)
> > compiler: clang version 20.1.8 (https://github.com/llvm/llvm-project 87f0227cb60147a26a1eeb4fb06e3b505e9c7261)
> > reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20251017/202510172159.iLR9bfcc-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/202510172159.iLR9bfcc-lkp@intel.com/
> >
> > sparse warnings: (new ones prefixed by >>)
> [...]
> > 3308 void xfrm_state_fini(struct net *net)
> > 3309 {
> > 3310 unsigned int sz;
> > 3311 int i;
> > 3312
> > 3313 flush_work(&net->xfrm.state_hash_work);
> > 3314 xfrm_state_flush(net, 0, false);
> > 3315 flush_work(&xfrm_state_gc_work);
> > 3316
> > 3317 WARN_ON(!list_empty(&net->xfrm.state_all));
> > 3318
> > 3319 for (i = 0; i <= net->xfrm.state_hmask; i++) {
> > > 3320 WARN_ON(!hlist_empty(net->xfrm.state_byseq + i));
>
> So, before my patch there was a sparse waraning on the
>
> WARN_ON(!hlist_empty(net->xfrm.state_by*));
>
> lines, and now there's a sparse warning on the loop.
> (and plenty on other lines in net/xfrm/xfrm_state.c)
>
> This bot message gave me the push to finally take a look at all the
> sparse warnings in net/xfrm/xfrm_state.c, I have solutions for a big
> chunk of them (and a few in other files).
>
> If you want to drop this patch from the set, I'll re-send it later, on
> top of the sparse stuff. The rest of the series works without it. If
> you want to take it as is, it doesn't change the sparse situation in
> this file (a few warnings moved around) and I'll do the sparse
> cleanups on top of it.
I'll take the patchset as is and wait for your sparse fixes on top.
Thanks!
next prev parent reply other threads:[~2025-10-21 8:50 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-16 10:39 [PATCH ipsec 0/6] xfrm: misc fixes Sabrina Dubroca
2025-10-16 10:39 ` [PATCH ipsec 1/6] xfrm: drop SA reference in xfrm_state_update if dir doesn't match Sabrina Dubroca
2025-10-16 10:39 ` [PATCH ipsec 2/6] xfrm: also call xfrm_state_delete_tunnel at destroy time for states that were never added Sabrina Dubroca
2025-10-16 10:39 ` [PATCH ipsec 3/6] xfrm: make state as DEAD before final put when migrate fails Sabrina Dubroca
2025-10-16 10:39 ` [PATCH ipsec 4/6] xfrm: call xfrm_dev_state_delete when xfrm_state_migrate fails to add the state Sabrina Dubroca
2025-10-19 13:46 ` Leon Romanovsky
2025-10-16 10:39 ` [PATCH ipsec 5/6] xfrm: set err and extack on failure to create pcpu SA Sabrina Dubroca
2025-10-16 10:39 ` [PATCH ipsec 6/6] xfrm: check all hash buckets for leftover states during netns deletion Sabrina Dubroca
2025-10-17 15:10 ` kernel test robot
2025-10-19 23:00 ` Sabrina Dubroca
2025-10-21 8:50 ` Steffen Klassert [this message]
2025-10-22 5:42 ` [PATCH ipsec 0/6] xfrm: misc fixes Steffen Klassert
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=aPdJO3k9C-bhqHSQ@secunet.com \
--to=steffen.klassert@secunet.com \
--cc=adobriyan@gmail.com \
--cc=lkp@intel.com \
--cc=netdev@vger.kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=sd@queasysnail.net \
/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.