linux/drivers, branch v2.6.28.7

Bluetooth: Fix TX error path in btsdio driver

2009-02-20T22:40:22Z

commit 7644d63d1348ec044ccd8f775fefe5eb7cbcac69 upstream. This patch fixes accumulating of the header in case packet was requeued in the error path. Signed-off-by: Tomas Winkler Signed-off-by: Marcel Holtmann Signed-off-by: Greg Kroah-Hartman

3c505: do not set pcb->data.raw beyond its size

2009-02-20T22:40:22Z

commit 501aa061bd68169a5b54c123641f8dfa9ad31545 upstream. Ensure that we do not set pcb->data.raw beyond its size, print an error message and return false if we attempt to. A timout message was printed one too early. Signed-off-by: Roel Kluin Signed-off-by: David S. Miller Signed-off-by: Greg Kroah-Hartman

Add support for VT6415 PCIE PATA IDE Host Controller

2009-02-20T22:40:21Z

commit 5955c7a2cfb6a35429adea5dc480002b15ca8cfc upstream. Signed-off-by: Zlatko Calusic Signed-off-by: Linus Torvalds Signed-off-by: Greg Kroah-Hartman

SCSI: libiscsi: fix iscsi pool leak

2009-02-20T22:40:19Z

commit 2f5899a39dcffb404c9a3d06ad438aff3e03bf04 upstream. I am not sure what happened. It looks like we have always leaked the q->queue that is allocated from the kfifo_init call. nab finally noticed that we were leaking and this patch fixes it by adding a kfree call to iscsi_pool_free. kfifo_free is not used per kfifo_init's instructions to use kfree. Signed-off-by: Mike Christie Signed-off-by: James Bottomley Cc: Jean Delvare Signed-off-by: Greg Kroah-Hartman

Fix Intel IOMMU write-buffer flushing

2009-02-20T22:40:19Z

commit ca77fde8e62cecb2c0769052228d15b901367af8 upstream. This is the cause of the DMA faults and disk corruption that people have been seeing. Some chipsets neglect to report the RWBF "capability" -- the flag which says that we need to flush the chipset write-buffer when changing the DMA page tables, to ensure that the change is visible to the IOMMU. Override that bit on the affected chipsets, and everything is happy again. Thanks to Chris and Bhavesh and others for helping to debug. Signed-off-by: David Woodhouse Tested-by: Chris Wright Reviewed-by: Bhavesh Davda Signed-off-by: Linus Torvalds Signed-off-by: Greg Kroah-Hartman

sata_nv: give up hardreset on nf2

2009-02-20T22:40:18Z

commit 7dac745b8e367c99175b8f0d014d996f0e5ed9e5 upstream. Kernel bz#12176 reports that nf2 hardreset simply doesn't work. Give up. Argh... Signed-off-by: Tejun Heo Cc: Robert Hancock Reported-by: Saro Signed-off-by: Jeff Garzik Signed-off-by: Greg Kroah-Hartman

WATCHDOG: iTCO_wdt: fix SMI_EN regression 2

2009-02-20T22:40:17Z

commit 12d60e28bed3f593aac5385acbdbb089eb8ae21e upstream. bugzilla: #12363 commit 7cd5b08be3c489df11b559fef210b81133764ad4 added a second regression: some Dell's and Compaq's lockup on boot. So we revert most of the code. The ICH9 reboot issue remains in place and will need some more fixing... :-( Signed-off-by: Wim Van Sebroeck Signed-off-by: Greg Kroah-Hartman

ide-cd: fix DMA for non bio-backed requests

2009-02-17T17:29:05Z

commit 9e772d0135a5b5f8355320be429efa339700d52d upstream. This one fixes http://bugzilla.kernel.org/show_bug.cgi?id=12320. Signed-off-by: Borislav Petkov Signed-off-by: Bartlomiej Zolnierkiewicz Signed-off-by: Greg Kroah-Hartman

libata: fix EH device failure handling

2009-02-17T17:29:03Z

commit d89293abd95bfd7dd9229087d6c30c1464c5ac83 upstream. The dev->pio_mode > XFER_PIO_0 test is there to avoid unnecessary speed down warning messages but it accidentally disabled SATA link spd down during configuration phase after reset where PIO mode is always zero. This patch fixes the problem by moving the test where it belongs. This makes libata probing sequence behave better when the connection is flaky at higher link speeds which isn't too uncommon for eSATA devices. Signed-off-by: Tejun Heo Signed-off-by: Jeff Garzik Cc: Chuck Ebbert Signed-off-by: Greg Kroah-Hartman

HID: adjust report descriptor fixup for MS 1028 receiver

2009-02-17T17:29:02Z

commit 0fb21de0799a985d2da3da14ae5625d724256638 upstream. Report descriptor fixup for MS 1028 receiver changes also values for Keyboard and Consumer, which incorrectly trims the range, causing correct events being thrown away before passing to userspace. We need to keep the GenDesk usage fixup though, as it reports totally bogus values about axis. Reported-by: Lucas Gadani Signed-off-by: Jiri Kosina Signed-off-by: Greg Kroah-Hartman