From: Pavel Machek <pavel@ucw.cz>
To: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
Cc: Sakari Ailus <sakari.ailus@linux.intel.com>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Ivaylo Dimitrov <ivo.g.dimitrov.75@gmail.com>,
linux-media@vger.kernel.org, kernel@pengutronix.de
Subject: Re: [PATCH] media: i2c: et8ek8: Don't strip remove function when driver is builtin
Date: Mon, 29 Apr 2024 22:35:57 +0200 [thread overview]
Message-ID: <ZjAEra8oZ9se0V9G@duo.ucw.cz> (raw)
In-Reply-To: <20240324160045.238647-2-u.kleine-koenig@pengutronix.de>
[-- Attachment #1: Type: text/plain, Size: 2032 bytes --]
On Sun 2024-03-24 17:00:44, Uwe Kleine-König wrote:
> Using __exit for the remove function results in the remove callback
> being discarded with CONFIG_VIDEO_ET8EK8=y. When such a device gets
> unbound (e.g. using sysfs or hotplug), the driver is just removed
> without the cleanup being performed. This results in resource leaks. Fix
> it by compiling in the remove callback unconditionally.
>
> This also fixes a W=1 modpost warning:
>
> WARNING: modpost: drivers/media/i2c/et8ek8/et8ek8: section mismatch in reference: et8ek8_i2c_driver+0x10 (section: .data) -> et8ek8_remove (section: .exit.text)
>
> Fixes: c5254e72b8ed ("[media] media: Driver for Toshiba et8ek8 5MP sensor")
> Signed-off-by: Uwe Kleine-König <u.kleine-koenig@pengutronix.de>
Reviewed-by: Pavel Machek <pavel@ucw.cz>
You might want to cc akpm if this does not get picked up.
Best regards,
Pavel
> ---
> drivers/media/i2c/et8ek8/et8ek8_driver.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/media/i2c/et8ek8/et8ek8_driver.c b/drivers/media/i2c/et8ek8/et8ek8_driver.c
> index f548b1bb75fb..e932d25ca7b3 100644
> --- a/drivers/media/i2c/et8ek8/et8ek8_driver.c
> +++ b/drivers/media/i2c/et8ek8/et8ek8_driver.c
> @@ -1475,7 +1475,7 @@ static int et8ek8_probe(struct i2c_client *client)
> return ret;
> }
>
> -static void __exit et8ek8_remove(struct i2c_client *client)
> +static void et8ek8_remove(struct i2c_client *client)
> {
> struct v4l2_subdev *subdev = i2c_get_clientdata(client);
> struct et8ek8_sensor *sensor = to_et8ek8_sensor(subdev);
> @@ -1517,7 +1517,7 @@ static struct i2c_driver et8ek8_i2c_driver = {
> .of_match_table = et8ek8_of_table,
> },
> .probe = et8ek8_probe,
> - .remove = __exit_p(et8ek8_remove),
> + .remove = et8ek8_remove,
> .id_table = et8ek8_id_table,
> };
>
>
> base-commit: 70293240c5ce675a67bfc48f419b093023b862b3
--
People of Russia, stop Putin before his war on Ukraine escalates.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
prev parent reply other threads:[~2024-04-29 20:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-24 16:00 [PATCH] media: i2c: et8ek8: Don't strip remove function when driver is builtin Uwe Kleine-König
2024-04-29 20:20 ` Uwe Kleine-König
2024-04-29 20:26 ` Uwe Kleine-König
2024-04-29 21:43 ` Sakari Ailus
2024-04-30 17:04 ` Uwe Kleine-König
2024-04-29 20:35 ` Pavel Machek [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=ZjAEra8oZ9se0V9G@duo.ucw.cz \
--to=pavel@ucw.cz \
--cc=ivo.g.dimitrov.75@gmail.com \
--cc=kernel@pengutronix.de \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=sakari.ailus@linux.intel.com \
--cc=u.kleine-koenig@pengutronix.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;
as well as URLs for NNTP newsgroup(s).