linux-kernel - Re: usb-serial lockdep trace in linus' current tree.

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

Date:	Thu, 7 Nov 2013 19:24:51 -0500
From:	Dave Jones <davej@...hat.com>
To:	Johan Hovold <jhovold@...il.com>
Cc:	linux-usb@...r.kernel.org,
	Linux Kernel <linux-kernel@...r.kernel.org>
Subject: Re: usb-serial lockdep trace in linus' current tree.

On Fri, Nov 08, 2013 at 01:09:03AM +0100, Johan Hovold wrote:
 
 > A recent change in usb-serial used the wrong memory-allocation flag in
 > write(), which results in a
 > 
 > 	[    5.979005] BUG: sleeping function called from invalid context at /home/johan/src/linux/linux-nu/mm/dmapool.c:310
 > 
 > with usb-next when using a usb-serial console as you seem to do be doing
 > as well.
 > 
 > Could be related. Care to give the fix below a try?

Seems to work. Feel free to add

Tested-by: Dave Jones <davej@...oraproject.org>

if this is the agreed upon fix for this.

thanks,

	Dave

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