linux-toradex.git, branch v2.6.33.5

Linux 2.6.33.5

2010-05-26T21:49:41+00:00

crypto: authenc - Add EINPROGRESS check

2010-05-26T21:32:12+00:00

commit 180ce7e81030e1ef763d58f97f9ab840ff57d848 upstream.

When Steffen originally wrote the authenc async hash patch, he
correctly had EINPROGRESS checks in place so that we did not invoke
the original completion handler with it.

Unfortuantely I told him to remove it before the patch was applied.

As only MAY_BACKLOG request completion handlers are required to
handle EINPROGRESS completions, those checks are really needed.

This patch restores them.

Reported-by: Sebastian Andrzej Siewior 
Signed-off-by: Herbert Xu 
Signed-off-by: Greg Kroah-Hartman

Revert "ath9k: fix lockdep warning when unloading module" on stable kernels

2010-05-26T21:32:12+00:00

Johannes' patch 34e8950 titled:

	mac80211: allow station add/remove to sleep

changed the way mac80211 adds and removes peers. The new
sta_add() / sta_remove() callbacks allowed the driver callbacks
to sleep. Johannes also ported ath9k to use sta_add() / sta_remove()
via the patch 4ca7786 titled:

	ath9k: convert to new station add/remove callbacks

but this patch forgot to address a change in locking issue which
Ming Lei eventually found on his 2.6.33-wl #12 build. The 2.6.33-wl
build includes code for the 802.11 subsystem for 2.6.34 though so did
already have the above two patches (ath9k_sta_remove() on his trace),
the 2.6.33 kernel did not however have these two patches. Ming eventually
cured his lockdep warnign via the patch a9f042c titled:

	ath9k: fix lockdep warning when unloading module

This went in to 2.6.34 and although it was not marked as a stable
fix it did get trickled down and applied on both 2.6.33 and 2.6.32.

In review, the culprits:

	mac80211: allow station add/remove to sleep
git describe --contains 34e895075e21be3e21e71d6317440d1ee7969ad0
v2.6.34-rc1~233^2~49^2~107

	ath9k: convert to new station add/remove callbacks
git describe --contains 4ca778605cfec53d8a689f0b57babb93b030c784
v2.6.34-rc1~233^2~49^2~10

	ath9k: fix lockdep warning when unloading module

This last one trickled down to 2.6.33 (OK), 2.6.33 (invalid) and 2.6.32 (invalid).

git describe --contains a9f042cbe5284f34ccff15f3084477e11b39b17b
v2.6.34-rc2~48^2~77^2~7
git describe --contains 0524bcfa80f1fffb4e1fe18a0a28900869a58a7c
v2.6.33.2~125
git describe --contains 0dcc9985f34aef3c60bffab3dfc7f7ba3748f35a
v2.6.32.11~79

The patch titled "ath9k: fix lockdep warning when unloading module"
should be reverted on both 2.6.33 and 2.6.32 as it is invalid and
actually ended up causing the following warning:

