lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Date:	Mon, 28 Jul 2014 11:28:26 -0700
From:	"Luis R. Rodriguez" <mcgrof@...not-panic.com>
To:	gregkh@...uxfoundation.org
Cc:	tiwai@...e.de, linux-kernel@...r.kernel.org,
	"Luis R. Rodriguez" <mcgrof@...e.com>
Subject: [PATCH v2 0/4] driver core: allow explicit deferred probe preference

From: "Luis R. Rodriguez" <mcgrof@...e.com>

This adds support to let device drivers explicitly request to be
probed on the deferred workqueue. Note that another ideal solution
on top of this would be if we could detect somehow if kthread_create()
was SIGKILL'd for a modprobe, and also driver_deferred_probe_add() the
device there proactively. This would enable us to not have to be hunting
for these device drivers as a fix after a problem popped up. That would
allow us to look for device drivers that need this change in a proactive
way but without failing them first -- I just can't think of a way to do
this yet.

Luis R. Rodriguez (4):
  driver core: move deferred probe add / remove helpers down a bit
  driver core: enable drivers to use deferred probe from init
  cxgb4: ask for deferred probe
  mptsas: ask for deferred probe

 drivers/base/dd.c                               | 58 ++++++++++++++++---------
 drivers/message/fusion/mptsas.c                 |  3 ++
 drivers/net/ethernet/chelsio/cxgb4/cxgb4_main.c |  3 ++
 include/linux/device.h                          |  7 +++
 4 files changed, 50 insertions(+), 21 deletions(-)

-- 
2.0.1

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists