[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <5dde33b8-75ee-3de4-d694-d5700b9cc0a6@intel.com>
Date: Tue, 13 Jun 2023 11:57:43 +0200
From: "Wilczynski, Michal" <michal.wilczynski@...el.com>
To: Ilpo Järvinen <ilpo.jarvinen@...ux.intel.com>
CC: <linux-acpi@...r.kernel.org>, <rafael@...nel.org>,
<andriy.shevchenko@...el.com>, <pali@...nel.org>,
<hdegoede@...hat.com>, <markgross@...nel.org>,
<fengguang.wu@...el.com>, <dvhart@...ux.intel.com>,
<platform-driver-x86@...r.kernel.org>,
LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v1] platform/x86/dell/dell-rbtn: Fix resources leaking on
error path
On 6/13/2023 11:28 AM, Ilpo Järvinen wrote:
> On Mon, 12 Jun 2023, Michal Wilczynski wrote:
>
>> Currently rbtn_add() in case of failure is leaking resources. Fix this
>> by adding a proper rollback. While at it, remove unnecessary assignment
>> of NULL to device->driver_data and unnecessary whitespace, plus add a
>> break for the default case in a switch.
>>
>> Suggested-by: Ilpo Järvinen <ilpo.jarvinen@...ux.intel.com>
>> Fixes: 817a5cdb40c8 ("dell-rbtn: Dell Airplane Mode Switch driver")
>> Signed-off-by: Michal Wilczynski <michal.wilczynski@...el.com>
>> Reviewed-by: Andy Shevchenko <andriy.shevchenko@...ux.intel.com>
>> ---
>> drivers/platform/x86/dell/dell-rbtn.c | 5 +++--
>> 1 file changed, 3 insertions(+), 2 deletions(-)
>>
>> diff --git a/drivers/platform/x86/dell/dell-rbtn.c b/drivers/platform/x86/dell/dell-rbtn.c
>> index aa0e6c907494..e9b3f9c3ab7d 100644
>> --- a/drivers/platform/x86/dell/dell-rbtn.c
>> +++ b/drivers/platform/x86/dell/dell-rbtn.c
>> @@ -420,10 +420,12 @@ static int rbtn_add(struct acpi_device *device)
>> break;
>> default:
>> ret = -EINVAL;
>> + break;
>> }
>> + if (ret)
>> + rbtn_acquire(device, false);
>>
>> return ret;
>> -
>> }
>>
>> static void rbtn_remove(struct acpi_device *device)
>> @@ -442,7 +444,6 @@ static void rbtn_remove(struct acpi_device *device)
>> }
>>
>> rbtn_acquire(device, false);
>> - device->driver_data = NULL;
>> }
>>
>> static void rbtn_notify(struct acpi_device *device, u32 event)
> I'm a bit worried the stable people might not like "these while at it
> parts". Those changes too are all good but unrelated to the actual fix so
> they should appear in their own patches.
Hi, thanks for you input,
Changes seemed really minor and inconsequential, so it seemed to me like it would be an
overkill to create a separate patch for a cosmetic change.
>
Powered by blists - more mailing lists