mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
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>,
	"Johan Hovold" <johan@kernel.org>,
	"Saravana Kannan" <saravanak@kernel.org>,
	"Andrew Morton" <akpm@linux-foundation.org>,
	<driver-core@lists.linux.dev>, <rust-for-linux@vger.kernel.org>,
	<linux-kernel@vger.kernel.org>
Subject: [GIT PULL] Driver core fixes for 7.4-rc1 (2nd)
Date: Sat, 31 Oct 2026 01:07:07 +0100	[thread overview]
Message-ID: <DMIL3FNP8HDY.3K2425TJD0OU2@kernel.org> (raw)

Hi Linus,

Please pull these driver-core fixes.

The main fix is a revert of TAINT_FORCED_BIND, which is too broad and causes
established VFIO workflows to taint the kernel.

Thanks,
Danilo

The following changes since commit 0cc3ad8f4d2e2009c2005278c754caf7c07fe0a4:

  Merge tag 'driver-core-7.4-rc1-2' of git://git.kernel.org/pub/scm/linux/kernel/git/driver-core/driver-core (2026-10-26 07:04:41 -1000)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/driver-core/driver-core.git tags/driver-core-7.4-rc1-3

for you to fetch changes up to a287f97d4256b5f5527f5b5a54f8ada55e1482c7:

  Revert "driver core: add TAINT_FORCED_BIND for when userspace manually messes with devices and drivers" (2026-10-29 21:01:16 +0100)

----------------------------------------------------------------
Driver core fixes for 7.4-rc1

- Revert TAINT_FORCED_BIND, introduced to flag manual sysfs bind/unbind
  operations associated with misleading fuzzing reports. It also taints
  established workflows, including VFIO device passthrough; a more
  targeted approach will be revisited after 7.4.

- Rate limit synthetic uevent failure messages to prevent log flooding
  from repeated invalid writes to sysfs uevent files

----------------------------------------------------------------
Greg Kroah-Hartman (1):
      Revert "driver core: add TAINT_FORCED_BIND for when userspace manually messes with devices and drivers"

Josef Bacik (1):
      driver core: Limit the messages on a refused uevent

 Documentation/admin-guide/tainted-kernels.rst | 54 +++++++++++++++++++++++++-----------------------------
 drivers/base/bus.c                            |  3 ---
 drivers/base/core.c                           |  4 +++-
 include/linux/panic.h                         |  3 +--
 include/trace/events/module.h                 |  3 +--
 kernel/panic.c                                |  5 ++---
 lib/kobject_uevent.c                          |  6 +++---
 tools/debugging/kernel-chktaint               |  8 --------
 8 files changed, 35 insertions(+), 51 deletions(-)

             reply	other threads:[~2026-10-31  0:07 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-31  0:07 Danilo Krummrich [this message]
2026-10-31  0:40 ` 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=DMIL3FNP8HDY.3K2425TJD0OU2@kernel.org \
    --to=dakr@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=driver-core@lists.linux.dev \
    --cc=gregkh@linuxfoundation.org \
    --cc=johan@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rafael@kernel.org \
    --cc=rust-for-linux@vger.kernel.org \
    --cc=saravanak@kernel.org \
    --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®