From: krzk@kernel.org
To: Guangshuo Li <lgs201920130244@gmail.com>
Cc: stable@vger.kernel.org,
"Benedikt Niedermayr" <benedikt.niedermayr@siemens.com>,
linux-kernel@vger.kernel.org,
"Tobias Schaffner" <tobias.schaffner@siemens.com>,
platform-driver-x86@vger.kernel.org,
"Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>,
"Hans de Goede" <hansg@kernel.org>,
"Bao Cheng Su" <baocheng.su@siemens.com>,
"Henning Schild" <henning.schild@siemens.com>
Subject: Re: [PATCH] platform/x86: simatic-ipc: fix platform device leak on registration failure
Date: Mon, 21 Sep 2026 17:05:55 +0200 [thread overview]
Message-ID: <arFH0ridHWo3Z_w9@quoll> (raw)
In-Reply-To: <20260921075312.120983-1-lgs201920130244@gmail.com>
On Mon, 21 Sep 2026 15:53:12 +0800, Guangshuo Li wrote:
> register_platform_devices() creates multiple platform devices using
> platform_device_register_data(), but returns directly when a later
> platform device registration fails.
>
> If LED or watchdog platform device registration fails, previously
> registered platform devices are left registered. Since module init
> failure does not invoke the module exit cleanup path, these platform
> devices remain allocated and their backing platform_object memory is
> leaked.
>
> Unregister successfully created platform devices on registration failure
> paths to restore the missing cleanup.
>
> The issue was identified by a static analysis tool I developed and
> confirmed by manual review.
>
> Fixes: dd123e62bded ("platform/x86: simatic-ipc: add main driver for Siemens devices")
> Cc: stable@vger.kernel.org
> Signed-off-by: Guangshuo Li <lgs201920130244@gmail.com>
> ---
> drivers/platform/x86/siemens/simatic-ipc.c | 40 ++++++++++++++++++----
> 1 file changed, 34 insertions(+), 6 deletions(-)
>
You sent multiple independent patches, to multiple independent
subsystems. The amount of these patches clearly suggest this was
AI generated and most likely not tested.
More importantly, you sent all this work without properly organizing
relevant patches into patchsets. This makes reviewing difficult
and might cause multiple reviewers to address the same issue.
Replying to the entire set is impossible and requires handling each
patch independently, instead of applying or discarding the set.
Maintainers also won't see the bigger picture of your work. Quite
worrying.
This is on the verge of hostile patch: bomb us with so many
contributions, we won't be able to handle them in efficient manner,
like responding ONCE to ask you to slow down. Considering all this
is untested and LLM generated, I have even more doubts whether this
should be considered for review.
Please read kernel documentation BEFORE posting more work. It will
explain you how to identify subsystems, how to organize your work per
subsystem, how to document usage of LLM and how what you should not
do if this was posted in a good faith.
Best regards,
Krzysztof
next prev parent reply other threads:[~2026-09-21 15:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-21 7:53 Guangshuo Li
2026-09-21 10:10 ` Markus Elfring
2026-09-21 15:05 ` krzk [this message]
2026-09-21 15:09 ` krzk
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=arFH0ridHWo3Z_w9@quoll \
--to=krzk@kernel.org \
--cc=baocheng.su@siemens.com \
--cc=benedikt.niedermayr@siemens.com \
--cc=hansg@kernel.org \
--cc=henning.schild@siemens.com \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=lgs201920130244@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=platform-driver-x86@vger.kernel.org \
--cc=stable@vger.kernel.org \
--cc=tobias.schaffner@siemens.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
all inboxes | Powered by JetHome®