From: "Danilo Krummrich" <dakr@kernel.org>
To: "Linus Torvalds" <torvalds@linux-foundation.org>
Cc: "Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
"Rafael J. Wysocki" <rafael@kernel.org>,
"Saravana Kannan" <saravanak@google.com>,
"Andrew Morton" <akpm@linux-foundation.org>,
"Christian Brauner" <brauner@kernel.org>,
"Miguel Ojeda" <ojeda@kernel.org>, <linux-kernel@vger.kernel.org>
Subject: [GIT PULL] Driver core fixes for 6.17-rc3
Date: Sat, 23 Aug 2025 13:21:24 +0200 [thread overview]
Message-ID: <DC9RN9QVWOSM.1RH74QYO0EI73@kernel.org> (raw)
Hi Linus,
Please pull these driver-core fixes.
All commits have been in linux-next for a couple rounds.
No conflicts expected.
(You might receive a duplicate of commit ba6cc29351b1 ("debugfs: fix mount
options not being applied") from Christian, since it ended up to be picked into
both trees.)
- Danilo
The following changes since commit 8f5ae30d69d7543eee0d70083daf4de8fe15d585:
Linux 6.17-rc1 (2025-08-10 19:41:16 +0300)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/driver-core/driver-core.git tags/driver-core-6.17-rc3
for you to fetch changes up to 3a68841d1d9b6eb32b2652bbb83acd17d5eb9135:
Documentation: smooth the text flow in the security bug reporting process (2025-08-17 12:23:30 +0200)
----------------------------------------------------------------
Driver core fixes for 6.16-rc3
- Fix swapped handling of lru_gen and lru_gen_full debugfs files in
vmscan.
- Fix debugfs mount options (uid, gid, mode) being silently ignored.
- Fix leak of devres action in the unwind path of Devres::new().
- Documentation
- Expand and fix documentation of (outdated) Device, DeviceContext
and generic driver infrastructure.
- Fix C header link of faux device abstractions.
- Clarify expected interaction with the security team.
- Smooth text flow in the security bug reporting process
documentation.
----------------------------------------------------------------
Charalampos Mitrodimas (1):
debugfs: fix mount options not being applied
Danilo Krummrich (5):
mm/vmscan: fix inverted polarity in lru_gen_seq_show()
device: rust: expand documentation for DeviceContext
device: rust: expand documentation for Device
driver: rust: expand documentation for driver infrastructure
rust: devres: fix leaking call to devm_add_action()
Miguel Ojeda (1):
rust: faux: fix C header link
Willy Tarreau (2):
Documentation: clarify the expected collaboration with security bugs reporters
Documentation: smooth the text flow in the security bug reporting process
Documentation/process/security-bugs.rst | 25 +++++++++-----
fs/debugfs/inode.c | 11 +++++-
mm/vmscan.c | 4 +--
rust/kernel/device.rs | 208 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++-------------
rust/kernel/devres.rs | 27 ++++++++++-----
rust/kernel/driver.rs | 89 ++++++++++++++++++++++++++++++++++++++++++++++--
rust/kernel/faux.rs | 2 +-
7 files changed, 318 insertions(+), 48 deletions(-)
next reply other threads:[~2025-08-23 11:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-23 11:21 Danilo Krummrich [this message]
2025-08-23 13:30 ` 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=DC9RN9QVWOSM.1RH74QYO0EI73@kernel.org \
--to=dakr@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=brauner@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ojeda@kernel.org \
--cc=rafael@kernel.org \
--cc=saravanak@google.com \
--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®