mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Kurt Borja <kuurtb@gmail.com>
To: "Mark Pearson" <mpearson-lenovo@squebb.ca>,
	"Hans de Goede" <hdegoede@redhat.com>,
	"Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
Cc: platform-driver-x86@vger.kernel.org,
	linux-kernel@vger.kernel.org,  Kurt Borja <kuurtb@gmail.com>
Subject: [PATCH v2 0/3] platform/x86: think-lmi: Fix resource cleanup flaws
Date: Sat, 28 Jun 2025 23:32:52 -0300	[thread overview]
Message-ID: <20250628-lmi-fix-v2-0-c530e1c959d7@gmail.com> (raw)

Hi all,

First patch is a prerequisite in order to avoid NULL pointer
dereferences in error paths. Then two fixes follow.

Signed-off-by: Kurt Borja <kuurtb@gmail.com>
---
Changes in v2:

[PATCH 02]
  - Remove kobject_del() and commit message remark. It turns out it's
    optional to call this (my bad)
  - Leave only one fixes tag. The other two are not necessary.

- Link to v1: https://lore.kernel.org/r/20250628-lmi-fix-v1-0-c6eec9aa3ca7@gmail.com

---
Kurt Borja (3):
      platform/x86: think-lmi: Create ksets consecutively
      platform/x86: think-lmi: Fix kobject cleanup
      platform/x86: think-lmi: Fix sysfs group cleanup

 drivers/platform/x86/lenovo/think-lmi.c | 90 +++++++++++----------------------
 1 file changed, 30 insertions(+), 60 deletions(-)
---
base-commit: 73f0f2b52c5ea67b3140b23f58d8079d158839c8
change-id: 20250628-lmi-fix-98143b10d9fd
-- 
 ~ Kurt


             reply	other threads:[~2025-06-29  2:33 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-29  2:32 Kurt Borja [this message]
2025-06-29  2:32 ` [PATCH v2 1/3] platform/x86: think-lmi: Create ksets consecutively Kurt Borja
2025-06-29  2:32 ` [PATCH v2 2/3] platform/x86: think-lmi: Fix kobject cleanup Kurt Borja
2025-06-29  2:32 ` [PATCH v2 3/3] platform/x86: think-lmi: Fix sysfs group cleanup Kurt Borja
2025-06-30  8:54 ` [PATCH v2 0/3] platform/x86: think-lmi: Fix resource cleanup flaws Ilpo Järvinen
2025-06-30 17:19   ` Kurt Borja

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=20250628-lmi-fix-v2-0-c530e1c959d7@gmail.com \
    --to=kuurtb@gmail.com \
    --cc=hdegoede@redhat.com \
    --cc=ilpo.jarvinen@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mpearson-lenovo@squebb.ca \
    --cc=platform-driver-x86@vger.kernel.org \
    /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®