2.6.37.6-stable review
Subsystems (37)
cover 2.6.37.6-stable review
This is the start of the stable review cycle for the 2.6.37.6 release.
Note, this is the LAST 2.6.37 kernel release, after this one it is "end-of-life" or whatever your favorite term is for "not being updated anymore and you shouldn't be using it unless someone else is in charge of maintaining it for you."
There are 55 patches in this series, all will be posted as a response to this one. If anyone has any issues with these being applied, please let us know. If anyone is a maintainer of the proper subsystem, and wants to add a Signed-off-by: line to the patch, please respond with it.
Responses should be made by @date (day, month date, time)@ UTC. Anything received after that time might be too late.
The whole patch series can be found in one patch at:
kernel.org/pub/linux/kernel/v2.6/stable-review/patch-2.6.27.19-rc1.gz
and the diffstat can be found below.
thanks,
greg k-h
Makefile | 2 +- arch/sh/kernel/ptrace_32.c | 8 ++ arch/sh/kernel/ptrace_64.c | 6 + arch/x86/include/asm/msr-index.h | 5 + arch/x86/kernel/head64.c | 3 - arch/x86/kernel/setup.c | 5 + arch/x86/mm/init.c | 19 ---- arch/x86/mm/init_64.c | 11 +- arch/x86/xen/mmu.c | 13 ++- drivers/firmware/dcdbas.c | 4 +- drivers/gpu/drm/drm_crtc.c | 51 +++++++++ drivers/gpu/drm/drm_gem.c | 5 +- drivers/gpu/drm/i915/i915_gem.c | 6 +- drivers/gpu/drm/radeon/atombios_crtc.c | 6 +- drivers/gpu/drm/radeon/radeon_combios.c | 21 +++- drivers/gpu/drm/radeon/radeon_connectors.c | 30 +++++- drivers/gpu/drm/radeon/radeon_mode.h | 1 + drivers/idle/intel_idle.c | 24 +++++ drivers/input/xen-kbdfront.c | 45 +++++---- drivers/media/video/uvc/uvc_driver.c | 8 ++ drivers/media/video/uvc/uvc_video.c | 14 ++- drivers/pci/hotplug/acpiphp_glue.c | 1 + drivers/usb/class/cdc-acm.c | 7 +- drivers/usb/class/cdc-wdm.c | 2 +- drivers/usb/core/devio.c | 2 +- drivers/usb/host/ehci-q.c | 12 -- drivers/usb/misc/uss720.c | 7 +- drivers/video/console/tileblit.c | 2 +- fs/aio.c | 4 +- fs/dcache.c | 3 + fs/ext3/super.c | 7 ++ fs/ext4/super.c | 8 ++ fs/nfs/write.c | 31 ++++-- fs/nfsd/nfs4proc.c | 4 +- fs/nfsd/nfs4state.c | 155 +++++++++++++++------------- fs/nfsd/nfs4xdr.c | 5 +- fs/proc/array.c | 4 +- fs/proc/task_mmu.c | 4 +- fs/super.c | 2 + fs/sync.c | 4 +- include/linux/ethtool.h | 34 ++++++ kernel/cgroup.c | 14 +-- kernel/perf_event.c | 13 ++- kernel/signal.c | 16 ++- kernel/sysctl.c | 18 +++- mm/backing-dev.c | 2 +- mm/oom_kill.c | 50 ++++++---- mm/shmem.c | 1 + mm/slab.c | 8 +- mm/swapfile.c | 7 +- net/socket.c | 114 +++++++++++++++++++-- net/sunrpc/xprtsock.c | 2 + sound/pci/hda/patch_sigmatel.c | 18 +++ sound/pci/hda/patch_via.c | 53 ++++++++-- 54 files changed, 646 insertions(+), 255 deletions(-)
PATCH 1/55 ALSA: hda - VIA: Fix stereo mixer recording no sound issue
2.6.37-stable review patch. If anyone has any objections, please let us know.
------------------
From: Lydia Wang <[email protected]>
commit bff5fbf50bd498c217994bd2d41a53ac3141185a upstream.
Modify function via_mux_enum_put() to fix stereo mixer recording no sound issue.
--- sound/pci/hda/patch_via.c | 9 ++++++--- 1 file changed, 6 insertions(+), 3 deletions(-)
sound/pci/hda/patch_via.c +6 -3
@@ -1102,6 +1102,7 @@ static int via_mux_enum_put(struct snd_kstruct hda_codec *codec =snd_kcontrol_chip (kcontrol);struct via_spec *spec = codec->spec;unsigned int adc_idx =snd_ctl_get_ioffidx (kcontrol, &ucontrol->id); +int ret;if (!spec->mux_nids[adc_idx])return -EINVAL ;
@@ -1110,12 +1111,14 @@ static int via_mux_enum_put(struct snd_k AC_VERB_GET_POWER_STATE, 0x00) != AC_PWRST_D0)snd_hda_codec_write (codec, spec->mux_nids[adc_idx],0 ,AC_VERB_SET_POWER_STATE ,AC_PWRST_D0 ); -/* update jack power state */ -set_jack_power_state (codec); -return snd_hda_input_mux_put (codec, spec->input_mux, ucontrol, + ret =snd_hda_input_mux_put (codec, spec->input_mux, ucontrol, spec->mux_nids[adc_idx], &spec->cur_mux[adc_idx]); +/* update jack power state */ +set_jack_power_state (codec); + +return ret; } static int via_independent_hp_info(struct snd_kcontrol *kcontrol,
PATCH 2/55 ALSA: hda - VIA: Fix independent headphone no sound issue
In reply to Greg KH2.6.37-stable review patch. If anyone has any objections, please let us know.
------------------
From: Lydia Wang <[email protected]>
commit ce0e5a9e81fbb153ee15ca60246c6722f07fc546 upstream.
Modify via_independent_hp_put() function to support VT1718S and VT1812 codecs, and fix independent headphone no sound issue.
--- sound/pci/hda/patch_via.c | 12 +++++++++++- 1 file changed, 11 insertions(+), 1 deletion(-)
sound/pci/hda/patch_via.c +11 -1
@@ -1192,8 +1192,16 @@ static int via_independent_hp_put(struct/* Get Independent Mode index of headphone pin widget */ spec->hp_independent_mode = spec->hp_independent_mode_index == pinsel ?1 :0 ; -snd_hda_codec_write (codec, nid,0 ,AC_VERB_SET_CONNECT_SEL , pinsel); +if (spec->codec_type ==VT1718S ) +snd_hda_codec_write (codec, nid,0 , +AC_VERB_SET_CONNECT_SEL , pinsel ?2 :0 ); +else +snd_hda_codec_write (codec, nid,0 , +AC_VERB_SET_CONNECT_SEL , pinsel); +if (spec->codec_type ==VT1812 ) +snd_hda_codec_write (codec,0x35 ,0 , +AC_VERB_SET_CONNECT_SEL , pinsel);if (spec->multiout.hp_nid && spec->multiout.hp_nid != spec->multiout.dac_nids[HDA_FRONT ]) snd_hda_codec_setup_stream(codec, spec->multiout.hp_nid,
@@ -1212,6 +1220,8 @@ static int via_independent_hp_put(structactivate_ctl (codec,"Headphone Playback Switch" , spec->hp_independent_mode); } +/* update jack power state */ +set_jack_power_state (codec);return 0 ; }
PATCH 3/55 ALSA: hda - VIA: Add missing support for VT1718S in A-A path
In reply to Greg KH2.6.37-stable review patch. If anyone has any objections, please let us know.
------------------
From: Lydia Wang <[email protected]>
commit ab657e0cacc39d88145871c6a3c844597c02d406 upstream.
Modify mute_aa_path() function to support VT1718S codec.
--- sound/pci/hda/patch_via.c | 5 +++++ 1 file changed, 5 insertions(+)
sound/pci/hda/patch_via.c +5 -0
@@ -1324,6 +1324,11 @@ static void mute_aa_path(struct hda_code start_idx =2 ; end_idx =4 ;break ; +case VT1718S : + nid_mixer =0x21 ; + start_idx =1 ; + end_idx =3 ; +break ;default :return ; }
PATCH 4/55 ALSA: hda - VIA: Fix invalid A-A path volume adjust issue
In reply to Greg KH2.6.37-stable review patch. If anyone has any objections, please let us know.
------------------
From: Lydia Wang <[email protected]>
commit 169222813eec8403c76394fb7b35ecab98e3c607 upstream.
Modify vt_auto_create_analog_input_ctls() function to fix invalid a-a path volume adjust issue for VT1708S, VT1702 and VT1716S codecs.
--- sound/pci/hda/patch_via.c | 9 ++++++++- 1 file changed, 8 insertions(+), 1 deletion(-)
sound/pci/hda/patch_via.c +8 -1
@@ -2455,7 +2455,14 @@ static int vt_auto_create_analog_input_celse type_idx =0 ; label =hda_get_autocfg_input_label (codec, cfg, i); - err =via_new_analog_input (spec, label, type_idx, idx, cap_nid); +if (spec->codec_type ==VT1708S || + spec->codec_type ==VT1702 || + spec->codec_type ==VT1716S ) + err =via_new_analog_input (spec, label, type_idx, + idx+1 , cap_nid); +else + err =via_new_analog_input (spec, label, type_idx, + idx, cap_nid);if (err <0 )return err;snd_hda_add_imux_item (imux, label, idx,NULL );
PATCH 5/55 ALSA: hda - VIA: Fix codec type for VT1708BCE at the right timing
In reply to Greg KH2.6.37-stable review patch. If anyone has any objections, please let us know.
------------------
From: Lydia Wang <[email protected]>
commit 0341ccd7557fecafe6a79c55158670cf629d269e upstream.
Add get_codec_type() in via_new_spec() function to make sure getting correct codec type before building mixer controls.
--- sound/pci/hda/patch_via.c | 9 +++++---- 1 file changed, 5 insertions(+), 4 deletions(-)
sound/pci/hda/patch_via.c +5 -4
@@ -159,6 +159,7 @@ struct via_spec {#endif }; +static enum VIA_HDA_CODEC get_codec_type (struct hda_codec *codec);static struct via_spec *via_new_spec (struct hda_codec *codec) {struct via_spec *spec;
@@ -169,6 +170,10 @@ static struct via_spec * via_new_spec(st codec->spec = spec; spec->codec = codec; + spec->codec_type =get_codec_type (codec); +/* VT1708BCE & VT1708S are almost same */ +if (spec->codec_type ==VT1708BCE ) + spec->codec_type =VT1708S ;return spec; }
@@ -2204,10 +2209,6 @@ static int via_init(struct hda_codec *cofor (i =0 ; i < spec->num_iverbs; i++)snd_hda_sequence_write (codec, spec->init_verbs[i]); - spec->codec_type =get_codec_type (codec); -if (spec->codec_type ==VT1708BCE ) - spec->codec_type =VT1708S ;/* VT1708BCE & VT1708S are almost -same */ /* Lydia Add for EAPD enable */ if (!spec->dig_in_nid) {/* No Digital In connection */ if (spec->dig_in_pin) {
PATCH 6/55 ALSA: hda - VIA: Fix VT1708 cant build up Headphone control issue
In reply to Greg KH2.6.37-stable review patch. If anyone has any objections, please let us know.
------------------
From: Lydia Wang <[email protected]>
commit ee3c35c0827de02de414d08b2ddcbb910c2263ab upstream.
Since VT1708 didn't support the control of getting connection number, building of headphone control will fail in via_hp_build() function.
--- sound/pci/hda/patch_via.c | 9 ++++++--- 1 file changed, 6 insertions(+), 3 deletions(-)
sound/pci/hda/patch_via.c +6 -3
@@ -1267,9 +1267,12 @@ static int via_hp_build(struct hda_codecbreak ; } - nums =snd_hda_get_connections (codec, nid, conn,HDA_MAX_CONNECTIONS ); -if (nums <=1 ) -return 0 ; +if (spec->codec_type !=VT1708 ) { + nums =snd_hda_get_connections (codec, nid, + conn,HDA_MAX_CONNECTIONS ); +if (nums <=1 ) +return 0 ; + } knew =via_clone_control (spec, &via_hp_mixer[0 ]);if (knew ==NULL )
PATCH 7/55 ethtool: Compat handling for struct ethtool_rxnfc
In reply to Greg KH2.6.37-stable review patch. If anyone has any objections, please let us know.
------------------
From: Ben Hutchings <[email protected]>
commit 3a7da39d165e0c363c294feec119db1427032afd upstream.
This structure was accidentally defined such that its layout can differ between 32-bit and 64-bit processes. Add compat structure definitions and an ioctl wrapper function.
--- include/linux/ethtool.h | 34 ++++++++++++++ net/socket.c | 114 +++++++++++++++++++++++++++++++++++++++++++++--- 2 files changed, 141 insertions(+), 7 deletions(-)
include/linux/ethtool.h +34 -0
@@ -13,6 +13,9 @@#ifndef _LINUX_ETHTOOL_H#define _LINUX_ETHTOOL_H +#ifdef __KERNEL__ +#include <linux/compat.h> +#endif #include <linux/types.h> #include <linux/if_ether.h>
@@ -449,6 +452,37 @@ struct ethtool_rxnfc {__u32 rule_locs[0 ]; }; +#ifdef __KERNEL__ +#ifdef CONFIG_COMPAT + +struct compat_ethtool_rx_flow_spec { +u32 flow_type; +union { +struct ethtool_tcpip4_spec tcp_ip4_spec; +struct ethtool_tcpip4_spec udp_ip4_spec; +struct ethtool_tcpip4_spec sctp_ip4_spec; +struct ethtool_ah_espip4_spec ah_ip4_spec; +struct ethtool_ah_espip4_spec esp_ip4_spec; +struct ethtool_usrip4_spec usr_ip4_spec; +struct ethhdr ether_spec; +u8 hdata[72 ]; + } h_u, m_u; +compat_u64 ring_cookie; +u32 location; +}; + +struct compat_ethtool_rxnfc { +u32 cmd; +u32 flow_type; +compat_u64 data; +struct compat_ethtool_rx_flow_spec fs; +u32 rule_cnt; +u32 rule_locs[0 ]; +}; + +#endif /* CONFIG_COMPAT */ +#endif /* __KERNEL__ */ +/** * struct ethtool_rxfh_indir - command to get or set RX flow hash indirection * @cmd: Specific command number - %ETHTOOL_GRXFHINDIR or %ETHTOOL_SRXFHINDIR
net/socket.c +107 -7
130 lines not on this page · raw message
PATCH 8/55 Revert "slab: Fix missing DEBUG_SLAB last user"
In reply to Greg KH2.6.37-stable review patch. If anyone has any objections, please let us know.
------------------
From: Pekka Enberg <[email protected]>
commit 3ff84a7f36554b257cd57325b1a7c1fa4b49fbe3 upstream.
This reverts commit 5c5e3b33b7cb959a401f823707bee006caadd76e.
The commit breaks ARM thusly:
| Mount-cache hash table entries: 512 | slab error in verify_redzone_free(): cache `idr_layer_cache': memory outside object was overwritten | Backtrace: | [<c0227088>] (dump_backtrace+0x0/0x110) from [<c0431afc>] (dump_stack+0x18/0x1c) | [<c0431ae4>] (dump_stack+0x0/0x1c) from [<c0293304>] (__slab_error+0x28/0x30) | [<c02932dc>] (__slab_error+0x0/0x30) from [<c0293a74>] (cache_free_debugcheck+0x1c0/0x2b8) | [<c02938b4>] (cache_free_debugcheck+0x0/0x2b8) from [<c0293f78>] (kmem_cache_free+0x3c/0xc0) | [<c0293f3c>] (kmem_cache_free+0x0/0xc0) from [<c032b1c8>] (ida_get_new_above+0x19c/0x1c0) | [<c032b02c>] (ida_get_new_above+0x0/0x1c0) from [<c02af7ec>] (alloc_vfsmnt+0x54/0x144) | [<c02af798>] (alloc_vfsmnt+0x0/0x144) from [<c0299830>] (vfs_kern_mount+0x30/0xec) | [<c0299800>] (vfs_kern_mount+0x0/0xec) from [<c0299908>] (kern_mount_data+0x1c/0x20) | [<c02998ec>] (kern_mount_data+0x0/0x20) from [<c02146c4>] (sysfs_init+0x68/0xc8) | [<c021465c>] (sysfs_init+0x0/0xc8) from [<c02137d4>] (mnt_init+0x90/0x1b0) | [<c0213744>] (mnt_init+0x0/0x1b0) from [<c0213388>] (vfs_caches_init+0x100/0x140) | [<c0213288>] (vfs_caches_init+0x0/0x140) from [<c0208c0c>] (start_kernel+0x2e8/0x368) | [<c0208924>] (start_kernel+0x0/0x368) from [<c0208034>] (__enable_mmu+0x0/0x2c) | c0113268: redzone 1:0xd84156c5c032b3ac, redzone 2:0xd84156c5635688c0. | slab error in cache_alloc_debugcheck_after(): cache `idr_layer_cache': double free, or memory outside object was overwritten | ... | c011307c: redzone 1:0x9f91102ffffffff, redzone 2:0x9f911029d74e35b | slab: Internal list corruption detected in cache 'idr_layer_cache'(24), slabp c0113000(16). Hexdump: | | 000: 20 4f 10 c0 20 4f 10 c0 7c 00 00 00 7c 30 11 c0 | 010: 10 00 00 00 10 00 00 00 00 00 c9 17 fe ff ff ff | 020: fe ff ff ff fe ff ff ff fe ff ff ff fe ff ff ff | 030: fe ff ff ff fe ff ff ff fe ff ff ff fe ff ff ff | 040: fe ff ff ff fe ff ff ff fe ff ff ff fe ff ff ff | 050: fe ff ff ff fe ff ff ff fe ff ff ff 11 00 00 00 | 060: 12 00 00 00 13 00 00 00 14 00 00 00 15 00 00 00 | 070: 16 00 00 00 17 00 00 00 c0 88 56 63 | kernel BUG at /home/rmk/git/linux-2.6-rmk/mm/slab.c:2928!
Reference: https://lkml.org/lkml/2011/2/7/238
--- mm/slab.c | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-)
mm/slab.c +4 -4
@@ -2288,8 +2288,8 @@ kmem_cache_create (const char *name, sizif (ralign < align) { ralign = align; } -/* disable debug if not aligning with REDZONE_ALIGN */ -if (ralign & (__alignof__(unsigned long long ) -1 )) +/* disable debug if necessary */ +if (ralign > __alignof__(unsigned long long )) flags &= ~(SLAB_RED_ZONE |SLAB_STORE_USER );/* * 4) Store it.
@@ -2315,8 +2315,8 @@ kmem_cache_create (const char *name, siz*/ if (flags &SLAB_RED_ZONE ) {/* add space for red zone words */ - cachep->obj_offset += align; - size += align +sizeof (unsigned long long ); + cachep->obj_offset +=sizeof (unsigned long long ); + size +=2 *sizeof (unsigned long long ); }if (flags &SLAB_STORE_USER ) {/* user store requires one word storage behind the end of
PATCH 9/55 aio: wake all waiters when destroying ctx
In reply to Greg KH2.6.37-stable review patch. If anyone has any objections, please let us know.
------------------
From: Roland Dreier <[email protected]>
commit e91f90bb0bb10be9cc8efd09a3cf4ecffcad0db1 upstream.
The test program below will hang because io_getevents() uses add_wait_queue_exclusive(), which means the wake_up() in io_destroy() only wakes up one of the threads. Fix this by using wake_up_all() in the aio code paths where we want to make sure no one gets stuck.
// t.c -- compile with gcc -lpthread -laio t.c
#include <libaio.h>
#include <pthread.h>
#include <stdio.h>
#include <unistd.h>
static const int nthr = 2;
void *getev(void *ctx)
{
struct io_event ev;
io_getevents(ctx, 1, 1, &ev, NULL);
printf("io_getevents returned\n");
return NULL;
}
int main(int argc, char *argv[])
{
io_context_t ctx = 0;
pthread_t thread[nthr];
int i;
io_setup(1024, &ctx);
for (i = 0; i < nthr; ++i)
pthread_create(&thread[i], NULL, getev, ctx);
sleep(1);
io_destroy(ctx);
for (i = 0; i < nthr; ++i)
pthread_join(thread[i], NULL);
return 0;
}--- fs/aio.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)
fs/aio.c +2 -2
@@ -512,7 +512,7 @@ static inline void really_put_req(struct ctx->reqs_active--;if (unlikely (!ctx->reqs_active && ctx->dead)) -wake_up (&ctx->wait); +wake_up_all (&ctx->wait); }static void aio_fput_routine (struct work_struct *data)
@@ -1233,7 +1233,7 @@ static void io_destroy(struct kioctx *io* by other CPUs at this point. Right now, we rely on the * locking done by the above calls to ensure this consistency. */ -wake_up (&ioctx->wait); +wake_up_all (&ioctx->wait);put_ioctx (ioctx);/* once for the lookup */ }
PATCH 10/55 cgroups: if you list_empty() a head then dont list_del() it
In reply to Greg KH2.6.37-stable review patch. If anyone has any objections, please let us know.
------------------
From: Phil Carmody <[email protected]>
commit 8d2587970b8bdf7c8d9208e3f4bb93182aef1a0f upstream.
list_del() leaves poison in the prev and next pointers. The next list_empty() will compare those poisons, and say the list isn't empty. Any list operations that assume the node is on a list because of such a check will be fooled into dereferencing poison. One needs to INIT the node after the del, and fortunately there's already a wrapper for that - list_del_init().
Some of the dels are followed by deallocations, so can be ignored, and one can be merged with an add to make a move. Apart from that, I erred on the side of caution in making nodes list_empty()-queriable.
--- kernel/cgroup.c | 14 ++++++-------- 1 file changed, 6 insertions(+), 8 deletions(-)
kernel/cgroup.c +6 -8
@@ -1791,10 +1791,8 @@ int cgroup_attach_task(struct cgroup *cg/* Update the css_set linked lists if we're using them */ write_lock (&css_set_lock); -if (!list_empty (&tsk->cg_list)) { -list_del (&tsk->cg_list); -list_add (&tsk->cg_list, &newcg->tasks); - } +if (!list_empty (&tsk->cg_list)) +list_move (&tsk->cg_list, &newcg->tasks);write_unlock (&css_set_lock);for_each_subsys (root, ss) {
@@ -3630,12 +3628,12 @@ again:spin_lock (&release_list_lock);set_bit (CGRP_REMOVED , &cgrp->flags);if (!list_empty (&cgrp->release_list)) -list_del (&cgrp->release_list); +list_del_init (&cgrp->release_list);spin_unlock (&release_list_lock);cgroup_lock_hierarchy (cgrp->root);/* delete this cgroup from parent->children */ -list_del (&cgrp->sibling); +list_del_init (&cgrp->sibling);cgroup_unlock_hierarchy (cgrp->root);spin_lock (&cgrp->dentry->d_lock);
@@ -3856,7 +3854,7 @@ void cgroup_unload_subsys(struct cgroup_ subsys[ss->subsys_id] =NULL ;/* remove subsystem from rootnode's list of subsystems */ -list_del (&ss->sibling); +list_del_init (&ss->sibling);/* * disentangle the css from all css_sets attached to the dummytop. as
@@ -4230,7 +4228,7 @@ void cgroup_exit(struct task_struct *tskif (!list_empty (&tsk->cg_list)) {write_lock (&css_set_lock);if (!list_empty (&tsk->cg_list)) -list_del (&tsk->cg_list); +list_del_init (&tsk->cg_list);write_unlock (&css_set_lock); }
PATCH 11/55 shmem: let shared anonymous be nonlinear again
In reply to Greg KH2.6.37-stable review patch. If anyone has any objections, please let us know.
------------------
From: Hugh Dickins <[email protected]>
commit bee4c36a5cf5c9f63ce1d7372aa62045fbd16d47 upstream.
Up to 2.6.22, you could use remap_file_pages(2) on a tmpfs file or a shared mapping of /dev/zero or a shared anonymous mapping. In 2.6.23 we disabled it by default, but set VM_CAN_NONLINEAR to enable it on safe mappings. We made sure to set it in shmem_mmap() for tmpfs files, but missed it in shmem_zero_setup() for the others. Fix that at last.
--- mm/shmem.c | 1 + 1 file changed, 1 insertion(+)
mm/shmem.c +1 -0
@@ -2784,5 +2784,6 @@ int shmem_zero_setup(struct vm_area_strufput (vma->vm_file); vma->vm_file = file; vma->vm_ops = &shmem_vm_ops; + vma->vm_flags |=VM_CAN_NONLINEAR ;return 0 ; }
PATCH 12/55 mm: swap: unlock swapfile inode mutex before closing file on bad swapfiles
In reply to Greg KH2.6.37-stable review patch. If anyone has any objections, please let us know.
------------------
From: Mel Gorman <[email protected]>
commit 52c50567d8ab0a0a87f12cceaa4194967854f0bd upstream.
If an administrator tries to swapon a file backed by NFS, the inode mutex is taken (as it is for any swapfile) but later identified to be a bad swapfile due to the lack of bmap and tries to cleanup. During cleanup, an attempt is made to close the file but with inode->i_mutex still held. Closing an NFS file syncs it which tries to acquire the inode mutex leading to deadlock. If lockdep is enabled the following appears on the console;
=============================================
[ INFO: possible recursive locking detected ]
2.6.38-rc8-autobuild #1
---------------------------------------------
swapon/2192 is trying to acquire lock:
(&sb->s_type->i_mutex_key#13){+.+.+.}, at: vfs_fsync_range+0x47/0x7c
but task is already holding lock:
(&sb->s_type->i_mutex_key#13){+.+.+.}, at: sys_swapon+0x28d/0xae7
other info that might help us debug this:
1 lock held by swapon/2192:
#0: (&sb->s_type->i_mutex_key#13){+.+.+.}, at: sys_swapon+0x28d/0xae7
stack backtrace:
Pid: 2192, comm: swapon Not tainted 2.6.38-rc8-autobuild #1
Call Trace:
__lock_acquire+0x2eb/0x1623
find_get_pages_tag+0x14a/0x174
pagevec_lookup_tag+0x25/0x2e
vfs_fsync_range+0x47/0x7c
lock_acquire+0xd3/0x100
vfs_fsync_range+0x47/0x7c
nfs_flush_one+0x0/0xdf [nfs]
mutex_lock_nested+0x40/0x2b1
vfs_fsync_range+0x47/0x7c
vfs_fsync_range+0x47/0x7c
vfs_fsync+0x1c/0x1e
nfs_file_flush+0x64/0x69 [nfs]
filp_close+0x43/0x72
sys_swapon+0xa39/0xae7
sysret_check+0x2e/0x69
system_call_fastpath+0x16/0x1bThis patch releases the mutex if its held before calling filep_close() so swapon fails as expected without deadlock when the swapfile is backed by NFS. If accepted for 2.6.39, it should also be considered a -stable candidate for 2.6.38 and 2.6.37.
--- mm/swapfile.c | 7 ++++++- 1 file changed, 6 insertions(+), 1 deletion(-)
mm/swapfile.c +6 -1
@@ -2146,8 +2146,13 @@ bad_swap_2: p->flags =0 ;spin_unlock (&swap_lock);vfree (swap_map); -if (swap_file) +if (swap_file) { +if (did_down) { +mutex_unlock (&inode->i_mutex); + did_down =0 ; + }filp_close (swap_file,NULL ); + } out:if (page && !IS_ERR (page)) {kunmap (page);
PATCH 13/55 oom: prevent unnecessary oom kills or kernel panics
In reply to Greg KH2.6.37-stable review patch. If anyone has any objections, please let us know.
------------------
From: David Rientjes <[email protected]>
commit 3a5dda7a17cf3706f79b86293f29db02d61e0d48 upstream.
This patch prevents unnecessary oom kills or kernel panics by reverting two commits:
495789a5 (oom: make oom_score to per-process value) cef1d352 (oom: multi threaded process coredump don't make deadlock)
First, 495789a5 (oom: make oom_score to per-process value) ignores the fact that all threads in a thread group do not necessarily exit at the same time.
It is imperative that select_bad_process() detect threads that are in the exit path, specifically those with PF_EXITING set, to prevent needlessly killing additional tasks. If a process is oom killed and the thread group leader exits, select_bad_process() cannot detect the other threads that are PF_EXITING by iterating over only processes. Thus, it currently chooses another task unnecessarily for oom kill or panics the machine when nothing else is eligible.
By iterating over threads instead, it is possible to detect threads that are exiting and nominate them for oom kill so they get access to memory reserves.
Second, cef1d352 (oom: multi threaded process coredump don't make deadlock) erroneously avoids making the oom killer a no-op when an eligible thread other than current isfound to be exiting. We want to detect this situation so that we may allow that exiting thread time to exit and free its memory; if it is able to exit on its own, that should free memory so current is no loner oom. If it is not able to exit on its own, the oom killer will nominate it for oom kill which, in this case, only means it will get access to memory reserves.
Without this change, it is easy for the oom killer to unnecessarily target tasks when all threads of a victim don't exit before the thread group leader or, in the worst case, panic the machine.
--- mm/oom_kill.c | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-)
mm/oom_kill.c +4 -4
@@ -292,11 +292,11 @@ static struct task_struct *select_bad_pr unsigned long totalpages, struct mem_cgroup *mem, const nodemask_t *nodemask) { - struct task_struct *p; + struct task_struct *g, *p;struct task_struct *chosen =NULL ; *ppoints =0 ; -for_each_process (p) { + do_each_thread(g, p) {unsigned int points;if (oom_unkillable_task (p, mem, nodemask))
@@ -324,7 +324,7 @@ static struct task_struct *select_bad_pr* the process of exiting and releasing its resources. * Otherwise we could get an easy OOM deadlock. */ -if (thread_group_empty (p) && (p->flags &PF_EXITING ) && p->mm) { +if ((p->flags &PF_EXITING ) && p->mm) {if (p != current)return ERR_PTR (-1UL );
@@ -337,7 +337,7 @@ static struct task_struct *select_bad_pr chosen = p; *ppoints = points; } - } + }while_each_thread (g, p);return chosen; }
PATCH 14/55 oom: skip zombies when iterating tasklist
In reply to Greg KH2.6.37-stable review patch. If anyone has any objections, please let us know.
------------------
From: Andrey Vagin <[email protected]>
commit 30e2b41f20b6238f51e7cffb879c7a0f0073f5fe upstream.
We shouldn't defer oom killing if a thread has already detached its ->mm and still has TIF_MEMDIE set. Memory needs to be freed, so find kill other threads that pin the same ->mm or find another task to kill.
--- mm/oom_kill.c | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-)
mm/oom_kill.c +3 -1
@@ -299,6 +299,8 @@ static struct task_struct *select_bad_pr do_each_thread(g, p) {unsigned int points; +if (!p->mm) +continue ;if (oom_unkillable_task (p, mem, nodemask))continue ;
@@ -324,7 +326,7 @@ static struct task_struct *select_bad_pr* the process of exiting and releasing its resources. * Otherwise we could get an easy OOM deadlock. */ -if ((p->flags &PF_EXITING ) && p->mm) { +if (p->flags &PF_EXITING ) {if (p != current)return ERR_PTR (-1UL );
PATCH 15/55 oom: avoid deferring oom killer if exiting task is being traced
In reply to Greg KH2.6.37-stable review patch. If anyone has any objections, please let us know.
------------------
From: David Rientjes <[email protected]>
commit edd45544c6f09550df0a5491aa8a07af24767e73 upstream.
The oom killer naturally defers killing anything if it finds an eligible task that is already exiting and has yet to detach its ->mm. This avoids unnecessarily killing tasks when one is already in the exit path and may free enough memory that the oom killer is no longer needed. This is detected by PF_EXITING since threads that have already detached its ->mm are no longer considered at all.
The problem with always deferring when a thread is PF_EXITING, however, is that it may never actually exit when being traced, specifically if another task is tracing it with PTRACE_O_TRACEEXIT. The oom killer does not want to defer in this case since there is no guarantee that thread will ever exit without intervention.
This patch will now only defer the oom killer when a thread is PF_EXITING and no ptracer has stopped its progress in the exit path. It also ensures that a child is sacrificed for the chosen parent only if it has a different ->mm as the comment implies: this ensures that the thread group leader is always targeted appropriately.
--- mm/oom_kill.c | 40 +++++++++++++++++++++++++--------------- 1 file changed, 25 insertions(+), 15 deletions(-)
mm/oom_kill.c +25 -15
@@ -31,6 +31,7 @@#include <linux/memcontrol.h> #include <linux/mempolicy.h> #include <linux/security.h> +#include <linux/ptrace.h> int sysctl_panic_on_oom;int sysctl_oom_kill_allocating_task;
@@ -316,22 +317,29 @@ static struct task_struct *select_bad_prif (test_tsk_thread_flag (p,TIF_MEMDIE ))return ERR_PTR (-1UL ); -/* -* This is in the process of releasing memory so wait for it -* to finish before killing some other task by mistake. -* -* However, if p is the current task, we allow the 'kill' to -* go ahead if it is exiting: this will simply set TIF_MEMDIE, -* which will allow it to gain access to memory reserves in -* the process of exiting and releasing its resources. -* Otherwise we could get an easy OOM deadlock. -*/ if (p->flags &PF_EXITING ) { -if (p != current) -return ERR_PTR (-1UL ); - - chosen = p; - *ppoints =1000 ; +/* +* If p is the current task and is in the process of +* releasing memory, we allow the "kill" to set +* TIF_MEMDIE, which will allow it to gain access to +* memory reserves. Otherwise, it may stall forever. +* +* The loop isn't broken here, however, in case other +* threads are found to have already been oom killed. +*/ +if (p == current) { + chosen = p; + *ppoints =1000 ; + }else { +/* +* If this task is not being ptraced on exit, +* then wait for it to finish before killing +* some other task unnecessarily. +*/ +if (!(task_ptrace (p->group_leader) & +PT_TRACE_EXIT )) +return ERR_PTR (-1UL ); + } } points =oom_badness (p, mem, nodemask, totalpages);
@@ -493,6 +501,8 @@ static int oom_kill_process(struct task_list_for_each_entry (child, &t->children, sibling) {unsigned int child_points; +if (child->mm == p->mm) +continue ;/* * oom_badness() returns 0 if the thread is unkillable */
PATCH 16/55 PCI hotplug: acpiphp: set current_state to D0 in register_slot
In reply to Greg KH2.6.37-stable review patch. If anyone has any objections, please let us know.
------------------
From: Stefano Stabellini <[email protected]>
commit 47e9037ac16637cd7f12b8790ea7ce6680e42168 upstream.
If a device doesn't support power management (pm_cap == 0) but it is acpi_pci_power_manageable() because there is a _PS0 method declared for it and _EJ0 is also declared for the slot then nobody is going to set current_state = PCI_D0 for this device. This is what I think it is happening:
pci_enable_device
|
__pci_enable_device_flags
/* here we do not set current_state because !pm_cap */
|
do_pci_enable_device
|
pci_set_power_state
|
__pci_start_power_transition
|
pci_platform_power_transition
/* platform_pci_power_manageable() calls acpi_pci_power_manageable that
* returns true */
|platform_pci_set_power_state
/* acpi_pci_set_power_state gets called and does nothing because the
* acpi device has _EJ0, see the comment "If the ACPI device has _EJ0,
* ignore the device" */
at this point if we refer to the commit message that introduced the comment above (10b3dcae0f275e2546e55303d64ddbb58cec7599), it is up to the hotplug driver to set the state to D0.
However AFAICT the pci hotplug driver never does, in fact drivers/pci/hotplug/acpiphp_glue.c:register_slot sets the slot flags to (SLOT_ENABLED | SLOT_POWEREDON) but it does not set the pci device current state to PCI_D0.
So my proposed fix is also to set current_state = PCI_D0 in register_slot.
Comments are very welcome.
--- drivers/pci/hotplug/acpiphp_glue.c | 1 + 1 file changed, 1 insertion(+)
drivers/pci/hotplug/acpiphp_glue.c +1 -0
@@ -212,6 +212,7 @@ register_slot(acpi_handle handle, u32 lv pdev =pci_get_slot (pbus,PCI_DEVFN (device, function));if (pdev) { + pdev->current_state =PCI_D0 ; slot->flags |= (SLOT_ENABLED |SLOT_POWEREDON );pci_dev_put (pdev); }
PATCH 17/55 xen: set max_pfn_mapped to the last pfn mapped
In reply to Greg KH2.6.37-stable review patch. If anyone has any objections, please let us know.
------------------
From: Stefano Stabellini <[email protected]>
commit 14988a4d350ce3b41ecad4f63c4f44c56f5ae34d upstream.
Do not set max_pfn_mapped to the end of the initial memory mappings, that also contain pages that don't belong in pfn space (like the mfn list).
Set max_pfn_mapped to the last real pfn mapped in the initial memory mappings that is the pfn backing _end.
LKML-Reference: <alpine.DEB.2.00.1103171739050.3382@kaball-desktop>
--- arch/x86/xen/mmu.c | 13 +++++++------ 1 file changed, 7 insertions(+), 6 deletions(-)
arch/x86/xen/mmu.c +7 -6
@@ -2027,9 +2027,6 @@ static __init void xen_map_identity_earlfor (pteidx =0 ; pteidx <PTRS_PER_PTE ; pteidx++, pfn++) {pte_t pte; -if (pfn > max_pfn_mapped) - max_pfn_mapped = pfn; -if (!pte_none (pte_page[pteidx]))continue ;
@@ -2087,6 +2084,12 @@ __init pgd_t *xen_setup_kernel_pagetablepud_t *l3;pmd_t *l2; +/* max_pfn_mapped is the last pfn mapped in the initial memory +* mappings. Considering that on Xen after the kernel mappings we +* have the mappings of some pages that don't exist in pfn space, we +* set max_pfn_mapped to the last real pfn mapped. */ + max_pfn_mapped =PFN_DOWN (__pa (xen_start_info->mfn_list)); +/* Zap identity mapping */ init_level4_pgt[0 ] =__pgd (0 );
@@ -2191,9 +2194,7 @@ __init pgd_t *xen_setup_kernel_pagetable initial_kernel_pmd =extend_brk (sizeof (pmd_t) *PTRS_PER_PMD ,PAGE_SIZE ); - max_pfn_mapped =PFN_DOWN (__pa (xen_start_info->pt_base) + - xen_start_info->nr_pt_frames *PAGE_SIZE + -512 *1024 ); + max_pfn_mapped =PFN_DOWN (__pa (xen_start_info->mfn_list)); kernel_pmd =m2v (pgd[KERNEL_PGD_BOUNDARY ].pgd);memcpy (initial_kernel_pmd, kernel_pmd,sizeof (pmd_t) *PTRS_PER_PMD );
PATCH 18/55 intel_idle: disable NHM/WSM HW C-state auto-demotion
In reply to Greg KH2.6.37-stable review patch. If anyone has any objections, please let us know.
------------------
From: Len Brown <[email protected]>
commit 14796fca2bd22acc73dd0887248d003b0f441d08 upstream.
Hardware C-state auto-demotion is a mechanism where the HW overrides the OS C-state request, instead demoting to a shallower state, which is less expensive, but saves less power.
Modern Linux should generally get exactly the states it requests. In particular, when a CPU is taken off-line, it must not be demoted, else it can prevent the entire package from reaching deep C-states.
https://bugzilla.kernel.org/show_bug.cgi?id=25252
--- arch/x86/include/asm/msr-index.h | 4 ++++ drivers/idle/intel_idle.c | 20 ++++++++++++++++++++ 2 files changed, 24 insertions(+)
arch/x86/include/asm/msr-index.h +4 -0
@@ -36,6 +36,10 @@#define MSR_IA32_PERFCTR1 0x000000c2#define MSR_FSB_FREQ 0x000000cd +#define MSR_NHM_SNB_PKG_CST_CFG_CTL 0x000000e2 +#define NHM_C3_AUTO_DEMOTE (1UL << 25) +#define NHM_C1_AUTO_DEMOTE (1UL << 26) +#define MSR_MTRRcap 0x000000fe#define MSR_IA32_BBL_CR_CTL 0x00000119
drivers/idle/intel_idle.c +20 -0
@@ -62,6 +62,7 @@#include <linux/notifier.h> #include <linux/cpu.h> #include <asm/mwait.h> +#include <asm/msr.h> #define INTEL_IDLE_VERSION "0.4"#define PREFIX "intel_idle: "
@@ -85,6 +86,12 @@ static int intel_idle(struct cpuidle_devstatic struct cpuidle_state *cpuidle_state_table;/* +* Hardware C-state auto-demotion may not always be optimal. +* Indicate which enable bits to clear here. +*/ +static unsigned long long auto_demotion_disable_flags; + +/* * States are indexed by the cstate number, * which is also the index into the MWAIT hint array. * Thus C0 is a dummy.
@@ -276,6 +283,15 @@ static struct notifier_block setup_broad .notifier_call = setup_broadcast_cpuhp_notify, }; +static void auto_demotion_disable (void *dummy) +{ +unsigned long long msr_bits; + +rdmsrl (MSR_NHM_SNB_PKG_CST_CFG_CTL , msr_bits); + msr_bits &= ~auto_demotion_disable_flags; +wrmsrl (MSR_NHM_SNB_PKG_CST_CFG_CTL , msr_bits); +} +/* * intel_idle_probe() */
@@ -319,6 +335,8 @@ static int intel_idle_probe(void)case 0x25 :/* Westmere */ case 0x2C :/* Westmere */ cpuidle_state_table = nehalem_cstates; + auto_demotion_disable_flags = + (NHM_C1_AUTO_DEMOTE |NHM_C3_AUTO_DEMOTE );break ;case 0x1C :/* 28 - Atom Processor */
@@ -431,6 +449,8 @@ static int intel_idle_cpuidle_devices_inreturn -EIO ; } } +if (auto_demotion_disable_flags) +smp_call_function (auto_demotion_disable,NULL ,1 );return 0 ; }
PATCH 19/55 intel_idle: disable Atom/Lincroft HW C-state auto-demotion
In reply to Greg KH2.6.37-stable review patch. If anyone has any objections, please let us know.
------------------
From: Len Brown <[email protected]>
commit bfb53ccf1c734b1907df7189eef4c08489827951 upstream.
Just as we had to disable auto-demotion for NHM/WSM, we need to do the same for Atom (Lincroft version).
In particular, auto-demotion will prevent Lincroft from entering the S0i3 idle power saving state.
https://bugzilla.kernel.org/show_bug.cgi?id=25252
--- arch/x86/include/asm/msr-index.h | 1 + drivers/idle/intel_idle.c | 4 ++++ 2 files changed, 5 insertions(+)
arch/x86/include/asm/msr-index.h +1 -0
@@ -39,6 +39,7 @@#define MSR_NHM_SNB_PKG_CST_CFG_CTL 0x000000e2#define NHM_C3_AUTO_DEMOTE (1UL << 25)#define NHM_C1_AUTO_DEMOTE (1UL << 26) +#define ATM_LNC_C6_AUTO_DEMOTE (1UL << 25)#define MSR_MTRRcap 0x000000fe#define MSR_IA32_BBL_CR_CTL 0x00000119
drivers/idle/intel_idle.c +4 -0
@@ -340,8 +340,12 @@ static int intel_idle_probe(void)break ;case 0x1C :/* 28 - Atom Processor */ + cpuidle_state_table = atom_cstates; +break ; +case 0x26 :/* 38 - Lincroft Atom Processor */ cpuidle_state_table = atom_cstates; + auto_demotion_disable_flags =ATM_LNC_C6_AUTO_DEMOTE ;break ;case 0x2A :/* SNB */
PATCH 20/55 Prevent rt_sigqueueinfo and rt_tgsigqueueinfo from spoofing the signal code
In reply to Greg KH2.6.37-stable review patch. If anyone has any objections, please let us know.
------------------
From: Julien Tinnes <[email protected]>
commit da48524eb20662618854bb3df2db01fc65f3070c upstream.
Userland should be able to trust the pid and uid of the sender of a signal if the si_code is SI_TKILL.
Unfortunately, the kernel has historically allowed sigqueueinfo() to send any si_code at all (as long as it was negative - to distinguish it from kernel-generated signals like SIGILL etc), so it could spoof a SI_TKILL with incorrect siginfo values.
Happily, it looks like glibc has always set si_code to the appropriate SI_QUEUE, so there are probably no actual user code that ever uses anything but the appropriate SI_QUEUE flag.
So just tighten the check for si_code (we used to allow any negative value), and add a (one-time) warning in case there are binaries out there that might depend on using other si_code values.
--- kernel/signal.c | 16 ++++++++++++---- 1 file changed, 12 insertions(+), 4 deletions(-)
kernel/signal.c +12 -4
@@ -2421,9 +2421,13 @@ SYSCALL_DEFINE3(rt_sigqueueinfo, pid_t,return -EFAULT ;/* Not even root can pretend to send signals from the kernel. -Nor can they impersonate a kill(), which adds source info. */ -if (info.si_code >=0 ) +* Nor can they impersonate a kill()/tgkill(), which adds source info. +*/ +if (info.si_code !=SI_QUEUE ) { +/* We used to allow any < 0 si_code */ +WARN_ON_ONCE (info.si_code <0 );return -EPERM ; + } info.si_signo = sig;/* POSIX.1b doesn't mention process groups. */
@@ -2437,9 +2441,13 @@ long do_rt_tgsigqueueinfo(pid_t tgid, pireturn -EINVAL ;/* Not even root can pretend to send signals from the kernel. -Nor can they impersonate a kill(), which adds source info. */ -if (info->si_code >=0 ) +* Nor can they impersonate a kill()/tgkill(), which adds source info. +*/ +if (info->si_code !=SI_QUEUE ) { +/* We used to allow any < 0 si_code */ +WARN_ON_ONCE (info->si_code <0 );return -EPERM ; + } info->si_signo = sig;return do_send_specific (tgid, pid, sig, info);
PATCH 21/55 ALSA: HDA: Fix internal mic on Dell E5420/E5520
In reply to Greg KH2.6.37-stable review patch. If anyone has any objections, please let us know.
------------------
From: David Henningsson <[email protected]>
This is a fixup for the 2.6.38 kernel, as the issue is being resolved by upstream commits 699d899560cd7e72da39231e584412e7ac8114a4 and 094a42452abd5564429045e210281c6d22e67fca - which are too invasive to reach 2.6.38. Instead make pin fixes as a workaround.
--- sound/pci/hda/patch_sigmatel.c | 18 ++++++++++++++++++ 1 file changed, 18 insertions(+)
sound/pci/hda/patch_sigmatel.c +18 -0
@@ -94,6 +94,7 @@ enum {STAC_92HD83XXX_REF ,STAC_92HD83XXX_PWR_REF ,STAC_DELL_S14 , +STAC_DELL_E5520M ,STAC_92HD83XXX_HP ,STAC_HP_DV7_4000 ,STAC_92HD83XXX_MODELS
@@ -1649,6 +1650,13 @@ static unsigned int dell_s14_pin_configs 0x40f000f0, 0x40f000f0, }; +/* Switch int mic from 0x20 to 0x11 */ +static unsigned int dell_e5520m_pin_configs[10 ] = { +0x04a11020 ,0x0421101f ,0x400000f0 ,0x90170110 , +0x23011050 ,0x23a1102e ,0x400000f3 ,0xd5a30130 , +0x400000f0 ,0x40f000f0 , +}; +static unsigned int hp_dv7_4000_pin_configs[10 ] = {0x03a12050 ,0x0321201f ,0x40f000f0 ,0x90170110 ,0x40f000f0 ,0x40f000f0 ,0x90170110 ,0xd5a30140 ,
@@ -1659,6 +1667,7 @@ static unsigned int *stac92hd83xxx_brd_t [STAC_92HD83XXX_REF] = ref92hd83xxx_pin_configs, [STAC_92HD83XXX_PWR_REF] = ref92hd83xxx_pin_configs, [STAC_DELL_S14] = dell_s14_pin_configs, + [STAC_DELL_E5520M] = dell_e5520m_pin_configs, [STAC_HP_DV7_4000] = hp_dv7_4000_pin_configs, };
@@ -1667,6 +1676,7 @@ static const char *stac92hd83xxx_models[ [STAC_92HD83XXX_REF] = "ref", [STAC_92HD83XXX_PWR_REF] = "mic-ref", [STAC_DELL_S14] = "dell-s14", + [STAC_DELL_E5520M] = "dell-e5520m", [STAC_92HD83XXX_HP] = "hp", [STAC_HP_DV7_4000] = "hp-dv7-4000", };
@@ -1679,6 +1689,14 @@ static struct snd_pci_quirk stac92hd83xx "DFI LanParty", STAC_92HD83XXX_REF),SND_PCI_QUIRK (PCI_VENDOR_ID_DELL ,0x02ba ,"unknown Dell" ,STAC_DELL_S14 ), +SND_PCI_QUIRK (PCI_VENDOR_ID_DELL ,0x049a , +"Dell E5520" ,STAC_DELL_E5520M ), +SND_PCI_QUIRK (PCI_VENDOR_ID_DELL ,0x049b , +"Dell E5420" ,STAC_DELL_E5520M ), +SND_PCI_QUIRK (PCI_VENDOR_ID_DELL ,0x04eb , +"Dell E5420m" ,STAC_DELL_E5520M ), +SND_PCI_QUIRK (PCI_VENDOR_ID_DELL ,0x04ec , +"Dell E5520m" ,STAC_DELL_E5520M ),SND_PCI_QUIRK_MASK (PCI_VENDOR_ID_HP ,0xff00 ,0x3600 , "HP", STAC_92HD83XXX_HP), {} /* terminator */
PATCH 22/55 ext3: skip orphan cleanup on rocompat fs
In reply to Greg KH2.6.37-stable review patch. If anyone has any objections, please let us know.
------------------
From: Amir Goldstein <[email protected]>
commit ce654b37f87980d95f339080e4c3bdb2370bdf22 upstream.
Orphan cleanup is currently executed even if the file system has some number of unknown ROCOMPAT features, which deletes inodes and frees blocks, which could be very bad for some RO_COMPAT features.
This patch skips the orphan cleanup if it contains readonly compatible features not known by this ext3 implementation, which would prevent the fs from being mounted (or remounted) readwrite.
--- fs/ext3/super.c | 7 +++++++ 1 file changed, 7 insertions(+)
fs/ext3/super.c +7 -0
@@ -1440,6 +1440,13 @@ static void ext3_orphan_cleanup (structreturn ; } +/* Check if feature set allows readwrite operations */ +if (EXT3_HAS_RO_COMPAT_FEATURE (sb, ~EXT3_FEATURE_RO_COMPAT_SUPP )) { +ext3_msg (sb,KERN_INFO ,"Skipping orphan cleanup due to " +"unknown ROCOMPAT features" ); +return ; + } +if (EXT3_SB (sb)->s_mount_state &EXT3_ERROR_FS ) {if (es->s_last_orphan) jbd_debug(1, "Errors on filesystem, "
PATCH 23/55 sysctl: restrict write access to dmesg_restrict
In reply to Greg KH2.6.37-stable review patch. If anyone has any objections, please let us know.
------------------
From: Richard Weinberger <[email protected]>
commit bfdc0b497faa82a0ba2f9dddcf109231dd519fcc upstream.
When dmesg_restrict is set to 1 CAP_SYS_ADMIN is needed to read the kernel ring buffer. But a root user without CAP_SYS_ADMIN is able to reset dmesg_restrict to 0.
This is an issue when e.g. LXC (Linux Containers) are used and complete user space is running without CAP_SYS_ADMIN. A unprivileged and jailed root user can bypass the dmesg_restrict protection.
With this patch writing to dmesg_restrict is only allowed when root has CAP_SYS_ADMIN.
--- kernel/sysctl.c | 18 +++++++++++++++++- 1 file changed, 17 insertions(+), 1 deletion(-)
kernel/sysctl.c +17 -1
@@ -168,6 +168,11 @@ static int proc_taint(struct ctl_table * void __user *buffer, size_t *lenp, loff_t *ppos);#endif +#ifdef CONFIG_PRINTK +static int proc_dmesg_restrict (struct ctl_table *table,int write, +void __user *buffer,size_t *lenp,loff_t *ppos); +#endif +#ifdef CONFIG_MAGIC_SYSRQ /* Note: sysrq code uses it's own private copy */ static int __sysrq_enabled =SYSRQ_DEFAULT_ENABLE ;
@@ -1469,7 +1474,7 @@ static struct ctl_table fs_table[] = { .data = &suid_dumpable, .maxlen = sizeof(int), .mode = 0644, - .proc_handler = proc_dointvec_minmax, + .proc_handler = proc_dmesg_restrict, .extra1 = &zero, .extra2 = &two, },
@@ -2400,6 +2405,17 @@ static int proc_taint(struct ctl_table *return err; } +#ifdef CONFIG_PRINTK +static int proc_dmesg_restrict (struct ctl_table *table,int write, +void __user *buffer,size_t *lenp,loff_t *ppos) +{ +if (write && !capable (CAP_SYS_ADMIN )) +return -EPERM ; + +return proc_dointvec_minmax (table, write, buffer, lenp, ppos); +} +#endif +struct do_proc_dointvec_minmax_conv_param {int *min;int *max;
PATCH 24/55 procfs: fix /proc/<pid>/maps heap check
In reply to Greg KH2.6.37-stable review patch. If anyone has any objections, please let us know.
------------------
From: Aaro Koskinen <[email protected]>
commit 0db0c01b53a1a421513f91573241aabafb87802a upstream.
The current code fails to print the "[heap]" marking if the heap is split into multiple mappings.
Fix the check so that the marking is displayed in all possible cases:
1. vma matches exactly the heap
2. the heap vma is merged e.g. with bss
3. the heap vma is splitted e.g. due to locked pages
Test cases. In all cases, the process should have mapping(s) with [heap] marking:
(1) vma matches exactly the heap
#include <stdio.h>
#include <unistd.h>
#include <sys/types.h>
int main (void)
{
if (sbrk(4096) != (void *)-1) {
printf("check /proc/%d/maps\n", (int)getpid());
while (1)
sleep(1);
}
return 0;
}
# ./test1
check /proc/553/maps
[1] + Stopped ./test1
# cat /proc/553/maps | head -4
00008000-00009000 r-xp 00000000 01:00 3113640 /test1
00010000-00011000 rw-p 00000000 01:00 3113640 /test1
00011000-00012000 rw-p 00000000 00:00 0 [heap]
4006f000-40070000 rw-p 00000000 00:00 0
(2) the heap vma is merged
#include <stdio.h>
#include <unistd.h>
#include <sys/types.h>
char foo[4096] = "foo";
char bar[4096];
int main (void)
{
if (sbrk(4096) != (void *)-1) {
printf("check /proc/%d/maps\n", (int)getpid());
while (1)
sleep(1);
}
return 0;
}
# ./test2
check /proc/556/maps
[2] + Stopped ./test2
# cat /proc/556/maps | head -4
00008000-00009000 r-xp 00000000 01:00 3116312 /test2
00010000-00012000 rw-p 00000000 01:00 3116312 /test2
00012000-00014000 rw-p 00000000 00:00 0 [heap]
4004a000-4004b000 rw-p 00000000 00:00 0
(3) the heap vma is splitted (this fails without the patch)
#include <stdio.h>
#include <unistd.h>
#include <sys/mman.h>
#include <sys/types.h>
int main (void)
{
if ((sbrk(4096) != (void *)-1) && !mlockall(MCL_FUTURE) &&
(sbrk(4096) != (void *)-1)) {
printf("check /proc/%d/maps\n", (int)getpid());
while (1)
sleep(1);
}
return 0;
}
# ./test3
check /proc/559/maps
[1] + Stopped ./test3
# cat /proc/559/maps|head -4
00008000-00009000 r-xp 00000000 01:00 3119108 /test3
00010000-00011000 rw-p 00000000 01:00 3119108 /test3
00011000-00012000 rw-p 00000000 00:00 0 [heap]
00012000-00013000 rw-p 00000000 00:00 0 [heap]It looks like the bug has been there forever, and since it only results in some information missing from a procfile, it does not fulfil the -stable "critical issue" criteria.
--- fs/proc/task_mmu.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)
fs/proc/task_mmu.c +2 -2
@@ -248,8 +248,8 @@ static void show_map_vma(struct seq_fileconst char *name =arch_vma_name (vma);if (!name) {if (mm) { -if (vma->vm_start <= mm->start_brk && - vma->vm_end >= mm->brk) { +if (vma->vm_start <= mm->brk && + vma->vm_end >= mm->start_brk) { name ="[heap]" ; }else if (vma->vm_start <= mm->start_stack && vma->vm_end >= mm->start_stack) {
PATCH 25/55 proc: protect mm start_code/end_code in /proc/pid/stat
In reply to Greg KH2.6.37-stable review patch. If anyone has any objections, please let us know.
------------------
From: Kees Cook <[email protected]>
commit 5883f57ca0008ffc93e09cbb9847a1928e50c6f3 upstream.
While mm->start_stack was protected from cross-uid viewing (commit f83ce3e6b02d5 ("proc: avoid information leaks to non-privileged processes")), the start_code and end_code values were not. This would allow the text location of a PIE binary to leak, defeating ASLR.
Note that the value "1" is used instead of "0" for a protected value since "ps", "killall", and likely other readers of /proc/pid/stat, take start_code of "0" to mean a kernel thread and will misbehave. Thanks to Brad Spengler for pointing this out.
Addresses CVE-2011-0726
--- fs/proc/array.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)
fs/proc/array.c +2 -2
@@ -489,8 +489,8 @@ static int do_task_stat(struct seq_file vsize, mm ?get_mm_rss (mm) :0 , rsslim, - mm ? mm->start_code :0 , - mm ? mm->end_code :0 , + mm ? (permitted ? mm->start_code :1 ) :0 , + mm ? (permitted ? mm->end_code :1 ) :0 , (permitted && mm) ? mm->start_stack :0 , esp, eip,
PATCH 26/55 fbcon: Bugfix soft cursor detection in Tile Blitting
In reply to Greg KH2.6.37-stable review patch. If anyone has any objections, please let us know.
------------------
From: Henry Nestler <[email protected]>
commit d6244bc0ed0c52a795e6f4dcab3886daf3e74fac upstream.
Use mask 0x10 for "soft cursor" detection on in function tile_cursor. (Tile Blitting Operation in framebuffer console).
The old mask 0x01 for vc_cursor_type detects CUR_NONE, CUR_LOWER_THIRD and every second mode value as "software cursor". This hides the cursor for these modes (cursor.mode = 0). But, only CUR_NONE or "software cursor" should hide the cursor.
See also 0x10 in functions add_softcursor, bit_cursor and cw_cursor.
--- drivers/video/console/tileblit.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
drivers/video/console/tileblit.c +1 -1
@@ -83,7 +83,7 @@ static void tile_cursor(struct vc_data * int softback_lines, int fg, int bg) { struct fb_tilecursor cursor; -int use_sw = (vc->vc_cursor_type &0x01 ); +int use_sw = (vc->vc_cursor_type &0x10 ); cursor.sx = vc->vc_x; cursor.sy = vc->vc_y;
PATCH 27/55 nfsd41: modify the members value of nfsd4_op_flags
In reply to Greg KH2.6.37-stable review patch. If anyone has any objections, please let us know.
------------------
From: Mi Jinlong <[email protected]>
commit 5ece3cafbd88d4da5c734e1810c4a2e6474b57b2 upstream.
The members of nfsd4_op_flags, (ALLOWED_WITHOUT_FH | ALLOWED_ON_ABSENT_FS) equals to ALLOWED_AS_FIRST_OP, maybe that's not what we want.
OP_PUTROOTFH with op_flags = ALLOWED_WITHOUT_FH | ALLOWED_ON_ABSENT_FS, can't appears as the first operation with out SEQUENCE ops.
This patch modify the wrong value of ALLOWED_WITHOUT_FH etc which was introduced by f9bb94c4.
--- fs/nfsd/nfs4proc.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)
fs/nfsd/nfs4proc.c +2 -2
@@ -954,8 +954,8 @@ typedef __be32(*nfsd4op_func)(struct svc void *);enum nfsd4_op_flags {ALLOWED_WITHOUT_FH =1 <<0 ,/* No current filehandle required */ -ALLOWED_ON_ABSENT_FS =2 <<0 ,/* ops processed on absent fs */ -ALLOWED_AS_FIRST_OP =3 <<0 ,/* ops reqired first in compound */ +ALLOWED_ON_ABSENT_FS =1 <<1 ,/* ops processed on absent fs */ +ALLOWED_AS_FIRST_OP =1 <<2 ,/* ops reqired first in compound */ };struct nfsd4_operation {
PATCH 28/55 nfsd4: minor nfs4state.c reshuffling
In reply to Greg KH2.6.37-stable review patch. If anyone has any objections, please let us know.
------------------
From: J. Bruce Fields <[email protected]>
commit 529d7b2a7fa31e9f7d08bc790d232c3cbe64fa24 upstream.
Minor cleanup in preparation for a bugfix--moving some code to avoid forward references, etc. No change in functionality.
--- fs/nfsd/nfs4state.c | 125 +++++++++++++++++++++++++--------------------------- 1 file changed, 61 insertions(+), 64 deletions(-)
fs/nfsd/nfs4state.c +61 -64
@@ -327,64 +327,6 @@ static struct list_head unconf_id_hashtbstatic struct list_head client_lru;static struct list_head close_lru; -static void unhash_generic_stateid (struct nfs4_stateid *stp) -{ -list_del (&stp->st_hash); -list_del (&stp->st_perfile); -list_del (&stp->st_perstateowner); -} - -static void free_generic_stateid (struct nfs4_stateid *stp) -{ -put_nfs4_file (stp->st_file); -kmem_cache_free (stateid_slab, stp); -} - -static void release_lock_stateid (struct nfs4_stateid *stp) -{ -struct file *file; - -unhash_generic_stateid (stp); - file =find_any_file (stp->st_file); -if (file) -locks_remove_posix (file, (fl_owner_t )stp->st_stateowner); -free_generic_stateid (stp); -} - -static void unhash_lockowner (struct nfs4_stateowner *sop) -{ -struct nfs4_stateid *stp; - -list_del (&sop->so_idhash); -list_del (&sop->so_strhash); -list_del (&sop->so_perstateid); -while (!list_empty (&sop->so_stateids)) { - stp =list_first_entry (&sop->so_stateids, - struct nfs4_stateid, st_perstateowner); -release_lock_stateid (stp); - } -} - -static void release_lockowner (struct nfs4_stateowner *sop) -{ -unhash_lockowner (sop); -nfs4_put_stateowner (sop); -} - -static void -release_stateid_lockowners (struct nfs4_stateid *open_stp) -{ -struct nfs4_stateowner *lock_sop; - -while (!list_empty (&open_stp->st_lockowners)) { - lock_sop =list_entry (open_stp->st_lockowners.next, - struct nfs4_stateowner, so_perstateid); -/* list_del(&open_stp->st_lockowners); */ -BUG_ON (lock_sop->so_is_open_owner); -release_lockowner (lock_sop); - } -} -/* * We store the NONE, READ, WRITE, and BOTH bits separately in the * st_{access,deny}_bmap field of the stateid, in order to track not
@@ -457,6 +399,64 @@ static int nfs4_access_bmap_to_omode(strreturn nfs4_access_to_omode (access); } +static void unhash_generic_stateid (struct nfs4_stateid *stp) +{ +list_del (&stp->st_hash); +list_del (&stp->st_perfile); +list_del (&stp->st_perstateowner); +} + +static void free_generic_stateid (struct nfs4_stateid *stp) +{ +put_nfs4_file (stp->st_file); +kmem_cache_free (stateid_slab, stp); +} + +static void release_lock_stateid (struct nfs4_stateid *stp) +{ +struct file *file; + +unhash_generic_stateid (stp); + file =find_any_file (stp->st_file); +if (file) +locks_remove_posix (file, (fl_owner_t )stp->st_stateowner); +free_generic_stateid (stp); +} + +static void unhash_lockowner (struct nfs4_stateowner *sop) +{ +struct nfs4_stateid *stp; + +list_del (&sop->so_idhash); +list_del (&sop->so_strhash); +list_del (&sop->so_perstateid); +while (!list_empty (&sop->so_stateids)) { + stp =list_first_entry (&sop->so_stateids, + struct nfs4_stateid, st_perstateowner); +release_lock_stateid (stp); + } +} + +static void release_lockowner (struct nfs4_stateowner *sop) +{ +unhash_lockowner (sop); +nfs4_put_stateowner (sop); +} + +static void +release_stateid_lockowners (struct nfs4_stateid *open_stp) +{ +struct nfs4_stateowner *lock_sop; + +while (!list_empty (&open_stp->st_lockowners)) { + lock_sop =list_entry (open_stp->st_lockowners.next, + struct nfs4_stateowner, so_perstateid); +/* list_del(&open_stp->st_lockowners); */ +BUG_ON (lock_sop->so_is_open_owner); +release_lockowner (lock_sop); + } +} +static void release_open_stateid (struct nfs4_stateid *stp) {int oflag =nfs4_access_bmap_to_omode (stp);
@@ -3691,7 +3691,6 @@ nfsd4_lock(struct svc_rqst *rqstp, strucstruct file_lock conflock;__be32 status =0 ;unsigned int strhashval; -unsigned int cmd;int err; dprintk("NFSD: nfsd4_lock: start=%Ld length=%Ld\n",
@@ -3778,8 +3777,7 @@ nfsd4_lock(struct svc_rqst *rqstp, struc filp =find_readable_file (lock_stp->st_file); } file_lock.fl_type =F_RDLCK ; - cmd =F_SETLK ; -break ; +break ;case NFS4_WRITE_LT :case NFS4_WRITEW_LT :if (find_writeable_file (lock_stp->st_file)) {
@@ -3787,8 +3785,7 @@ nfsd4_lock(struct svc_rqst *rqstp, struc filp =find_writeable_file (lock_stp->st_file); } file_lock.fl_type =F_WRLCK ; - cmd =F_SETLK ; -break ; +break ;default : status = nfserr_inval; goto out;
@@ -3812,7 +3809,7 @@ nfsd4_lock(struct svc_rqst *rqstp, struc* Note: locks.c uses the BKL to protect the inode's lock list. */ - err =vfs_lock_file (filp, cmd, &file_lock, &conflock); + err =vfs_lock_file (filp,F_SETLK , &file_lock, &conflock);switch (-err) {case 0 :/* success! */ update_stateid (&lock_stp->st_stateid);
PATCH 29/55 nfsd4: fix struct file leak
In reply to Greg KH2.6.37-stable review patch. If anyone has any objections, please let us know.
------------------
From: J. Bruce Fields <[email protected]>
commit 0997b173609b9229ece28941c118a2a9b278796e upstream.
Make sure we properly reference count the struct files that a lock depends on, and release them when the lock stateid is released.
This fixes a major leak of struct files when using locking over nfsv4.
--- fs/nfsd/nfs4state.c | 32 +++++++++++++++++++++----------- 1 file changed, 21 insertions(+), 11 deletions(-)
fs/nfsd/nfs4state.c +21 -11
@@ -408,6 +408,9 @@ static void unhash_generic_stateid(strucstatic void free_generic_stateid (struct nfs4_stateid *stp) { +int oflag =nfs4_access_bmap_to_omode (stp); + +nfs4_file_put_access (stp->st_file, oflag);put_nfs4_file (stp->st_file);kmem_cache_free (stateid_slab, stp); }
@@ -459,11 +462,8 @@ release_stateid_lockowners(struct nfs4_sstatic void release_open_stateid (struct nfs4_stateid *stp) { -int oflag =nfs4_access_bmap_to_omode (stp); -unhash_generic_stateid (stp);release_stateid_lockowners (stp); -nfs4_file_put_access (stp->st_file, oflag);free_generic_stateid (stp); }
@@ -3661,6 +3661,7 @@ alloc_init_lock_stateid(struct nfs4_stat stp->st_stateid.si_stateownerid = sop->so_id; stp->st_stateid.si_fileid = fp->fi_id; stp->st_stateid.si_generation =0 ; + stp->st_access_bmap =0 ; stp->st_deny_bmap = open_stp->st_deny_bmap; stp->st_openstp = open_stp;
@@ -3675,6 +3676,17 @@ check_lock_length(u64 offset, u64 length LOFF_OVERFLOW(offset, length))); } +static void get_lock_access (struct nfs4_stateid *lock_stp,u32 access) +{ +struct nfs4_file *fp = lock_stp->st_file; +int oflag =nfs4_access_to_omode (access); + +if (test_bit (access, &lock_stp->st_access_bmap)) +return ; +nfs4_file_get_access (fp, oflag); +__set_bit (access, &lock_stp->st_access_bmap); +} +/* * LOCK operation */
@@ -3772,18 +3784,16 @@ nfsd4_lock(struct svc_rqst *rqstp, strucswitch (lock->lk_type) {case NFS4_READ_LT :case NFS4_READW_LT : -if (find_readable_file (lock_stp->st_file)) { -nfs4_get_vfs_file (rqstp, fp, &cstate->current_fh,NFS4_SHARE_ACCESS_READ ); - filp =find_readable_file (lock_stp->st_file); - } + filp =find_readable_file (lock_stp->st_file); +if (filp) +get_lock_access (lock_stp,NFS4_SHARE_ACCESS_READ ); file_lock.fl_type =F_RDLCK ;break ;case NFS4_WRITE_LT :case NFS4_WRITEW_LT : -if (find_writeable_file (lock_stp->st_file)) { -nfs4_get_vfs_file (rqstp, fp, &cstate->current_fh,NFS4_SHARE_ACCESS_WRITE ); - filp =find_writeable_file (lock_stp->st_file); - } + filp =find_writeable_file (lock_stp->st_file); +if (filp) +get_lock_access (lock_stp,NFS4_SHARE_ACCESS_WRITE ); file_lock.fl_type =F_WRLCK ;break ;default :
PATCH 30/55 nfsd: wrong index used in inner loop
In reply to Greg KH2.6.37-stable review patch. If anyone has any objections, please let us know.
------------------
From: Mi Jinlong <[email protected]>
commit 5a02ab7c3c4580f94d13c683721039855b67cda6 upstream.
We must not use dummy for index.
After the first index, READ32(dummy) will change dummy!!!!
--- fs/nfsd/nfs4xdr.c | 5 +---- 1 file changed, 1 insertion(+), 4 deletions(-)
fs/nfsd/nfs4xdr.c +1 -4
@@ -1107,7 +1107,7 @@ nfsd4_decode_create_session(struct nfsd4u32 dummy;char *machine_name; -int i, j; +int i;int nr_secflavs;READ_BUF (16 );
@@ -1180,8 +1180,6 @@ nfsd4_decode_create_session(struct nfsd4READ_BUF (4 );READ32 (dummy);READ_BUF (dummy *4 ); -for (j =0 ; j < dummy; ++j) -READ32 (dummy);break ;case RPC_AUTH_GSS : dprintk("RPC_AUTH_GSS callback secflavor "
@@ -1197,7 +1195,6 @@ nfsd4_decode_create_session(struct nfsd4READ_BUF (4 );READ32 (dummy);READ_BUF (dummy); - p +=XDR_QUADLEN (dummy);break ;default :dprintk ("Illegal callback secflavor\n" );
PATCH 31/55 uvcvideo: Fix uvc_fixup_video_ctrl() format search
In reply to Greg KH2.6.37-stable review patch. If anyone has any objections, please let us know.
------------------
From: Stephan Lachowsky <[email protected]>
commit 38a66824d96de8aeeb915e6f46f0d3fe55828eb1 upstream.
The scheme used to index format in uvc_fixup_video_ctrl() is not robust:
format index is based on descriptor ordering, which does not necessarily match bFormatIndex ordering. Searching for first matching format will prevent uvc_fixup_video_ctrl() from using the wrong format/frame to make adjustments.
--- drivers/media/video/uvc/uvc_video.c | 14 +++++++++----- 1 file changed, 9 insertions(+), 5 deletions(-)
drivers/media/video/uvc/uvc_video.c +9 -5
@@ -89,15 +89,19 @@ int uvc_query_ctrl(struct uvc_device *destatic void uvc_fixup_video_ctrl (struct uvc_streaming *stream,struct uvc_streaming_control *ctrl) { -struct uvc_format *format; +struct uvc_format *format =NULL ;struct uvc_frame *frame =NULL ;unsigned int i; -if (ctrl->bFormatIndex <=0 || - ctrl->bFormatIndex > stream->nformats) -return ; +for (i =0 ; i < stream->nformats; ++i) { +if (stream->format[i].index == ctrl->bFormatIndex) { + format = &stream->format[i]; +break ; + } + } - format = &stream->format[ctrl->bFormatIndex -1 ]; +if (format ==NULL ) +return ;for (i =0 ; i < format->nframes; ++i) {if (format->frame[i].bFrameIndex == ctrl->bFrameIndex) {
PATCH 32/55 uvcvideo: Fix descriptor parsing for video output devices
In reply to Greg KH2.6.37-stable review patch. If anyone has any objections, please let us know.
------------------
From: Laurent Pinchart <[email protected]>
commit 4093a5c4a3f59cba1a085bbf87b6ffdddc5a443d upstream.
Commit 4057ac6ca9a77c4275b34b5925ab5c99557913b1
V4L/DVB (13505): uvcvideo: Refactor chain scan
broke output terminals parsing. Fix it.
--- drivers/media/video/uvc/uvc_driver.c | 8 ++++++++ 1 file changed, 8 insertions(+)
drivers/media/video/uvc/uvc_driver.c +8 -0
@@ -1264,6 +1264,14 @@ static int uvc_scan_chain_entity(structbreak ; +case UVC_OTT_VENDOR_SPECIFIC : +case UVC_OTT_DISPLAY : +case UVC_OTT_MEDIA_TRANSPORT_OUTPUT : +if (uvc_trace_param &UVC_TRACE_PROBE ) +printk (" OT %d" , entity->id); + +break ; +case UVC_TT_STREAMING :if (UVC_ENTITY_IS_ITERM (entity)) {if (uvc_trace_param &UVC_TRACE_PROBE )
PATCH 33/55 sh: Fix ptrace fpu state initialisation
In reply to Greg KH2.6.37-stable review patch. If anyone has any objections, please let us know.
------------------
From: Phil Edworthy <[email protected]>
commit c49b6ecf0870e78fa40497cd8b142915c1d5c7c9 upstream.
Commit 0ea820cf introduced the PTRACE_GETFPREGS/SETFPREGS cmds, but gdb-server still accesses the FPU state using the PTRACE_PEEKUSR/POKEUSR commands. In this case, xstate was not initialised.
--- arch/sh/kernel/ptrace_32.c | 6 ++++++ arch/sh/kernel/ptrace_64.c | 6 ++++++ 2 files changed, 12 insertions(+)
arch/sh/kernel/ptrace_32.c +6 -0
@@ -392,6 +392,9 @@ long arch_ptrace(struct task_struct *chi tmp =0 ; }else {unsigned long index; + ret =init_fpu (child); +if (ret) +break ; index = addr - offsetof(struct user , fpu); tmp = ((unsigned long *)child->thread.xstate) [index >>2 ];
@@ -423,6 +426,9 @@ long arch_ptrace(struct task_struct *chielse if (addr >= offsetof(struct user , fpu) && addr < offsetof(struct user , u_fpvalid)) {unsigned long index; + ret =init_fpu (child); +if (ret) +break ; index = addr - offsetof(struct user , fpu);set_stopped_child_used_math (child); ((unsigned long *)child->thread.xstate)
arch/sh/kernel/ptrace_64.c +6 -0
@@ -403,6 +403,9 @@ long arch_ptrace(struct task_struct *chielse if ((addr >= offsetof(struct user , fpu)) && (addr < offsetof(struct user , u_fpvalid))) {unsigned long index; + ret =init_fpu (child); +if (ret) +break ; index = addr - offsetof(struct user , fpu); tmp =get_fpu_long (child, index); }else if (addr == offsetof(struct user , u_fpvalid)) {
@@ -442,6 +445,9 @@ long arch_ptrace(struct task_struct *chielse if ((addr >= offsetof(struct user , fpu)) && (addr < offsetof(struct user , u_fpvalid))) {unsigned long index; + ret =init_fpu (child); +if (ret) +break ; index = addr - offsetof(struct user , fpu); ret =put_fpu_long (child, index, data); }
PATCH 34/55 sh: Fix ptrace hw_breakpoint handling
In reply to Greg KH2.6.37-stable review patch. If anyone has any objections, please let us know.
------------------
From: David Engraf <[email protected]>
commit fb7f045ace0624f1e59a7db8497e460bd54b1cbc upstream.
Since commit 34d0b5af50a063cded842716633501b38ff815fb it is no longer possible to debug an application using singlestep. The old commit converted singlestep handling via ptrace to hw_breakpoints. The hw_breakpoint is disabled when an event is triggered and not re-enabled again. This patch re-enables the existing hw_breakpoint before the existing breakpoint is reused.
--- arch/sh/kernel/ptrace_32.c | 2 ++ 1 file changed, 2 insertions(+)
arch/sh/kernel/ptrace_32.c +2 -0
@@ -101,6 +101,8 @@ static int set_single_step(struct task_s attr = bp->attr; attr.bp_addr = addr; +/* reenable breakpoint */ + attr.disabled = false; err =modify_user_hw_breakpoint (bp, &attr);if (unlikely (err))return err;
PATCH 35/55 USB: Do not pass negative length to snoop_urb()
In reply to Greg KH2.6.37-stable review patch. If anyone has any objections, please let us know.
------------------
From: Michal Sojka <[email protected]>
commit 9d02b42614149ebccf12c9c580601ed01bd83070 upstream.
When echo Y > /sys/module/usbcore/parameters/usbfs_snoop and usb_control_msg() returns error, a lot of kernel memory is dumped to dmesg until unhandled kernel paging request occurs.
--- drivers/usb/core/devio.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
drivers/usb/core/devio.c +1 -1
@@ -802,7 +802,7 @@ static int proc_control(struct dev_state tbuf, ctrl.wLength, tmo);usb_lock_device (dev);snoop_urb (dev,NULL , pipe,max (i,0 ),min (i,0 ),COMPLETE , - tbuf, i); + tbuf,max (i,0 ));if ((i >0 ) && ctrl.wLength) {if (copy_to_user (ctrl.data, tbuf, i)) {free_page ((unsigned long )tbuf);
PATCH 36/55 ehci-hcd: Bug fix: dont set a QHs Halt bit
In reply to Greg KH2.6.37-stable review patch. If anyone has any objections, please let us know.
------------------
From: Alan Stern <[email protected]>
commit b5a3b3d985493c173925907adfebf3edab236fe7 upstream.
This patch (as1453) fixes a long-standing bug in the ehci-hcd driver.
There is no need to set the Halt bit in the overlay region for an unlinked or blocked QH. Contrary to what the comment says, setting the Halt bit does not cause the QH to be patched later; that decision (made in qh_refresh()) depends only on whether the QH is currently pointing to a valid qTD. Likewise, setting the Halt bit does not prevent completions from activating the QH while it is "stopped"; they are prevented by the fact that qh_completions() temporarily changes qh->qh_state to QH_STATE_COMPLETING.
On the other hand, there are circumstances in which the QH will be reactivated _without_ being patched; this happens after an URB beyond the head of the queue is unlinked. Setting the Halt bit will then cause the hardware to see the QH with both the Active and Halt bits set, an invalid combination that will prevent the queue from advancing and may even crash some controllers.
Apparently the only reason this hasn't been reported before is that unlinking URBs from the middle of a running queue is quite uncommon. However Test 17, recently added to the usbtest driver, does exactly this, and it confirms the presence of the bug.
In short, there is no reason to set the Halt bit for an unlinked or blocked QH, and there is a very good reason not to set it. Therefore the code that sets it is removed.
--- drivers/usb/host/ehci-q.c | 12 ------------ 1 file changed, 12 deletions(-)
drivers/usb/host/ehci-q.c +0 -12
@@ -315,7 +315,6 @@ qh_completions (struct ehci_hcd *ehci, sint stopped;unsigned count =0 ;u8 state; -const __le32 halt =HALT_BIT (ehci);struct ehci_qh_hw *hw = qh->hw;if (unlikely (list_empty (&qh->qtd_list)))
@@ -422,7 +421,6 @@ qh_completions (struct ehci_hcd *ehci, s && !(qtd->hw_alt_next & EHCI_LIST_END(ehci))) { stopped =1 ; - goto halt; }/* stop scanning when we reach qtds the hc is using */
@@ -456,16 +454,6 @@ qh_completions (struct ehci_hcd *ehci, s*/ ehci_clear_tt_buffer (ehci, qh, urb, token); } - -/* force halt for unlinked or blocked qh, so we'll -* patch the qh later and so that completions can't -* activate it while we "know" it's stopped. -*/ -if ((halt & hw->hw_token) ==0 ) { -halt: - hw->hw_token |= halt; -wmb (); - } }/* unless we already know the urb's status, collect qtd status
PATCH 37/55 USB: uss720 fixup refcount position
In reply to Greg KH2.6.37-stable review patch. If anyone has any objections, please let us know.
------------------
From: Peter Holik <[email protected]>
commit adaa3c6342b249548ea830fe8e02aa5b45be8688 upstream.
My testprog do a lot of bitbang - after hours i got following warning and my machine lockups:
WARNING: at /build/buildd/linux-2.6.38/lib/kref.c:34
After debugging uss720 driver i discovered that the completion callback was called before usb_submit_urb returns. The callback frees the request structure that is krefed on return by usb_submit_urb.
--- drivers/usb/misc/uss720.c | 7 +++---- 1 file changed, 3 insertions(+), 4 deletions(-)
drivers/usb/misc/uss720.c +3 -4
@@ -177,12 +177,11 @@ static struct uss720_async_request *submspin_lock_irqsave (&priv->asynclock, flags);list_add_tail (&rq->asynclist, &priv->asynclist);spin_unlock_irqrestore (&priv->asynclock, flags); +kref_get (&rq->ref_count); ret =usb_submit_urb (rq->urb, mem_flags); -if (!ret) { -kref_get (&rq->ref_count); +if (!ret)return rq; - } -kref_put (&rq->ref_count, destroy_async); +destroy_async (&rq->ref_count);err ("submit_async_request submit_urb failed with %d" , ret);return NULL ; }
PATCH 38/55 USB: Fix bad dma problem on WDM device disconnect
In reply to Greg KH2.6.37-stable review patch. If anyone has any objections, please let us know.
------------------
From: Robert Lukassen <[email protected]>
commit 878b753e32ca765cd346a5d3038d630178ec78ff upstream.
In the WDM class driver a disconnect event leads to calls to usb_free_coherent to put back two USB DMA buffers allocated earlier. The call to usb_free_coherent uses a different size parameter (desc->wMaxCommand) than the corresponding call to usb_alloc_coherent (desc->bMaxPacketSize0).
When a disconnect event occurs, this leads to 'bad dma' complaints from usb core because the USB DMA buffer is being pushed back to the 'buffer-2048' pool from which it has not been allocated.
This patch against the most recent linux-2.6 kernel ensures that the parameters used by usb_alloc_coherent & usb_free_coherent calls in cdc-wdm.c match.
--- drivers/usb/class/cdc-wdm.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
drivers/usb/class/cdc-wdm.c +1 -1
@@ -281,7 +281,7 @@ static void cleanup(struct wdm_device *d desc->sbuf, desc->validity->transfer_dma);usb_free_coherent (interface_to_usbdev (desc->intf), - desc->wMaxCommand, + desc->bMaxPacketSize0, desc->inbuf, desc->response->transfer_dma);kfree (desc->orq);
PATCH 39/55 USB: cdc-acm: fix memory corruption / panic
In reply to Greg KH2.6.37-stable review patch. If anyone has any objections, please let us know.
------------------
From: Johan Hovold <[email protected]>
commit 23b80550e2aa61d0ba3af98b831b9195be0db9ee upstream.
Prevent read urbs from being resubmitted from tasklet after port close.
The receive tasklet was not disabled on port close, which could lead to corruption of receive lists on consecutive port open. In particular, read urbs could be re-submitted before port open, added to free list in open, and then added a second time to the free list in the completion handler.
cdc-acm.c: Entering acm_tty_open.cdc-acm.c: acm_control_msg: rq: 0x22 val: 0x3 len: 0x0 result: 0 cdc-acm.c: Entering acm_rx_taskletcdc-acm.c: acm_rx_tasklet: sending urb 0xf50da280, rcv 0xf57fbc24, buf 0xf57fbd64 cdc-acm.c: set line: 115200 0 0 8cdc-acm.c: acm_control_msg: rq: 0x20 val: 0x0 len: 0x7 result: 7 cdc-acm.c: acm_tty_closecdc-acm.c: acm_port_downcdc-acm.c: acm_control_msg: rq: 0x22 val: 0x0 len: 0x0 result: 0 cdc-acm.c: acm_ctrl_irq - urb shutting down with status: -2 cdc-acm.c: acm_rx_tasklet: sending urb 0xf50da300, rcv 0xf57fbc10, buf 0xf57fbd50 cdc-acm.c: Entering acm_read_bulk with status -2cdc_acm 4-1:1.1: Aborting, acm not readycdc-acm.c: Entering acm_read_bulk with status -2cdc_acm 4-1:1.1: Aborting, acm not readycdc-acm.c: acm_rx_tasklet: sending urb 0xf50da380, rcv 0xf57fbbfc, buf 0xf57fbd3c cdc-acm.c: acm_rx_tasklet: sending urb 0xf50da400, rcv 0xf57fbbe8, buf 0xf57fbd28 cdc-acm.c: acm_rx_tasklet: sending urb 0xf50da480, rcv 0xf57fbbd4, buf 0xf57fbd14 cdc-acm.c: acm_rx_tasklet: sending urb 0xf50da900, rcv 0xf57fbbc0, buf 0xf57fbd00 cdc-acm.c: acm_rx_tasklet: sending urb 0xf50da980, rcv 0xf57fbbac, buf 0xf57fbcec cdc-acm.c: acm_rx_tasklet: sending urb 0xf50daa00, rcv 0xf57fbb98, buf 0xf57fbcd8 cdc-acm.c: acm_rx_tasklet: sending urb 0xf50daa80, rcv 0xf57fbb84, buf 0xf57fbcc4 cdc-acm.c: acm_rx_tasklet: sending urb 0xf50dab00, rcv 0xf57fbb70, buf 0xf57fbcb0 cdc-acm.c: acm_rx_tasklet: sending urb 0xf50dab80, rcv 0xf57fbb5c, buf 0xf57fbc9c cdc-acm.c: acm_rx_tasklet: sending urb 0xf50dac00, rcv 0xf57fbb48, buf 0xf57fbc88 cdc-acm.c: acm_rx_tasklet: sending urb 0xf50dac80, rcv 0xf57fbb34, buf 0xf57fbc74 cdc-acm.c: acm_rx_tasklet: sending urb 0xf50dad00, rcv 0xf57fbb20, buf 0xf57fbc60 cdc-acm.c: acm_rx_tasklet: sending urb 0xf50dad80, rcv 0xf57fbb0c, buf 0xf57fbc4c cdc-acm.c: acm_rx_tasklet: sending urb 0xf50da880, rcv 0xf57fbaf8, buf 0xf57fbc38 cdc-acm.c: Entering acm_tty_open.cdc-acm.c: acm_control_msg: rq: 0x22 val: 0x3 len: 0x0 result: 0 cdc-acm.c: Entering acm_rx_taskletcdc-acm.c: acm_rx_tasklet: sending urb 0xf50da280, rcv 0xf57fbc24, buf 0xf57fbd64 cdc-acm.c: Entering acm_tty_write to write 3 bytes,cdc-acm.c: Get 3 bytes...cdc-acm.c: acm_write_start susp_count: 0cdc-acm.c: Entering acm_read_bulk with status 0
------------[ cut here ]------------ WARNING: at /home/johan/src/linux/linux-2.6/lib/list_debug.c:57 list_del+0x10c/0x120() Hardware name: Vostro 1520 list_del corruption. next->prev should be f57fbc10, but was f57fbaf8 Modules linked in: cdc_acm Pid: 3, comm: ksoftirqd/0 Not tainted 2.6.37+ #39 Call Trace: [<c103c7e2>] warn_slowpath_common+0x72/0xa0 [<c11dd8ac>] ? list_del+0x10c/0x120 [<c11dd8ac>] ? list_del+0x10c/0x120 [<c103c8b3>] warn_slowpath_fmt+0x33/0x40 [<c11dd8ac>] list_del+0x10c/0x120 [<f8051dbf>] acm_rx_tasklet+0xef/0x3e0 [cdc_acm] [<c135465d>] ? net_rps_action_and_irq_enable+0x6d/0x80 [<c1042bb6>] tasklet_action+0xe6/0x140 [<c104342f>] __do_softirq+0xaf/0x210 [<c1043380>] ? __do_softirq+0x0/0x210 <IRQ> [<c1042c9a>] ? run_ksoftirqd+0x8a/0x1c0 [<c1042c10>] ? run_ksoftirqd+0x0/0x1c0 [<c105ac24>] ? kthread+0x74/0x80 [<c105abb0>] ? kthread+0x0/0x80 [<c100337a>] ? kernel_thread_helper+0x6/0x10 ---[ end trace efd9a11434f0082e ]--- ------------[ cut here ]------------ WARNING: at /home/johan/src/linux/linux-2.6/lib/list_debug.c:57 list_del+0x10c/0x120() Hardware name: Vostro 1520 list_del corruption. next->prev should be f57fbd50, but was f57fbdb0 Modules linked in: cdc_acm Pid: 3, comm: ksoftirqd/0 Tainted: G W 2.6.37+ #39 Call Trace: [<c103c7e2>] warn_slowpath_common+0x72/0xa0 [<c11dd8ac>] ? list_del+0x10c/0x120 [<c11dd8ac>] ? list_del+0x10c/0x120 [<c103c8b3>] warn_slowpath_fmt+0x33/0x40 [<c11dd8ac>] list_del+0x10c/0x120 [<f8051dd6>] acm_rx_tasklet+0x106/0x3e0 [cdc_acm] [<c135465d>] ? net_rps_action_and_irq_enable+0x6d/0x80 [<c1042bb6>] tasklet_action+0xe6/0x140 [<c104342f>] __do_softirq+0xaf/0x210 [<c1043380>] ? __do_softirq+0x0/0x210 <IRQ> [<c1042c9a>] ? run_ksoftirqd+0x8a/0x1c0 [<c1042c10>] ? run_ksoftirqd+0x0/0x1c0 [<c105ac24>] ? kthread+0x74/0x80 [<c105abb0>] ? kthread+0x0/0x80 [<c100337a>] ? kernel_thread_helper+0x6/0x10 ---[ end trace efd9a11434f0082f ]---
cdc-acm.c: acm_rx_tasklet: sending urb 0xf50da300, rcv 0xf57fbc10, buf 0xf57fbd50 cdc-acm.c: disconnected from networkcdc-acm.c: acm_rx_tasklet: sending urb 0xf50da380, rcv 0xf57fbbfc, buf 0xf57fbd3c cdc-acm.c: Entering acm_rx_tasklet
------------[ cut here ]------------ WARNING: at /home/johan/src/linux/linux-2.6/lib/list_debug.c:48 list_del+0xd5/0x120() Hardware name: Vostro 1520 list_del corruption, next is LIST_POISON1 (00100100) Modules linked in: cdc_acm Pid: 3, comm: ksoftirqd/0 Tainted: G W 2.6.37+ #39 Call Trace: [<c103c7e2>] warn_slowpath_common+0x72/0xa0 [<c11dd875>] ? list_del+0xd5/0x120 [<c11dd875>] ? list_del+0xd5/0x120 [<c103c8b3>] warn_slowpath_fmt+0x33/0x40 [<c11dd875>] list_del+0xd5/0x120 [<f8051fac>] acm_rx_tasklet+0x2dc/0x3e0 [cdc_acm] [<c106dbab>] ? trace_hardirqs_on+0xb/0x10 [<c1042b30>] ? tasklet_action+0x60/0x140 [<c1042bb6>] tasklet_action+0xe6/0x140 [<c104342f>] __do_softirq+0xaf/0x210 [<c1043380>] ? __do_softirq+0x0/0x210 <IRQ> [<c1042c9a>] ? run_ksoftirqd+0x8a/0x1c0 [<c1042c10>] ? run_ksoftirqd+0x0/0x1c0 [<c105ac24>] ? kthread+0x74/0x80 [<c105abb0>] ? kthread+0x0/0x80 [<c100337a>] ? kernel_thread_helper+0x6/0x10 ---[ end trace efd9a11434f00830 ]--- BUG: unable to handle kernel paging request at 00200200 IP: [<c11dd7bd>] list_del+0x1d/0x120 *pde = 00000000 Oops: 0000 [#1] PREEMPT SMP last sysfs file: /sys/devices/pci0000:00/0000:00:1a.1/usb4/4-1/4-1:1.0/tty/ttyACM0/uevent Modules linked in: cdc_acm
Pid: 3, comm: ksoftirqd/0 Tainted: G W 2.6.37+ #39 0T816J/Vostro 1520
EIP: 0060:[<c11dd7bd>] EFLAGS: 00010046 CPU: 0
EIP is at list_del+0x1d/0x120
EAX: f57fbd3c EBX: f57fb800 ECX: ffff8000 EDX: 00200200
ESI: f57fbe90 EDI: f57fbd3c EBP: f600bf54 ESP: f600bf3c
DS: 007b ES: 007b FS: 00d8 GS: 0000 SS: 0068
Process ksoftirqd/0 (pid: 3, ti=f600a000 task=f60791c0 task.ti=f6082000)
Stack: c1527e84 00000030 c1527e54 00100100 f57fb800 f57fbd3c f600bf98 f8051fac f8053104 f8052b94 f600bf6c c106dbab f600bf80 00000286 f60791c0 c1042b30 f57fbda8 f57f5800 f57fbdb0 f57fbd80 f57fbe7c c1656b04 00000000 f600bfb0 Call Trace: [<f8051fac>] ? acm_rx_tasklet+0x2dc/0x3e0 [cdc_acm] [<c106dbab>] ? trace_hardirqs_on+0xb/0x10 [<c1042b30>] ? tasklet_action+0x60/0x140 [<c1042bb6>] ? tasklet_action+0xe6/0x140 [<c104342f>] ? __do_softirq+0xaf/0x210 [<c1043380>] ? __do_softirq+0x0/0x210 <IRQ> [<c1042c9a>] ? run_ksoftirqd+0x8a/0x1c0 [<c1042c10>] ? run_ksoftirqd+0x0/0x1c0 [<c105ac24>] ? kthread+0x74/0x80 [<c105abb0>] ? kthread+0x0/0x80 [<c100337a>] ? kernel_thread_helper+0x6/0x10 Code: ff 48 14 e9 57 ff ff ff 90 90 90 90 90 90 55 89 e5 83 ec 18 81 38 00 01 10 00 0f 84 9c 00 00 00 8b 50 04 81 fa 00 02 20 00 74 33 <8b> 12 39 d0 75 5c 8b 10 8b 4a 04 39 c8 0f 85 b5 00 00 00 8b 48 EIP: [<c11dd7bd>] list_del+0x1d/0x120 SS:ESP 0068:f600bf3c CR2: 0000000000200200 ---[ end trace efd9a11434f00831 ]--- Kernel panic - not syncing: Fatal exception in interrupt Pid: 3, comm: ksoftirqd/0 Tainted: G D W 2.6.37+ #39 Call Trace: [<c13fede1>] ? printk+0x1d/0x24 [<c13fecce>] panic+0x66/0x15c [<c10067df>] oops_end+0x8f/0x90 [<c1025476>] no_context+0xc6/0x160 [<c10255a8>] __bad_area_nosemaphore+0x98/0x140 [<c103cf68>] ? release_console_sem+0x1d8/0x210 [<c1025667>] bad_area_nosemaphore+0x17/0x20 [<c1025a49>] do_page_fault+0x279/0x420 [<c1006a8f>] ? show_trace+0x1f/0x30 [<c13fede1>] ? printk+0x1d/0x24 [<c10257d0>] ? do_page_fault+0x0/0x420 [<c140333b>] error_code+0x5f/0x64 [<c103007b>] ? select_task_rq_fair+0x37b/0x6a0 [<c10257d0>] ? do_page_fault+0x0/0x420 [<c11dd7bd>] ? list_del+0x1d/0x120 [<f8051fac>] acm_rx_tasklet+0x2dc/0x3e0 [cdc_acm] [<c106dbab>] ? trace_hardirqs_on+0xb/0x10 [<c1042b30>] ? tasklet_action+0x60/0x140 [<c1042bb6>] tasklet_action+0xe6/0x140 [<c104342f>] __do_softirq+0xaf/0x210 [<c1043380>] ? __do_softirq+0x0/0x210 <IRQ> [<c1042c9a>] ? run_ksoftirqd+0x8a/0x1c0 [<c1042c10>] ? run_ksoftirqd+0x0/0x1c0 [<c105ac24>] ? kthread+0x74/0x80 [<c105abb0>] ? kthread+0x0/0x80 [<c100337a>] ? kernel_thread_helper+0x6/0x10 panic occurred, switching back to text console ------------[ cut here ]------------
--- drivers/usb/class/cdc-acm.c | 2 ++ 1 file changed, 2 insertions(+)
drivers/usb/class/cdc-acm.c +2 -0
@@ -646,8 +646,10 @@ static void acm_port_down(struct acm *acusb_kill_urb (acm->ctrlurb);for (i =0 ; i <ACM_NW ; i++)usb_kill_urb (acm->wb[i].urb); +tasklet_disable (&acm->urb_task);for (i =0 ; i < nr; i++)usb_kill_urb (acm->ru[i].urb); +tasklet_enable (&acm->urb_task); acm->control->needs_remote_wakeup =0 ;usb_autopm_put_interface (acm->control); }
PATCH 40/55 USB: cdc-acm: fix potential null-pointer dereference
In reply to Greg KH2.6.37-stable review patch. If anyone has any objections, please let us know.
------------------
From: Johan Hovold <[email protected]>
commit 15e5bee33ffc11d0e5c6f819a65e7881c5c407be upstream.
Must check return value of tty_port_tty_get.
--- drivers/usb/class/cdc-acm.c | 2 ++ 1 file changed, 2 insertions(+)
drivers/usb/class/cdc-acm.c +2 -0
@@ -533,6 +533,8 @@ static void acm_softint(struct work_struif (!ACM_READY (acm))return ; tty =tty_port_tty_get (&acm->port); +if (!tty) +return ;tty_wakeup (tty);tty_kref_put (tty); }
PATCH 41/55 USB: cdc-acm: fix potential null-pointer dereference on disconnect
In reply to Greg KH2.6.37-stable review patch. If anyone has any objections, please let us know.
------------------
From: Johan Hovold <[email protected]>
commit 7e7797e7f6f7bfab73fca02c65e40eaa5bb9000c upstream.
Fix potential null-pointer exception on disconnect introduced by commit 11ea859d64b69a747d6b060b9ed1520eab1161fe (USB: additional power savings for cdc-acm devices that support remote wakeup).
Only access acm->dev after making sure it is non-null in control urb completion handler.
--- drivers/usb/class/cdc-acm.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-)
drivers/usb/class/cdc-acm.c +2 -1
@@ -297,6 +297,8 @@ static void acm_ctrl_irq(struct urb *urbif (!ACM_READY (acm)) goto exit; +usb_mark_last_busy (acm->dev); + data = (unsigned char *)(dr +1 );switch (dr->bNotificationType) {case USB_CDC_NOTIFY_NETWORK_CONNECTION :
@@ -336,7 +338,6 @@ static void acm_ctrl_irq(struct urb *urbbreak ; } exit: -usb_mark_last_busy (acm->dev); retval =usb_submit_urb (urb,GFP_ATOMIC );if (retval) dev_err(&urb->dev->dev, "%s - usb_submit_urb failed with "
PATCH 42/55 fs: assign sb->s_bdi to default_backing_dev_info if the bdi is going away
In reply to Greg KH2.6.37-stable review patch. If anyone has any objections, please let us know.
------------------
From: Jens Axboe <[email protected]>
commit 95f28604a65b1c40b6c6cd95e58439cd7ded3add upstream.
We don't have proper reference counting for this yet, so we run into cases where the device is pulled and we OOPS on flushing the fs data. This happens even though the dirty inodes have already been migrated to the default_backing_dev_info.
--- fs/super.c | 2 ++ fs/sync.c | 4 ++-- mm/backing-dev.c | 2 +- 3 files changed, 5 insertions(+), 3 deletions(-)
fs/super.c +2 -0
@@ -70,6 +70,7 @@ static struct super_block *alloc_super(s#else INIT_LIST_HEAD (&s->s_files);#endif + s->s_bdi = &default_backing_dev_info;INIT_LIST_HEAD (&s->s_instances);INIT_HLIST_HEAD (&s->s_anon);INIT_LIST_HEAD (&s->s_inodes);
@@ -996,6 +997,7 @@ vfs_kern_mount(struct file_system_type * }BUG_ON (!mnt->mnt_sb);WARN_ON (!mnt->mnt_sb->s_bdi); +WARN_ON (mnt->mnt_sb->s_bdi == &default_backing_dev_info); mnt->mnt_sb->s_flags |=MS_BORN ; error =security_sb_kern_mount (mnt->mnt_sb, flags, secdata);
fs/sync.c +2 -2
@@ -33,7 +33,7 @@ static int __sync_filesystem(struct supe* This should be safe, as we require bdi backing to actually * write out data in the first place */ -if (!sb->s_bdi || sb->s_bdi == &noop_backing_dev_info) +if (sb->s_bdi == &noop_backing_dev_info)return 0 ;if (sb->s_qcop && sb->s_qcop->quota_sync)
@@ -79,7 +79,7 @@ EXPORT_SYMBOL_GPL(sync_filesystem);static void sync_one_sb (struct super_block *sb,void *arg) { -if (!(sb->s_flags &MS_RDONLY ) && sb->s_bdi) +if (!(sb->s_flags &MS_RDONLY ))__sync_filesystem (sb, *(int *)arg); }/*
mm/backing-dev.c +1 -1
@@ -604,7 +604,7 @@ static void bdi_prune_sb(struct backing_spin_lock (&sb_lock);list_for_each_entry (sb, &super_blocks, s_list) {if (sb->s_bdi == bdi) - sb->s_bdi =NULL ; + sb->s_bdi = &default_backing_dev_info; }spin_unlock (&sb_lock); }
PATCH 43/55 Input: xen-kbdfront - advertise either absolute or relative coordinates
In reply to Greg KH2.6.37-stable review patch. If anyone has any objections, please let us know.
------------------
From: Olaf Hering <[email protected]>
commit 8c3c283e6bf463ab498d6e7823aff6c4762314b6 upstream.
A virtualized display device is usually viewed with the vncviewer application, either by 'xm vnc domU' or with vncviewer localhost:port. vncviewer and the RFB protocol provides absolute coordinates to the virtual display. These coordinates are either passed through to a PV guest or converted to relative coordinates for a HVM guest.
A PV guest receives these coordinates and passes them to the kernels evdev driver. There it can be picked up by applications such as the xorg-input drivers. Using absolute coordinates avoids issues such as guest mouse pointer not tracking host mouse pointer due to wrong mouse acceleration settings in the guests X display.
Advertise either absolute or relative coordinates to the input system and the evdev driver, depending on what dom0 provides. The xorg-input driver prefers relative coordinates even if a devices provides both.
--- drivers/input/xen-kbdfront.c | 45 ++++++++++++++++++++++--------------------- 1 file changed, 24 insertions(+), 21 deletions(-)
drivers/input/xen-kbdfront.c +24 -21
@@ -109,7 +109,7 @@ static irqreturn_t input_handler(int rq,static int __devinit xenkbd_probe (struct xenbus_device *dev,const struct xenbus_device_id *id) { -int ret, i; +int ret, i, abs;struct xenkbd_info *info;struct input_dev *kbd, *ptr;
@@ -127,6 +127,11 @@ static int __devinit xenkbd_probe(structif (!info->page) goto error_nomem; +if (xenbus_scanf (XBT_NIL , dev->otherend,"feature-abs-pointer" ,"%d" , &abs) <0 ) + abs =0 ; +if (abs) +xenbus_printf (XBT_NIL , dev->nodename,"request-abs-pointer" ,"1" ); +/* keyboard */ kbd =input_allocate_device ();if (!kbd)
@@ -136,11 +141,12 @@ static int __devinit xenkbd_probe(struct kbd->id.bustype =BUS_PCI ; kbd->id.vendor =0x5853 ; kbd->id.product =0xffff ; - kbd->evbit[0 ] =BIT (EV_KEY ); + +__set_bit (EV_KEY , kbd->evbit);for (i =KEY_ESC ; i <KEY_UNKNOWN ; i++) -set_bit (i, kbd->keybit); +__set_bit (i, kbd->keybit);for (i =KEY_OK ; i <KEY_MAX ; i++) -set_bit (i, kbd->keybit); +__set_bit (i, kbd->keybit); ret =input_register_device (kbd);if (ret) {
@@ -159,12 +165,20 @@ static int __devinit xenkbd_probe(struct ptr->id.bustype =BUS_PCI ; ptr->id.vendor =0x5853 ; ptr->id.product =0xfffe ; - ptr->evbit[0 ] =BIT (EV_KEY ) |BIT (EV_REL ) |BIT (EV_ABS ); + +if (abs) { +__set_bit (EV_ABS , ptr->evbit); +input_set_abs_params (ptr,ABS_X ,0 ,XENFB_WIDTH ,0 ,0 ); +input_set_abs_params (ptr,ABS_Y ,0 ,XENFB_HEIGHT ,0 ,0 ); + }else { +input_set_capability (ptr,EV_REL ,REL_X ); +input_set_capability (ptr,EV_REL ,REL_Y ); + } +input_set_capability (ptr,EV_REL ,REL_WHEEL ); + +__set_bit (EV_KEY , ptr->evbit);for (i =BTN_LEFT ; i <=BTN_TASK ; i++) -set_bit (i, ptr->keybit); - ptr->relbit[0 ] =BIT (REL_X ) |BIT (REL_Y ) |BIT (REL_WHEEL ); -input_set_abs_params (ptr,ABS_X ,0 ,XENFB_WIDTH ,0 ,0 ); -input_set_abs_params (ptr,ABS_Y ,0 ,XENFB_HEIGHT ,0 ,0 ); +__set_bit (i, ptr->keybit); ret =input_register_device (ptr);if (ret) {
@@ -271,7 +285,7 @@ static void xenkbd_backend_changed(struc enum xenbus_state backend_state) {struct xenkbd_info *info =dev_get_drvdata (&dev->dev); -int ret, val; +int val;switch (backend_state) {case XenbusStateInitialising:
@@ -284,17 +298,6 @@ static void xenkbd_backend_changed(struccase XenbusStateInitWait: InitWait: - ret =xenbus_scanf (XBT_NIL , info->xbdev->otherend, -"feature-abs-pointer" ,"%d" , &val); -if (ret <0 ) - val =0 ; -if (val) { - ret =xenbus_printf (XBT_NIL , info->xbdev->nodename, -"request-abs-pointer" ,"1" ); -if (ret) -printk (KERN_WARNING -"xenkbd: can't request abs-pointer" ); - }xenbus_switch_state (dev, XenbusStateConnected);break ;
PATCH 44/55 x86: Cleanup highmap after brk is concluded
In reply to Greg KH2.6.37-stable review patch. If anyone has any objections, please let us know.
------------------
From: Yinghai Lu <[email protected]>
commit e5f15b45ddf3afa2bbbb10c7ea34fb32b6de0a0e upstream.
Now cleanup_highmap actually is in two steps: one is early in head64.c and only clears above _end; a second one is in init_memory_mapping() and tries to clean from _brk_end to _end.
It should check if those boundaries are PMD_SIZE aligned but currently does not.
Also init_memory_mapping() is called several times for numa or memory hotplug, so we really should not handle initial kernel mappings there.
This patch moves cleanup_highmap() down after _brk_end is settled so we can do everything in one step.
Also we honor max_pfn_mapped in the implementation of cleanup_highmap.
LKML-Reference: <alpine.DEB.2.00.1103171739050.3382@kaball-desktop>
--- arch/x86/kernel/head64.c | 3 --- arch/x86/kernel/setup.c | 5 +++++ arch/x86/mm/init.c | 19 ------------------- arch/x86/mm/init_64.c | 11 ++++++----- 4 files changed, 11 insertions(+), 27 deletions(-)
arch/x86/kernel/head64.c +0 -3
@@ -77,9 +77,6 @@ void __init x86_64_start_kernel(char * r/* Make NULL pointers segfault */ zap_identity_mappings (); -/* Cleanup the over mapped high alias */ -cleanup_highmap (); - max_pfn_mapped =KERNEL_IMAGE_SIZE >>PAGE_SHIFT ;for (i =0 ; i <NUM_EXCEPTION_VECTORS ; i++) {
arch/x86/kernel/setup.c +5 -0
@@ -297,6 +297,9 @@ static void __init init_gbpages(void)static inline void init_gbpages (void ) { } +static void __init cleanup_highmap (void ) +{ +}#endif static void __init reserve_brk (void )
@@ -922,6 +925,8 @@ void __init setup_arch(char **cmdline_p)*/ reserve_brk (); +cleanup_highmap (); + memblock.current_limit =get_max_mapped ();memblock_x86_fill ();
arch/x86/mm/init.c +0 -19
@@ -279,25 +279,6 @@ unsigned long __init_refok init_memory_mload_cr3 (swapper_pg_dir);#endif -#ifdef CONFIG_X86_64 -if (!after_bootmem && !start) { -pud_t *pud; -pmd_t *pmd; - - mmu_cr4_features =read_cr4 (); - -/* -* _brk_end cannot change anymore, but it and _end may be -* located on different 2M pages. cleanup_highmap(), however, -* can only consider _end when it runs, so destroy any -* mappings beyond _brk_end here. -*/ - pud =pud_offset (pgd_offset_k (_brk_end), _brk_end); - pmd =pmd_offset (pud, _brk_end -1 ); -while (++pmd <=pmd_offset (pud, (unsigned long )_end -1 )) -pmd_clear (pmd); - } -#endif __flush_tlb_all ();if (!after_bootmem && e820_table_end > e820_table_start)
arch/x86/mm/init_64.c +6 -5
@@ -51,6 +51,7 @@#include <asm/numa.h> #include <asm/cacheflush.h> #include <asm/init.h> +#include <asm/setup.h> static int __init parse_direct_gbpages_off (char *arg) {
@@ -293,18 +294,18 @@ void __init init_extra_mapping_uc(unsign* to the compile time generated pmds. This results in invalid pmds up * to the point where we hit the physaddr 0 mapping. * -* We limit the mappings to the region from _text to _end. _end is -* rounded up to the 2MB boundary. This catches the invalid pmds as +* We limit the mappings to the region from _text to _brk_end. _brk_end +* is rounded up to the 2MB boundary. This catches the invalid pmds as * well, as they are located before _text: */ void __init cleanup_highmap (void ) {unsigned long vaddr = __START_KERNEL_map; -unsigned long end =roundup ((unsigned long )_end,PMD_SIZE ) -1 ; +unsigned long vaddr_end = __START_KERNEL_map + (max_pfn_mapped <<PAGE_SHIFT ); +unsigned long end =roundup ((unsigned long )_brk_end,PMD_SIZE ) -1 ;pmd_t *pmd = level2_kernel_pgt; -pmd_t *last_pmd = pmd +PTRS_PER_PMD ; -for (; pmd < last_pmd; pmd++, vaddr +=PMD_SIZE ) { +for (; vaddr +PMD_SIZE -1 < vaddr_end; pmd++, vaddr +=PMD_SIZE ) {if (pmd_none (*pmd))continue ;if (vaddr < (unsigned long ) _text || vaddr > end)
PATCH 45/55 drm: check for modesetting on modeset ioctls
In reply to Greg KH2.6.37-stable review patch. If anyone has any objections, please let us know.
------------------
From: Dave Airlie <[email protected]>
commit fb3b06c8a1fd1a80298f13b738ab38ef8c73baff upstream.
Noticed this while working on some other things, helps if we check for modeset enabled on modesetting ioctls.
--- drivers/gpu/drm/drm_crtc.c | 51 +++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 51 insertions(+)
drivers/gpu/drm/drm_crtc.c +51 -0
@@ -1073,6 +1073,9 @@ int drm_mode_getresources(struct drm_devuint32_t __user *encoder_id;struct drm_mode_group *mode_group; +if (!drm_core_check_feature (dev,DRIVER_MODESET )) +return -EINVAL ; +mutex_lock (&dev->mode_config.mutex);/*
@@ -1244,6 +1247,9 @@ int drm_mode_getcrtc(struct drm_device *struct drm_mode_object *obj;int ret =0 ; +if (!drm_core_check_feature (dev,DRIVER_MODESET )) +return -EINVAL ; +mutex_lock (&dev->mode_config.mutex); obj = drm_mode_object_find(dev, crtc_resp->crtc_id,
@@ -1312,6 +1318,9 @@ int drm_mode_getconnector(struct drm_devuint64_t __user *prop_values;uint32_t __user *encoder_ptr; +if (!drm_core_check_feature (dev,DRIVER_MODESET )) +return -EINVAL ; +memset (&u_mode,0 ,sizeof (struct drm_mode_modeinfo ));DRM_DEBUG_KMS ("[CONNECTOR:%d:?]\n" , out_resp->connector_id);
@@ -1431,6 +1440,9 @@ int drm_mode_getencoder(struct drm_devicstruct drm_encoder *encoder;int ret =0 ; +if (!drm_core_check_feature (dev,DRIVER_MODESET )) +return -EINVAL ; +mutex_lock (&dev->mode_config.mutex); obj =drm_mode_object_find (dev, enc_resp->encoder_id,DRM_MODE_OBJECT_ENCODER );
@@ -1486,6 +1498,9 @@ int drm_mode_setcrtc(struct drm_device *int ret =0 ;int i; +if (!drm_core_check_feature (dev,DRIVER_MODESET )) +return -EINVAL ; +mutex_lock (&dev->mode_config.mutex); obj =drm_mode_object_find (dev, crtc_req->crtc_id,DRM_MODE_OBJECT_CRTC );
@@ -1603,6 +1618,9 @@ int drm_mode_cursor_ioctl(struct drm_devstruct drm_crtc *crtc;int ret =0 ; +if (!drm_core_check_feature (dev,DRIVER_MODESET )) +return -EINVAL ; +if (!req->flags) {DRM_ERROR ("no operation set\n" );return -EINVAL ;
@@ -1667,6 +1685,9 @@ int drm_mode_addfb(struct drm_device *destruct drm_framebuffer *fb;int ret =0 ; +if (!drm_core_check_feature (dev,DRIVER_MODESET )) +return -EINVAL ; +if ((config->min_width > r->width) || (r->width > config->max_width)) {DRM_ERROR ("mode new framebuffer width not within limits\n" );return -EINVAL ;
@@ -1724,6 +1745,9 @@ int drm_mode_rmfb(struct drm_device *devint ret =0 ;int found =0 ; +if (!drm_core_check_feature (dev,DRIVER_MODESET )) +return -EINVAL ; +mutex_lock (&dev->mode_config.mutex); obj =drm_mode_object_find (dev, *id,DRM_MODE_OBJECT_FB );/* TODO check that we realy get a framebuffer back. */
@@ -1780,6 +1804,9 @@ int drm_mode_getfb(struct drm_device *destruct drm_framebuffer *fb;int ret =0 ; +if (!drm_core_check_feature (dev,DRIVER_MODESET )) +return -EINVAL ; +mutex_lock (&dev->mode_config.mutex); obj =drm_mode_object_find (dev, r->fb_id,DRM_MODE_OBJECT_FB );if (!obj) {
@@ -1813,6 +1840,9 @@ int drm_mode_dirtyfb_ioctl(struct drm_deint num_clips;int ret =0 ; +if (!drm_core_check_feature (dev,DRIVER_MODESET )) +return -EINVAL ; +mutex_lock (&dev->mode_config.mutex); obj =drm_mode_object_find (dev, r->fb_id,DRM_MODE_OBJECT_FB );if (!obj) {
@@ -1996,6 +2026,9 @@ int drm_mode_attachmode_ioctl(struct drmstruct drm_mode_modeinfo *umode = &mode_cmd->mode;int ret =0 ; +if (!drm_core_check_feature (dev,DRIVER_MODESET )) +return -EINVAL ; +mutex_lock (&dev->mode_config.mutex); obj =drm_mode_object_find (dev, mode_cmd->connector_id,DRM_MODE_OBJECT_CONNECTOR );
@@ -2042,6 +2075,9 @@ int drm_mode_detachmode_ioctl(struct drmstruct drm_mode_modeinfo *umode = &mode_cmd->mode;int ret =0 ; +if (!drm_core_check_feature (dev,DRIVER_MODESET )) +return -EINVAL ; +mutex_lock (&dev->mode_config.mutex); obj =drm_mode_object_find (dev, mode_cmd->connector_id,DRM_MODE_OBJECT_CONNECTOR );
@@ -2211,6 +2247,9 @@ int drm_mode_getproperty_ioctl(struct druint64_t __user *values_ptr;uint32_t __user *blob_length_ptr; +if (!drm_core_check_feature (dev,DRIVER_MODESET )) +return -EINVAL ; +mutex_lock (&dev->mode_config.mutex); obj =drm_mode_object_find (dev, out_resp->prop_id,DRM_MODE_OBJECT_PROPERTY );if (!obj) {
@@ -2333,6 +2372,9 @@ int drm_mode_getblob_ioctl(struct drm_deint ret =0 ;void *blob_ptr; +if (!drm_core_check_feature (dev,DRIVER_MODESET )) +return -EINVAL ; +mutex_lock (&dev->mode_config.mutex); obj =drm_mode_object_find (dev, out_resp->blob_id,DRM_MODE_OBJECT_BLOB );if (!obj) {
@@ -2393,6 +2435,9 @@ int drm_mode_connector_property_set_ioctint ret = -EINVAL ;int i; +if (!drm_core_check_feature (dev,DRIVER_MODESET )) +return -EINVAL ; +mutex_lock (&dev->mode_config.mutex); obj =drm_mode_object_find (dev, out_resp->connector_id,DRM_MODE_OBJECT_CONNECTOR );
@@ -2509,6 +2554,9 @@ int drm_mode_gamma_set_ioctl(struct drm_int size;int ret =0 ; +if (!drm_core_check_feature (dev,DRIVER_MODESET )) +return -EINVAL ; +mutex_lock (&dev->mode_config.mutex); obj =drm_mode_object_find (dev, crtc_lut->crtc_id,DRM_MODE_OBJECT_CRTC );if (!obj) {
@@ -2560,6 +2608,9 @@ int drm_mode_gamma_get_ioctl(struct drm_int size;int ret =0 ; +if (!drm_core_check_feature (dev,DRIVER_MODESET )) +return -EINVAL ; +mutex_lock (&dev->mode_config.mutex); obj =drm_mode_object_find (dev, crtc_lut->crtc_id,DRM_MODE_OBJECT_CRTC );if (!obj) {
PATCH 46/55 drm/i915: Prevent racy removal of request from client list
In reply to Greg KH2.6.37-stable review patch. If anyone has any objections, please let us know.
------------------
From: Herton Ronaldo Krzesinski <[email protected]>
commit 09bfa51773c1e90f13000dc2fc0c4b84047009bc upstream.
When i915_gem_retire_requests_ring calls i915_gem_request_remove_from_client, the client_list for that request may already be removed in i915_gem_release. So we may call twice list_del(&request->client_list), resulting in an oops like this report:
[126167.230394] BUG: unable to handle kernel paging request at 00100104 [126167.230699] IP: [<f8c2ce44>] i915_gem_retire_requests_ring+0xd4/0x240 [i915] [126167.231042] *pdpt = 00000000314c1001 *pde = 0000000000000000 [126167.231314] Oops: 0002 [#1] SMP [126167.231471] last sysfs file: /sys/devices/LNXSYSTM:00/device:00/PNP0C0A:00/power_supply/BAT1/current_now [126167.231901] Modules linked in: snd_seq_dummy nls_utf8 isofs btrfs zlib_deflate libcrc32c ufs qnx4 hfsplus hfs minix ntfs vfat msdos fat jfs xfs exportfs reiserfs cryptd aes_i586 aes_generic binfmt_misc vboxnetadp vboxnetflt vboxdrv parport_pc ppdev snd_hda_codec_hdmi snd_hda_codec_conexant snd_hda_intel snd_hda_codec snd_hwdep arc4 snd_pcm snd_seq_midi snd_rawmidi snd_seq_midi_event snd_seq uvcvideo videodev snd_timer snd_seq_device joydev iwlagn iwlcore mac80211 snd cfg80211 soundcore i915 drm_kms_helper snd_page_alloc psmouse drm serio_raw i2c_algo_bit video lp parport usbhid hid sky2 sdhci_pci ahci sdhci libahci [126167.232018] [126167.232018] Pid: 1101, comm: Xorg Not tainted 2.6.38-6-generic-pae #34-Ubuntu Gateway MC7833U / [126167.232018] EIP: 0060:[<f8c2ce44>] EFLAGS: 00213246 CPU: 0 [126167.232018] EIP is at i915_gem_retire_requests_ring+0xd4/0x240 [i915] [126167.232018] EAX: 00200200 EBX: f1ac25b0 ECX: 00000040 EDX: 00100100 [126167.232018] ESI: f1a2801c EDI: e87fc060 EBP: ef4d7dd8 ESP: ef4d7db0 [126167.232018] DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068 [126167.232018] Process Xorg (pid: 1101, ti=ef4d6000 task=f1ba6500 task.ti=ef4d6000) [126167.232018] Stack: [126167.232018] f1a28000 f1a2809c f1a28094 0058bd97 f1aa2400 f1a2801c 0058bd7b 0058bd85 [126167.232018] f1a2801c f1a28000 ef4d7e38 f8c2e995 ef4d7e30 ef4d7e60 c14d1ebc f6b3a040 [126167.232018] f1522cc0 000000db 00000000 f1ba6500 ffffffa1 00000000 00000001 f1a29214 [126167.232018] Call Trace:
Unfortunately the call trace reported was cut, but looking at debug symbols the crash is at __list_del, when probably list_del is called twice on the same request->client_list, as the dereferenced value is LIST_POISON1 + 4, and by looking more at the debug symbols before list_del call it should have being called by i915_gem_request_remove_from_client
And as I can see in the code, it seems we indeed have the possibility to remove a request->client_list twice, which would cause the above, because we do list_del(&request->client_list) on both i915_gem_request_remove_from_client and i915_gem_release
As Chris Wilson pointed out, it's indeed the case:
"(...) I had thought that the actual insertion/deletion was serialised under the struct mutex and the intention of the spinlock was to protect the unlocked list traversal during throttling. However, I missed that i915_gem_release() is also called without struct mutex and so we do need the double check for i915_gem_request_remove_from_client()."
This change does the required check to avoid the duplicate remove of request->client_list.
Bugzilla: http://bugs.launchpad.net/bugs/733780
--- drivers/gpu/drm/i915/i915_gem.c | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-)
drivers/gpu/drm/i915/i915_gem.c +4 -2
@@ -1748,8 +1748,10 @@ i915_gem_request_remove_from_client(strureturn ;spin_lock (&file_priv->mm.lock); -list_del (&request->client_list); - request->file_priv =NULL ; +if (request->file_priv) { +list_del (&request->client_list); + request->file_priv =NULL ; + }spin_unlock (&file_priv->mm.lock); }
PATCH 47/55 drm: Fix use-after-free in drm_gem_vm_close()
In reply to Greg KH2.6.37-stable review patch. If anyone has any objections, please let us know.
------------------
From: Chris Wilson <[email protected]>
commit b74ad5ae14def5e81ad0be3dddb96e485b861b1b upstream.
As we may release the last reference, we need to store the device in a local variable in order to unlock afterwards.
[ 60.140768] BUG: unable to handle kernel paging request at 6b6b6b9f [ 60.140973] IP: [<c1536d11>] __mutex_unlock_slowpath+0x5a/0x111 [ 60.141014] *pdpt = 0000000024a54001 *pde = 0000000000000000 [ 60.141014] Oops: 0002 [#1] PREEMPT SMP [ 60.141014] last sysfs file: /sys/devices/LNXSYSTM:00/device:00/PNP0A08:00/PNP0C0A:00/power_supply/BAT0/voltage_now [ 60.141014] Modules linked in: uvcvideo ath9k pegasus ath9k_common ath9k_hw hid_egalax ath3k joydev asus_laptop sparse_keymap battery input_polldev [ 60.141014] [ 60.141014] Pid: 771, comm: meego-ux-daemon Not tainted 2.6.37.2-7.1 #1 EXOPC EXOPG06411/EXOPG06411 [ 60.141014] EIP: 0060:[<c1536d11>] EFLAGS: 00010046 CPU: 0 [ 60.141014] EIP is at __mutex_unlock_slowpath+0x5a/0x111 [ 60.141014] EAX: 00000100 EBX: 6b6b6b9b ECX: e9b4a1b0 EDX: e4a4e580 [ 60.141014] ESI: db162558 EDI: 00000246 EBP: e480be50 ESP: e480be44 [ 60.141014] DS: 007b ES: 007b FS: 00d8 GS: 0000 SS: 0068 [ 60.141014] Process meego-ux-daemon (pid: 771, ti=e480a000 task=e9b4a1b0 task.ti=e480a000) [ 60.141014] Stack: [ 60.141014] e4a4e580 db162558 f5a2f838 e480be58 c1536dd0 e480be68 c125ab1b db162558 [ 60.141014] db1624e0 e480be78 c10ba071 db162558 f760241c e480be94 c10bb0bc 000155fe [ 60.141014] f760241c f5a2f838 f5a2f8c8 00000000 e480bea4 c1037c24 00000000 f5a2f838 [ 60.141014] Call Trace: [ 60.141014] [<c1536dd0>] ? mutex_unlock+0x8/0xa [ 60.141014] [<c125ab1b>] ? drm_gem_vm_close+0x39/0x3d [ 60.141014] [<c10ba071>] ? remove_vma+0x2d/0x58 [ 60.141014] [<c10bb0bc>] ? exit_mmap+0x126/0x13f [ 60.141014] [<c1037c24>] ? mmput+0x37/0x9a [ 60.141014] [<c10d450d>] ? exec_mmap+0x178/0x19c [ 60.141014] [<c1537f85>] ? _raw_spin_unlock+0x1d/0x36 [ 60.141014] [<c10d4eb0>] ? flush_old_exec+0x42/0x75 [ 60.141014] [<c1104442>] ? load_elf_binary+0x32a/0x922 [ 60.141014] [<c10d3f76>] ? search_binary_handler+0x200/0x2ea [ 60.141014] [<c10d3ecf>] ? search_binary_handler+0x159/0x2ea [ 60.141014] [<c1104118>] ? load_elf_binary+0x0/0x922 [ 60.141014] [<c10d56b2>] ? do_execve+0x1ff/0x2e6 [ 60.141014] [<c100970e>] ? sys_execve+0x2d/0x55 [ 60.141014] [<c1002a5a>] ? ptregs_execve+0x12/0x18 [ 60.141014] [<c10029dc>] ? sysenter_do_call+0x12/0x3c [ 60.141014] [<c1530000>] ? init_centaur+0x9c/0x1ba [ 60.141014] Code: c1 00 75 0f ba 38 01 00 00 b8 8c 3a 6c c1 e8 cc 2e b0 ff 9c 58 8d 74 26 00 89 c7 fa 90 8d 74 26 00 e8 d2 b4 b2 ff b8 00 01 00 00 <f0> 66 0f c1 43 04 38 e0 74 07 f3 90 8a 43 04 eb f5 83 3d 64 ef [ 60.141014] EIP: [<c1536d11>] __mutex_unlock_slowpath+0x5a/0x111 SS:ESP 0068:e480be44 [ 60.141014] CR2: 000000006b6b6b9f
--- drivers/gpu/drm/drm_gem.c | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-)
drivers/gpu/drm/drm_gem.c +3 -2
@@ -498,11 +498,12 @@ EXPORT_SYMBOL(drm_gem_vm_open);void drm_gem_vm_close (struct vm_area_struct *vma) {struct drm_gem_object *obj = vma->vm_private_data; +struct drm_device *dev = obj->dev; -mutex_lock (&obj->dev->struct_mutex); +mutex_lock (&dev->struct_mutex);drm_vm_close_locked (vma);drm_gem_object_unreference (obj); -mutex_unlock (&obj->dev->struct_mutex); +mutex_unlock (&dev->struct_mutex); }EXPORT_SYMBOL (drm_gem_vm_close);
PATCH 48/55 drm/radeon/kms: prefer legacy pll algo for tv-out
In reply to Greg KH2.6.37-stable review patch. If anyone has any objections, please let us know.
------------------
From: Alex Deucher <[email protected]>
commit 64146f8b2af1ba77fe3c21d9d6d7213b9bb72b40 upstream.
ntsc seems to work fine with either algo, some pal TVs seem pickier.
Fixes:
https://bugzilla.kernel.org/show_bug.cgi?id=30832
--- drivers/gpu/drm/radeon/atombios_crtc.c | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-)
drivers/gpu/drm/radeon/atombios_crtc.c +5 -1
@@ -921,7 +921,11 @@ static void atombios_crtc_set_pll(struct/* adjust pixel clock as needed */ adjusted_clock =atombios_adjust_pll (crtc, mode, pll, ss_enabled, &ss); -if (ASIC_IS_AVIVO (rdev)) +if (radeon_encoder->active_device & (ATOM_DEVICE_TV_SUPPORT )) +/* TV seems to prefer the legacy algo on some boards */ +radeon_compute_pll_legacy (pll, adjusted_clock, &pll_clock, &fb_div, &frac_fb_div, + &ref_div, &post_div); +else if (ASIC_IS_AVIVO (rdev))radeon_compute_pll_avivo (pll, adjusted_clock, &pll_clock, &fb_div, &frac_fb_div, &ref_div, &post_div);else
PATCH 49/55 drm/radeon/kms: fix hardcoded EDID handling
In reply to Greg KH2.6.37-stable review patch. If anyone has any objections, please let us know.
------------------
From: Alex Deucher <[email protected]>
commit fafcf94e2b5732d1e13b440291c53115d2b172e9 upstream.
On some servers there is a hardcoded EDID provided in the vbios so that the driver will always see a display connected even if something like a KVM prevents traditional means like DDC or load detection from working properly. Also most server boards with DVI are not actually DVI, but DVO connected to a virtual KVM service processor. If we fail to detect a monitor via DDC or load detection and a hardcoded EDID is available, use it.
Additionally, when using the hardcoded EDID, use a copy of it rather than the actual one stored in the driver as the detect() and get_modes() functions may free it if DDC is successful.
This fixes the virtual KVM on several internal servers.
--- drivers/gpu/drm/radeon/radeon_combios.c | 21 +++++++++++++++----- drivers/gpu/drm/radeon/radeon_connectors.c | 30 +++++++++++++++++++++++++++-- drivers/gpu/drm/radeon/radeon_mode.h | 1 3 files changed, 45 insertions(+), 7 deletions(-)
drivers/gpu/drm/radeon/radeon_combios.c +16 -5
@@ -448,7 +448,7 @@ static uint16_t combios_get_table_offsetbool radeon_combios_check_hardcoded_edid (struct radeon_device *rdev) { -int edid_info; +int edid_info, size;struct edid *edid;unsigned char *raw; edid_info =combios_get_table_offset (rdev->ddev,COMBIOS_HARDCODED_EDID_TABLE );
@@ -456,11 +456,12 @@ bool radeon_combios_check_hardcoded_edidreturn false; raw = rdev->bios + edid_info; - edid =kmalloc (EDID_LENGTH * (raw[0x7e ] +1 ),GFP_KERNEL ); + size =EDID_LENGTH * (raw[0x7e ] +1 ); + edid =kmalloc (size,GFP_KERNEL );if (edid ==NULL )return false; -memcpy ((unsigned char *)edid, raw,EDID_LENGTH * (raw[0x7e ] +1 )); +memcpy ((unsigned char *)edid, raw, size);if (!drm_edid_is_valid (edid)) {kfree (edid);
@@ -468,14 +469,24 @@ bool radeon_combios_check_hardcoded_edid } rdev->mode_info.bios_hardcoded_edid = edid; + rdev->mode_info.bios_hardcoded_edid_size = size;return true; }struct edid *radeon_combios_get_hardcoded_edid (struct radeon_device *rdev) { -if (rdev->mode_info.bios_hardcoded_edid) -return rdev->mode_info.bios_hardcoded_edid; +struct edid *edid; + +if (rdev->mode_info.bios_hardcoded_edid) { + edid =kmalloc (rdev->mode_info.bios_hardcoded_edid_size,GFP_KERNEL ); +if (edid) { +memcpy ((unsigned char *)edid, + (unsigned char *)rdev->mode_info.bios_hardcoded_edid, + rdev->mode_info.bios_hardcoded_edid_size); +return edid; + } + }return NULL ; }
drivers/gpu/drm/radeon/radeon_connectors.c +28 -2
@@ -626,6 +626,8 @@ static int radeon_vga_mode_valid(structstatic enum drm_connector_status radeon_vga_detect (struct drm_connector *connector,bool force) { +struct drm_device *dev = connector->dev; +struct radeon_device *rdev = dev->dev_private;struct radeon_connector *radeon_connector =to_radeon_connector (connector);struct drm_encoder *encoder;struct drm_encoder_helper_funcs *encoder_funcs;
@@ -676,6 +678,17 @@ radeon_vga_detect(struct drm_connector *if (ret == connector_status_connected) ret =radeon_connector_analog_encoder_conflict_solve (connector, encoder, ret, true); + +/* RN50 and some RV100 asics in servers often have a hardcoded EDID in the +* vbios to deal with KVMs. If we have one and are not able to detect a monitor +* by other means, assume the CRT is connected and use that EDID. +*/ +if ((!rdev->is_atom_bios) && + (ret == connector_status_disconnected) && + rdev->mode_info.bios_hardcoded_edid_size) { + ret = connector_status_connected; + } +radeon_connector_update_scratch_regs (connector, ret);return ret; }
@@ -787,6 +800,8 @@ static int radeon_dvi_get_modes(struct dstatic enum drm_connector_status radeon_dvi_detect (struct drm_connector *connector,bool force) { +struct drm_device *dev = connector->dev; +struct radeon_device *rdev = dev->dev_private;struct radeon_connector *radeon_connector =to_radeon_connector (connector);struct drm_encoder *encoder =NULL ;struct drm_encoder_helper_funcs *encoder_funcs;
@@ -826,8 +841,6 @@ radeon_dvi_detect(struct drm_connector ** you don't really know what's connected to which port as both are digital. */ if (radeon_connector->shared_ddc && (ret == connector_status_connected)) { -struct drm_device *dev = connector->dev; -struct radeon_device *rdev = dev->dev_private;struct drm_connector *list_connector;struct radeon_connector *list_radeon_connector;list_for_each_entry (list_connector, &dev->mode_config.connector_list, head) {
@@ -892,6 +905,19 @@ radeon_dvi_detect(struct drm_connector * ret =radeon_connector_analog_encoder_conflict_solve (connector, encoder, ret, true); } +/* RN50 and some RV100 asics in servers often have a hardcoded EDID in the +* vbios to deal with KVMs. If we have one and are not able to detect a monitor +* by other means, assume the DFP is connected and use that EDID. In most +* cases the DVI port is actually a virtual KVM port connected to the service +* processor. +*/ +if ((!rdev->is_atom_bios) && + (ret == connector_status_disconnected) && + rdev->mode_info.bios_hardcoded_edid_size) { + radeon_connector->use_digital = true; + ret = connector_status_connected; + } + out:/* updated in get modes as well since we need to know if it's analog or digital */ radeon_connector_update_scratch_regs (connector, ret);
drivers/gpu/drm/radeon/radeon_mode.h +1 -0
@@ -239,6 +239,7 @@ struct radeon_mode_info {struct drm_property *underscan_vborder_property;/* hardcoded DFP edid from BIOS */ struct edid *bios_hardcoded_edid; +int bios_hardcoded_edid_size;/* pointer to fbdev info structure */ struct radeon_fbdev *rfbdev;
PATCH 50/55 perf: Fix tear-down of inherited group events
In reply to Greg KH2.6.37-stable review patch. If anyone has any objections, please let us know.
------------------
From: Peter Zijlstra <[email protected]>
commit 38b435b16c36b0d863efcf3f07b34a6fac9873fd upstream.
When destroying inherited events, we need to destroy groups too, otherwise the event iteration in perf_event_exit_task_context() will miss group siblings and we leak events with all the consequences.
LKML-Reference: <1300196470.2203.61.camel@twins>
--- kernel/perf_event.c | 13 ++++++++----- 1 file changed, 8 insertions(+), 5 deletions(-)
kernel/perf_event.c +8 -5
@@ -5863,17 +5863,20 @@ __perf_event_exit_task(struct perf_event struct perf_event_context *child_ctx, struct task_struct *child) { - struct perf_event *parent_event; +if (child_event->parent) { +raw_spin_lock_irq (&child_ctx->lock); +perf_group_detach (child_event); +raw_spin_unlock_irq (&child_ctx->lock); + }perf_event_remove_from_context (child_event); - parent_event = child_event->parent;/* -* It can happen that parent exits first, and has events +* It can happen that the parent exits first, and has events * that are still around due to the child reference. These -* events need to be zapped - but otherwise linger. +* events need to be zapped. */ -if (parent_event) { +if (child_event->parent) {sync_child_event (child_event, child);free_event (child_event); }
PATCH 51/55 NFS: Fix a hang/infinite loop in nfs_wb_page()
In reply to Greg KH2.6.37-stable review patch. If anyone has any objections, please let us know.
------------------
From: Trond Myklebust <[email protected]>
commit b8413f98f997bb3ed7327e6d7117e7e91ce010c3 upstream.
When one of the two waits in nfs_commit_inode() is interrupted, it returns a non-negative value, which causes nfs_wb_page() to think that the operation was successful causing it to busy-loop rather than exiting.
It also causes nfs_file_fsync() to incorrectly report the file as being successfully committed to disk.
This patch fixes both problems by ensuring that we return an error if the attempts to wait fail.
--- fs/nfs/write.c | 31 +++++++++++++++++++------------ 1 file changed, 19 insertions(+), 12 deletions(-)
fs/nfs/write.c +19 -12
@@ -1214,13 +1214,17 @@ int nfs_writeback_done(struct rpc_task *#if defined(CONFIG_NFS_V3 ) || defined(CONFIG_NFS_V4 )static int nfs_commit_set_lock (struct nfs_inode *nfsi,int may_wait) { +int ret; +if (!test_and_set_bit (NFS_INO_COMMIT , &nfsi->flags))return 1 ; -if (may_wait && !out_of_line_wait_on_bit_lock (&nfsi->flags, -NFS_INO_COMMIT , nfs_wait_bit_killable, -TASK_KILLABLE )) -return 1 ; -return 0 ; +if (!may_wait) +return 0 ; + ret =out_of_line_wait_on_bit_lock (&nfsi->flags, +NFS_INO_COMMIT , + nfs_wait_bit_killable, +TASK_KILLABLE ); +return (ret <0 ) ? ret :1 ; }static void nfs_commit_clear_lock (struct nfs_inode *nfsi)
@@ -1394,9 +1398,10 @@ int nfs_commit_inode(struct inode *inode {LIST_HEAD (head);int may_wait = how &FLUSH_SYNC ; -int res =0 ; +int res; -if (!nfs_commit_set_lock (NFS_I (inode), may_wait)) + res =nfs_commit_set_lock (NFS_I (inode), may_wait); +if (res <=0 ) goto out_mark_dirty;spin_lock (&inode->i_lock); res =nfs_scan_commit (inode, &head,0 ,0 );
@@ -1405,12 +1410,14 @@ int nfs_commit_inode(struct inode *inodeint error =nfs_commit_list (inode, &head, how);if (error <0 )return error; -if (may_wait) -wait_on_bit (&NFS_I (inode)->flags,NFS_INO_COMMIT , - nfs_wait_bit_killable, -TASK_KILLABLE ); -else +if (!may_wait) goto out_mark_dirty; + error =wait_on_bit (&NFS_I (inode)->flags, +NFS_INO_COMMIT , + nfs_wait_bit_killable, +TASK_KILLABLE ); +if (error <0 ) +return error; }else nfs_commit_clear_lock (NFS_I (inode));return res;
PATCH 52/55 SUNRPC: Never reuse the socket port after an xs_close()
In reply to Greg KH2.6.37-stable review patch. If anyone has any objections, please let us know.
------------------
From: Trond Myklebust <[email protected]>
commit 246408dcd5dfeef2df437ccb0ef4d6ee87805f58 upstream.
If we call xs_close(), we're in one of two situations:
- Autoclose, which means we don't expect to resend a request
- bind+connect failed, which probably means the port is in use
--- net/sunrpc/xprtsock.c | 2 ++ 1 file changed, 2 insertions(+)
net/sunrpc/xprtsock.c +2 -0
@@ -710,6 +710,8 @@ static void xs_reset_transport(struct soif (sk ==NULL )return ; + transport->srcport =0 ; +write_lock_bh (&sk->sk_callback_lock); transport->inet =NULL ; transport->sock =NULL ;
PATCH 53/55 fs: call security_d_instantiate in d_obtain_alias V2
In reply to Greg KH2.6.37-stable review patch. If anyone has any objections, please let us know.
------------------
From: Josef Bacik <[email protected]>
commit 24ff6663ccfdaf088dfa7acae489cb11ed4f43c4 upstream.
While trying to track down some NFS problems with BTRFS, I kept noticing I was getting -EACCESS for no apparent reason. Eric Paris and printk() helped me figure out that it was SELinux that was giving me grief, with the following denial
type=AVC msg=audit(1290013638.413:95): avc: denied { 0x800000 } for pid=1772 comm="nfsd" name="" dev=sda1 ino=256 scontext=system_u:system_r:kernel_t:s0 tcontext=system_u:object_r:unlabeled_t:s0 tclass=file
Turns out this is because in d_obtain_alias if we can't find an alias we create one and do all the normal instantiation stuff, but we don't do the security_d_instantiate.
Usually we are protected from getting a hashed dentry that hasn't yet run security_d_instantiate() by the parent's i_mutex, but obviously this isn't an option there, so in order to deal with the case that a second thread comes in and finds our new dentry before we get to run security_d_instantiate(), we go ahead and call it if we find a dentry already. Eric assures me that this is ok as the code checks to see if the dentry has been initialized already so calling security_d_instantiate() against the same dentry multiple times is ok. With this patch I'm no longer getting errant -EACCESS values.
--- fs/dcache.c | 3 +++ 1 file changed, 3 insertions(+)
fs/dcache.c +3 -0
@@ -1201,9 +1201,12 @@ struct dentry *d_obtain_alias(struct inospin_unlock (&tmp->d_lock);spin_unlock (&dcache_lock); +security_d_instantiate (tmp, inode);return tmp; out_iput: +if (res && !IS_ERR (res)) +security_d_instantiate (res, inode);iput (inode);return res; }
PATCH 54/55 dcdbas: force SMI to happen when expected
In reply to Greg KH2.6.37-stable review patch. If anyone has any objections, please let us know.
------------------
From: Stuart Hayes <[email protected]>
commit dd65c736d1b5312c80c88a64bf521db4959eded5 upstream.
The dcdbas driver can do an I/O write to cause a SMI to occur. The SMI handler looks at certain registers and memory locations, so the SMI needs to happen immediately. On some systems I/O writes are posted, though, causing the SMI to happen well after the "outb" occurred, which causes random failures. Following the "outb" with an "inb" forces the write to go through even if it is posted.
--- drivers/firmware/dcdbas.c | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-)
drivers/firmware/dcdbas.c +3 -1
@@ -268,8 +268,10 @@ int dcdbas_smi_request(struct smi_cmd *s }/* generate SMI */ +/* inb to force posted write through and make SMI happen now */ asm volatile ( - "outb %b0,%w1" + "outb %b0,%w1\n" + "inb %w1" : /* no output args */ : "a" (smi_cmd->command_code), "d" (smi_cmd->command_address),
PATCH 55/55 ext4: skip orphan cleanup if fs has unknown ROCOMPAT features
In reply to Greg KH2.6.37-stable review patch. If anyone has any objections, please let us know.
------------------
From: Amir Goldstein <[email protected]>
commit d39195c33bb1b5fdcb0f416e8a0b34bfdb07a027 upstream.
Orphan cleanup is currently executed even if the file system has some number of unknown ROCOMPAT features, which deletes inodes and frees blocks, which could be very bad for some RO_COMPAT features, especially the SNAPSHOT feature.
This patch skips the orphan cleanup if it contains readonly compatible features not known by this ext4 implementation, which would prevent the fs from being mounted (or remounted) readwrite.
--- fs/ext4/super.c | 8 ++++++++ 1 file changed, 8 insertions(+)
fs/ext4/super.c +8 -0
@@ -75,6 +75,7 @@ static void ext4_write_super(struct supestatic int ext4_freeze (struct super_block *sb);static struct dentry *ext4_mount (struct file_system_type *fs_type,int flags,const char *dev_name,void *data); +static int ext4_feature_set_ok (struct super_block *sb,int readonly);static void ext4_destroy_lazyinit_thread (void );static void ext4_unregister_li_request (struct super_block *sb);static void ext4_clear_request_list (void );
@@ -2107,6 +2108,13 @@ static void ext4_orphan_cleanup(struct sreturn ; } +/* Check if feature set would not allow a r/w mount */ +if (!ext4_feature_set_ok (sb,0 )) { +ext4_msg (sb,KERN_INFO ,"Skipping orphan cleanup due to " +"unknown ROCOMPAT features" ); +return ; + } +if (EXT4_SB (sb)->s_mount_state &EXT4_ERROR_FS ) {if (es->s_last_orphan) jbd_debug(1, "Errors on filesystem, "