From: Sabrina Dubroca <sd@queasysnail.net>
To: Steffen Klassert <steffen.klassert@secunet.com>
Cc: netdev@vger.kernel.org, devel@linux-ipsec.org
Subject: Re: [PATCH ipsec-next] xfrm: Use regular error handling instead of BUG_ON() in the netlink API.
Date: Wed, 6 May 2026 19:20:22 +0200 [thread overview]
Message-ID: <aft4VvklN84f0xX8@krikkit> (raw)
In-Reply-To: <aftnl6d59WUM_Dfm@secunet.com>
2026-05-06, 18:08:55 +0200, Steffen Klassert wrote:
> The xfrm netlink API uses BUG_ON() on failures since it exists.
> However all these error are uncritical and can be handled
> with regular error handling. This fixes machine crashes
> in situations where an emergency break is not needed.
Nice clean up!
[...]
> @@ -1794,7 +1797,11 @@ static int xfrm_get_sadinfo(struct sk_buff *skb, struct nlmsghdr *nlh,
> return -ENOMEM;
>
> err = build_sadinfo(r_skb, net, sportid, seq, *flags);
> - BUG_ON(err < 0);
> + if (err < 0) {
> + kfree_skb(r_skb);
> + return err;
> + }
> +
nit: extra blank line
>
> return nlmsg_unicast(xfrm_net_nlsk(net, skb), r_skb, sportid);
> }
[...]
> @@ -4151,7 +4170,8 @@ static int xfrm_send_report(struct net *net, u8 proto,
> return -ENOMEM;
>
> err = build_report(skb, proto, sel, addr);
> - BUG_ON(err < 0);
> + if (err < 0)
> + return err;
This one is missing the kfree_skb(skb).
>
> return xfrm_nlmsg_multicast(net, skb, 0, XFRMNLGRP_REPORT);
> }
--
Sabrina
next prev parent reply other threads:[~2026-05-06 17:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-06 16:08 [PATCH ipsec-next] xfrm: Use regular error handling instead of BUG_ON() in the netlink API Steffen Klassert
2026-05-06 17:20 ` Sabrina Dubroca [this message]
2026-05-07 5:21 ` Antony Antony
2026-05-07 8:11 ` Sabrina Dubroca
2026-05-08 3:44 ` Antony Antony
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=aft4VvklN84f0xX8@krikkit \
--to=sd@queasysnail.net \
--cc=devel@linux-ipsec.org \
--cc=netdev@vger.kernel.org \
--cc=steffen.klassert@secunet.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