ADDRCONF(NETDEV_CHANGE): wlan31: link becomes ready
phy0: WMM queue=2 aci=0 acm=0 aifs=3 cWmin=15 cWmax=1023 txop=0
phy0: WMM queue=3 aci=1 acm=0 aifs=7 cWmin=15 cWmax=1023 txop=0
phy0: WMM queue=1 aci=2 acm=0 aifs=2 cWmin=7 cWmax=15 txop=94
phy0: WMM queue=0 aci=3 acm=0 aifs=2 cWmin=3 cWmax=7 txop=47
phy0: device now idle
------------[ cut here ]------------
WARNING: at kernel/softirq.c:143 local_bh_enable_ip+0x7b/0xa0()
Hardware name: 7660A14
Modules linked in: ath9k(-) mac80211 ath cfg80211 
Pid: 2003, comm: rmmod Not tainted 2.6.32.11 #6
Call Trace:
 [] warn_slowpath_common+0x78/0xb0
 [] warn_slowpath_null+0xf/0x20
 [] local_bh_enable_ip+0x7b/0xa0
 [] _spin_unlock_bh+0x14/0x20
 [] ath_tx_node_cleanup+0x185/0x1b0 [ath9k]
 [] ath9k_sta_notify+0x57/0xb0 [ath9k]
 [] __sta_info_unlink+0x15a/0x260 [mac80211]
 [] sta_info_unlink+0x38/0x60 [mac80211]
 [] ieee80211_set_disassoc+0x1ae/0x210 [mac80211]
 [] ieee80211_mgd_deauth+0x109/0x110 [mac80211]
 [] ieee80211_deauth+0x19/0x20 [mac80211]
 [] __cfg80211_mlme_deauth+0xee/0x130 [cfg80211]
 [] ? init_object+0x50/0x90
 [] __cfg80211_disconnect+0x159/0x1d0 [cfg80211]
 [] cfg80211_netdev_notifier_call+0x10f/0x450 [cfg80211]
 [] notifier_call_chain+0x47/0x90
 [] raw_notifier_call_chain+0x11/0x20
 [] call_netdevice_notifiers+0x16/0x20
 [] dev_close+0x4d/0xa0
 [] rollback_registered+0x48/0x120
 [] unregister_netdevice+0x1d/0x70
 [] ieee80211_remove_interfaces+0x84/0xc0 [mac80211]
 [] ieee80211_unregister_hw+0x42/0xf0 [mac80211]
 [] ath_detach+0x8e/0x180 [ath9k]
 [] ath_cleanup+0x11/0x50 [ath9k]
 [] ath_pci_remove+0x1c/0x20 [ath9k]
 [] pci_device_remove+0x32/0x60
 [] __device_release_driver+0x53/0xb0
 [] driver_detach+0xc8/0xd0
 [] bus_remove_driver+0x85/0xe0
 [] driver_unregister+0x5a/0x90
 [] pci_unregister_driver+0x40/0xb0
 [] ath_pci_exit+0x10/0x20 [ath9k]
 [] ath9k_exit+0x9/0x2a [ath9k]
 [] sys_delete_module+0x1a8/0x270
 [] ? up_read+0x9/0x10
 [] system_call_fastpath+0x16/0x1b
---[ end trace fad957019ffdd40b ]---
phy0: Removed STA 00:22:6b:56:fd:e8
phy0: Destroyed STA 00:22:6b:56:fd:e8
wlan31: deauthenticating from 00:22:6b:56:fd:e8 by local choice (reason=3)
ath9k 0000:16:00.0: PCI INT A disabled

The original lockdep fixed an issue where due to the new changes
the driver was not disabling the bottom halves but it is incorrect
to do this on the older kernels since IRQs are already disabled.

Cc: Ming Lei 
Cc: Johannes Berg 
Cc: John W. Linville 
Signed-off-by: Luis R. Rodriguez 
Signed-off-by: Greg Kroah-Hartman

nilfs2: fix sync silent failure

2010-05-26T21:32:12+00:00

commit 973bec34bfc1bc2465646181653d67f767d418c8 upstream.

