linux-kernel - Re: Kernel Oops: btusb: 4.2rc1 System lockup with BT dongle insert

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]

Message-ID: <51dad0b8500cb7904dbe3438b15c5a7c.squirrel@mungewell.org>
Date:	Sun, 19 Jul 2015 21:48:22 -0400
From:	simon@...gewell.org
To:	simon@...gewell.org
Cc:	"Laura Abbott" <labbott@...hat.com>,
	"Shuah Khan" <shuahkh@....samsung.com>,
	"Kim, Milo" <milo.kim@...com>, linux-bluetooth@...r.kernel.org,
	linux-kernel@...r.kernel.org
Subject: Re: Kernel Oops: btusb: 4.2rc1 System lockup with BT dongle insert -
 log attached


>> https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=6f957724b94cb19f5c1c97efd01dd4df8ced323c
>>
>
> Certainly looks like a plausible solution, will build kernel tonight to
> confirm.

Just to confirm; 4.2rc1 + above patch, and 4.2rc2 both function correctly
and I no longer see the lock up/Oops.

Thanks to all who helped out,
Simon.

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