linux-kernel - 2.6.27-rc5-git7 iwl3945: driver still has receiver lockups and is worse than before

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

Date:	Fri, 5 Sep 2008 10:29:44 -0600 (MDT)
From:	jmerkey@...fmountaingroup.com
To:	linux-kernel@...r.kernel.org
Subject: 2.6.27-rc5-git7 iwl3945: driver still has receiver lockups and is 
     worse than before

Same problems as previously reported, except now it's gotten worse.  Where
before the adapter would lockup only when setting encryption keys, now it
locks up intermittently even without using encryption using the native
linux iwl3945 driver

This same kernel now causes ndis drivers to crash under ndiswrapper (which
wrked before) with bugs being reported in the "workqueue" functions.  The
specific area where I tracked down some serious bugginess and sickness was
here (I LOVE MY SHINY NEW LINUX KERNEL DEBUGGER).

		if (unlikely(in_atomic() || lockdep_depth(current) > 0)) {
			printk(KERN_ERR "BUG: workqueue leaked lock or atomic: "
					"%s/0x%08x/%d\n",
					current->comm, preempt_count(),
				       	task_pid_nr(current));
			printk(KERN_ERR "    last function: ");
			print_symbol("%s\n", (unsigned long)f);
			debug_show_held_locks(current);
			dump_stack();
		}

These iwl3945 problems seem related to the copy of Novell's work-to-do
subsystem called "workqueues" in linux when preemption is active, at least
in the ndiswrapper case.

Jeff

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