From: Greg KH <gregkh@linuxfoundation.org>
To: Linus Torvalds <torvalds@linux-foundation.org>,
Andrew Morton <akpm@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org,
Stephen Rothwell <sfr@canb.auug.org.au>,
Saravana Kannan <saravanak@google.com>
Subject: [GIT PULL] Driver core fixes for 6.0-rc5
Date: Fri, 9 Sep 2022 20:23:25 +0200 [thread overview]
Message-ID: <YxuEnRoUlZPzjfL6@kroah.com> (raw)
The following changes since commit 789bba82f63c3e81dce426ba457fc7905b30ac6e:
firmware_loader: Fix memory leak in firmware upload (2022-09-01 17:47:27 +0200)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/driver-core.git tags/driver-core-6.0-rc5
for you to fetch changes up to 5ac251c8a05ce074e5efac779debf82a15d870a3:
arch_topology: Make cluster topology span at least SMT CPUs (2022-09-07 17:57:31 +0200)
----------------------------------------------------------------
Driver core fixes for 6.0-rc5
Here are some small driver core and debugfs fixes for 6.0-rc5.
Included in here are:
- multiple attempts to get the arch_topology code to work properly on
non-cluster SMT systems. First attempt caused build breakages in
linux-next and 0-day, second try worked.
- debugfs fixes for a long-suffering memory leak. The pattern of
debugfs_remove(debugfs_lookup(...)) turns out to leak dentries, so
add debugfs_lookup_and_remove() to fix this problem. Also fix up
the scheduler debug code that highlighted this problem. Fixes for
other subsystems will be trickling in over the next few months for
this same issue once the debugfs function is merged.
All of these have been in linux-next since Wednesday with no reported
problems.
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
----------------------------------------------------------------
Greg Kroah-Hartman (4):
Revert "arch_topology: Make cluster topology span at least SMT CPUs"
driver core: fix driver_set_override() issue with empty strings
debugfs: add debugfs_lookup_and_remove()
sched/debug: fix dentry leak in update_sched_domain_debugfs
Yicong Yang (2):
arch_topology: Make cluster topology span at least SMT CPUs
arch_topology: Make cluster topology span at least SMT CPUs
drivers/base/arch_topology.c | 2 +-
drivers/base/driver.c | 6 ++++++
fs/debugfs/inode.c | 22 ++++++++++++++++++++++
include/linux/debugfs.h | 6 ++++++
kernel/sched/debug.c | 2 +-
5 files changed, 36 insertions(+), 2 deletions(-)
next reply other threads:[~2022-09-09 18:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-09 18:23 Greg KH [this message]
2022-09-09 19:13 ` pr-tracker-bot
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=YxuEnRoUlZPzjfL6@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=saravanak@google.com \
--cc=sfr@canb.auug.org.au \
--cc=torvalds@linux-foundation.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®