commit 95a9b647d158d0c13cd7604ba53cd97a88d96f7e Author: root Date: Sun Nov 16 14:49:25 2008 +0100 Revert "disable CONFIG_DYNAMIC_FTRACE due to possible memory corruption on module unload" This reverts commit 67d9b90a1c844bf1c6daaffd2c60561fc8c445f7. commit f36789c71cde4689aeb9b80aafc6895b270b05d2 Author: Tim Gardner Date: Wed Nov 5 13:42:32 2008 -0700 UBUNTU: Ubuntu-2.6.27-8.17 Ignore: yes Signed-off-by: Tim Gardner commit 8e80cc54c0b08f38cf1f9a66ebd96284b55f0d2f Author: John W. Linville Date: Thu Oct 30 13:59:16 2008 -0400 UBUNTU: SAUCE: iwlagn: avoid sleep in softirq context LP: #286285 __ieee80211_tasklet_handler -> __ieee80211_rx -> __ieee80211_rx_handle_packet -> ieee80211_invoke_rx_handlers -> ieee80211_rx_h_decrypt -> ieee80211_crypto_tkip_decrypt -> ieee80211_tkip_decrypt_data -> iwl4965_mac_update_tkip_key -> iwl_scan_cancel_timeout -> msleep Ooops! Avoid the sleep by changing iwl_scan_cancel_timeout with iwl_scan_cancel and simply returning on failure if the scan persists. This will cause hardware decryption to fail and we'll handle a few more frames with software decryption. Carry this as a SAUCE patch until applied by upstream. I suspect there will be a conflict if John fixes the spelling in the patch comment, e.g., decrpyption v.s. decryption. Signed-off-by: John W. Linville Signed-off-by: Tim Gardner commit c631c0647c67da861593a88040adcc282745866c Author: Tim Gardner Date: Wed Nov 5 09:21:20 2008 -0700 UBUNTU: Bump ABI Ignore: yes Signed-off-by: Tim Gardner commit 5519323b70dbc2833b0e2675f2d2ad5f07d7887d Author: Greg Kroah-Hartman Date: Sat Oct 25 15:05:07 2008 -0700 Linux 2.6.27.4 Signed-off-by: Tim Gardner commit dd5a9dcccd27bcd5207307ba943e4a1c1decc949 Author: Mike Isely Date: Sun Oct 19 16:26:05 2008 -0300 V4L/DVB (9300): pvrusb2: Fix deadlock problem commit c82732a42896364296599b0f73f01c5e3fd781ae upstream Fix deadlock problem in 2.6.27 caused by new USB core behavior in response to a USB device reset request. With older kernels, the USB device reset was "in line"; the reset simply took place and the driver retained its association with the hardware. However now this reset triggers a disconnect, and worse still the disconnect callback happens in the context of the caller who asked for the device reset. This results in an attempt by the pvrusb2 driver to recursively take a mutex it already has, which deadlocks the driver's worker thread. (Even if the disconnect callback were to happen on a different thread we'd still have problems however - because while the driver should survive and correctly disconnect / reconnect, it will then trigger another device reset during the repeated initialization, which will then cause another disconect, etc, forever.) The fix here is simply to not attempt the device reset (it was of marginal value anyway). Signed-off-by: Mike Isely Signed-off-by: Mauro Carvalho Chehab Signed-off-by: Mike Krufky Signed-off-by: Greg Kroah-Hartman Signed-off-by: Tim Gardner commit 9b1f27a683de01dde60c400358f7ff0e1f5e1baa Author: Kenji Kaneshige Date: Fri Oct 24 02:50:03 2008 +0000 PCI hotplug: cpqphp: fix kernel NULL pointer dereference commit d2174c3c07adad88dd9ba37a731e0b00b746822a upstream The following patch fixes the regression in 2.6.27 that causes kernel NULL pointer dereference at cpqphp driver probe time. This patch should be backported to the .27 stable series.