As of 32a88aa1, __sync_filesystem() will return 0 if s_bdi is not set.
And nilfs does not set s_bdi anywhere.  I noticed this problem by the
warning introduced by the recent commit 5129a469 ("Catch filesystem
lacking s_bdi").

 WARNING: at fs/super.c:959 vfs_kern_mount+0xc5/0x14e()
 Hardware name: PowerEdge 2850
 Modules linked in: nilfs2 loop tpm_tis tpm tpm_bios video shpchp pci_hotplug output dcdbas
 Pid: 3773, comm: mount.nilfs2 Not tainted 2.6.34-rc6-debug #38
 Call Trace:
  [] warn_slowpath_common+0x60/0x90
  [] warn_slowpath_null+0xd/0x10
  [] vfs_kern_mount+0xc5/0x14e
  [] do_kern_mount+0x32/0xbd
  [] do_mount+0x671/0x6d0
  [] ? __get_free_pages+0x1f/0x21
  [] ? copy_mount_options+0x2b/0xe2
  [] ? strndup_user+0x48/0x67
  [] sys_mount+0x61/0x8f
  [] sysenter_do_call+0x12/0x32

This ensures to set s_bdi for nilfs and fixes the sync silent failure.

Signed-off-by: Ryusuke Konishi 
Acked-by: Jens Axboe 
Signed-off-by: Linus Torvalds 
Signed-off-by: Greg Kroah-Hartman

mmap_min_addr check CAP_SYS_RAWIO only for write

2010-05-26T21:32:11+00:00

commit 4ae69e6b718589abe97c9625ccbb1e0bc95a8c0e upstream.

Redirecting directly to lsm, here's the patch discussed on lkml:
http://lkml.org/lkml/2010/4/22/219

The mmap_min_addr value is useful information for an admin to see without
being root ("is my system vulnerable to kernel NULL pointer attacks?") and
its setting is trivially easy for an attacker to determine by calling
mmap() in PAGE_SIZE increments starting at 0, so trying to keep it private
has no value.

Only require CAP_SYS_RAWIO if changing the value, not reading it.

Comment from Serge :

  Me, I like to write my passwords with light blue pen on dark blue
  paper, pasted on my window - if you're going to get my password, you're
  gonna get a headache.

Signed-off-by: Kees Cook 
Acked-by: Serge Hallyn 
Signed-off-by: James Morris 
(cherry picked from commit 822cceec7248013821d655545ea45d1c6a9d15b3)
Signed-off-by: Greg Kroah-Hartman

CacheFiles: Fix error handling in cachefiles_determine_cache_security()

2010-05-26T21:32:11+00:00

commit 7ac512aa8237c43331ffaf77a4fd8b8d684819ba upstream.

cachefiles_determine_cache_security() is expected to return with a
security override in place.  However, if set_create_files_as() fails, we
fail to do this.  In this case, we should just reinstate the security
override that was set by the caller.

Furthermore, if set_create_files_as() fails, we should dispose of the
new credentials we were in the process of creating.

Signed-off-by: David Howells 
Signed-off-by: Linus Torvalds 
Signed-off-by: Greg Kroah-Hartman

iwlwifi: clear all the stop_queue flag after load firmware

2010-05-26T21:32:11+00:00

commit a9e10fb9b1c6ad16e73cf2656951fce3a817611e upstream.

All the queues are awake and ready to use after loading firmware,
for firmware reload case, if any queues was stopped before
reload, mac80211 will wake those queues after restart hardware, so make
sure all the flag used to keep track of the queue status are
reset correctly.

Signed-off-by: Wey-Yi Guy 
Signed-off-by: Reinette Chatre 
Signed-off-by: Greg Kroah-Hartman

iwlwifi: check for aggregation frame and queue

2010-05-26T21:32:11+00:00

commit 45d427001b5eec03cecaacddb53c73af46bb263e upstream.

Error checking for aggregation frames should go into aggregation queue,
if aggregation queue not available, use legacy queue instead.
Also make sure the aggregation queue is available to activate,
if driver and mac80211 is out-of-sync, try to disable the queue and
sync-up with mac80211.

Signed-off-by: Wey-Yi Guy 
Signed-off-by: Reinette Chatre 
Signed-off-by: Greg Kroah-Hartman

drm/i915: Disable FBC on 915GM and 945GM.

2010-05-26T21:32:10+00:00

commit 8d06a1e1e9c69244f08beb7d17146483f9dcd120 upstream.

It is causing hangs after a suspend/resume cycle with the default
powersave=1 module option on these chipsets since 2.6.32-rc.

BugLink: http://bugs.launchpad.net/bugs/492392
Signed-off-by: Robert Hooker 
Acked-by: Jesse Barnes 
Signed-off-by: Eric Anholt 
Signed-off-by: Greg Kroah-Hartman

ALSA: hda - New Intel HDA controller

2010-05-26T21:32:10+00:00

commit c602c8ad45d6ee6ad91fc544513cc96f70790983 upstream.

Added a PCI controller id on new Dell laptops.

Signed-off-by: Vitaliy Kulikov 
Cc: AmenophisIII 
Signed-off-by: Takashi Iwai 
Signed-off-by: Greg Kroah-Hartman