From: Jakub Kicinski <kuba@kernel.org>
To: Pablo Neira Ayuso <pablo@netfilter.org>
Cc: kovalev@altlinux.org, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org, edumazet@google.com,
laforge@gnumonks.org, davem@davemloft.net, pabeni@redhat.com,
nickel@altlinux.org, oficerovas@altlinux.org,
dutyrok@altlinux.org, stable@vger.kernel.org
Subject: Re: [PATCH ver.2] gtp: fix use-after-free and null-ptr-deref in gtp_genl_dump_pdp()
Date: Tue, 20 Feb 2024 16:04:34 -0800 [thread overview]
Message-ID: <20240220160434.29bcaf43@kernel.org> (raw)
In-Reply-To: <Zc5NP/5Eyh8bsbH6@calendula>
On Thu, 15 Feb 2024 18:43:46 +0100 Pablo Neira Ayuso wrote:
> > Yes, I can prepare several patches with the same commit message. Is it
> > better to send them individually (like this patch) or in a series with a
> > brief preliminary description (PATCH 0/x)?
>
> I'd suggest one patch for each subsystem as per MAINTAINER file, that
> should also make it easier for Linux kernel -stable maintainers to
> pick up this fix series.
Pablo is anything expected to change from gtp patch itself?
Someone (DaveM?) marked this as Changes Requested but I don't see
a clear ask, other that to follow up with patches to other families.
next prev parent reply other threads:[~2024-02-21 0:04 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-14 16:27 [PATCH ver.2] gtp: fix use-after-free and null-ptr-deref in gtp_genl_dump_pdp() kovalev
2024-02-14 16:49 ` Pablo Neira Ayuso
2024-02-14 17:06 ` kovalev
2024-02-14 17:13 ` Pablo Neira Ayuso
2024-02-14 17:30 ` kovalev
2024-02-15 17:43 ` Pablo Neira Ayuso
2024-02-21 0:04 ` Jakub Kicinski [this message]
2024-02-21 10:47 ` Pablo Neira Ayuso
2024-02-21 11:03 ` Pablo Neira Ayuso
2024-02-21 22:30 ` patchwork-bot+netdevbpf
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=20240220160434.29bcaf43@kernel.org \
--to=kuba@kernel.org \
--cc=davem@davemloft.net \
--cc=dutyrok@altlinux.org \
--cc=edumazet@google.com \
--cc=kovalev@altlinux.org \
--cc=laforge@gnumonks.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=nickel@altlinux.org \
--cc=oficerovas@altlinux.org \
--cc=pabeni@redhat.com \
--cc=pablo@netfilter.org \
--cc=stable@vger.kernel.org \
/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.