linux-kernel - Re: hci_usb strikes again (was Re: BUG kmalloc-2048: Poison overwritten)

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: <dd18b0c30806030130j9273d8bq380bdea71e60250d@mail.gmail.com>
Date:	Tue, 3 Jun 2008 08:30:20 +0000
From:	"Justin Mattock" <justinmattock@...il.com>
To:	"Pavel Machek" <pavel@...e.cz>
Cc:	"Rafael J. Wysocki" <rjw@...k.pl>,
	"Linux Kernel Mailing List" <linux-kernel@...r.kernel.org>,
	"Andrew Morton" <akpm@...ux-foundation.org>, marcel@...tmann.org,
	linux-bluetooth@...r.kernel.org
Subject: Re: hci_usb strikes again (was Re: BUG kmalloc-2048: Poison overwritten)

On Tue, Jun 3, 2008 at 6:43 AM, Pavel Machek <pavel@...e.cz> wrote:
> Hi!
>> >> > cpufreq_performance cpufreq_powersave rfcomm hidp l2cap bluetooth fan
>> >> > ipmi_watchdog ipmi_msghandler uinput wlan_tkip ieee80211_crypt_tkip
>> >> > ieee80211_crypt arpt_mangle arptable_filter arp_tables
>> >> > nf_conntrack_ipv4 nf_conntrack iptable_mangle iptable_filter ip_tables
>> >> > x_tables intelfb i2c_i810 i2c_algo_bit coretemp eeprom acpi_cpufreq
>> >> > fglrx(P) applesmc joydev uvcvideo appletouch wlan_scan_sta
>> >> > ath_rate_sample firewire_ohci firewire_core snd_hda_intel ath_pci
>> >> > snd_pcm wlan ohci1394 intel_agp evdev ath_hal(P) snd_timer ieee1394
>> >> > pata_acpi thermal ehci_hcd uhci_hcd snd_page_alloc snd_hwdep agpgart
>> >> > video button processor
>> >> > [  232.270800]
>> >> > [  232.270802] Pid: 2690, comm: btdelconn Tainted: P
>> >> > (2.6.26-rc4-00033-g5463508 #4)
>> >
>> > ...and we get oops in bluetooth.
>> >
>> > Use btusb, instead.
>> >
>> > Actually, I guess we should mark hci_usb as broken. I don't see why we
>> > should debug the same problem over and over again.
>
>> Well; "shizzle my frizzle," The funny thing is, is I have not seen
>> this after performing more suspends,
>> maybe this is a every once in a while scenario.
>
> It was "one in three" in my tests; but you need usb actively in use
> while you are suspending for this to bite.
>                                                                        Pavel
>
> --
> (english) http://www.livejournal.com/~pavelmachek
> (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
>

Aahhhh the beast has been discovered.
That's pretty cool!! I quess from my side, I'll try what you had
suggested "btusb".
("I just have to allocate enough time to do so, ("come on people", get
out of my way!!"))
I'm finding myself in one of those days where I'm away from my laptop
(contingency or not).
regards;

-- 
Justin P. Mattock
--
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/