From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Jiri Kosina <jikos@kernel.org>,
Benjamin Tissoires <benjamin.tissoires@redhat.com>
Cc: linux-input@vger.kernel.org, linux-kernel@vger.kernel.org,
Stephen Boyd <swboyd@chromium.org>
Subject: [PATCH v2 0/2] HID: ensure timely release of driver resources
Date: Tue, 23 May 2023 14:04:30 -0700 [thread overview]
Message-ID: <20230523-hid-devres-v2-0-5220211a428c@gmail.com> (raw)
These 2 patches address an issue in HID subsystem where cleanup code in
the bus code runs before releasing devres-managed resources by the
driver core.
This is a V2 of the patch, which was split in 2 parts - generic cleanup
and the actualy change addressing the issue.
Link: https://lore.kernel.org/r/20230505232417.1377393-1-swboyd@chromium.org
Link: https://lore.kernel.org/r/ZFWarGkRAfPOmI6E@google.com
Signed-off-by: Dmitry Torokhov <dmitry.torokhov@gmail.com>
---
Dmitry Torokhov (2):
HID: split apart hid_device_probe to make logic more apparent
HID: ensure timely release of driver-allocated resources
drivers/hid/hid-core.c | 118 +++++++++++++++++++++++++++++--------------------
include/linux/hid.h | 1 +
2 files changed, 72 insertions(+), 47 deletions(-)
---
base-commit: 9f925874281f7e8855855d6210d6e29d844e4307
change-id: 20230523-hid-devres-b0edd05de354
Best regards,
--
Dmitry
next reply other threads:[~2023-05-23 21:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-23 21:04 Dmitry Torokhov [this message]
2023-05-23 21:04 ` [PATCH v2 1/2] HID: split apart hid_device_probe to make logic more apparent Dmitry Torokhov
2023-05-23 21:04 ` [PATCH v2 2/2] HID: ensure timely release of driver-allocated resources Dmitry Torokhov
2023-05-26 18:46 ` [PATCH v2 0/2] HID: ensure timely release of driver resources Jiri Kosina
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=20230523-hid-devres-v2-0-5220211a428c@gmail.com \
--to=dmitry.torokhov@gmail.com \
--cc=benjamin.tissoires@redhat.com \
--cc=jikos@kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=swboyd@chromium.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;
as well as URLs for NNTP newsgroup(s).