From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Qing Ming <a0yami@mailbox.org>
Cc: Harald Welte <laforge@gnumonks.org>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
osmocom-net-gprs@lists.osmocom.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, Simon Horman <horms@kernel.org>
Subject: Re: [PATCH net] gtp: serialize PDP deletion with link teardown
Date: Fri, 7 Aug 2026 16:22:40 +0200 [thread overview]
Message-ID: <anXqMEQ8wajKIbTE@chamomile> (raw)
In-Reply-To: <20260806023226.5537-1-a0yami@mailbox.org>
Hi,
On Thu, Aug 06, 2026 at 10:32:26AM +0800, Qing Ming wrote:
> PDP contexts can be deleted through GTP_CMD_DELPDP or while the GTP
> network device is being unregistered. The latter is serialized by RTNL,
> but the generic-netlink delete path only holds RCU.
>
> Running both paths concurrently can therefore make both paths delete the
> same PDP context. On a KASAN-enabled kernel, a reproducer racing DELPDP
> against RTM_DELLINK triggered:
>
> Oops: general protection fault, probably for non-canonical address
> KASAN: maybe wild-memory-access in range
> [0xdead000000000120-0xdead000000000127]
> RIP: gtp_genl_del_pdp+0x1c1/0x420 [gtp]
> RBP: dead000000000122
>
> The second deletion dereferenced the poisoned hlist pprev pointer.
>
> Take RTNL around the DELPDP lookup and deletion so that PDP creation,
> generic-netlink deletion and link teardown use the same serialization
> domain.
Could please you instead add a mutex to a use it to protect PDP ctx
updates? genetlink mutex is not enough, and I'd prefer not to fix this
with the rtnl lock.
Please, use this new mutex from gtp_dellink() path to protect the
iteration over the hashtable.
gtp_genl_del_pdp() must use it too as well as gtp_pdp_add().
Thanks.
next prev parent reply other threads:[~2026-08-07 14:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-06 2:32 [PATCH net] gtp: serialize PDP deletion with link teardown Qing Ming
2026-08-07 13:13 ` Simon Horman
2026-08-07 14:11 ` Pablo Neira Ayuso
2026-08-07 14:22 ` Pablo Neira Ayuso [this message]
2026-08-08 12:43 ` [PATCH net v2] gtp: serialize PDP context updates Qing Ming
2026-08-11 0:39 ` Jakub Kicinski
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=anXqMEQ8wajKIbTE@chamomile \
--to=pablo@netfilter.org \
--cc=a0yami@mailbox.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=laforge@gnumonks.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=osmocom-net-gprs@lists.osmocom.org \
--cc=pabeni@redhat.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.