linux-kernel - Re: [PATCH 148/196] Infiniband: make ipath driver use default driver groups.

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-prev] [thread-next>] [day] [month] [year] [list]

Date:	Fri, 25 Jan 2008 13:51:32 -0800
From:	Roland Dreier <rdreier@...co.com>
To:	Greg Kroah-Hartman <gregkh@...e.de>
Cc:	linux-kernel@...r.kernel.org,
	"Bryan O'Sullivan" <bryan.osullivan@...gic.com>,
	Arthur Jones <arthur.jones@...gic.com>,
	Cornelia Huck <cornelia.huck@...ibm.com>
Subject: Re: [PATCH 148/196] Infiniband: make ipath driver use default driver groups.

Hey Greg,

with Linus's latest kernel v2.6.24-412-gb47711b (which includes the
patch in the email I'm replying to), I see the following when I do
"modprobe -r ib_ipath" (on a system that actually has ipath hardware):

 kernel BUG at fs/sysfs/group.c:74!
 invalid opcode: 0000 [1] SMP
 CPU 1
 Modules linked in: fan ac battery ipv6 nfs lockd nfs_acl sunrpc dm_snapshot dm_mirror dm_mod loop ide_cd cdrom e1000 amd74xx generic psmouse shpchp pci_hotplug thermal ib_ipath serio_raw ehci_hcd ohci_hcd evdev button i2c_nforce2 ide_core processor ib_core k8temp i2c_core
 Pid: 3975, comm: modprobe Not tainted 2.6.24 #24
 RIP: 0010:[<ffffffff802bdbdb>]  [<ffffffff802bdbdb>] sysfs_remove_group+0x25/0x94
 RSP: 0000:ffff8101fbc33db8  EFLAGS: 00010246
 RAX: 0000000000000000 RBX: 0000000000000000 RCX: ffff81007d8bc070
 RDX: ffff81007d634272 RSI: ffff81007d634d00 RDI: ffffffff80503090
 RBP: ffffffff880a7220 R08: 0000000000000000 R09: ffff81007d8bc070
 R10: 0000000000000000 R11: 00000000fd812590 R12: ffff81007d8bc070
 R13: 00007fffc6f88c80 R14: 0000000000000000 R15: 0000000000000000
 FS:  00002acbe409b6e0(0000) GS:ffff81007e001a00(0000) knlGS:0000000000000000
 CS:  0010 DS: 0000 ES: 0000 CR0: 000000008005003b
 CR2: 00002acbe3e59de0 CR3: 000000007d482000 CR4: 00000000000006e0
 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
 DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
 Process modprobe (pid: 3975, threadinfo ffff8101fbc32000, task ffff8101fbead590)
 Stack:  000000000e9000ff ffff81007d8bc160 ffff81007d8bc070 ffffffff88087574
  ffffc20001734000 ffffc20001734000 ffffffff880a7050 ffffffff88074b26
  ffffffff804bd39a ffff81007d8bc000 ffffffff880a7050 ffffffff804bd39a
 Call Trace:
  [<ffffffff88087574>] :ib_ipath:ipath_device_remove_group+0x20/0x42
  [<ffffffff88074b26>] :ib_ipath:ipath_remove_one+0x9f/0x431
  [<ffffffff803235e5>] pci_device_remove+0x24/0x47
  [<ffffffff8036ec01>] __device_release_driver+0x74/0x97
  [<ffffffff8036f075>] driver_detach+0x96/0xd5
  [<ffffffff8036e568>] bus_remove_driver+0x7b/0x9e
  [<ffffffff803238da>] pci_unregister_driver+0x29/0x7d
  [<ffffffff8809093f>] :ib_ipath:infinipath_cleanup+0x33/0x40
  [<ffffffff8025032a>] sys_delete_module+0x199/0x1cf
  [<ffffffff80318400>] __up_read+0x2/0x8a
  [<ffffffff8020befe>] system_call+0x7e/0x83

 Code: 0f 0b eb fe 48 85 db 74 2e 83 3b 00 75 26 48 c7 c1 d8 ae 43
 RIP  [<ffffffff802bdbdb>] sysfs_remove_group+0x25/0x94
  RSP <ffff8101fbc33db8>

The BUG() in question is the one here:

	void sysfs_remove_group(struct kobject * kobj, 
				const struct attribute_group * grp)
	{
		struct sysfs_dirent *dir_sd = kobj->sd;
		struct sysfs_dirent *sd;
	
		if (grp->name) {
			sd = sysfs_get_dirent(dir_sd, grp->name);
			BUG_ON(!sd);

Any ideas here?  I'll continue to try to relearn all the sysfs stuff
but a hint my make things go faster.

Thanks,
  Roland
--
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/