From: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
To: Markus Elfring <Markus.Elfring@web.de>
Cc: Guangshuo Li <lgs201920130244@gmail.com>,
kernel@pengutronix.de, Thorsten Scherer <t.scherer@eckelmann.de>,
stable@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] siox: fix master memory leak on registration failure
Date: Mon, 21 Sep 2026 15:02:01 +0200 [thread overview]
Message-ID: <arEpuhA24xUlA-vw@monoceros> (raw)
In-Reply-To: <2784d61d-99d7-41f0-8c51-7736b788dc6c@web.de>
[-- Attachment #1: Type: text/plain, Size: 1094 bytes --]
On Mon, Sep 21, 2026 at 12:51:00PM +0200, Markus Elfring wrote:
> …
> > +++ b/drivers/siox/siox-core.c
> > @@ -753,14 +753,21 @@ int siox_master_register(struct siox_master *smaster)
> > smaster->poll_thread = kthread_run(siox_poll_thread, smaster,
> > "siox-%d", smaster->busno);
> > if (IS_ERR(smaster->poll_thread)) {
> > + ret = PTR_ERR(smaster->poll_thread);
>
> Would it be nicer to use this variable assignment directly before
> the goto statement?
No, please don't, IMHO it's fine to have IS_ERR and PTR_ERR together.
But I wonder if it's sensible to create a function to all the usual init
stuff such that the error handling in siox_master_register() can become
just:
get_device(&smaster->dev);
ret = siox_master_init(...);
if (ret)
put_device();
return ret;
Having said that, I wonder about the smaster->active = 0 assignment.
It's quite some time ago that I wrote that code, but either it's
useless (that's where my bet is on), or this assignment is missing in
the error path of device_add()? Thorsten?
Best regards
Uwe
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2026-09-21 13:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-19 18:10 Guangshuo Li
2026-09-21 10:51 ` Markus Elfring
2026-09-21 13:02 ` Uwe Kleine-König [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=arEpuhA24xUlA-vw@monoceros \
--to=u.kleine-koenig@pengutronix.de \
--cc=Markus.Elfring@web.de \
--cc=kernel@pengutronix.de \
--cc=lgs201920130244@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=stable@vger.kernel.org \
--cc=t.scherer@eckelmann.de \
/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®