From: Harald Welte <email@example.com>
To: Arnd Bergmann <firstname.lastname@example.org>
Cc: "Hyunwoo Kim" <email@example.com>,
"Greg Kroah-Hartman" <firstname.lastname@example.org>,
"Ilpo Järvinen" <email@example.com>,
"Dominik Brodowski" <firstname.lastname@example.org>,
"Paul Fulghum" <email@example.com>,
firstname.lastname@example.org, "Lubomir Rintel" <email@example.com>
Subject: Re: [PATCH] pcmcia: synclink_cs: Fix use-after-free in mgslpc_ioctl()
Date: Thu, 15 Sep 2022 16:05:17 +0200 [thread overview]
Message-ID: <YyMxHRXUTft4bG28@nataraja> (raw)
On Thu, Sep 15, 2022 at 09:35:51AM +0200, Arnd Bergmann wrote:
> There is a good chance that we can remove both now, along with the
> synclink_cs. The scr24x driver is from 2016, but of course the
> hardware is much older. The cm4040/cm4000 drivers are from 2005.
> My guess is that the hardware still exists in actively used systems,
> but none of them get upgraded to modern kernels any more.
It is probably true. But the same argument can be made about all of the
PCMCIA drivers. It's been a long time since any new mass-market hardware
with PCMCIA slots has been produced. Even if you count in the (non-express)
cardbus, the same argument holds true.
I personally haven't used any of those cm4000/cm4040 in ages. But what
particularly the last decade of my professional career has taught me:
There are typically always more users of legacy tech out there than you
would imagine. The question is whether those users are relevant enough
for today's kernel maintainers to care. This isn't meant to sound
bitter - I'm just stating facts. It can be a valid "developer resource
economic" decision to not care.
- Harald Welte <firstname.lastname@example.org> http://laforge.gnumonks.org/
"Privacy in residential applications is a desirable marketing option."
(ETSI EN 300 175-7 Ch. A6)
prev parent reply other threads:[~2022-09-15 14:33 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-13 5:20 [PATCH] pcmcia: synclink_cs: Fix use-after-free in mgslpc_ioctl() Hyunwoo Kim
2022-09-13 14:59 ` Arnd Bergmann
2022-09-13 15:14 ` Paul Fulghum
2022-09-13 15:43 ` Hyunwoo Kim
2022-09-15 2:08 ` Hyunwoo Kim
2022-09-15 7:35 ` Arnd Bergmann
2022-09-15 8:02 ` Dominik Brodowski
2022-09-15 9:00 ` Hyunwoo Kim
2022-09-16 5:03 ` Hyunwoo Kim
2022-09-15 14:05 ` Harald Welte [this message]
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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;
as well as URLs for NNTP newsgroup(s).