From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Mohamad Raizudeen <raizudeen.kerneldev@gmail.com>
Cc: kees@kernel.org, linux-input@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Input: serio - fix O(n^2) complexity in serio_unregister_driver()
Date: Wed, 8 Apr 2026 10:07:29 -0700 [thread overview]
Message-ID: <adaJ1MJ-Rg9qeeyr@google.com> (raw)
In-Reply-To: <20260408162849.4639-1-raizudeen.kerneldev@gmail.com>
Hi Mohamad,
On Wed, Apr 08, 2026 at 09:58:47PM +0530, Mohamad Raizudeen wrote:
> The current implementation restarts the scan from the beginning after
> each disconnection(goto start_over) because serio_disconnect_port() may
> delete the current list entry. This results in O(n^2) worst case
> behaviour.
The "big O" notation only makes sense when numbers are big. Here we are
dealing with 6 serio ports max (1 KBC, 4xMUX, 1 Synaptics pass-through)
unless you have a serial port expander and hooked up a few ports there.
But still, the number if very limited.
>
> Replace with a two-phase approach:
>
> 1.Collect only top-level ports bound to the driver(skip those whose parent is also bound to the same driver) into a
> temporary list.
We do not have such setups at the moment, but what about parent's
parent's parent?
>
> 2.Process each collected port once, moving it back to serio_list first to maintain invariants expected by serio_destroy_port().
>
> This eliminates the restart loop, reduces complexity from O(n^2) to O(n)
> and avoids use-after-free by never collecting child ports separately.
Could you explain more about the use-after-free scenario?
Thanks.
--
Dmitry
next prev parent reply other threads:[~2026-04-08 17:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-08 16:28 [PATCH] Input: serio - fix O(n^2) complexity in serio_unregister_driver() Mohamad Raizudeen
2026-04-08 17:07 ` Dmitry Torokhov [this message]
[not found] ` <CABkOv5cU8D8oo8scTOojvJ8hUeq4nxm6GGuA3GaBvebzdMBYpg@mail.gmail.com>
2026-04-08 17:56 ` Dmitry Torokhov
2026-04-08 18:19 ` Mohamad Raizudeen
2026-04-08 18:36 ` Dmitry Torokhov
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=adaJ1MJ-Rg9qeeyr@google.com \
--to=dmitry.torokhov@gmail.com \
--cc=kees@kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=raizudeen.kerneldev@gmail.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