linux-kernel - [GIT PATCH] driver core fixes against 2.6.24-git

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 linux-cve-announce 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:	Thu, 7 Feb 2008 12:01:40 -0800
From:	Greg KH <gregkh@...e.de>
To:	Linus Torvalds <torvalds@...l.org>, Andrew Morton <akpm@...l.org>
Cc:	linux-kernel@...r.kernel.org,
	"David S. Miller" <davem@...emloft.net>, kay.sievers@...y.org,
	Michael_E_Brown@...l.com, rdreier@...co.com, htejun@...il.com
Subject: [GIT PATCH] driver core fixes against 2.6.24-git

Here's 3 patches against your current git tree that fix some more
problems that have cropped up:
	- whole_disk attribute file causes oopses when read from.
	- the firmware class name change broke Dell machines that were
	  working just fine.
	- we shouldn't BUG on a programming error in sysfs by the
	  caller, do a WARN_ON instead.

Please pull from:
	master.kernel.org:/pub/scm/linux/kernel/git/gregkh/driver-2.6.git/

Patches will be sent as a follow-on to this message to lkml for people
to see.

thanks,

greg k-h

------------

 drivers/base/firmware_class.c |    3 ++-
 fs/partitions/check.c         |   17 ++++++++++-------
 fs/sysfs/group.c              |    7 ++++++-
 3 files changed, 18 insertions(+), 9 deletions(-)

---------------

Greg Kroah-Hartman (2):
      Block: Fix whole_disk attribute bug
      sysfs: remove BUG_ON() from sysfs_remove_group()

Michael E Brown (1):
      Driver core: Revert "Fix Firmware class name collision"

--
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/