From: Jakub Kicinski <kuba@kernel.org>
To: Hugh Blemings <hugh@blemings.org>
Cc: hugh@blemings.id.au, Paolo Abeni <pabeni@redhat.com>,
Mashiro Chen <mashiro.chen@mailbox.org>,
netdev@vger.kernel.org, linux-hams@vger.kernel.org,
horms@kernel.org, davem@davemloft.net, edumazet@google.com,
Greg KH <gregkh@linuxfoundation.org>
Subject: Re: [PATCH v4 net] net: ax25: fix integer overflow in ax25_rx_fragment()
Date: Tue, 21 Apr 2026 07:16:46 -0700 [thread overview]
Message-ID: <20260421071646.472c39c3@kernel.org> (raw)
In-Reply-To: <e2a47378-9008-45a2-92e3-d1f374b5e766@blemings.org>
On Tue, 21 Apr 2026 18:45:39 +1000 Hugh Blemings wrote:
> We'd hoped to have a period of a few months to do an orderly exit from
> the tree to minimise the impact on the (admittedly small, but non-zero)
> users that build trees/make use of the in kernel support.
Sorry about the CC, I trusted get_maintainer.pl too much, clearly :(
If you only need a few months I'd strongly prefer to delete now.
We are getting multiple "fixes" for this code a day, and if we don't
delete it now we have to process these fixes for 2.5 more months,
until the next merge window. IOW even if we delete now you have
2.5 months until 7.1 is actually released, and of course LTS is
available, too.
prev parent reply other threads:[~2026-04-21 14:16 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-09 2:50 [PATCH v2 net] net: ax25: fix integer overflow in ax25_rx_fragment() Mashiro Chen
2026-04-12 20:17 ` Jakub Kicinski
2026-04-12 21:05 ` David Laight
2026-04-13 11:21 ` Mashiro Chen
2026-04-13 11:14 ` [PATCH v3 " Mashiro Chen
2026-04-13 20:49 ` [PATCH v4 " Mashiro Chen
2026-04-21 7:29 ` Paolo Abeni
2026-04-21 8:45 ` Hugh Blemings
2026-04-21 12:25 ` Andrew Lunn
2026-04-21 14:16 ` Jakub Kicinski [this message]
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=20260421071646.472c39c3@kernel.org \
--to=kuba@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=gregkh@linuxfoundation.org \
--cc=horms@kernel.org \
--cc=hugh@blemings.id.au \
--cc=hugh@blemings.org \
--cc=linux-hams@vger.kernel.org \
--cc=mashiro.chen@mailbox.org \
--cc=netdev@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox