)]}' { "log": [ { "commit": "136d76de5b72b4a45eec80e4e5ee14f397aa1fed", "tree": "80fb7a9d156401590fa78da5bc35d9ea80b8713c", "parents": [ "0530082c3595511fa2bfc1434a5ad809e5ec90a3" ], "author": { "name": "Guillaume Nault", "email": "g.nault@alphalink.fr", "time": "Fri Mar 01 05:02:02 2013 +0000" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Wed Mar 20 13:05:01 2013 -0700" }, "message": "l2tp: Restore socket refcount when sendmsg succeeds\n\n[ Upstream commit 8b82547e33e85fc24d4d172a93c796de1fefa81a ]\n\nThe sendmsg() syscall handler for PPPoL2TP doesn\u0027t decrease the socket\nreference counter after successful transmissions. Any successful\nsendmsg() call from userspace will then increase the reference counter\nforever, thus preventing the kernel\u0027s session and tunnel data from\nbeing freed later on.\n\nThe problem only happens when writing directly on L2TP sockets.\nPPP sockets attached to L2TP are unaffected as the PPP subsystem\nuses pppol2tp_xmit() which symmetrically increase/decrease reference\ncounters.\n\nThis patch adds the missing call to sock_put() before returning from\npppol2tp_sendmsg().\n\nSigned-off-by: Guillaume Nault \u003cg.nault@alphalink.fr\u003e\nSigned-off-by: David S. Miller \u003cdavem@davemloft.net\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n" }, { "commit": "0530082c3595511fa2bfc1434a5ad809e5ec90a3", "tree": "8ff0366e6bfc136bd5e4f65bce642e22bb4599e5", "parents": [ "51dfcbf53c4cc6b1a65a99f27cec3311531b982b" ], "author": { "name": "Stéphane Marchesin", "email": "marcheu@chromium.org", "time": "Tue Jan 29 19:41:59 2013 -0800" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Wed Mar 20 13:05:01 2013 -0700" }, "message": "drm/i915: Increase the RC6p threshold.\n\ncommit 0920a48719f1ceefc909387a64f97563848c7854 upstream.\n\nThis increases GEN6_RC6p_THRESHOLD from 100000 to 150000. For some\nreason this avoids the gen6_gt_check_fifodbg.isra warnings and\nassociated GPU lockups, which makes my ivy bridge machine stable.\n\nSigned-off-by: Stéphane Marchesin \u003cmarcheu@chromium.org\u003e\nAcked-by: Jesse Barnes \u003cjbarnes@virtuousgeek.org\u003e\nSigned-off-by: Daniel Vetter \u003cdaniel.vetter@ffwll.ch\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "51dfcbf53c4cc6b1a65a99f27cec3311531b982b", "tree": "88d86a8dac37766b3e3ab394d8505a869e70733a", "parents": [ "187c2bd82defa4d64910eed4d8c39ac93a984306" ], "author": { "name": "Guo Chao", "email": "yan@linux.vnet.ibm.com", "time": "Thu Feb 21 15:16:49 2013 -0800" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Wed Mar 20 13:05:01 2013 -0700" }, "message": "loopdev: remove an user triggerable oops\n\ncommit b1a6650406875b9097a032eed89af50682fe1160 upstream.\n\nWhen loopdev is built as module and we pass an invalid parameter,\nloop_init() will return directly without deregister misc device, which\nwill cause an oops when insert loop module next time because we left some\ngarbage in the misc device list.\n\nTest case:\nsudo modprobe loop max_part\u003d1024\n(failed due to invalid parameter)\nsudo modprobe loop\n(oops)\n\nClean up nicely to avoid such oops.\n\nSigned-off-by: Guo Chao \u003cyan@linux.vnet.ibm.com\u003e\nCc: Alexander Viro \u003cviro@zeniv.linux.org.uk\u003e\nCc: Guo Chao \u003cyan@linux.vnet.ibm.com\u003e\nCc: M. Hindess \u003chindessm@uk.ibm.com\u003e\nCc: Nikanth Karthikesan \u003cknikanth@suse.de\u003e\nCc: Jens Axboe \u003caxboe@kernel.dk\u003e\nSigned-off-by: Andrew Morton \u003cakpm@linux-foundation.org\u003e\nSigned-off-by: Jens Axboe \u003caxboe@kernel.dk\u003e\nAcked-by: Jeff Mahoney \u003cjeffm@suse.com\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "187c2bd82defa4d64910eed4d8c39ac93a984306", "tree": "01c7ae69a8d93c59f5702762afa0acf778b3d3b2", "parents": [ "d72b4f90a2b042136f74a3de50b29d6ce76b5f12" ], "author": { "name": "Guo Chao", "email": "yan@linux.vnet.ibm.com", "time": "Thu Feb 21 15:16:45 2013 -0800" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Wed Mar 20 13:05:01 2013 -0700" }, "message": "loopdev: fix a deadlock\n\ncommit 5370019dc2d2c2ff90e95d181468071362934f3a upstream.\n\nbd_mutex and lo_ctl_mutex can be held in different order.\n\nPath #1:\n\nblkdev_open\n blkdev_get\n __blkdev_get (hold bd_mutex)\n lo_open (hold lo_ctl_mutex)\n\nPath #2:\n\nblkdev_ioctl\n lo_ioctl (hold lo_ctl_mutex)\n lo_set_capacity (hold bd_mutex)\n\nLockdep does not report it, because path #2 actually holds a subclass of\nlo_ctl_mutex. This subclass seems creep into the code by mistake. The\npatch author actually just mentioned it in the changelog, see commit\nf028f3b2 (\"loop: fix circular locking in loop_clr_fd()\"), also see:\n\n\thttp://marc.info/?l\u003dlinux-kernel\u0026m\u003d123806169129727\u0026w\u003d2\n\nPath #2 hold bd_mutex to call bd_set_size(), I\u0027ve protected it\nwith i_mutex in a previous patch, so drop bd_mutex at this site.\n\nSigned-off-by: Guo Chao \u003cyan@linux.vnet.ibm.com\u003e\nCc: Alexander Viro \u003cviro@zeniv.linux.org.uk\u003e\nCc: Guo Chao \u003cyan@linux.vnet.ibm.com\u003e\nCc: M. Hindess \u003chindessm@uk.ibm.com\u003e\nCc: Nikanth Karthikesan \u003cknikanth@suse.de\u003e\nCc: Jens Axboe \u003caxboe@kernel.dk\u003e\nSigned-off-by: Andrew Morton \u003cakpm@linux-foundation.org\u003e\nSigned-off-by: Jens Axboe \u003caxboe@kernel.dk\u003e\nAcked-by: Jeff Mahoney \u003cjeffm@suse.com\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "d72b4f90a2b042136f74a3de50b29d6ce76b5f12", "tree": "61006b7819cf5bf3eebe63702f0aa6a8eb095c15", "parents": [ "969ff7dc5423e50938e7b42b59fe1163aced714c" ], "author": { "name": "Guo Chao", "email": "yan@linux.vnet.ibm.com", "time": "Thu Feb 21 15:16:42 2013 -0800" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Wed Mar 20 13:05:00 2013 -0700" }, "message": "block: use i_size_write() in bd_set_size()\n\ncommit d646a02a9d44d1421f273ae3923d97b47b918176 upstream.\n\nblkdev_ioctl(GETBLKSIZE) uses i_size_read() to read size of block device.\nIf we update block size directly, reader may see intermediate result in\nsome machines and configurations. Use i_size_write() instead.\n\nSigned-off-by: Guo Chao \u003cyan@linux.vnet.ibm.com\u003e\nCc: Alexander Viro \u003cviro@zeniv.linux.org.uk\u003e\nCc: Guo Chao \u003cyan@linux.vnet.ibm.com\u003e\nCc: M. Hindess \u003chindessm@uk.ibm.com\u003e\nCc: Nikanth Karthikesan \u003cknikanth@suse.de\u003e\nCc: Jens Axboe \u003caxboe@kernel.dk\u003e\nSigned-off-by: Andrew Morton \u003cakpm@linux-foundation.org\u003e\nSigned-off-by: Jens Axboe \u003caxboe@kernel.dk\u003e\nAcked-by: Jeff Mahoney \u003cjeffm@suse.com\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "969ff7dc5423e50938e7b42b59fe1163aced714c", "tree": "ce4ad064d2103322f8b11964f1e089909982a5fc", "parents": [ "81da76ae314c66e32b8c06b0ce155a5b61670dd7" ], "author": { "name": "Ben Hutchings", "email": "ben@decadent.org.uk", "time": "Sat Mar 16 06:32:16 2013 -0700" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Wed Mar 20 13:05:00 2013 -0700" }, "message": "hwmon: (sht15) Fix memory leak if regulator_enable() fails\n\nCommit 3e78080f8148 (\u0027hwmon: (sht15) Check return value of\nregulator_enable()\u0027) depends on the use of devm_kmalloc() for automatic\nresource cleanup in the failure cases, which was introduced in 3.7. In\nolder stable branches, explicit cleanup is needed.\n\nSigned-off-by: Ben Hutchings \u003cben@decadent.org.uk\u003e\nSigned-off-by: Guenter Roeck \u003clinux@roeck-us.net\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n" }, { "commit": "81da76ae314c66e32b8c06b0ce155a5b61670dd7", "tree": "360ac46ec63c1a9fed6e2b255a895643b8dab47b", "parents": [ "cb505e2eb68fe9e22afa220bf172f6aa090b7dca" ], "author": { "name": "Dmitry Rogozhkin", "email": "dmitry.v.rogozhkin@intel.com", "time": "Wed Oct 03 17:15:26 2012 +0300" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Wed Mar 20 13:05:00 2013 -0700" }, "message": "drm/i915: EBUSY status handling added to i915_gem_fault().\n\ncommit e79e0fe380847493266fba557217e2773c61bd1b upstream.\n\nSubsequent threads returning EBUSY from vm_insert_pfn() was not handled\ncorrectly. As a result concurrent access from new threads to\nmmapped data caused SIGBUS.\n\nNote that this fixes i-g-t/tests/gem_threaded_tiled_access.\n\nTested-by: Mika Kuoppala \u003cmika.kuoppala@intel.com\u003e\nSigned-off-by: Dmitry Rogozhkin \u003cdmitry.v.rogozhkin@intel.com\u003e\nReviewed-by: Chris Wilson \u003cchris@chris-wilson.co.uk\u003e\nSigned-off-by: Daniel Vetter \u003cdaniel.vetter@ffwll.ch\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "cb505e2eb68fe9e22afa220bf172f6aa090b7dca", "tree": "d1b25dcc977afffedbca41ee63b331c6f49f1f00", "parents": [ "a40a945f829a2b95d5460491d81061166817e3cb" ], "author": { "name": "Johan Hovold", "email": "jhovold@gmail.com", "time": "Tue Feb 05 14:35:11 2013 +0100" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Wed Mar 20 13:05:00 2013 -0700" }, "message": "atmel_lcdfb: fix 16-bpp modes on older SOCs\n\ncommit a79eac7165ed62114e6ca197195aa5060a54f137 upstream.\n\nFix regression introduced by commit 787f9fd23283 (\"atmel_lcdfb: support\n16bit BGR:565 mode, remove unsupported 15bit modes\") which broke 16-bpp\nmodes for older SOCs which use IBGR:555 (msb is intensity) rather\nthan BGR:565.\n\nUse SOC-type to determine the pixel layout.\n\nTested on at91sam9263 and at91sam9g45.\n\nAcked-by: Peter Korsgaard \u003cjacmet@sunsite.dk\u003e\nSigned-off-by: Johan Hovold \u003cjhovold@gmail.com\u003e\nSigned-off-by: Nicolas Ferre \u003cnicolas.ferre@atmel.com\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "a40a945f829a2b95d5460491d81061166817e3cb", "tree": "829e7fb09e5576636361e52b8a54c8c0fbb122be", "parents": [ "59c0110f7ee64a9b5389b8b4fd2ec5feab9c6dc8" ], "author": { "name": "Eric Sandeen", "email": "sandeen@redhat.com", "time": "Sat Mar 09 15:18:39 2013 +0000" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Wed Mar 20 13:05:00 2013 -0700" }, "message": "btrfs: use rcu_barrier() to wait for bdev puts at unmount\n\ncommit bc178622d40d87e75abc131007342429c9b03351 upstream.\n\nDoing this would reliably fail with -EBUSY for me:\n\n# mount /dev/sdb2 /mnt/scratch; umount /mnt/scratch; mkfs.btrfs -f /dev/sdb2\n...\nunable to open /dev/sdb2: Device or resource busy\n\nbecause mkfs.btrfs tries to open the device O_EXCL, and somebody still has it.\n\nUsing systemtap to track bdev gets \u0026 puts shows a kworker thread doing a\nblkdev put after mkfs attempts a get; this is left over from the unmount\npath:\n\nbtrfs_close_devices\n\t__btrfs_close_devices\n\t\tcall_rcu(\u0026device-\u003ercu, free_device);\n\t\t\tfree_device\n\t\t\t\tINIT_WORK(\u0026device-\u003ercu_work, __free_device);\n\t\t\t\tschedule_work(\u0026device-\u003ercu_work);\n\nso unmount might complete before __free_device fires \u0026 does its blkdev_put.\n\nAdding an rcu_barrier() to btrfs_close_devices() causes unmount to wait\nuntil all blkdev_put()s are done, and the device is truly free once\nunmount completes.\n\nSigned-off-by: Eric Sandeen \u003csandeen@redhat.com\u003e\nSigned-off-by: Josef Bacik \u003cjbacik@fusionio.com\u003e\nSigned-off-by: Chris Mason \u003cchris.mason@fusionio.com\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "59c0110f7ee64a9b5389b8b4fd2ec5feab9c6dc8", "tree": "78f1f0031158bd52e529d72e6280c238a7d6b3e2", "parents": [ "8a52ddf504acc488696bdbe7bc4cef7a30a40091" ], "author": { "name": "Heiko Carstens", "email": "heiko.carstens@de.ibm.com", "time": "Mon Mar 04 14:14:11 2013 +0100" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Wed Mar 20 13:05:00 2013 -0700" }, "message": "s390/mm: fix flush_tlb_kernel_range()\n\ncommit f6a70a07079518280022286a1dceb797d12e1edf upstream.\n\nOur flush_tlb_kernel_range() implementation calls __tlb_flush_mm() with\n\u0026init_mm as argument. __tlb_flush_mm() however will only flush tlbs\nfor the passed in mm if its mm_cpumask is not empty.\n\nFor the init_mm however its mm_cpumask has never any bits set. Which in\nturn means that our flush_tlb_kernel_range() implementation doesn\u0027t\nwork at all.\n\nThis can be easily verified with a vmalloc/vfree loop which allocates\na page, writes to it and then frees the page again. A crash will follow\nalmost instantly.\n\nTo fix this remove the cpumask_empty() check in __tlb_flush_mm() since\nthere shouldn\u0027t be too many mms with a zero mm_cpumask, besides the\ninit_mm of course.\n\nSigned-off-by: Heiko Carstens \u003cheiko.carstens@de.ibm.com\u003e\nSigned-off-by: Martin Schwidefsky \u003cschwidefsky@de.ibm.com\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "8a52ddf504acc488696bdbe7bc4cef7a30a40091", "tree": "ef37d60b72766c144f0fe15d7189d15ac771e03e", "parents": [ "6bf083ffc825244992274a23017655caee8e4c58" ], "author": { "name": "Martin Schwidefsky", "email": "schwidefsky@de.ibm.com", "time": "Thu Feb 28 16:28:41 2013 +0100" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Wed Mar 20 13:05:00 2013 -0700" }, "message": "s390: critical section cleanup vs. machine checks\n\ncommit 6551fbdfd8b85d1ab5822ac98abb4fb449bcfae0 upstream.\n\nThe current machine check code uses the registers stored by the machine\nin the lowcore at __LC_GPREGS_SAVE_AREA as the registers of the interrupted\ncontext. The registers 0-7 of a user process can get clobbered if a machine\nchecks interrupts the execution of a critical section in entry[64].S.\n\nThe reason is that the critical section cleanup code may need to modify\nthe PSW and the registers for the previous context to get to the end of a\ncritical section. If registers 0-7 have to be replaced the relevant copy\nwill be in the registers, which invalidates the copy in the lowcore. The\nmachine check handler needs to explicitly store registers 0-7 to the stack.\n\nSigned-off-by: Martin Schwidefsky \u003cschwidefsky@de.ibm.com\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "6bf083ffc825244992274a23017655caee8e4c58", "tree": "e74f39428f6ed033b83b5e1e227d9883669fee7c", "parents": [ "d7805638b85ce978f7c0cf1ac49204d4288084f6" ], "author": { "name": "David Rientjes", "email": "rientjes@google.com", "time": "Sun Mar 17 15:49:10 2013 -0700" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Wed Mar 20 13:05:00 2013 -0700" }, "message": "perf,x86: fix link failure for non-Intel configs\n\ncommit 6c4d3bc99b3341067775efd4d9d13cc8e655fd7c upstream.\n\nCommit 1d9d8639c063 (\"perf,x86: fix kernel crash with PEBS/BTS after\nsuspend/resume\") introduces a link failure since\nperf_restore_debug_store() is only defined for CONFIG_CPU_SUP_INTEL:\n\n\tarch/x86/power/built-in.o: In function `restore_processor_state\u0027:\n\t(.text+0x45c): undefined reference to `perf_restore_debug_store\u0027\n\nFix it by defining the dummy function appropriately.\n\nSigned-off-by: David Rientjes \u003crientjes@google.com\u003e\nSigned-off-by: Linus Torvalds \u003ctorvalds@linux-foundation.org\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "d7805638b85ce978f7c0cf1ac49204d4288084f6", "tree": "07e7e08575d7ab4e3af38f0bac9e1835973491e8", "parents": [ "8c97feb5edd118fe633ed29773c599536d562d43" ], "author": { "name": "Linus Torvalds", "email": "torvalds@linux-foundation.org", "time": "Sun Mar 17 15:44:43 2013 -0700" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Wed Mar 20 13:05:00 2013 -0700" }, "message": "perf,x86: fix wrmsr_on_cpu() warning on suspend/resume\n\ncommit 2a6e06b2aed6995af401dcd4feb5e79a0c7ea554 upstream.\n\nCommit 1d9d8639c063 (\"perf,x86: fix kernel crash with PEBS/BTS after\nsuspend/resume\") fixed a crash when doing PEBS performance profiling\nafter resuming, but in using init_debug_store_on_cpu() to restore the\nDS_AREA mtrr it also resulted in a new WARN_ON() triggering.\n\ninit_debug_store_on_cpu() uses \"wrmsr_on_cpu()\", which in turn uses CPU\ncross-calls to do the MSR update. Which is not really valid at the\nearly resume stage, and the warning is quite reasonable. Now, it all\nhappens to _work_, for the simple reason that smp_call_function_single()\nends up just doing the call directly on the CPU when the CPU number\nmatches, but we really should just do the wrmsr() directly instead.\n\nThis duplicates the wrmsr() logic, but hopefully we can just remove the\nwrmsr_on_cpu() version eventually.\n\nReported-and-tested-by: Parag Warudkar \u003cparag.lkml@gmail.com\u003e\nSigned-off-by: Linus Torvalds \u003ctorvalds@linux-foundation.org\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "8c97feb5edd118fe633ed29773c599536d562d43", "tree": "95bae3db178398cd3d451efed85c9ee2b69dd1f0", "parents": [ "e55005034b11c0dd52ac08b7f769ec410b6bfa1f" ], "author": { "name": "Dan Carpenter", "email": "dan.carpenter@oracle.com", "time": "Sat Mar 16 12:48:11 2013 +0300" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Wed Mar 20 13:05:00 2013 -0700" }, "message": "selinux: use GFP_ATOMIC under spin_lock\n\ncommit 4502403dcf8f5c76abd4dbab8726c8e4ecb5cd34 upstream.\n\nThe call tree here is:\n\nsk_clone_lock() \u003c- takes bh_lock_sock(newsk);\nxfrm_sk_clone_policy()\n__xfrm_sk_clone_policy()\nclone_policy() \u003c- uses GFP_ATOMIC for allocations\nsecurity_xfrm_policy_clone()\nsecurity_ops-\u003exfrm_policy_clone_security()\nselinux_xfrm_policy_clone()\n\nSigned-off-by: Dan Carpenter \u003cdan.carpenter@oracle.com\u003e\nSigned-off-by: James Morris \u003cjames.l.morris@oracle.com\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "e55005034b11c0dd52ac08b7f769ec410b6bfa1f", "tree": "ecb7ca5c21191bb2248c5989f72c5034e28a5dc3", "parents": [ "9d4a6f2cee36dab61a3bd58d1f197f733738995f" ], "author": { "name": "Benjamin Herrenschmidt", "email": "benh@kernel.crashing.org", "time": "Wed Mar 13 09:55:02 2013 +1100" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Wed Mar 20 13:04:59 2013 -0700" }, "message": "powerpc: Fix cputable entry for 970MP rev 1.0\n\ncommit d63ac5f6cf31c8a83170a9509b350c1489a7262b upstream.\n\nCommit 44ae3ab3358e962039c36ad4ae461ae9fb29596c forgot to update\nthe entry for the 970MP rev 1.0 processor when moving some CPU\nfeatures bits to the MMU feature bit mask. This breaks booting\non some rare G5 models using that chip revision.\n\nReported-by: Phileas Fogg \u003cphileas-fogg@mail.ru\u003e\nSigned-off-by: Benjamin Herrenschmidt \u003cbenh@kernel.crashing.org\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "9d4a6f2cee36dab61a3bd58d1f197f733738995f", "tree": "75835b0c3a149ef4a17066ce36fe7e6a2f0bdb97", "parents": [ "32f81345140d7f237afba1a26d42a11117a0304e" ], "author": { "name": "Benjamin Herrenschmidt", "email": "benh@kernel.crashing.org", "time": "Wed Mar 13 09:49:06 2013 +1100" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Wed Mar 20 13:04:59 2013 -0700" }, "message": "powerpc: Fix STAB initialization\n\ncommit 13938117a57f88a22f0df9722a5db7271fda85cd upstream.\n\nCommit f5339277eb8d3aed37f12a27988366f68ab68930 accidentally removed\nmore than just iSeries bits and took out the call to stab_initialize()\nthus breaking support for POWER3 processors.\n\nPut it back. (Yes, nobody noticed until now ...)\n\nSigned-off-by: Benjamin Herrenschmidt \u003cbenh@kernel.crashing.org\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "32f81345140d7f237afba1a26d42a11117a0304e", "tree": "9a2b49bb4b5a7dbecf92bcd8263cd5857492028d", "parents": [ "dce5c33d7abb21e165722b32c43899457c73106f" ], "author": { "name": "Marcin Jurkowski", "email": "marcin1j@gmail.com", "time": "Sat Mar 02 14:50:15 2013 +0100" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Wed Mar 20 13:04:59 2013 -0700" }, "message": "w1: fix oops when w1_search is called from netlink connector\n\ncommit 9d1817cab2f030f6af360e961cc69bb1da8ad765 upstream.\n\nOn Sat, Mar 02, 2013 at 10:45:10AM +0100, Sven Geggus wrote:\n\u003e This is the bad commit I found doing git bisect:\n\u003e 04f482faf50535229a5a5c8d629cf963899f857c is the first bad commit\n\u003e commit 04f482faf50535229a5a5c8d629cf963899f857c\n\u003e Author: Patrick McHardy \u003ckaber@trash.net\u003e\n\u003e Date: Mon Mar 28 08:39:36 2011 +0000\n\nGood job. I was too lazy to bisect for bad commit;)\n\nReading the code I found problematic kthread_should_stop call from netlink\nconnector which causes the oops. After applying a patch, I\u0027ve been testing\nowfs+w1 setup for nearly two days and it seems to work very reliable (no\nhangs, no memleaks etc).\nMore detailed description and possible fix is given below:\n\nFunction w1_search can be called from either kthread or netlink callback.\nWhile the former works fine, the latter causes oops due to kthread_should_stop\ninvocation.\n\nThis patch adds a check if w1_search is serving netlink command, skipping\nkthread_should_stop invocation if so.\n\nSigned-off-by: Marcin Jurkowski \u003cmarcin1j@gmail.com\u003e\nAcked-by: Evgeniy Polyakov \u003czbr@ioremap.net\u003e\nCc: Josh Boyer \u003cjwboyer@gmail.com\u003e\nTested-by: Sven Geggus \u003clists@fuchsschwanzdomain.de\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "dce5c33d7abb21e165722b32c43899457c73106f", "tree": "c6dd866ca0eea137fd1d35a48d434a28d329c18a", "parents": [ "fa5553789ef0bb74434ffedad2fd9e2d994ba92f" ], "author": { "name": "Axel Lin", "email": "axel.lin@ingics.com", "time": "Thu Mar 14 16:27:18 2013 +0800" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Wed Mar 20 13:04:59 2013 -0700" }, "message": "hwmon: (lineage-pem) Add missing terminating entry for pem_[input|fan]_attributes\n\ncommit df069079c153d22adf6c28dcc0b1cf62bba75167 upstream.\n\nSigned-off-by: Axel Lin \u003caxel.lin@ingics.com\u003e\nAcked-by: Jean Delvare \u003ckhali@linux-fr.org\u003e\nSigned-off-by: Guenter Roeck \u003clinux@roeck-us.net\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "fa5553789ef0bb74434ffedad2fd9e2d994ba92f", "tree": "42ff70e044b30525c1b358d35b6a394995890ab0", "parents": [ "fe88b8bc2e9e9f97428337582919b41bd7d3d22a" ], "author": { "name": "Guenter Roeck", "email": "linux@roeck-us.net", "time": "Thu Feb 21 10:27:54 2013 -0800" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Wed Mar 20 13:04:59 2013 -0700" }, "message": "hwmon: (pmbus/ltc2978) Fix temperature reporting\n\ncommit 8c958c703ef8804093437959221951eaf0e1e664 upstream.\n\nOn LTC2978, only READ_TEMPERATURE is supported. It reports\nthe internal junction temperature. This register is unpaged.\n\nOn LTC3880, READ_TEMPERATURE and READ_TEMPERATURE2 are supported.\nREAD_TEMPERATURE is paged and reports external temperatures.\nREAD_TEMPERATURE2 is unpaged and reports the internal junction\ntemperature.\n\nSigned-off-by: Guenter Roeck \u003clinux@roeck-us.net\u003e\nAcked-by: Jean Delvare \u003ckhali@linux-fr.org\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "fe88b8bc2e9e9f97428337582919b41bd7d3d22a", "tree": "7afb49d8f7026eb71976ff75168b7be18f381367", "parents": [ "9a9b01c04ef4b844f64bbf36987f918e64e304a2" ], "author": { "name": "Takashi Iwai", "email": "tiwai@suse.de", "time": "Fri Mar 08 18:11:17 2013 +0100" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Wed Mar 20 13:04:59 2013 -0700" }, "message": "ALSA: seq: Fix missing error handling in snd_seq_timer_open()\n\ncommit 66efdc71d95887b652a742a5dae51fa834d71465 upstream.\n\nsnd_seq_timer_open() didn\u0027t catch the whole error path but let through\nif the timer id is a slave. This may lead to Oops by accessing the\nuninitialized pointer.\n\n BUG: unable to handle kernel NULL pointer dereference at 00000000000002ae\n IP: [\u003cffffffff819b3477\u003e] snd_seq_timer_open+0xe7/0x130\n PGD 785cd067 PUD 76964067 PMD 0\n Oops: 0002 [#4] SMP\n CPU 0\n Pid: 4288, comm: trinity-child7 Tainted: G D W 3.9.0-rc1+ #100 Bochs Bochs\n RIP: 0010:[\u003cffffffff819b3477\u003e] [\u003cffffffff819b3477\u003e] snd_seq_timer_open+0xe7/0x130\n RSP: 0018:ffff88006ece7d38 EFLAGS: 00010246\n RAX: 0000000000000286 RBX: ffff88007851b400 RCX: 0000000000000000\n RDX: 000000000000ffff RSI: ffff88006ece7d58 RDI: ffff88006ece7d38\n RBP: ffff88006ece7d98 R08: 000000000000000a R09: 000000000000fffe\n R10: 0000000000000000 R11: 0000000000000000 R12: 0000000000000000\n R13: ffff8800792c5400 R14: 0000000000e8f000 R15: 0000000000000007\n FS: 00007f7aaa650700(0000) GS:ffff88007f800000(0000) GS:0000000000000000\n CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033\n CR2: 00000000000002ae CR3: 000000006efec000 CR4: 00000000000006f0\n DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000\n DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400\n Process trinity-child7 (pid: 4288, threadinfo ffff88006ece6000, task ffff880076a8a290)\n Stack:\n 0000000000000286 ffffffff828f2be0 ffff88006ece7d58 ffffffff810f354d\n 65636e6575716573 2065756575712072 ffff8800792c0030 0000000000000000\n ffff88006ece7d98 ffff8800792c5400 ffff88007851b400 ffff8800792c5520\n Call Trace:\n [\u003cffffffff810f354d\u003e] ? trace_hardirqs_on+0xd/0x10\n [\u003cffffffff819b17e9\u003e] snd_seq_queue_timer_open+0x29/0x70\n [\u003cffffffff819ae01a\u003e] snd_seq_ioctl_set_queue_timer+0xda/0x120\n [\u003cffffffff819acb9b\u003e] snd_seq_do_ioctl+0x9b/0xd0\n [\u003cffffffff819acbe0\u003e] snd_seq_ioctl+0x10/0x20\n [\u003cffffffff811b9542\u003e] do_vfs_ioctl+0x522/0x570\n [\u003cffffffff8130a4b3\u003e] ? file_has_perm+0x83/0xa0\n [\u003cffffffff810f354d\u003e] ? trace_hardirqs_on+0xd/0x10\n [\u003cffffffff811b95ed\u003e] sys_ioctl+0x5d/0xa0\n [\u003cffffffff813663fe\u003e] ? trace_hardirqs_on_thunk+0x3a/0x3f\n [\u003cffffffff81faed69\u003e] system_call_fastpath+0x16/0x1b\n\nReported-and-tested-by: Tommi Rantala \u003ctt.rantala@gmail.com\u003e\nSigned-off-by: Takashi Iwai \u003ctiwai@suse.de\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "9a9b01c04ef4b844f64bbf36987f918e64e304a2", "tree": "12cd294a8b45e518c2083f399ef67b22348039df", "parents": [ "75750fc43320a6b2ef9852b3437fa25104add6f6" ], "author": { "name": "Stephane Eranian", "email": "eranian@google.com", "time": "Fri Mar 15 14:26:07 2013 +0100" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Wed Mar 20 13:04:59 2013 -0700" }, "message": "perf,x86: fix kernel crash with PEBS/BTS after suspend/resume\n\ncommit 1d9d8639c063caf6efc2447f5f26aa637f844ff6 upstream.\n\nThis patch fixes a kernel crash when using precise sampling (PEBS)\nafter a suspend/resume. Turns out the CPU notifier code is not invoked\non CPU0 (BP). Therefore, the DS_AREA (used by PEBS) is not restored properly\nby the kernel and keeps it power-on/resume value of 0 causing any PEBS\nmeasurement to crash when running on CPU0.\n\nThe workaround is to add a hook in the actual resume code to restore\nthe DS Area MSR value. It is invoked for all CPUS. So for all but CPU0,\nthe DS_AREA will be restored twice but this is harmless.\n\nReported-by: Linus Torvalds \u003ctorvalds@linux-foundation.org\u003e\nSigned-off-by: Stephane Eranian \u003ceranian@google.com\u003e\nSigned-off-by: Linus Torvalds \u003ctorvalds@linux-foundation.org\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "75750fc43320a6b2ef9852b3437fa25104add6f6", "tree": "d4a051b23235706a0abd627799fc15d192017e1c", "parents": [ "3b11e57876950e7530fc9f6122179525000fda20" ], "author": { "name": "Jiri Slaby", "email": "jslaby@suse.cz", "time": "Tue Jan 15 23:26:22 2013 +0100" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Wed Mar 20 13:04:59 2013 -0700" }, "message": "TTY: do not reset master\u0027s packet mode\n\ncommit b81273a132177edd806476b953f6afeb17b786d5 upstream.\n\nNow that login from util-linux is forced to drop all references to a\nTTY which it wants to hangup (to reach reference count 1) we are\nseeing issues with telnet. When login closes its last reference to the\nslave PTY, it also resets packet mode on the *master* side. And we\nhave a race here.\n\nWhat telnet does is fork+exec of `login\u0027. Then there are two\nscenarios:\n* `login\u0027 closes the slave TTY and resets thus master\u0027s packet mode,\n but even now telnet properly sets the mode, or\n* `telnetd\u0027 sets packet mode on the master, `login\u0027 closes the slave\n TTY and resets master\u0027s packet mode.\n\nThe former case is OK. However the latter happens in much more cases,\nby the order of magnitude to be precise. So when one tries to login to\nsuch a messed telnet setup, they see the following:\ninux login:\n ogin incorrect\n\nNote the missing first letters -- telnet thinks it is still in the\npacket mode, so when it receives \"linux login\" from `login\u0027, it\nconsiders \"l\" as the type of the packet and strips it.\n\nSuS does not mention how the implementation should behave. Both BSDs I\nchecked (Free and Net) do not reset the flag upon the last close.\n\nBy this I am resurrecting an old bug, see References. We are hitting\nit regularly now, i.e. with updated util-linux, ergo login.\n\nHere, I am changing a behavior introduced back in 2.1 times. It would\nbetter have a long time testing before goes upstream.\n\nSigned-off-by: Jiri Slaby \u003cjslaby@suse.cz\u003e\nCc: Mauro Carvalho Chehab \u003cmchehab@redhat.com\u003e\nCc: Bryan Mason \u003cbmason@redhat.com\u003e\nReferences: https://lkml.org/lkml/2009/11/11/223\nReferences: https://bugzilla.redhat.com/show_bug.cgi?id\u003d504703\nReferences: https://bugzilla.novell.com/show_bug.cgi?id\u003d797042\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "3b11e57876950e7530fc9f6122179525000fda20", "tree": "555033dad6b74594078125723909032269c364ad", "parents": [ "d91371bb47c16271e8dcb0da255ab1e0b5d15733" ], "author": { "name": "Paul Bolle", "email": "pebolle@tiscali.nl", "time": "Sat Mar 09 23:16:44 2013 +0100" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Wed Mar 20 13:04:59 2013 -0700" }, "message": "tty: serial: fix typo \"ARCH_S5P6450\"\n\ncommit 827aa0d36d486f359808c8fb931cf7a71011a09d upstream.\n\nThis could have been either ARCH_S5P64X0 or CPU_S5P6450. Looking at\ncommit 2555e663b367b8d555e76023f4de3f6338c28d6c (\"ARM: S5P64X0: Add UART\nserial support for S5P6450\") - which added this typo - makes clear this\nshould be CPU_S5P6450.\n\nSigned-off-by: Paul Bolle \u003cpebolle@tiscali.nl\u003e\nAcked-by: Kukjin Kim \u003ckgene.kim@samsung.com\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "d91371bb47c16271e8dcb0da255ab1e0b5d15733", "tree": "4b239aaeadac642d3d1232ee933a2eb910d2f4c5", "parents": [ "e3c51d6b8b4cc278196897e624bc2bdeae8f7798" ], "author": { "name": "Wang YanQing", "email": "udknight@gmail.com", "time": "Fri Mar 01 11:47:20 2013 +0800" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Wed Mar 20 13:04:58 2013 -0700" }, "message": "serial: 8250_pci: add support for another kind of NetMos Technology PCI 9835 Multi-I/O Controller\n\ncommit 8d2f8cd424ca0b99001f3ff4f5db87c4e525f366 upstream.\n\n01:08.0 Communication controller: NetMos Technology PCI 9835 Multi-I/O Controller (rev 01)\n\tSubsystem: Device [1000:0012]\n\tControl: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-\n\tStatus: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL\u003dmedium \u003eTAbort- \u003cTAbort- \u003cMAbort- \u003eSERR- \u003cPERR- INTx-\n\tInterrupt: pin A routed to IRQ 20\n\tRegion 0: I/O ports at e050 [size\u003d8]\n\tRegion 1: I/O ports at e040 [size\u003d8]\n\tRegion 2: I/O ports at e030 [size\u003d8]\n\tRegion 3: I/O ports at e020 [size\u003d8]\n\tRegion 4: I/O ports at e010 [size\u003d8]\n\tRegion 5: I/O ports at e000 [size\u003d16]\n\nSigned-off-by: Wang YanQing \u003cudknight@gmail.com\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "e3c51d6b8b4cc278196897e624bc2bdeae8f7798", "tree": "ee6be9f35cdf1cc3ba023b20da1ed9d925850996", "parents": [ "44ddae422775744b49248dff8818a141d3a03820" ], "author": { "name": "Lars-Peter Clausen", "email": "lars@metafoo.de", "time": "Sat Mar 09 15:28:44 2013 +0100" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Wed Mar 20 13:04:58 2013 -0700" }, "message": "ext3: Fix format string issues\n\ncommit 8d0c2d10dd72c5292eda7a06231056a4c972e4cc upstream.\n\next3_msg() takes the printk prefix as the second parameter and the\nformat string as the third parameter. Two callers of ext3_msg omit the\nprefix and pass the format string as the second parameter and the first\nparameter to the format string as the third parameter. In both cases\nthis string comes from an arbitrary source. Which means the string may\ncontain format string characters, which will\nlead to undefined and potentially harmful behavior.\n\nThe issue was introduced in commit 4cf46b67eb(\"ext3: Unify log messages\nin ext3\") and is fixed by this patch.\n\nSigned-off-by: Lars-Peter Clausen \u003clars@metafoo.de\u003e\nSigned-off-by: Jan Kara \u003cjack@suse.cz\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "44ddae422775744b49248dff8818a141d3a03820", "tree": "22f91f1b83b72fa8cf4c652b70a30ce0ba7f99a9", "parents": [ "a4371b6605f7b6930ba95df316948be6b306be73" ], "author": { "name": "Kees Cook", "email": "keescook@chromium.org", "time": "Wed Mar 13 14:59:33 2013 -0700" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Wed Mar 20 13:04:58 2013 -0700" }, "message": "signal: always clear sa_restorer on execve\n\ncommit 2ca39528c01a933f6689cd6505ce65bd6d68a530 upstream.\n\nWhen the new signal handlers are set up, the location of sa_restorer is\nnot cleared, leaking a parent process\u0027s address space location to\nchildren. This allows for a potential bypass of the parent\u0027s ASLR by\nexamining the sa_restorer value returned when calling sigaction().\n\nBased on what should be considered \"secret\" about addresses, it only\nmatters across the exec not the fork (since the VMAs haven\u0027t changed\nuntil the exec). But since exec sets SIG_DFL and keeps sa_restorer,\nthis is where it should be fixed.\n\nGiven the few uses of sa_restorer, a \"set\" function was not written\nsince this would be the only use. Instead, we use\n__ARCH_HAS_SA_RESTORER, as already done in other places.\n\nExample of the leak before applying this patch:\n\n $ cat /proc/$$/maps\n ...\n 7fb9f3083000-7fb9f3238000 r-xp 00000000 fd:01 404469 .../libc-2.15.so\n ...\n $ ./leak\n ...\n 7f278bc74000-7f278be29000 r-xp 00000000 fd:01 404469 .../libc-2.15.so\n ...\n 1 0 (nil) 0x7fb9f30b94a0\n 2 4000000 (nil) 0x7f278bcaa4a0\n 3 4000000 (nil) 0x7f278bcaa4a0\n 4 0 (nil) 0x7fb9f30b94a0\n ...\n\n[akpm@linux-foundation.org: use SA_RESTORER for backportability]\nSigned-off-by: Kees Cook \u003ckeescook@chromium.org\u003e\nReported-by: Emese Revfy \u003cre.emese@gmail.com\u003e\nCc: Emese Revfy \u003cre.emese@gmail.com\u003e\nCc: PaX Team \u003cpageexec@freemail.hu\u003e\nCc: Al Viro \u003cviro@zeniv.linux.org.uk\u003e\nCc: Oleg Nesterov \u003coleg@redhat.com\u003e\nCc: \"Eric W. Biederman\" \u003cebiederm@xmission.com\u003e\nCc: Serge Hallyn \u003cserge.hallyn@canonical.com\u003e\nCc: Julien Tinnes \u003cjln@google.com\u003e\nSigned-off-by: Andrew Morton \u003cakpm@linux-foundation.org\u003e\nSigned-off-by: Linus Torvalds \u003ctorvalds@linux-foundation.org\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "a4371b6605f7b6930ba95df316948be6b306be73", "tree": "4ce486c02b0df229d6bffa31ccd2059e92a2ab6a", "parents": [ "0319f9909ce68a7516dfc8d53400e07168d281a8" ], "author": { "name": "Malcolm Priestley", "email": "tvboxspy@gmail.com", "time": "Mon Feb 18 19:54:18 2013 +0000" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Wed Mar 20 13:04:58 2013 -0700" }, "message": "staging: vt6656: Fix oops on resume from suspend.\n\ncommit 6987a6dabfc40222ef767f67b57212fe3a0225fb upstream.\n\nRemove usb_put_dev from vt6656_suspend and usb_get_dev\nfrom vt6566_resume.\n\nThese are not normally in suspend/resume functions.\n\nSigned-off-by: Malcolm Priestley \u003ctvboxspy@gmail.com\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "0319f9909ce68a7516dfc8d53400e07168d281a8", "tree": "adafa4d021035c055a5d1e417760db27eb62b9c1", "parents": [ "0b520a5db298be1d1e74b8e51a02d73e1dbf6045" ], "author": { "name": "Alan Stern", "email": "stern@rowland.harvard.edu", "time": "Fri Mar 01 10:51:15 2013 -0500" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Wed Mar 20 13:04:58 2013 -0700" }, "message": "USB: EHCI: don\u0027t check DMA values in QH overlays\n\ncommit feca7746d5d9e84b105a613b7f3b6ad00d327372 upstream.\n\nThis patch (as1661) fixes a rather obscure bug in ehci-hcd. In a\ncouple of places, the driver compares the DMA address stored in a QH\u0027s\noverlay region with the address of a particular qTD, in order to see\nwhether that qTD is the one currently being processed by the hardware.\n(If it is then the status in the QH\u0027s overlay region is more\nup-to-date than the status in the qTD, and if it isn\u0027t then the\noverlay\u0027s value needs to be adjusted when the QH is added back to the\nactive schedule.)\n\nHowever, DMA address in the overlay region isn\u0027t always valid. It\nsometimes will contain a stale value, which may happen by coincidence\nto be equal to a qTD\u0027s DMA address. Instead of checking the DMA\naddress, we should check whether the overlay region is active and\nvalid. The patch tests the ACTIVE bit in the overlay, and clears this\nbit when the overlay becomes invalid (which happens when the\ncurrently-executing URB is unlinked).\n\nThis is the second part of a fix for the regression reported at:\n\n\thttps://bugs.launchpad.net/bugs/1088733\n\nSigned-off-by: Alan Stern \u003cstern@rowland.harvard.edu\u003e\nReported-by: Joseph Salisbury \u003cjoseph.salisbury@canonical.com\u003e\nReported-and-tested-by: Stephen Thirlwall \u003csdt@dr.com\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "0b520a5db298be1d1e74b8e51a02d73e1dbf6045", "tree": "d1930051aa1003fd087b44c446f7e6f96c592fc1", "parents": [ "e870d9d8383f893b4b825220249e2f4d1014c3c0" ], "author": { "name": "Bjørn Mork", "email": "bjorn@mork.no", "time": "Mon Mar 04 14:19:21 2013 +0100" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Wed Mar 20 13:04:58 2013 -0700" }, "message": "USB: storage: fix Huawei mode switching regression\n\ncommit ab4b71644a26d1ab92b987b2fd30e17c25e89f85 upstream.\n\nThis reverts commit 200e0d99 (\"USB: storage: optimize to match the\nHuawei USB storage devices and support new switch command\" and the\nfollowup bugfix commit cd060956 (\"USB: storage: properly handle\nthe endian issues of idProduct\").\n\nThe commit effectively added a large number of Huawei devices to\nthe deprecated usb-storage mode switching logic. Many of these\ndevices have been in use and supported by the userspace\nusb_modeswitch utility for years. Forcing the switching inside\nthe kernel causes a number of regressions as a result of ignoring\nexisting onfigurations, and also completely takes away the ability\nto configure mode switching per device/system/user.\n\nKnown regressions caused by this:\n - Some of the devices support multiple modes, using different\n switching commands. There are existing configurations taking\n advantage of this.\n\n - There is a real use case for disabling mode switching and\n instead mounting the exposed storage device. This becomes\n impossible with switching logic inside the usb-storage driver.\n\n - At least on device fail as a result of the usb-storage switching\n command, becoming completely unswitchable. This is possibly a\n firmware bug, but still a regression because the device work as\n expected using usb_modeswitch defaults.\n\nIn-kernel mode switching was deprecated years ago with the\ndevelopment of the more user friendly userspace alternatives. The\nexisting list of devices in usb-storage was only kept to prevent\nbreaking already working systems. The long term plan is to remove\nthe list, not to add to it. Ref:\nhttp://permalink.gmane.org/gmane.linux.usb.general/28543\n\nSigned-off-by: Bjørn Mork \u003cbjorn@mork.no\u003e\nCc: \u003cfangxiaozhi@huawei.com\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "e870d9d8383f893b4b825220249e2f4d1014c3c0", "tree": "ec4d623cefc7170f404d3064a8fc6ec986d2fea4", "parents": [ "5c1892eea53d57d2264195a3ba0de6b1e852ab79" ], "author": { "name": "Steve Conklin", "email": "sconklin@canonical.com", "time": "Thu Mar 07 17:19:33 2013 -0600" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Wed Mar 20 13:04:58 2013 -0700" }, "message": "usb: serial: Add Rigblaster Advantage to device table\n\ncommit a57e82a18779ab8a5e5a1f5841cef937cf578913 upstream.\n\nThe Rigblaster Advantage is an amateur radio interface sold by West Mountain\nRadio. It contains a cp210x serial interface but the device ID is not in\nthe driver.\n\nSigned-off-by: Steve Conklin \u003csconklin@canonical.com\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "5c1892eea53d57d2264195a3ba0de6b1e852ab79", "tree": "b9f71e46a7dbd719785e41155adedca5ecc4ccc0", "parents": [ "0864bc57e945053f733ff54adf2a60336734b9cc" ], "author": { "name": "Christian Schmiedl", "email": "christian.schmiedl@gemalto.com", "time": "Wed Mar 06 17:08:50 2013 +0100" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Wed Mar 20 13:04:58 2013 -0700" }, "message": "USB: added support for Cinterion\u0027s products AH6 and PLS8\n\ncommit 1941138e1c024ecb5bd797d414928d3eb94d8662 upstream.\n\nadd support for Cinterion\u0027s products AH6 and PLS8 by adding Product IDs\nand USB_DEVICE tuples.\n\nSigned-off-by: Christian Schmiedl \u003cchristian.schmiedl@gemalto.com\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "0864bc57e945053f733ff54adf2a60336734b9cc", "tree": "4432d4f3fe0e745dd168c0b8ff43e19d0a79cab5", "parents": [ "5c6142cc0c0e58daff87e26b1fce585397418bc4" ], "author": { "name": "Matwey V. Kornilov", "email": "matwey@sai.msu.ru", "time": "Sat Mar 09 13:57:32 2013 +0400" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Wed Mar 20 13:04:58 2013 -0700" }, "message": "usb: cp210x new Vendor/Device IDs\n\ncommit be3101c23394af59694c8a2aae6d07f5da62fea5 upstream.\n\nThis patch adds support for the Lake Shore Cryotronics devices to\nthe CP210x driver.\n\nThese lines are ported from cp210x driver distributed by Lake Shore web site:\n http://www.lakeshore.com/Documents/Lake%20Shore%20cp210x-3.0.0.tar.gz\nand licensed under the terms of GPLv2.\n\nMoreover, I\u0027ve tested this changes with Lake Shore 335 in my labs.\n\nSigned-off-by: Matwey V. Kornilov \u003cmatwey@sai.msu.ru\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "5c6142cc0c0e58daff87e26b1fce585397418bc4", "tree": "055d24effa02f6391285cebaebb63ecb107d9d57", "parents": [ "82eccc247f86010b0936983b6e963ffd5d4c79e1" ], "author": { "name": "Oliver Neukum", "email": "oneukum@suse.de", "time": "Tue Mar 12 14:52:42 2013 +0100" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Wed Mar 20 13:04:58 2013 -0700" }, "message": "USB: cdc-wdm: fix buffer overflow\n\ncommit c0f5ecee4e741667b2493c742b60b6218d40b3aa upstream.\n\nThe buffer for responses must not overflow.\nIf this would happen, set a flag, drop the data and return\nan error after user space has read all remaining data.\n\nSigned-off-by: Oliver Neukum \u003coliver@neukum.org\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "82eccc247f86010b0936983b6e963ffd5d4c79e1", "tree": "dcbef9914d5cbbc0e47d05050de8d32d9ac78fc3", "parents": [ "c8fba5853260c3114ed0a24f721cd4c415ea011c" ], "author": { "name": "Bjørn Mork", "email": "bjorn@mork.no", "time": "Wed Feb 27 15:52:56 2013 +0100" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Wed Mar 20 13:04:57 2013 -0700" }, "message": "USB: option: add Huawei E5331\n\ncommit daec90e7382cbd0e73eb6861109b3da91e5ab1f3 upstream.\n\nAnother device using CDC ACM with vendor specific protocol to mark\nserial functions.\n\nSigned-off-by: Bjørn Mork \u003cbjorn@mork.no\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "c8fba5853260c3114ed0a24f721cd4c415ea011c", "tree": "83878b4513702cea4f37637340447278274e85c6", "parents": [ "40e0c1e9b65e94462498ead4a63b1ee08fa40d42" ], "author": { "name": "Amit Shah", "email": "amit.shah@redhat.com", "time": "Fri Mar 08 11:30:18 2013 +1100" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Wed Mar 20 13:04:57 2013 -0700" }, "message": "virtio: rng: disallow multiple device registrations, fixes crashes\n\ncommit e84e7a56a3aa2963db506299e29a5f3f09377f9b upstream.\n\nThe code currently only supports one virtio-rng device at a time.\nInvoking guests with multiple devices causes the guest to blow up.\n\nCheck if we\u0027ve already registered and initialised the driver. Also\ncleanup in case of registration errors or hot-unplug so that a new\ndevice can be used.\n\nReported-by: Peter Krempa \u003cpkrempa@redhat.com\u003e\nReported-by: \u003cyunzheng@redhat.com\u003e\nSigned-off-by: Amit Shah \u003camit.shah@redhat.com\u003e\nSigned-off-by: Rusty Russell \u003crusty@rustcorp.com.au\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "40e0c1e9b65e94462498ead4a63b1ee08fa40d42", "tree": "ef5ecf1e689db161578d4ec3af4ce78e72878243", "parents": [ "990942383df7d1c11471621a7fe25067cc270dd0" ], "author": { "name": "Konrad Rzeszutek Wilk", "email": "konrad.wilk@oracle.com", "time": "Tue Mar 05 13:14:19 2013 -0500" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Wed Mar 20 13:04:57 2013 -0700" }, "message": "xen/pciback: Don\u0027t disable a PCI device that is already disabled.\n\ncommit bdc5c1812cea6efe1aaefb3131fcba28cd0b2b68 upstream.\n\nWhile shuting down a HVM guest with pci devices passed through we\nget this:\n\npciback 0000:04:00.0: restoring config space at offset 0x4 (was 0x100000, writing 0x100002)\n------------[ cut here ]------------\nWARNING: at drivers/pci/pci.c:1397 pci_disable_device+0x88/0xa0()\nHardware name: MS-7640\nDevice pciback\ndisabling already-disabled device\nModules linked in:\nPid: 53, comm: xenwatch Not tainted 3.9.0-rc1-20130304a+ #1\nCall Trace:\n [\u003cffffffff8106994a\u003e] warn_slowpath_common+0x7a/0xc0\n [\u003cffffffff81069a31\u003e] warn_slowpath_fmt+0x41/0x50\n [\u003cffffffff813cf288\u003e] pci_disable_device+0x88/0xa0\n [\u003cffffffff814554a7\u003e] xen_pcibk_reset_device+0x37/0xd0\n [\u003cffffffff81454b6f\u003e] ? pcistub_put_pci_dev+0x6f/0x120\n [\u003cffffffff81454b8d\u003e] pcistub_put_pci_dev+0x8d/0x120\n [\u003cffffffff814582a9\u003e] __xen_pcibk_release_devices+0x59/0xa0\n\nThis fixes the bug.\n\nReported-and-Tested-by: Sander Eikelenboom \u003clinux@eikelenboom.it\u003e\nSigned-off-by: Konrad Rzeszutek Wilk \u003ckonrad.wilk@oracle.com\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "990942383df7d1c11471621a7fe25067cc270dd0", "tree": "5910b8b8096813fa42f2289f13f3a2b127dcbde4", "parents": [ "92a7adfb8118f64787beb27b597d43f0202715d2" ], "author": { "name": "Dan Williams", "email": "dcbw@redhat.com", "time": "Tue Feb 19 09:47:09 2013 -0600" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Wed Mar 20 13:04:57 2013 -0700" }, "message": "qcaux: add Franklin U600\n\ncommit 2d90e63603ac235aecd7d20e234616e0682c8b1f upstream.\n\n4 ports; AT/PPP is standard CDC-ACM. The other three (added by this\npatch) are QCDM/DIAG, possibly GPS, and unknown.\n\nSigned-off-by: Dan Williams \u003cdcbw@redhat.com\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "92a7adfb8118f64787beb27b597d43f0202715d2", "tree": "0c3c30ab7fc136cf3aed6ae967666917180245fd", "parents": [ "8420d82e3a25e0f64526db253056945b1585dc08" ], "author": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Thu Mar 14 11:30:25 2013 -0700" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Thu Mar 14 11:30:25 2013 -0700" }, "message": "Linux 3.4.36\n" }, { "commit": "8420d82e3a25e0f64526db253056945b1585dc08", "tree": "68a87ed7a1303b50ef4b5f451d93c45eb3c60ee7", "parents": [ "983c9b4e483b7720e72378d69ef18b6188d17ab1" ], "author": { "name": "Sarah Sharp", "email": "sarah.a.sharp@linux.intel.com", "time": "Wed Mar 13 10:59:21 2013 -0700" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Thu Mar 14 11:29:52 2013 -0700" }, "message": "USB: Fix connected device switch to Inactive state.\n\n[This is upstream commit d3b9d7a9051d7024a93c76a84b2f84b3b66ad6d5.\nIt needs to be backported to kernels as old as 3.2, because it fixes the\nbuggy commit 9dbcaec830cd97f44a0b91b315844e0d7144746b \"USB: Handle warm\nreset failure on empty port.\"]\n\nA USB 3.0 device can transition to the Inactive state if a U1 or U2 exit\ntransition fails. The current code in hub_events simply issues a warm\nreset, but does not call any pre-reset or post-reset driver methods (or\nunbind/rebind drivers without them). Therefore the drivers won\u0027t know\ntheir device has just been reset.\n\nhub_events should instead call usb_reset_device. This means\nhub_port_reset now needs to figure out whether it should issue a warm\nreset or a hot reset.\n\nRemove the FIXME note about needing disconnect() for a NOTATTACHED\ndevice. This patch fixes that.\n\nSigned-off-by: Sarah Sharp \u003csarah.a.sharp@linux.intel.com\u003e\nAcked-by: Alan Stern \u003cstern@rowland.harvard.edu\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "983c9b4e483b7720e72378d69ef18b6188d17ab1", "tree": "1284c4d0cf1ae0f60a1acf75627b3820f6ca80fc", "parents": [ "beabe20445c60322719d8f58e9eb9dd4660c1b3e" ], "author": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Tue Mar 12 15:18:13 2013 -0700" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Thu Mar 14 11:29:52 2013 -0700" }, "message": "Revert \"ALSA: hda - hdmi: Make jacks phantom, if they\u0027re not detectable\"\n\nThis reverts commit 30efd8debd1ef30be342d374f01e993509f5b76b upstream\n(dd54ec4067a23236736afecbda120030d7ce8fe9 in this tree) as it is not\nneeded for the 3.4-stable tree.\n\nCc: David Henningsson \u003cdavid.henningsson@canonical.com\u003e\nCc: Takashi Iwai \u003ctiwai@suse.de\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "beabe20445c60322719d8f58e9eb9dd4660c1b3e", "tree": "55166ff183186b0faa5b95fc71ac6747b9d9eaf2", "parents": [ "e850004e595d6322c6b7ccbfe21a4582051ad56b" ], "author": { "name": "Sarah Sharp", "email": "sarah.a.sharp@linux.intel.com", "time": "Thu Mar 07 16:24:24 2013 -0800" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Thu Mar 14 11:29:52 2013 -0700" }, "message": "USB: Rip out recursive call on warm port reset.\n\n[This is upstream commit 24a6078754f28528bc91e7e7b3e6ae86bd936d8.\nIt needs to be backported to kernels as old as 3.2, because it fixes the\nbuggy commit 9dbcaec830cd97f44a0b91b315844e0d7144746b \"USB: Handle warm\nreset failure on empty port.\"]\n\nWhen a hot reset fails on a USB 3.0 port, the current port reset code\nrecursively calls hub_port_reset inside hub_port_wait_reset. This isn\u0027t\nideal, since we should avoid recursive calls in the kernel, and it also\ndoesn\u0027t allow us to issue multiple warm resets on reset failures.\n\nRip out the recursive call. Instead, add code to hub_port_reset to\nissue a warm reset if the hot reset fails, and try multiple warm resets\nbefore giving up on the port.\n\nIn hub_port_wait_reset, remove the recursive call and re-indent. The\ncode is basically the same, except:\n\n1. It bails out early if the port has transitioned to Inactive or\nCompliance Mode after the reset completed.\n\n2. It doesn\u0027t consider a connect status change to be a failed reset. If\nmultiple warm resets needed to be issued, the connect status may have\nchanged, so we need to ignore that and look at the port link state\ninstead. hub_port_reset will now do that.\n\n3. It unconditionally sets udev-\u003espeed on all types of successful\nresets. The old recursive code would set the port speed when the second\nhub_port_reset returned.\n\nThe old code did not handle connected devices needing a warm reset well.\nThere were only two situations that the old code handled correctly: an\nempty port needing a warm reset, and a hot reset that migrated to a warm\nreset.\n\nWhen an empty port needed a warm reset, hub_port_reset was called with\nthe warm variable set. The code in hub_port_finish_reset would skip\ntelling the USB core and the xHC host that the device was reset, because\notherwise that would result in a NULL pointer dereference.\n\nWhen a USB 3.0 device reset migrated to a warm reset, the recursive call\nmade the call stack look like this:\n\nhub_port_reset(warm \u003d false)\n hub_wait_port_reset(warm \u003d false)\n hub_port_reset(warm \u003d true)\n hub_wait_port_reset(warm \u003d true)\n hub_port_finish_reset(warm \u003d true)\n (return up the call stack to the first wait)\n\n hub_port_finish_reset(warm \u003d false)\n\nThe old code didn\u0027t want to notify the USB core or the xHC host of device reset\ntwice, so it only did it in the second call to hub_port_finish_reset,\nwhen warm was set to false. This was necessary because\nbefore patch two (\"USB: Ignore xHCI Reset Device status.\"), the USB core\nwould pay attention to the xHC Reset Device command error status, and\nthe second call would always fail.\n\nNow that we no longer have the recursive call, and warm can change from\nfalse to true in hub_port_reset, we need to have hub_port_finish_reset\nunconditionally notify the USB core and the xHC of the device reset.\n\nIn hub_port_finish_reset, unconditionally clear the connect status\nchange (CSC) bit for USB 3.0 hubs when the port reset is done. If we\nhad to issue multiple warm resets for a device, that bit may have been\nset if the device went into SS.Inactive and then was successfully warm\nreset.\n\nSigned-off-by: Sarah Sharp \u003csarah.a.sharp@linux.intel.com\u003e\nAcked-by: Alan Stern \u003cstern@rowland.harvard.edu\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "e850004e595d6322c6b7ccbfe21a4582051ad56b", "tree": "250637573ab5224f068a63723d461ac6d7a7c2ba", "parents": [ "ac79dc9b4a929bd8c0d9e4a2fccd3b7215cbaee4" ], "author": { "name": "Sarah Sharp", "email": "sarah.a.sharp@linux.intel.com", "time": "Thu Mar 07 16:24:22 2013 -0800" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Thu Mar 14 11:29:51 2013 -0700" }, "message": "USB: Prepare for refactoring by adding extra udev checks.\n\n[This is upstream commit 2d4fa940f99663c82ba55b2244638833b388e4e2.\nIt needs to be backported to kernels as old as 3.2, because it fixes the\nbuggy commit 9dbcaec830cd97f44a0b91b315844e0d7144746b \"USB: Handle warm\nreset failure on empty port.\"]\n\nThe next patch will refactor the hub port code to rip out the recursive\ncall to hub_port_reset on a failed hot reset. In preparation for that,\nmake sure all code paths can deal with being called with a NULL udev.\nThe usb_device will not be valid if warm reset was issued because a port\ntransitioned to the Inactive or Compliance Mode on a device connect.\n\nThis patch should have no effect on current behavior.\n\nSigned-off-by: Sarah Sharp \u003csarah.a.sharp@linux.intel.com\u003e\nAcked-by: Alan Stern \u003cstern@rowland.harvard.edu\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "ac79dc9b4a929bd8c0d9e4a2fccd3b7215cbaee4", "tree": "a35a070a9f7dfc07f0de6945b0de1442ae032a77", "parents": [ "d2c96b7257048e9a558f2ebe4fe884b51fd9016f" ], "author": { "name": "Sarah Sharp", "email": "sarah.a.sharp@linux.intel.com", "time": "Thu Mar 07 16:24:19 2013 -0800" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Thu Mar 14 11:29:51 2013 -0700" }, "message": "USB: Don\u0027t use EHCI port sempahore for USB 3.0 hubs.\n\n[This is upstream commit 0fe51aa5eee51db7c7ecd201d42a977ad79c58b6.\nIt needs to be backported to kernels as old as 3.2, because it fixes the\nbuggy commit 9dbcaec830cd97f44a0b91b315844e0d7144746b \"USB: Handle warm\nreset failure on empty port.\"]\n\nThe EHCI host controller needs to prevent EHCI initialization when the\nUHCI or OHCI companion controller is in the middle of a port reset. It\nuses ehci_cf_port_reset_rwsem to do this. USB 3.0 hubs can\u0027t be under\nan EHCI host controller, so it makes no sense to down the semaphore for\nUSB 3.0 hubs. It also makes the warm port reset code more complex.\n\nDon\u0027t down ehci_cf_port_reset_rwsem for USB 3.0 hubs.\n\nSigned-off-by: Sarah Sharp \u003csarah.a.sharp@linux.intel.com\u003e\nAcked-by: Alan Stern \u003cstern@rowland.harvard.edu\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "d2c96b7257048e9a558f2ebe4fe884b51fd9016f", "tree": "ef4f78def19091c0ece2c45daad02fb99222072a", "parents": [ "abf73cb191a83045c3cc6f46ea78b94439957585" ], "author": { "name": "Ben Hutchings", "email": "ben@decadent.org.uk", "time": "Fri Mar 08 12:43:32 2013 -0800" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Thu Mar 14 11:29:51 2013 -0700" }, "message": "dmi_scan: fix missing check for _DMI_ signature in smbios_present()\n\ncommit a40e7cf8f06b4e322ba902e4e9f6a6b0c2daa907 upstream.\n\nCommit 9f9c9cbb6057 (\"drivers/firmware/dmi_scan.c: fetch dmi version\nfrom SMBIOS if it exists\") hoisted the check for \"_DMI_\" into\ndmi_scan_machine(), which means that we don\u0027t bother to check for\n\"_DMI_\" at offset 16 in an SMBIOS entry. smbios_present() may also call\ndmi_present() for an address where we found \"_SM_\", if it failed further\nvalidation.\n\nCheck for \"_DMI_\" in smbios_present() before calling dmi_present().\n\n[akpm@linux-foundation.org: fix build]\nSigned-off-by: Ben Hutchings \u003cben@decadent.org.uk\u003e\nReported-by: Tim McGrath \u003ctmhikaru@gmail.com\u003e\nTested-by: Tim Mcgrath \u003ctmhikaru@gmail.com\u003e\nCc: Zhenzhong Duan \u003czhenzhong.duan@oracle.com\u003e\nSigned-off-by: Andrew Morton \u003cakpm@linux-foundation.org\u003e\nSigned-off-by: Linus Torvalds \u003ctorvalds@linux-foundation.org\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "abf73cb191a83045c3cc6f46ea78b94439957585", "tree": "cb88f3a2335ab2db1e92601774312115f230d274", "parents": [ "f39e4f133d52fad48f5c823b6c8a867caf101677" ], "author": { "name": "Steven Rostedt", "email": "srostedt@redhat.com", "time": "Wed Feb 27 21:48:09 2013 -0500" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Thu Mar 14 11:29:51 2013 -0700" }, "message": "ftrace: Update the kconfig for DYNAMIC_FTRACE\n\ncommit db05021d49a994ee40a9735d9c3cb0060c9babb8 upstream.\n\nThe prompt to enable DYNAMIC_FTRACE (the ability to nop and\nenable function tracing at run time) had a confusing statement:\n\n \"enable/disable ftrace tracepoints dynamically\"\n\nThis was written before tracepoints were added to the kernel,\nbut now that tracepoints have been added, this is very confusing\nand has confused people enough to give wrong information during\npresentations.\n\nNot only that, I looked at the help text, and it still references\nthat dreaded daemon that use to wake up once a second to update\nthe nop locations and brick NICs, that hasn\u0027t been around for over\nfive years.\n\nTime to bring the text up to the current decade.\n\nReported-by: Ezequiel Garcia \u003celezegarcia@gmail.com\u003e\nSigned-off-by: Steven Rostedt \u003crostedt@goodmis.org\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "f39e4f133d52fad48f5c823b6c8a867caf101677", "tree": "11fb57f56fb2444218c217f865350dc375a0a543", "parents": [ "cc6de71e8c24edbad16e45c011013d40eb903ffd" ], "author": { "name": "Tu, Xiaobing", "email": "xiaobing.tu@intel.com", "time": "Tue Oct 23 01:03:00 2012 +0200" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Thu Mar 14 11:29:51 2013 -0700" }, "message": "Fix memory leak in cpufreq stats.\n\ncommit e37736777254ce1abc85493a5cacbefe5983b896 upstream.\n\nWhen system enters sleep, non-boot CPUs will be disabled.\nCpufreq stats sysfs is created when the CPU is up, but it is not\nfreed when the CPU is going down. This will cause memory leak.\n\nSigned-off-by: xiaobing tu \u003cxiaobing.tu@intel.com\u003e\nSigned-off-by: guifang tang \u003cguifang.tang@intel.com\u003e\nSigned-off-by: Rafael J. Wysocki \u003crafael.j.wysocki@intel.com\u003e\nCc: Colin Cross \u003cccross@google.com\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "cc6de71e8c24edbad16e45c011013d40eb903ffd", "tree": "0679f9de7e5d8b83b8aae72cac37cc9e052f9c78", "parents": [ "3126603e01babcec7cfe2f284099e2adff095bff" ], "author": { "name": "Al Viro", "email": "viro@ZenIV.linux.org.uk", "time": "Tue Mar 12 02:59:49 2013 +0000" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Thu Mar 14 11:29:51 2013 -0700" }, "message": "vfs: fix pipe counter breakage\n\ncommit a930d8790552658140d7d0d2e316af4f0d76a512 upstream.\n\nIf you open a pipe for neither read nor write, the pipe code will not\nadd any usage counters to the pipe, causing the \u0027struct pipe_inode_info\"\nto be potentially released early.\n\nThat doesn\u0027t normally matter, since you cannot actually use the pipe,\nbut the pipe release code - particularly fasync handling - still expects\nthe actual pipe infrastructure to all be there. And rather than adding\nNULL pointer checks, let\u0027s just disallow this case, the same way we\nalready do for the named pipe (\"fifo\") case.\n\nThis is ancient going back to pre-2.4 days, and until trinity, nobody\nnaver noticed.\n\nReported-by: Dave Jones \u003cdavej@redhat.com\u003e\nSigned-off-by: Linus Torvalds \u003ctorvalds@linux-foundation.org\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "3126603e01babcec7cfe2f284099e2adff095bff", "tree": "edd0b3fd6d738ef785f4338825b703f1e7fa7db7", "parents": [ "96ace773358d2989ea522a1cdccf65d75c1335f3" ], "author": { "name": "Mathieu Desnoyers", "email": "mathieu.desnoyers@efficios.com", "time": "Mon Feb 25 10:20:36 2013 -0500" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Thu Mar 14 11:29:51 2013 -0700" }, "message": "Fix: compat_rw_copy_check_uvector() misuse in aio, readv, writev, and security keys\n\ncommit 8aec0f5d4137532de14e6554fd5dd201ff3a3c49 upstream.\n\nLooking at mm/process_vm_access.c:process_vm_rw() and comparing it to\ncompat_process_vm_rw() shows that the compatibility code requires an\nexplicit \"access_ok()\" check before calling\ncompat_rw_copy_check_uvector(). The same difference seems to appear when\nwe compare fs/read_write.c:do_readv_writev() to\nfs/compat.c:compat_do_readv_writev().\n\nThis subtle difference between the compat and non-compat requirements\nshould probably be debated, as it seems to be error-prone. In fact,\nthere are two others sites that use this function in the Linux kernel,\nand they both seem to get it wrong:\n\nNow shifting our attention to fs/aio.c, we see that aio_setup_iocb()\nalso ends up calling compat_rw_copy_check_uvector() through\naio_setup_vectored_rw(). Unfortunately, the access_ok() check appears to\nbe missing. Same situation for\nsecurity/keys/compat.c:compat_keyctl_instantiate_key_iov().\n\nI propose that we add the access_ok() check directly into\ncompat_rw_copy_check_uvector(), so callers don\u0027t have to worry about it,\nand it therefore makes the compat call code similar to its non-compat\ncounterpart. Place the access_ok() check in the same location where\ncopy_from_user() can trigger a -EFAULT error in the non-compat code, so\nthe ABI behaviors are alike on both compat and non-compat.\n\nWhile we are here, fix compat_do_readv_writev() so it checks for\ncompat_rw_copy_check_uvector() negative return values.\n\nAnd also, fix a memory leak in compat_keyctl_instantiate_key_iov() error\nhandling.\n\nAcked-by: Linus Torvalds \u003ctorvalds@linux-foundation.org\u003e\nAcked-by: Al Viro \u003cviro@ZenIV.linux.org.uk\u003e\nSigned-off-by: Mathieu Desnoyers \u003cmathieu.desnoyers@efficios.com\u003e\nSigned-off-by: Linus Torvalds \u003ctorvalds@linux-foundation.org\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "96ace773358d2989ea522a1cdccf65d75c1335f3", "tree": "c9b078ec66184fb1d8f59930b3cf48f7b0cdcbe3", "parents": [ "30e39b7c57422b29533a1bf43f2fd921e088a71d" ], "author": { "name": "David Howells", "email": "dhowells@redhat.com", "time": "Tue Mar 12 16:44:31 2013 +1100" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Thu Mar 14 11:29:51 2013 -0700" }, "message": "keys: fix race with concurrent install_user_keyrings()\n\ncommit 0da9dfdd2cd9889201bc6f6f43580c99165cd087 upstream.\n\nThis fixes CVE-2013-1792.\n\nThere is a race in install_user_keyrings() that can cause a NULL pointer\ndereference when called concurrently for the same user if the uid and\nuid-session keyrings are not yet created. It might be possible for an\nunprivileged user to trigger this by calling keyctl() from userspace in\nparallel immediately after logging in.\n\nAssume that we have two threads both executing lookup_user_key(), both\nlooking for KEY_SPEC_USER_SESSION_KEYRING.\n\n\tTHREAD A\t\t\tTHREAD B\n\t\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\t\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\n\t\t\t\t\t\u003d\u003d\u003ecall install_user_keyrings();\n\tif (!cred-\u003euser-\u003esession_keyring)\n\t\u003d\u003d\u003ecall install_user_keyrings()\n\t\t\t\t\t...\n\t\t\t\t\tuser-\u003euid_keyring \u003d uid_keyring;\n\tif (user-\u003euid_keyring)\n\t\treturn 0;\n\t\u003c\u003d\u003d\n\tkey \u003d cred-\u003euser-\u003esession_keyring [\u003d\u003d NULL]\n\t\t\t\t\tuser-\u003esession_keyring \u003d session_keyring;\n\tatomic_inc(\u0026key-\u003eusage); [oops]\n\nAt the point thread A dereferences cred-\u003euser-\u003esession_keyring, thread B\nhasn\u0027t updated user-\u003esession_keyring yet, but thread A assumes it is\npopulated because install_user_keyrings() returned ok.\n\nThe race window is really small but can be exploited if, for example,\nthread B is interrupted or preempted after initializing uid_keyring, but\nbefore doing setting session_keyring.\n\nThis couldn\u0027t be reproduced on a stock kernel. However, after placing\nsystemtap probe on \u0027user-\u003esession_keyring \u003d session_keyring;\u0027 that\nintroduced some delay, the kernel could be crashed reliably.\n\nFix this by checking both pointers before deciding whether to return.\nAlternatively, the test could be done away with entirely as it is checked\ninside the mutex - but since the mutex is global, that may not be the best\nway.\n\nSigned-off-by: David Howells \u003cdhowells@redhat.com\u003e\nReported-by: Mateusz Guzik \u003cmguzik@redhat.com\u003e\nSigned-off-by: Andrew Morton \u003cakpm@linux-foundation.org\u003e\nSigned-off-by: James Morris \u003cjames.l.morris@oracle.com\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "30e39b7c57422b29533a1bf43f2fd921e088a71d", "tree": "49dc959d9bb11deb5be1cf30f7e3bc4cd8bc3db1", "parents": [ "76de736ea670500c46e84bff7ae0e040f69d4397" ], "author": { "name": "Mathias Krause", "email": "minipli@googlemail.com", "time": "Tue Feb 05 18:19:13 2013 +0100" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Thu Mar 14 11:29:50 2013 -0700" }, "message": "crypto: user - fix info leaks in report API\n\ncommit 9a5467bf7b6e9e02ec9c3da4e23747c05faeaac6 upstream.\n\nThree errors resulting in kernel memory disclosure:\n\n1/ The structures used for the netlink based crypto algorithm report API\nare located on the stack. As snprintf() does not fill the remainder of\nthe buffer with null bytes, those stack bytes will be disclosed to users\nof the API. Switch to strncpy() to fix this.\n\n2/ crypto_report_one() does not initialize all field of struct\ncrypto_user_alg. Fix this to fix the heap info leak.\n\n3/ For the module name we should copy only as many bytes as\nmodule_name() returns -- not as much as the destination buffer could\nhold. But the current code does not and therefore copies random data\nfrom behind the end of the module name, as the module name is always\nshorter than CRYPTO_MAX_ALG_NAME.\n\nAlso switch to use strncpy() to copy the algorithm\u0027s name and\ndriver_name. They are strings, after all.\n\nSigned-off-by: Mathias Krause \u003cminipli@googlemail.com\u003e\nCc: Steffen Klassert \u003csteffen.klassert@secunet.com\u003e\nSigned-off-by: Herbert Xu \u003cherbert@gondor.apana.org.au\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "76de736ea670500c46e84bff7ae0e040f69d4397", "tree": "c985211c84b8686c11101e06c37a8a00fceeb410", "parents": [ "626614bf45e336d2623c90a812e6bd141e86949e" ], "author": { "name": "Konrad Rzeszutek Wilk", "email": "konrad.wilk@oracle.com", "time": "Tue Feb 26 12:51:27 2013 -0500" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Thu Mar 14 11:29:50 2013 -0700" }, "message": "xen/pat: Disable PAT using pat_enabled value.\n\ncommit c79c49826270b8b0061b2fca840fc3f013c8a78a upstream.\n\nThe git commit 8eaffa67b43e99ae581622c5133e20b0f48bcef1\n(xen/pat: Disable PAT support for now) explains in details why\nwe want to disable PAT for right now. However that\nchange was not enough and we should have also disabled\nthe pat_enabled value. Otherwise we end up with:\n\nmmap-example:3481 map pfn expected mapping type write-back for\n[mem 0x00010000-0x00010fff], got uncached-minus\n ------------[ cut here ]------------\nWARNING: at /build/buildd/linux-3.8.0/arch/x86/mm/pat.c:774 untrack_pfn+0xb8/0xd0()\nmem 0x00010000-0x00010fff], got uncached-minus\n------------[ cut here ]------------\nWARNING: at /build/buildd/linux-3.8.0/arch/x86/mm/pat.c:774\nuntrack_pfn+0xb8/0xd0()\n...\nPid: 3481, comm: mmap-example Tainted: GF 3.8.0-6-generic #13-Ubuntu\nCall Trace:\n [\u003cffffffff8105879f\u003e] warn_slowpath_common+0x7f/0xc0\n [\u003cffffffff810587fa\u003e] warn_slowpath_null+0x1a/0x20\n [\u003cffffffff8104bcc8\u003e] untrack_pfn+0xb8/0xd0\n [\u003cffffffff81156c1c\u003e] unmap_single_vma+0xac/0x100\n [\u003cffffffff81157459\u003e] unmap_vmas+0x49/0x90\n [\u003cffffffff8115f808\u003e] exit_mmap+0x98/0x170\n [\u003cffffffff810559a4\u003e] mmput+0x64/0x100\n [\u003cffffffff810560f5\u003e] dup_mm+0x445/0x660\n [\u003cffffffff81056d9f\u003e] copy_process.part.22+0xa5f/0x1510\n [\u003cffffffff81057931\u003e] do_fork+0x91/0x350\n [\u003cffffffff81057c76\u003e] sys_clone+0x16/0x20\n [\u003cffffffff816ccbf9\u003e] stub_clone+0x69/0x90\n [\u003cffffffff816cc89d\u003e] ? system_call_fastpath+0x1a/0x1f\n---[ end trace 4918cdd0a4c9fea4 ]---\n\n(a similar message shows up if you end up launching \u0027mcelog\u0027)\n\nThe call chain is (as analyzed by Liu, Jinsong):\ndo_fork\n --\u003e copy_process\n --\u003e dup_mm\n --\u003e dup_mmap\n \t--\u003e copy_page_range\n --\u003e track_pfn_copy\n --\u003e reserve_pfn_range\n --\u003e line 624: flags !\u003d want_flags\nIt comes from different memory types of page table (_PAGE_CACHE_WB) and MTRR\n(_PAGE_CACHE_UC_MINUS).\n\nStefan Bader dug in this deep and found out that:\n\"That makes it clearer as this will do\n\nreserve_memtype(...)\n--\u003e pat_x_mtrr_type\n --\u003e mtrr_type_lookup\n --\u003e __mtrr_type_lookup\n\nAnd that can return -1/0xff in case of MTRR not being enabled/initialized. Which\nis not the case (given there are no messages for it in dmesg). This is not equal\nto MTRR_TYPE_WRBACK and thus becomes _PAGE_CACHE_UC_MINUS.\n\nIt looks like the problem starts early in reserve_memtype:\n\n \tif (!pat_enabled) {\n /* This is identical to page table setting without PAT */\n if (new_type) {\n if (req_type \u003d\u003d _PAGE_CACHE_WC)\n *new_type \u003d _PAGE_CACHE_UC_MINUS;\n else\n \t*new_type \u003d req_type \u0026 _PAGE_CACHE_MASK;\n \t}\n return 0;\n }\n\nThis would be what we want, that is clearing the PWT and PCD flags from the\nsupported flags - if pat_enabled is disabled.\"\n\nThis patch does that - disabling PAT.\n\nReported-by: Sander Eikelenboom \u003clinux@eikelenboom.it\u003e\nReported-and-Tested-by: Konrad Rzeszutek Wilk \u003ckonrad.wilk@oracle.com\u003e\nReported-and-Tested-by: Stefan Bader \u003cstefan.bader@canonical.com\u003e\nSigned-off-by: Konrad Rzeszutek Wilk \u003ckonrad.wilk@oracle.com\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "626614bf45e336d2623c90a812e6bd141e86949e", "tree": "890650fe2548e3d1a6ed4db87651221917c49419", "parents": [ "1c48233e2eea4790e4b85b0e8b40537cecdba841" ], "author": { "name": "Benjamin Tissoires", "email": "benjamin.tissoires@redhat.com", "time": "Tue Mar 05 17:09:00 2013 +0100" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Thu Mar 14 11:29:50 2013 -0700" }, "message": "HID: logitech-dj: do not directly call hid_output_raw_report() during probe\n\ncommit dcd9006b1b053c7b1cebe81333261d4fd492ffeb upstream.\n\nhid_output_raw_report() makes a direct call to usb_control_msg(). However,\nsome USB3 boards have shown that the usb device is not ready during the\n.probe(). This blocks the entire usb device, and the paired mice, keyboards\nare not functional. The dmesg output is the following:\n\n[ 11.912287] logitech-djreceiver 0003:046D:C52B.0003: hiddev0,hidraw0: USB HID v1.11 Device [Logitech USB Receiver] on usb-0000:00:14.0-2/input2\n[ 11.912537] logitech-djreceiver 0003:046D:C52B.0003: logi_dj_probe:logi_dj_recv_query_paired_devices error:-32\n[ 11.912636] logitech-djreceiver: probe of 0003:046D:C52B.0003 failed with error -32\n\nRelying on the scheduled call to usbhid_submit_report() fixes the problem.\n\nrelated bugs:\nhttps://bugs.launchpad.net/ubuntu/+source/linux/+bug/1072082\nhttps://bugs.launchpad.net/ubuntu/+source/linux/+bug/1039143\nhttps://bugzilla.redhat.com/show_bug.cgi?id\u003d840391\nhttps://bugzilla.kernel.org/show_bug.cgi?id\u003d49781\n\nReported-and-tested-by: Bob Bowles \u003cbobjohnbowles@gmail.com\u003e\nSigned-off-by: Benjamin Tissoires \u003cbenjamin.tissoires@redhat.com\u003e\nSigned-off-by: Jiri Kosina \u003cjkosina@suse.cz\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "1c48233e2eea4790e4b85b0e8b40537cecdba841", "tree": "c3dc35acdad304af9b21459ba569894fcb985770", "parents": [ "f4ec9b23b178caab8e4ecc8b4a4c3531211411a9" ], "author": { "name": "Konstantin Khlebnikov", "email": "khlebnikov@openvz.org", "time": "Tue Mar 05 09:42:59 2013 +0000" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Thu Mar 14 11:29:50 2013 -0700" }, "message": "e1000e: fix pci-device enable-counter balance\n\ncommit 4e0855dff094b0d56d6b5b271e0ce7851cc1e063 upstream.\n\nThis patch removes redundant and unbalanced pci_disable_device() from\n__e1000_shutdown(). pci_clear_master() is enough, device can go into\nsuspended state with elevated enable_cnt.\n\nBug was introduced in commit 23606cf5d1192c2b17912cb2ef6e62f9b11de133\n(\"e1000e / PCI / PM: Add basic runtime PM support (rev. 4)\") in v2.6.35\n\nSigned-off-by: Konstantin Khlebnikov \u003ckhlebnikov@openvz.org\u003e\nCc: Bruce Allan \u003cbruce.w.allan@intel.com\u003e\nAcked-by: Rafael J. Wysocki \u003crafael.j.wysocki@intel.com\u003e\nTested-by: Borislav Petkov \u003cbp@suse.de\u003e\nTested-by: Aaron Brown \u003caaron.f.brown@intel.com\u003e\nSigned-off-by: Jeff Kirsher \u003cjeffrey.t.kirsher@intel.com\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "f4ec9b23b178caab8e4ecc8b4a4c3531211411a9", "tree": "7dd92517801633d10b7f51c563b51b5d6c0a7ba2", "parents": [ "1515f18665088e33e35706bd35268a16e8e7665d" ], "author": { "name": "Takashi Iwai", "email": "tiwai@suse.de", "time": "Tue Mar 05 15:43:39 2013 +0100" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Thu Mar 14 11:29:50 2013 -0700" }, "message": "ALSA: vmaster: Fix slave change notification\n\ncommit 2069d483b39a603a5f3428a19d3b4ac89aa97f48 upstream.\n\nWhen a value of a vmaster slave control is changed, the ctl change\nnotification is sometimes ignored. This happens when the master\ncontrol overrides, e.g. when the corresponding master control is\nmuted. The reason is that slave_put() returns the value of the actual\nslave put callback, and it doesn\u0027t reflect the virtual slave value\nchange.\n\nThis patch fixes the function just to return 1 whenever a slave value\nis changed.\n\nSigned-off-by: Takashi Iwai \u003ctiwai@suse.de\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "1515f18665088e33e35706bd35268a16e8e7665d", "tree": "cb54a188347e40c805429826ae1b4fcb726fddd0", "parents": [ "724285cf2c0ef53c2217a6a866ab50d57c386292" ], "author": { "name": "Sean Connor", "email": "sconnor004@allyinics.org", "time": "Thu Feb 28 09:20:00 2013 -0500" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Thu Mar 14 11:29:50 2013 -0700" }, "message": "ALSA: ice1712: Initialize card-\u003eprivate_data properly\n\ncommit 69a4cfdd444d1fe5c24d29b3a063964ac165d2cd upstream.\n\nSet card-\u003eprivate_data in snd_ice1712_create for fixing NULL\ndereference in snd_ice1712_remove().\n\nSigned-off-by: Sean Connor \u003csconnor004@allyinics.org\u003e\nSigned-off-by: Takashi Iwai \u003ctiwai@suse.de\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "724285cf2c0ef53c2217a6a866ab50d57c386292", "tree": "e43d0833c284196ace7af1ed7b42d80ce1c6316d", "parents": [ "b08994da73be68f17f82a522f4f129c18dbbf77f" ], "author": { "name": "Will Deacon", "email": "will.deacon@arm.com", "time": "Thu Feb 28 17:49:11 2013 +0100" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Thu Mar 14 11:29:50 2013 -0700" }, "message": "ARM: 7663/1: perf: fix ARMv7 EVTYPE_MASK to include NSH bit\n\ncommit f2fe09b055e2549de41fb107b34c60bac4a1b0cf upstream.\n\nMasked out PMXEVTYPER.NSH means that we can\u0027t enable profiling at PL2,\nregardless of the settings in the HDCR.\n\nThis patch fixes the broken mask.\n\nReported-by: Christoffer Dall \u003ccdall@cs.columbia.edu\u003e\nSigned-off-by: Will Deacon \u003cwill.deacon@arm.com\u003e\nSigned-off-by: Russell King \u003crmk+kernel@arm.linux.org.uk\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "b08994da73be68f17f82a522f4f129c18dbbf77f", "tree": "9ef4f61a17637eeb435862bb6e11b32e8fb3395a", "parents": [ "bc37694dbaf8604619228ccc6e34528182b3a987" ], "author": { "name": "Alex Deucher", "email": "alexander.deucher@amd.com", "time": "Wed Feb 27 12:01:58 2013 -0500" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Thu Mar 14 11:29:49 2013 -0700" }, "message": "drm/radeon: add primary dac adj quirk for R200 board\n\ncommit e8fc41377f5037ff7a661ea06adc05f1daec1548 upstream.\n\nvbios values are wrong leading to colors that are\ntoo bright. Use the default values instead.\n\nSigned-off-by: Alex Deucher \u003calexander.deucher@amd.com\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "bc37694dbaf8604619228ccc6e34528182b3a987", "tree": "1628db2c9b0630899717a786060804de8b643fa7", "parents": [ "ec2bc2f65c469aa5d0a1eb21f8404e0e3114bde4" ], "author": { "name": "Guenter Roeck", "email": "linux@roeck-us.net", "time": "Thu Feb 21 10:49:40 2013 -0800" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Thu Mar 14 11:29:49 2013 -0700" }, "message": "hwmon: (pmbus/ltc2978) Use detected chip ID to select supported functionality\n\ncommit f366fccd0809f13ba20d64cae3c83f7338c88af7 upstream.\n\nWe read the chip ID from the chip, use it to determine if the chip ID provided\nto the driver is correct, and report it if wrong. We should also use the\ncorrect chip ID to select supported functionality.\n\nSigned-off-by: Guenter Roeck \u003clinux@roeck-us.net\u003e\nAcked-by: Jean Delvare \u003ckhali@linux-fr.org\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "ec2bc2f65c469aa5d0a1eb21f8404e0e3114bde4", "tree": "2bce7b7a154e6bff7e658e62e4d1668106f70218", "parents": [ "cca30bd4c94123776dc3620cd13c6aedb76e4b55" ], "author": { "name": "Guenter Roeck", "email": "linux@roeck-us.net", "time": "Thu Feb 21 09:33:25 2013 -0800" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Thu Mar 14 11:29:49 2013 -0700" }, "message": "hwmon: (pmbus/ltc2978) Fix peak attribute handling\n\ncommit dbd712c2272764a536e29ad6841dba74989a39d9 upstream.\n\nPeak attributes were not initialized and cleared correctly.\nAlso, temp2_max is only supported on page 0 and thus does not need to be\nan array.\n\nSigned-off-by: Guenter Roeck \u003clinux@roeck-us.net\u003e\nAcked-by: Jean Delvare \u003ckhali@linux-fr.org\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "cca30bd4c94123776dc3620cd13c6aedb76e4b55", "tree": "ccd84ecbb358e3203b3b417b4dcec1a1695a6ae9", "parents": [ "fbad8075baa695da5da4952969682172966a4fac" ], "author": { "name": "Mark Brown", "email": "broonie@opensource.wolfsonmicro.com", "time": "Sat Mar 02 15:33:30 2013 +0800" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Thu Mar 14 11:29:49 2013 -0700" }, "message": "hwmon: (sht15) Check return value of regulator_enable()\n\ncommit 3e78080f81481aa8340374d5a37ae033c1cf4272 upstream.\n\nNot having power is a pretty serious error so check that we are able to\nenable the supply and error out if we can\u0027t.\n\nSigned-off-by: Mark Brown \u003cbroonie@opensource.wolfsonmicro.com\u003e\nSigned-off-by: Guenter Roeck \u003clinux@roeck-us.net\u003e\n\n" }, { "commit": "fbad8075baa695da5da4952969682172966a4fac", "tree": "4de9c4b8a6363687a93b79d9a3ee342b3d75b831", "parents": [ "c443082d1998879713ecf9f97ee4ba8c76f8b7f0" ], "author": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Thu Feb 21 15:36:38 2013 +1100" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Thu Mar 14 11:29:49 2013 -0700" }, "message": "md: raid0: fix error return from create_stripe_zones.\n\ncommit 58ebb34c49fcfcaa029e4b1c1453d92583900f9a upstream.\n\nCreate_stripe_zones returns an error slightly differently to\nraid0_run and to raid0_takeover_*.\n\nThe error returned used by the second was wrong and an error would\nresult in mddev-\u003eprivate being set to NULL and sooner or later a\ncrash.\n\nSo never return NULL, return ERR_PTR(err), not NULL from\ncreate_stripe_zones.\n\nThis bug has been present since 2.6.35 so the fix is suitable\nfor any kernel since then.\n\nSigned-off-by: NeilBrown \u003cneilb@suse.de\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "c443082d1998879713ecf9f97ee4ba8c76f8b7f0", "tree": "37f83d7390c5b3abc206ee45a5d327cb9b5ce5bb", "parents": [ "517557f2323d11a1a355e9c9155a1e315d87d487" ], "author": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Thu Feb 21 14:33:17 2013 +1100" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Thu Mar 14 11:29:49 2013 -0700" }, "message": "md: fix two bugs when attempting to resize RAID0 array.\n\ncommit a64685399181780998281fe07309a94b25dd24c3 upstream.\n\nYou cannot resize a RAID0 array (in terms of making the devices\nbigger), but the code doesn\u0027t entirely stop you.\nSo:\n\n disable setting of the available size on each device for\n RAID0 and Linear devices. This must not change as doing so\n can change the effective layout of data.\n\n Make sure that the size that raid0_size() reports is accurate,\n but rounding devices sizes to chunk sizes. As the device sizes\n cannot change now, this isn\u0027t so important, but it is best to be\n safe.\n\nWithout this change:\n mdadm --grow /dev/md0 -z max\n mdadm --grow /dev/md0 -Z max\n then read to the end of the array\n\ncan cause a BUG in a RAID0 array.\n\nThese bugs have been present ever since it became possible\nto resize any device, which is a long time. So the fix is\nsuitable for any -stable kerenl.\n\nSigned-off-by: NeilBrown \u003cneilb@suse.de\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "517557f2323d11a1a355e9c9155a1e315d87d487", "tree": "8809012bed39c1ba189e248a8f9aba3185c45c91", "parents": [ "f9c89dac69cb99c00d4c273cad43f466fb9a1c8b" ], "author": { "name": "Sebastian Riemer", "email": "sebastian.riemer@profitbricks.com", "time": "Thu Feb 21 13:28:09 2013 +1100" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Thu Mar 14 11:29:48 2013 -0700" }, "message": "md: protect against crash upon fsync on ro array\n\ncommit bbfa57c0f2243a7c31fd248d22e9861a2802cad5 upstream.\n\nIf an fsync occurs on a read-only array, we need to send a\ncompletion for the IO and may not increment the active IO count.\nOtherwise, we hit a bug trace and can\u0027t stop the MD array anymore.\n\nBy advice of Christoph Hellwig we return success upon a flush\nrequest but we return -EROFS for other writes.\nWe detect flush requests by checking if the bio has zero sectors.\n\nThis patch is suitable to any -stable kernel to which it applies.\n\nSigned-off-by: Sebastian Riemer \u003csebastian.riemer@profitbricks.com\u003e\nCc: Christoph Hellwig \u003chch@infradead.org\u003e\nCc: Ben Hutchings \u003cben@decadent.org.uk\u003e\nCc: NeilBrown \u003cneilb@suse.de\u003e\nReported-by: Ben Hutchings \u003cben@decadent.org.uk\u003e\nAcked-by: Paul Menzel \u003cpaulepanter@users.sourceforge.net\u003e\nSigned-off-by: NeilBrown \u003cneilb@suse.de\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "f9c89dac69cb99c00d4c273cad43f466fb9a1c8b", "tree": "49e3ea411e482407ad92c211ed416725291e45e9", "parents": [ "34127f32d576cb64717afade55c6fcff6b062451" ], "author": { "name": "Felix Fietkau", "email": "nbd@openwrt.org", "time": "Mon Feb 25 20:51:07 2013 +0100" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Thu Mar 14 11:29:43 2013 -0700" }, "message": "ath9k_hw: improve reset reliability after errors\n\ncommit 3412f2f086ea7531378fabe756bd4a1109994ae6 upstream.\n\nOn many different chips, important aspects of the MAC state are not\nfully cleared by a warm reset. This can show up as tx/rx hangs, those\nannoying \"DMA failed to stop in 10 ms...\" messages or other quirks.\n\nOn AR933x, the chip can occasionally get stuck in a way that only a\ndriver unload/reload or a reboot would bring it back to life.\n\nWith this patch, a full reset is issued when bringing the chip out of\nFULL-SLEEP state (after idle), or if either Rx or Tx was not shut down\nproperly. This makes the DMA related error messages disappear completely\nin my tests on AR933x, and the chip does not get stuck anymore.\n\nSigned-off-by: Felix Fietkau \u003cnbd@openwrt.org\u003e\nSigned-off-by: John W. Linville \u003clinville@tuxdriver.com\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "34127f32d576cb64717afade55c6fcff6b062451", "tree": "9d24c07e748d6430bef2aa6af300a20d5845e859", "parents": [ "97cf710a238290b049f1f09dd220ca2f813d5fb9" ], "author": { "name": "Felix Fietkau", "email": "nbd@openwrt.org", "time": "Fri Feb 22 21:09:17 2013 +0100" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Thu Mar 14 11:29:43 2013 -0700" }, "message": "ath9k: fix RSSI dummy marker value\n\ncommit a3d63cadbad97671d740a9698acc2c95d1ca6e79 upstream.\n\nRSSI is being stored internally as s8 in several places. The indication\nof an unset RSSI value, ATH_RSSI_DUMMY_MARKER, was supposed to have been\nset to 127, but ended up being set to 0x127 because of a code cleanup\nmistake. This could lead to invalid signal strength values in a few\nplaces.\n\nSigned-off-by: Felix Fietkau \u003cnbd@openwrt.org\u003e\nSigned-off-by: John W. Linville \u003clinville@tuxdriver.com\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "97cf710a238290b049f1f09dd220ca2f813d5fb9", "tree": "d6fbd5b02e7672710c5d94cb792d805f14a44932", "parents": [ "681e3b15fef858a9512d5fb2baceb85b0913385f" ], "author": { "name": "Avinash Patil", "email": "patila@marvell.com", "time": "Mon Feb 25 16:01:34 2013 -0800" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Thu Mar 14 11:29:43 2013 -0700" }, "message": "mwifiex: correct sleep delay counter\n\ncommit 3e7a4ff7c5b6423ddb644df9c41b8b6d2fb79d30 upstream.\n\nMaximum delay for waking up card is 50 ms. Because of typo in\ncounter, this delay goes to 500ms. This patch fixes the bug.\n\nSigned-off-by: Avinash Patil \u003cpatila@marvell.com\u003e\nSigned-off-by: Amitkumar Karwar \u003cakarwar@marvell.com\u003e\nSigned-off-by: Yogesh Ashok Powar \u003cyogeshp@marvell.com\u003e\nSigned-off-by: Bing Zhao \u003cbzhao@marvell.com\u003e\nSigned-off-by: John W. Linville \u003clinville@tuxdriver.com\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "681e3b15fef858a9512d5fb2baceb85b0913385f", "tree": "305a75805b006c16e5ced9bd6a356fb32607ca87", "parents": [ "7ae6c92933a962e3ff8b3999f88b5c7c86841b7f" ], "author": { "name": "Rusty Russell", "email": "rusty@rustcorp.com.au", "time": "Tue Mar 05 10:07:08 2013 +1030" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Thu Mar 14 11:29:42 2013 -0700" }, "message": "hw_random: make buffer usable in scatterlist.\n\ncommit f7f154f1246ccc5a0a7e9ce50932627d60a0c878 upstream.\n\nvirtio_rng feeds the randomness buffer handed by the core directly\ninto the scatterlist, since commit bb347d98079a547e80bd4722dee1de61e4dca0e8.\n\nHowever, if CONFIG_HW_RANDOM\u003dm, the static buffer isn\u0027t a linear address\n(at least on most archs). We could fix this in virtio_rng, but it\u0027s actually\nfar easier to just do it in the core as virtio_rng would have to allocate\na buffer every time (it doesn\u0027t know how much the core will want to read).\n\nReported-by: Aurelien Jarno \u003caurelien@aurel32.net\u003e\nTested-by: Aurelien Jarno \u003caurelien@aurel32.net\u003e\nSigned-off-by: Rusty Russell \u003crusty@rustcorp.com.au\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "7ae6c92933a962e3ff8b3999f88b5c7c86841b7f", "tree": "f5e3b5a652bfc743f25fa3c7814e27a4b72c183a", "parents": [ "1ecb6934fa86281d26d60d984f0e0e6554531813" ], "author": { "name": "Olaf Hering", "email": "olaf@aepfle.de", "time": "Tue Sep 18 17:48:01 2012 +0200" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Thu Mar 14 11:29:42 2013 -0700" }, "message": "ata_piix: reenable MS Virtual PC guests\n\ncommit d9904344fc4052fbe7e4dc137eba0dcdadf326bd upstream.\n\nAn earlier commit cd006086fa5d91414d8ff9ff2b78fbb593878e3c (\"ata_piix:\ndefer disks to the Hyper-V drivers by default\") broke MS Virtual PC\nguests. Hyper-V guests and Virtual PC guests have nearly identical DMI\ninfo. As a result the driver does currently ignore the emulated hardware\nin Virtual PC guests and defers the handling to hv_blkvsc. Since Virtual\nPC does not offer paravirtualized drivers no disks will be found in the\nguest.\n\nOne difference in the DMI info is the product version. This patch adds a\nmatch for MS Virtual PC 2007 and \"unignores\" the emulated hardware.\n\nThis was reported for openSuSE 12.1 in bugzilla:\nhttps://bugzilla.novell.com/show_bug.cgi?id\u003d737532\n\nHere is a detailed list of DMI info from example guests:\n\nhwinfo --bios:\n\nvirtual pc guest:\n\n System Info: #1\n Manufacturer: \"Microsoft Corporation\"\n Product: \"Virtual Machine\"\n Version: \"VS2005R2\"\n Serial: \"3178-9905-1533-4840-9282-0569-59\"\n UUID: undefined, but settable\n Wake-up: 0x06 (Power Switch)\n Board Info: #2\n Manufacturer: \"Microsoft Corporation\"\n Product: \"Virtual Machine\"\n Version: \"5.0\"\n Serial: \"3178-9905-1533-4840-9282-0569-59\"\n Chassis Info: #3\n Manufacturer: \"Microsoft Corporation\"\n Version: \"5.0\"\n Serial: \"3178-9905-1533-4840-9282-0569-59\"\n Asset Tag: \"7188-3705-6309-9738-9645-0364-00\"\n Type: 0x03 (Desktop)\n Bootup State: 0x03 (Safe)\n Power Supply State: 0x03 (Safe)\n Thermal State: 0x01 (Other)\n Security Status: 0x01 (Other)\n\nwin2k8 guest:\n\n System Info: #1\n Manufacturer: \"Microsoft Corporation\"\n Product: \"Virtual Machine\"\n Version: \"7.0\"\n Serial: \"9106-3420-9819-5495-1514-2075-48\"\n UUID: undefined, but settable\n Wake-up: 0x06 (Power Switch)\n Board Info: #2\n Manufacturer: \"Microsoft Corporation\"\n Product: \"Virtual Machine\"\n Version: \"7.0\"\n Serial: \"9106-3420-9819-5495-1514-2075-48\"\n Chassis Info: #3\n Manufacturer: \"Microsoft Corporation\"\n Version: \"7.0\"\n Serial: \"9106-3420-9819-5495-1514-2075-48\"\n Asset Tag: \"7076-9522-6699-1042-9501-1785-77\"\n Type: 0x03 (Desktop)\n Bootup State: 0x03 (Safe)\n Power Supply State: 0x03 (Safe)\n Thermal State: 0x01 (Other)\n Security Status: 0x01 (Other)\n\nwin2k12 guest:\n\n System Info: #1\n Manufacturer: \"Microsoft Corporation\"\n Product: \"Virtual Machine\"\n Version: \"7.0\"\n Serial: \"8179-1954-0187-0085-3868-2270-14\"\n UUID: undefined, but settable\n Wake-up: 0x06 (Power Switch)\n Board Info: #2\n Manufacturer: \"Microsoft Corporation\"\n Product: \"Virtual Machine\"\n Version: \"7.0\"\n Serial: \"8179-1954-0187-0085-3868-2270-14\"\n Chassis Info: #3\n Manufacturer: \"Microsoft Corporation\"\n Version: \"7.0\"\n Serial: \"8179-1954-0187-0085-3868-2270-14\"\n Asset Tag: \"8374-0485-4557-6331-0620-5845-25\"\n Type: 0x03 (Desktop)\n Bootup State: 0x03 (Safe)\n Power Supply State: 0x03 (Safe)\n Thermal State: 0x01 (Other)\n Security Status: 0x01 (Other)\n\nSigned-off-by: Olaf Hering \u003colaf@aepfle.de\u003e\nSigned-off-by: Jeff Garzik \u003cjgarzik@redhat.com\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "1ecb6934fa86281d26d60d984f0e0e6554531813", "tree": "7189db0c2e263bba7e36a27e0079d4cbb0993e7e", "parents": [ "d3e8a1806bb6a9f2b4d56de44a87efc18e3e82fd" ], "author": { "name": "Trond Myklebust", "email": "Trond.Myklebust@netapp.com", "time": "Fri Feb 22 14:57:57 2013 -0500" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Thu Mar 14 11:29:42 2013 -0700" }, "message": "SUNRPC: Don\u0027t start the retransmission timer when out of socket space\n\ncommit a9a6b52ee1baa865283a91eb8d443ee91adfca56 upstream.\n\nIf the socket is full, we\u0027re better off just waiting until it empties,\nor until the connection is broken. The reason why we generally don\u0027t\nwant to time out is that the call to xprt-\u003eops-\u003erelease_xprt() will\ntrigger a connection reset, which isn\u0027t helpful...\n\nLet\u0027s make an exception for soft RPC calls, since they have to provide\ntimeout guarantees.\n\nSigned-off-by: Trond Myklebust \u003cTrond.Myklebust@netapp.com\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "d3e8a1806bb6a9f2b4d56de44a87efc18e3e82fd", "tree": "5957d80e189d2fc088f68f9566febe75d147fec0", "parents": [ "18d2c795ad10c2834518b083e3c6a58400f46a1a" ], "author": { "name": "Trond Myklebust", "email": "Trond.Myklebust@netapp.com", "time": "Fri Feb 22 12:53:43 2013 -0500" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Thu Mar 14 11:29:42 2013 -0700" }, "message": "NFS: Don\u0027t allow NFS silly-renamed files to be deleted, no signal\n\ncommit 5a7a613a47a715711b3f2d3322a0eac21d459166 upstream.\n\nCommit 73ca100 broke the code that prevents the client from deleting\na silly renamed dentry. This affected \"delete on last close\"\nsemantics as after that commit, nothing prevented removal of\nsilly-renamed files. As a result, a process holding a file open\ncould easily get an ESTALE on the file in a directory where some\nother process issued \u0027rm -rf some_dir_containing_the_file\u0027 twice.\nBefore the commit, any attempt at unlinking silly renamed files would\nfail inside may_delete() with -EBUSY because of the\nDCACHE_NFSFS_RENAMED flag. The following testcase demonstrates\nthe problem:\n tail -f /nfsmnt/dir/file \u0026\n rm -rf /nfsmnt/dir\n rm -rf /nfsmnt/dir\n # second removal does not fail, \u0027tail\u0027 process receives ESTALE\n\nThe problem with the above commit is that it unhashes the old and\nnew dentries from the lookup path, even in the normal case when\na signal is not encountered and it would have been safe to call\nd_move. Unfortunately the old dentry has the special\nDCACHE_NFSFS_RENAMED flag set on it. Unhashing has the\nside-effect that future lookups call d_alloc(), allocating a new\ndentry without the special flag for any silly-renamed files. As a\nresult, subsequent calls to unlink silly renamed files do not fail\nbut allow the removal to go through. This will result in ESTALE\nerrors for any other process doing operations on the file.\n\nTo fix this, go back to using d_move on success.\nFor the signal case, it\u0027s unclear what we may safely do beyond d_drop.\n\nReported-by: Dave Wysochanski \u003cdwysocha@redhat.com\u003e\nSigned-off-by: Trond Myklebust \u003cTrond.Myklebust@netapp.com\u003e\nAcked-by: Jeff Layton \u003cjlayton@redhat.com\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "18d2c795ad10c2834518b083e3c6a58400f46a1a", "tree": "6c3d84663eb9936f6be4a24f3a2a199165795ff0", "parents": [ "d0e44ede196b82c0448776b4b0c7c59989e3bea8" ], "author": { "name": "Jeff Layton", "email": "jlayton@redhat.com", "time": "Fri Feb 01 15:11:01 2013 -0500" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Thu Mar 14 11:29:42 2013 -0700" }, "message": "cifs: ensure that cifs_get_root() only traverses directories\n\ncommit ce2ac52105aa663056dfc17966ebed1bf93e6e64 upstream.\n\nKjell Braden reported this oops:\n\n[ 833.211970] BUG: unable to handle kernel NULL pointer dereference at (null)\n[ 833.212816] IP: [\u003c (null)\u003e] (null)\n[ 833.213280] PGD 1b9b2067 PUD e9f7067 PMD 0\n[ 833.213874] Oops: 0010 [#1] SMP\n[ 833.214344] CPU 0\n[ 833.214458] Modules linked in: des_generic md4 nls_utf8 cifs vboxvideo drm snd_intel8x0 snd_ac97_codec ac97_bus snd_pcm snd_seq_midi snd_rawmidi snd_seq_midi_event snd_seq bnep rfcomm snd_timer bluetooth snd_seq_device ppdev snd vboxguest parport_pc joydev mac_hid soundcore snd_page_alloc psmouse i2c_piix4 serio_raw lp parport usbhid hid e1000\n[ 833.215629]\n[ 833.215629] Pid: 1752, comm: mount.cifs Not tainted 3.0.0-rc7-bisectcifs-fec11dd9a0+ #18 innotek GmbH VirtualBox/VirtualBox\n[ 833.215629] RIP: 0010:[\u003c0000000000000000\u003e] [\u003c (null)\u003e] (null)\n[ 833.215629] RSP: 0018:ffff8800119c9c50 EFLAGS: 00010282\n[ 833.215629] RAX: ffffffffa02186c0 RBX: ffff88000c427780 RCX: 0000000000000000\n[ 833.215629] RDX: 0000000000000000 RSI: ffff88000c427780 RDI: ffff88000c4362e8\n[ 833.215629] RBP: ffff8800119c9c88 R08: ffff88001fc15e30 R09: 00000000d69515c7\n[ 833.215629] R10: ffffffffa0201972 R11: ffff88000e8f6a28 R12: ffff88000c4362e8\n[ 833.215629] R13: 0000000000000000 R14: 0000000000000000 R15: ffff88001181aaa6\n[ 833.215629] FS: 00007f2986171700(0000) GS:ffff88001fc00000(0000) knlGS:0000000000000000\n[ 833.215629] CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b\n[ 833.215629] CR2: 0000000000000000 CR3: 000000001b982000 CR4: 00000000000006f0\n[ 833.215629] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000\n[ 833.215629] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400\n[ 833.215629] Process mount.cifs (pid: 1752, threadinfo ffff8800119c8000, task ffff88001c1c16f0)\n[ 833.215629] Stack:\n[ 833.215629] ffffffff8116a9b5 ffff8800119c9c88 ffffffff81178075 0000000000000286\n[ 833.215629] 0000000000000000 ffff88000c4276c0 ffff8800119c9ce8 ffff8800119c9cc8\n[ 833.215629] ffffffff8116b06e ffff88001bc6fc00 ffff88000c4276c0 ffff88000c4276c0\n[ 833.215629] Call Trace:\n[ 833.215629] [\u003cffffffff8116a9b5\u003e] ? d_alloc_and_lookup+0x45/0x90\n[ 833.215629] [\u003cffffffff81178075\u003e] ? d_lookup+0x35/0x60\n[ 833.215629] [\u003cffffffff8116b06e\u003e] __lookup_hash.part.14+0x9e/0xc0\n[ 833.215629] [\u003cffffffff8116b1d6\u003e] lookup_one_len+0x146/0x1e0\n[ 833.215629] [\u003cffffffff815e4f7e\u003e] ? _raw_spin_lock+0xe/0x20\n[ 833.215629] [\u003cffffffffa01eef0d\u003e] cifs_do_mount+0x26d/0x500 [cifs]\n[ 833.215629] [\u003cffffffff81163bd3\u003e] mount_fs+0x43/0x1b0\n[ 833.215629] [\u003cffffffff8117d41a\u003e] vfs_kern_mount+0x6a/0xd0\n[ 833.215629] [\u003cffffffff8117e584\u003e] do_kern_mount+0x54/0x110\n[ 833.215629] [\u003cffffffff8117fdc2\u003e] do_mount+0x262/0x840\n[ 833.215629] [\u003cffffffff81108a0e\u003e] ? __get_free_pages+0xe/0x50\n[ 833.215629] [\u003cffffffff8117f9ca\u003e] ? copy_mount_options+0x3a/0x180\n[ 833.215629] [\u003cffffffff8118075d\u003e] sys_mount+0x8d/0xe0\n[ 833.215629] [\u003cffffffff815ece82\u003e] system_call_fastpath+0x16/0x1b\n[ 833.215629] Code: Bad RIP value.\n[ 833.215629] RIP [\u003c (null)\u003e] (null)\n[ 833.215629] RSP \u003cffff8800119c9c50\u003e\n[ 833.215629] CR2: 0000000000000000\n[ 833.238525] ---[ end trace ec00758b8d44f529 ]---\n\nWhen walking down the path on the server, it\u0027s possible to hit a\nsymlink. The path walking code assumes that the caller will handle that\nsituation properly, but cifs_get_root() isn\u0027t set up for it. This patch\nprevents the oops by simply returning an error.\n\nA better solution would be to try and chase the symlinks here, but that\u0027s\nfairly complicated to handle.\n\nFixes:\n\n https://bugzilla.kernel.org/show_bug.cgi?id\u003d53221\n\nReported-and-tested-by: Kjell Braden \u003cafflux@pentabarf.de\u003e\nSigned-off-by: Jeff Layton \u003cjlayton@redhat.com\u003e\nSigned-off-by: Steve French \u003csfrench@us.ibm.com\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "d0e44ede196b82c0448776b4b0c7c59989e3bea8", "tree": "c2a31136a2dd6435b51ab37a03e9738ffd61f26a", "parents": [ "a5646410c2d80c4dd4692f5f6bc2fcdfc3aa557b" ], "author": { "name": "Thomas Gleixner", "email": "tglx@linutronix.de", "time": "Wed Feb 20 14:06:20 2013 -0500" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Thu Mar 14 11:29:42 2013 -0700" }, "message": "btrfs: Init io_lock after cloning btrfs device struct\n\ncommit 1cba0cdf5e4dbcd9e5fa5b54d7a028e55e2ca057 upstream.\n\n__btrfs_close_devices() clones btrfs device structs with\nmemcpy(). Some of the fields in the clone are reinitialized, but it\u0027s\nmissing to init io_lock. In mainline this goes unnoticed, but on RT it\nleaves the plist pointing to the original about to be freed lock\nstruct.\n\nInitialize io_lock after cloning, so no references to the original\nstruct are left.\n\nReported-and-tested-by: Mike Galbraith \u003cefault@gmx.de\u003e\nSigned-off-by: Thomas Gleixner \u003ctglx@linutronix.de\u003e\nSigned-off-by: Chris Mason \u003cchris.mason@fusionio.com\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "a5646410c2d80c4dd4692f5f6bc2fcdfc3aa557b", "tree": "eeaf3a5dc5bbbbe2abe76ecee486769078a0b480", "parents": [ "c60de9344ceeedd5f61a655af34306002fda9167" ], "author": { "name": "Asias He", "email": "asias@redhat.com", "time": "Wed Feb 27 13:29:29 2013 +0800" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Thu Mar 14 11:29:42 2013 -0700" }, "message": "target/pscsi: Fix page increment\n\ncommit 472b72f2db7831d7dbe22ffdff4adee3bd49b05d upstream.\n\nThe page++ is wrong. It makes bio_add_pc_page() pointing to a wrong page\naddress if the \u0027while (len \u003e 0 \u0026\u0026 data_len \u003e 0) { ... }\u0027 loop is\nexecuted more than one once.\n\nSigned-off-by: Asias He \u003casias@redhat.com\u003e\nSigned-off-by: Nicholas Bellinger \u003cnab@linux-iscsi.org\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "c60de9344ceeedd5f61a655af34306002fda9167", "tree": "1970c7ee8ee3d51ef4824aeef694e300942acaea", "parents": [ "76284215d03e98df97e12fa5b41ce5241ba47c35" ], "author": { "name": "K. Y. Srinivasan", "email": "kys@microsoft.com", "time": "Wed Feb 06 05:15:28 2013 -0800" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Thu Mar 14 11:29:42 2013 -0700" }, "message": "SCSI: storvsc: Initialize the sglist\n\ncommit 9d2696e658ef4f209955ddaa987d43f1a1bd81a1 upstream.\n\nProperly initialize scatterlist before using it.\n\nSigned-off-by: K. Y. Srinivasan \u003ckys@microsoft.com\u003e\nSigned-off-by: James Bottomley \u003cJBottomley@Parallels.com\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "76284215d03e98df97e12fa5b41ce5241ba47c35", "tree": "a08bce66e47d44605423efdd663a72fb0dea774a", "parents": [ "f8ac69742302f0571303c7b21157295a122bec5d" ], "author": { "name": "Dan Carpenter", "email": "dan.carpenter@oracle.com", "time": "Mon Feb 11 22:03:18 2013 +0300" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Thu Mar 14 11:29:41 2013 -0700" }, "message": "SCSI: dc395x: uninitialized variable in device_alloc()\n\ncommit 208afec4f3be8c51ad6eebe6611dd6d2ad2fa298 upstream.\n\nThis bug was introduced back in bitkeeper days in 2003. We use\n\"dcb-\u003edev_mode\" before it has been initialized.\n\nSigned-off-by: Dan Carpenter \u003cdan.carpenter@oracle.com\u003e\nAcked-by: Oliver Neukum \u003coliver@neukum.org\u003e\nSigned-off-by: James Bottomley \u003cJBottomley@Parallels.com\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "f8ac69742302f0571303c7b21157295a122bec5d", "tree": "21125af2d78d323a2189fb75e0319f12b6eae2a4", "parents": [ "b9dfac7b1a9263181f7027285d5335f25b1eabfd" ], "author": { "name": "Konrad Rzeszutek Wilk", "email": "konrad.wilk@oracle.com", "time": "Thu Feb 28 09:05:41 2013 -0500" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Thu Mar 14 11:29:41 2013 -0700" }, "message": "xen/pci: We don\u0027t do multiple MSI\u0027s.\n\ncommit 884ac2978a295b7df3c4a686d3bff6932bbbb460 upstream.\n\nThere is no hypercall to setup multiple MSI per PCI device.\nAs such with these two new commits:\n- 08261d87f7d1b6253ab3223756625a5c74532293\n PCI/MSI: Enable multiple MSIs with pci_enable_msi_block_auto()\n- 5ca72c4f7c412c2002363218901eba5516c476b1\n AHCI: Support multiple MSIs\n\nwe would call the PHYSDEVOP_map_pirq \u0027nvec\u0027 times with the same\ncontents of the PCI device. Sander discovered that we would get\nthe same PIRQ value \u0027nvec\u0027 times and return said values to the\ncaller. That of course meant that the device was configured only\nwith one MSI and AHCI would fail with:\n\nahci 0000:00:11.0: version 3.0\nxen: registering gsi 19 triggering 0 polarity 1\nxen: --\u003e pirq\u003d19 -\u003e irq\u003d19 (gsi\u003d19)\n(XEN) [2013-02-27 19:43:07] IOAPIC[0]: Set PCI routing entry (6-19 -\u003e 0x99 -\u003e IRQ 19 Mode:1 Active:1)\nahci 0000:00:11.0: AHCI 0001.0200 32 slots 4 ports 6 Gbps 0xf impl SATA mode\nahci 0000:00:11.0: flags: 64bit ncq sntf ilck pm led clo pmp pio slum part\nahci: probe of 0000:00:11.0 failed with error -22\n\nThat is b/c in ahci_host_activate the second call to\ndevm_request_threaded_irq would return -EINVAL as we passed in\n(on the second run) an IRQ that was never initialized.\n\nReported-and-Tested-by: Sander Eikelenboom \u003clinux@eikelenboom.it\u003e\nSigned-off-by: Konrad Rzeszutek Wilk \u003ckonrad.wilk@oracle.com\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "b9dfac7b1a9263181f7027285d5335f25b1eabfd", "tree": "b6f022038c1070c453bba6626e918224cca1f5ab", "parents": [ "65723919649125f443ecfb2373b00f9febc62c47" ], "author": { "name": "Russell King", "email": "rmk+kernel@arm.linux.org.uk", "time": "Mon Feb 25 16:10:42 2013 +0000" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Thu Mar 14 11:29:41 2013 -0700" }, "message": "ARM: fix scheduling while atomic warning in alignment handling code\n\ncommit b255188f90e2bade1bd11a986dd1ca4861869f4d upstream.\n\nPaolo Pisati reports that IPv6 triggers this warning:\n\nBUG: scheduling while atomic: swapper/0/0/0x40000100\nModules linked in:\n[\u003cc001b1c4\u003e] (unwind_backtrace+0x0/0xf0) from [\u003cc0503c5c\u003e] (__schedule_bug+0x48/0x5c)\n[\u003cc0503c5c\u003e] (__schedule_bug+0x48/0x5c) from [\u003cc0508608\u003e] (__schedule+0x700/0x740)\n[\u003cc0508608\u003e] (__schedule+0x700/0x740) from [\u003cc007007c\u003e] (__cond_resched+0x24/0x34)\n[\u003cc007007c\u003e] (__cond_resched+0x24/0x34) from [\u003cc05086dc\u003e] (_cond_resched+0x3c/0x44)\n[\u003cc05086dc\u003e] (_cond_resched+0x3c/0x44) from [\u003cc0021f6c\u003e] (do_alignment+0x178/0x78c)\n[\u003cc0021f6c\u003e] (do_alignment+0x178/0x78c) from [\u003cc00083e0\u003e] (do_DataAbort+0x34/0x98)\n[\u003cc00083e0\u003e] (do_DataAbort+0x34/0x98) from [\u003cc0509a60\u003e] (__dabt_svc+0x40/0x60)\nException stack(0xc0763d70 to 0xc0763db8)\n3d60: e97e805e e97e806e 2c000000 11000000\n3d80: ea86bb00 0000002c 00000011 e97e807e c076d2a8 e97e805e e97e806e 0000002c\n3da0: 3d000000 c0763dbc c04b98fc c02a8490 00000113 ffffffff\n[\u003cc0509a60\u003e] (__dabt_svc+0x40/0x60) from [\u003cc02a8490\u003e] (__csum_ipv6_magic+0x8/0xc8)\n\nFix this by using probe_kernel_address() stead of __get_user().\n\nReported-by: Paolo Pisati \u003cp.pisati@gmail.com\u003e\nTested-by: Paolo Pisati \u003cp.pisati@gmail.com\u003e\nSigned-off-by: Russell King \u003crmk+kernel@arm.linux.org.uk\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "65723919649125f443ecfb2373b00f9febc62c47", "tree": "7c4beaa8ce18d4eb4d9e8da605f46696d89533aa", "parents": [ "2713e2797a78a0fdda765bc5ad7fed41e94818ba" ], "author": { "name": "Russell King", "email": "rmk+kernel@arm.linux.org.uk", "time": "Mon Feb 25 16:09:12 2013 +0000" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Thu Mar 14 11:29:41 2013 -0700" }, "message": "ARM: VFP: fix emulation of second VFP instruction\n\ncommit 5e4ba617c1b584b2e376f31a63bd4e734109318a upstream.\n\nMartin Storsjö reports that the sequence:\n\n ee312ac1 vsub.f32 s4, s3, s2\n ee702ac0 vsub.f32 s5, s1, s0\n e59f0028 ldr r0, [pc, #40]\n ee111a90 vmov r1, s3\n\non Raspberry Pi (implementor 41 architecture 1 part 20 variant b rev 5)\nwhere s3 is a denormal and s2 is zero results in incorrect behaviour -\nthe instruction \"vsub.f32 s5, s1, s0\" is not executed:\n\n VFP: bounce: trigger ee111a90 fpexc d0000780\n VFP: emulate: INST\u003d0xee312ac1 SCR\u003d0x00000000\n ...\n\nAs we can see, the instruction triggering the exception is the \"vmov\"\ninstruction, and we emulate the \"vsub.f32 s4, s3, s2\" but fail to\nproperly take account of the FPEXC_FP2V flag in FPEXC. This is because\nthe test for the second instruction register being valid is bogus, and\nwill always skip emulation of the second instruction.\n\nReported-by: Martin Storsjö \u003cmartin@martin.st\u003e\nTested-by: Martin Storsjö \u003cmartin@martin.st\u003e\nSigned-off-by: Russell King \u003crmk+kernel@arm.linux.org.uk\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "2713e2797a78a0fdda765bc5ad7fed41e94818ba", "tree": "affc7b9c0b3dcb3de601c67e1553f4000016c776", "parents": [ "e7e24f96cacd091ecd6ed0a4c10c83daae28f3c4" ], "author": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Mon Mar 04 06:07:21 2013 +0800" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Mon Mar 04 06:07:21 2013 +0800" }, "message": "Linux 3.4.35\n" }, { "commit": "e7e24f96cacd091ecd6ed0a4c10c83daae28f3c4", "tree": "f834206602993d0f9bc5efe1d16294c58814ee0b", "parents": [ "a059654e30e7f0d0aaba17a44165332443d3f48e" ], "author": { "name": "Alexey Klimov", "email": "klimov.linux@gmail.com", "time": "Mon Nov 12 02:57:03 2012 -0300" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Mon Mar 04 06:06:46 2013 +0800" }, "message": "usb hid quirks for Masterkit MA901 usb radio\n\ncommit 0322bd3980b3ebf7dde8474e22614cb443d6479a upstream.\n\nDon\u0027t let Masterkit MA901 USB radio be handled by usb hid drivers.\nThis device will be handled by radio-ma901.c driver.\n\nSigned-off-by: Alexey Klimov \u003cklimov.linux@gmail.com\u003e\nAcked-by: Hans Verkuil \u003chans.verkuil@cisco.com\u003e\nAcked-by: Jiri Kosina \u003cjkosina@suse.cz\u003e\nSigned-off-by: Mauro Carvalho Chehab \u003cmchehab@redhat.com\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "a059654e30e7f0d0aaba17a44165332443d3f48e", "tree": "34fafd1361cdf3c1518188817d84738cab63c5ac", "parents": [ "78b6767929e77f40b455b115d1643b82678b6a26" ], "author": { "name": "James Ralston", "email": "james.d.ralston@intel.com", "time": "Fri Feb 08 17:24:12 2013 -0800" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Mon Mar 04 06:06:45 2013 +0800" }, "message": "ata_piix: Add Device IDs for Intel Wellsburg PCH\n\ncommit 3aee8bc52c415aba8148f144e5e5359b0fd75dd1 upstream.\n\nThis patch adds the IDE-mode SATA Device IDs for the Intel Wellsburg PCH\n\nSigned-off-by: James Ralston \u003cjames.d.ralston@intel.com\u003e\nSigned-off-by: Jeff Garzik \u003cjgarzik@redhat.com\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "78b6767929e77f40b455b115d1643b82678b6a26", "tree": "91f96132fe860300e27ebb8b8a3d27d1348bd5f3", "parents": [ "3f14f68ff0121c770930b061fe23008af45006a2" ], "author": { "name": "Seth Heasley", "email": "seth.heasley@intel.com", "time": "Fri Jan 25 11:57:05 2013 -0800" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Mon Mar 04 06:06:45 2013 +0800" }, "message": "ata_piix: IDE-mode SATA patch for Intel Avoton DeviceIDs\n\ncommit aaa515277db9585eeb4fdeb4637b9f9df50a1dd9 upstream.\n\nThis patch adds the IDE-mode SATA DeviceIDs for the Intel Avoton SOC.\n\nSigned-off-by: Seth Heasley \u003cseth.heasley@intel.com\u003e\nSigned-off-by: Jeff Garzik \u003cjgarzik@redhat.com\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "3f14f68ff0121c770930b061fe23008af45006a2", "tree": "c8ba28ceae4e0fc3f8cc1b011d2e8d88167d76ab", "parents": [ "0685b5924819447dad0413312b508e68168a1ee2" ], "author": { "name": "Vinson Lee", "email": "vlee@twitter.com", "time": "Tue Feb 26 18:30:30 2013 -0800" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Mon Mar 04 06:06:45 2013 +0800" }, "message": "perf tools: Fix build with bison 2.3 and older.\n\ncommit 85df3b3769222894e9692b383c7af124b7721086 upstream.\n\nThe %name-prefix \"prefix\" syntax is not available on bison 2.3 and\nolder. Substitute with the -p \"prefix\" command-line option for\ncompatibility with older versions of bison.\n\nThis patch fixes this build error with older versions of bison.\n\n CC util/sysfs.o\n BISON util/pmu-bison.c\nutil/pmu.y:2.14-24: syntax error, unexpected string, expecting \u003d\nmake: *** [util/pmu-bison.c] Error 1\n\nSigned-off-by: Vinson Lee \u003cvlee@twitter.com\u003e\nTested-by: Li Zefan \u003clizefan@huawei.com\u003e\nCc: Ingo Molnar \u003cmingo@redhat.com\u003e\nCc: Jiri Olsa \u003cjolsa@redhat.com\u003e\nCc: Li Zefan \u003clizefan@huawei.com\u003e\nCc: Namhyung Kim \u003cnamhyung@gmail.com\u003e\nCc: Paul Mackerras \u003cpaulus@samba.org\u003e\nCc: Pekka Enberg \u003cpenberg@kernel.org\u003e\nLink: http://lkml.kernel.org/r/1360792138-29186-1-git-send-email-vlee@twitter.com\nSigned-off-by: Arnaldo Carvalho de Melo \u003cacme@redhat.com\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n" }, { "commit": "0685b5924819447dad0413312b508e68168a1ee2", "tree": "6c28d6da87c5a8171da679408beab513cb5c4ffa", "parents": [ "e4cd1e4dba29c756272c2ee9d06b094b4319b90a" ], "author": { "name": "Ian Abbott", "email": "abbotti@mev.co.uk", "time": "Wed Feb 27 10:56:19 2013 +0000" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Mon Mar 04 06:06:45 2013 +0800" }, "message": "staging: comedi: check s-\u003easync for poll(), read() and write()\n\ncommit cc400e185c07c15a42d2635995f422de5b94b696 upstream.\n\nSome low-level comedi drivers (incorrectly) point `dev-\u003eread_subdev` or\n`dev-\u003ewrite_subdev` to a subdevice that does not support asynchronous\ncommands. Comedi\u0027s poll(), read() and write() file operation handlers\nassume these subdevices do support asynchronous commands. In\nparticular, they assume `s-\u003easync` is valid (where `s` points to the\nread or write subdevice), which it won\u0027t be if it has been set\nincorrectly. This can lead to a NULL pointer dereference.\n\nCheck `s-\u003easync` is non-NULL in `comedi_poll()`, `comedi_read()` and\n`comedi_write()` to avoid the bug.\n\nSigned-off-by: Ian Abbott \u003cabbotti@mev.co.uk\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "e4cd1e4dba29c756272c2ee9d06b094b4319b90a", "tree": "248ff8f159a9473ab6e16ecad27245e332f5a754", "parents": [ "1e05b9964644382e9994e62dc5c8eb815e5225fa" ], "author": { "name": "Ian Abbott", "email": "abbotti@mev.co.uk", "time": "Wed Feb 27 12:52:46 2013 +0000" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Mon Mar 04 06:06:45 2013 +0800" }, "message": "staging: comedi: ni_labpc: set up command4 register *after* command3\n\nCommit 22056e2b46246d97ff0f7c6e21a77b8daa07f02c upstream.\n\nTuomas \u003ctvainikk _at_ gmail _dot_ com\u003e reported problems getting\nmeaningful output from a Lab-PC+ in differential mode for AI cmds, but\nAI insn reads gave correct readings. He tracked it down to two\nproblems, one of which is addressed by this patch.\n\nIt seems that writing to the command3 register after writing to the\ncommand4 register in `labpc_ai_cmd()` messes up the differential\nreference bit setting in the command4 register. Set up the command4\nregister after the command3 register (as in `labpc_ai_rinsn()`) to avoid\nthe problem.\n\nThanks to Tuomas for suggesting the fix.\n\nSigned-off-by: Ian Abbott \u003cabbotti@mev.co.uk\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "1e05b9964644382e9994e62dc5c8eb815e5225fa", "tree": "52941852db4bd560ee32abaf033d208c6633b751", "parents": [ "427e85ba0d2e3811c130714eea3fec0800ef2fcd" ], "author": { "name": "Ian Abbott", "email": "abbotti@mev.co.uk", "time": "Wed Feb 27 12:52:45 2013 +0000" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Mon Mar 04 06:06:44 2013 +0800" }, "message": "staging: comedi: ni_labpc: correct differential channel sequence for AI commands\n\nCommit 4c4bc25d0fa6beaf054c0b4c3b324487f266c820 upstream.\n\nTuomas \u003ctvainikk _at_ gmail _dot_ com\u003e reported problems getting\nmeaningful output from a Lab-PC+ in differential mode for AI cmds, but\nAI insn reads gave correct readings. He tracked it down to two\nproblems, one of which is addressed by this patch.\n\nIt seems the setting of the channel bits for particular scanning modes\nwas incorrect for differential mode. (Only half the number of channels\nare available in differential mode; comedi refers to them as channels 0,\n1, 2 and 3, but the hardware documentation refers to them as channels 0,\n2, 4 and 6.) In differential mode, the setting of the channel enable\nbits in the command1 register should depend on whether the scan enable\nbit is set. Effectively, we need to double the comedi channel number\nwhen the scan enable bit is not set in differential mode. The scan\nenable bit gets set when the AI scan mode is `MODE_MULT_CHAN_UP` or\n`MODE_MULT_CHAN_DOWN`, and gets cleared when the AI scan mode is\n`MODE_SINGLE_CHAN` or `MODE_SINGLE_CHAN_INTERVAL`. The existing test\nfor whether the comedi channel number needs to be doubled in\ndifferential mode is incorrect in `labpc_ai_cmd()`. This patch corrects\nthe test.\n\nThanks to Tuomas for suggesting the fix.\n\nSigned-off-by: Ian Abbott \u003cabbotti@mev.co.uk\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "427e85ba0d2e3811c130714eea3fec0800ef2fcd", "tree": "0ab997499b615cbe9a9929f34d92c40d6187083b", "parents": [ "7eb0fad53ef76201d81a2e9e1bad5b68a457e4e3" ], "author": { "name": "Joseph Salisbury", "email": "joseph.salisbury@canonical.com", "time": "Tue Feb 05 00:16:29 2013 +0000" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Mon Mar 04 06:06:44 2013 +0800" }, "message": "ACPI: Add DMI entry for Sony VGN-FW41E_H\n\ncommit 66f2fda93b67fa744d406e6dcf443f67bac204b6 upstream.\n\nThis patch adds a quirk to allow the Sony VGN-FW41E_H to suspend/resume\nproperly.\n\nReferences: http://bugs.launchpad.net/bugs/1113547\nSigned-off-by: Joseph Salisbury \u003cjoseph.salisbury@canonical.com\u003e\nSigned-off-by: Rafael J. Wysocki \u003crafael.j.wysocki@intel.com\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "7eb0fad53ef76201d81a2e9e1bad5b68a457e4e3", "tree": "db4fcf2a3f452c623755d6141ba775badc747162", "parents": [ "f9a8884a35a74f1fb9f12a17f62331bdc6eac2af" ], "author": { "name": "Rajanikanth H.V", "email": "rajanikanth.hv@stericsson.com", "time": "Wed Jan 23 09:56:45 2013 +0530" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Mon Mar 04 06:06:44 2013 +0800" }, "message": "ab8500_btemp: Demote initcall sequence\n\ncommit eeb0751c99522a4d1bbcc7b6bc1460cd07d07488 upstream.\n\nPower supply subsystem creates thermal zone device for the property\n\u0027POWER_SUPPLY_PROP_TEMP\u0027 which requires thermal subsystem to be ready\nbefore \u0027ab8500 battery temperature monitor\u0027 driver is initialized. ab8500\nbtemp driver is initialized with subsys_initcall whereas thermal subsystem\nis initialized with fs_initcall which causes\nthermal_zone_device_register(...) to crash since the required structure\n\u0027thermal_class\u0027 is not initialized yet:\n\nUnable to handle kernel NULL pointer dereference at virtual address 000000a4\npgd \u003d c0004000\n[000000a4] *pgd\u003d00000000\nInternal error: Oops: 5 [#1] PREEMPT SMP ARM\nModules linked in:\nCPU: 0 Tainted: G W (3.8.0-rc4-00001-g632fda8-dirty #1)\nPC is at _raw_spin_lock+0x18/0x54\nLR is at get_device_parent+0x50/0x1b8\npc : [\u003cc02f1dd0\u003e] lr : [\u003cc01cb248\u003e] psr: 60000013\nsp : ef04bdc8 ip : 00000000 fp : c0446180\nr10: ef216e38 r9 : c03af5d0 r8 : ef275c18\nr7 : 00000000 r6 : c0476c14 r5 : ef275c18 r4 : ef095840\nr3 : ef04a000 r2 : 00000001 r1 : 00000000 r0 : 000000a4\nFlags: nZCv IRQs on FIQs on Mode SVC_32 ISA ARM Segment kernel\nControl: 10c5787d Table: 0000404a DAC: 00000015\nProcess swapper/0 (pid: 1, stack limit \u003d 0xef04a238)\nStack: (0xef04bdc8 to 0xef04c000)\n[...]\n[\u003cc02f1dd0\u003e] (_raw_spin_lock+0x18/0x54) from [\u003cc01cb248\u003e] (get_device_parent+0x50/0x1b8)\n[\u003cc01cb248\u003e] (get_device_parent+0x50/0x1b8) from [\u003cc01cb8d8\u003e] (device_add+0xa4/0x574)\n[\u003cc01cb8d8\u003e] (device_add+0xa4/0x574) from [\u003cc020b91c\u003e] (thermal_zone_device_register+0x118/0x938)\n[\u003cc020b91c\u003e] (thermal_zone_device_register+0x118/0x938) from [\u003cc0202030\u003e] (power_supply_register+0x170/0x1f8)\n[\u003cc0202030\u003e] (power_supply_register+0x170/0x1f8) from [\u003cc02055ec\u003e] (ab8500_btemp_probe+0x208/0x47c)\n[\u003cc02055ec\u003e] (ab8500_btemp_probe+0x208/0x47c) from [\u003cc01cf0dc\u003e] (platform_drv_probe+0x14/0x18)\n[\u003cc01cf0dc\u003e] (platform_drv_probe+0x14/0x18) from [\u003cc01cde70\u003e] (driver_probe_device+0x74/0x20c)\n[\u003cc01cde70\u003e] (driver_probe_device+0x74/0x20c) from [\u003cc01ce094\u003e] (__driver_attach+0x8c/0x90)\n[\u003cc01ce094\u003e] (__driver_attach+0x8c/0x90) from [\u003cc01cc640\u003e] (bus_for_each_dev+0x4c/0x80)\n[\u003cc01cc640\u003e] (bus_for_each_dev+0x4c/0x80) from [\u003cc01cd6b4\u003e] (bus_add_driver+0x16c/0x23c)\n[\u003cc01cd6b4\u003e] (bus_add_driver+0x16c/0x23c) from [\u003cc01ce54c\u003e] (driver_register+0x78/0x14c)\n[\u003cc01ce54c\u003e] (driver_register+0x78/0x14c) from [\u003cc00086ac\u003e] (do_one_initcall+0xfc/0x164)\n[\u003cc00086ac\u003e] (do_one_initcall+0xfc/0x164) from [\u003cc02e89c8\u003e] (kernel_init+0x120/0x2b8)\n[\u003cc02e89c8\u003e] (kernel_init+0x120/0x2b8) from [\u003cc000e358\u003e] (ret_from_fork+0x14/0x3c)\nCode: e3c3303f e5932004 e2822001 e5832004 (e1903f9f)\n---[ end trace ed9df72941b5bada ]---\n\nSigned-off-by: Rajanikanth H.V \u003crajanikanth.hv@stericsson.com\u003e\nSigned-off-by: Anton Vorontsov \u003canton@enomsg.org\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "f9a8884a35a74f1fb9f12a17f62331bdc6eac2af", "tree": "ede355a00b21014fd4e8ba7b614a3856dfca8abe", "parents": [ "916b6c67cd471fafa3e5e53ce8389c36749ed6f1" ], "author": { "name": "Lee Jones", "email": "lee.jones@linaro.org", "time": "Thu Jan 17 14:21:53 2013 +0000" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Mon Mar 04 06:06:44 2013 +0800" }, "message": "ab8500-chargalg: Only root should have write permission on sysfs file\n\ncommit e3455002d04276c256a531f7175dce0f7d1cb78a upstream.\n\nOnly root should have write permission on sysfs file ab8500_chargalg/chargalg.\n\nSigned-off-by: Lee Jones \u003clee.jones@linaro.org\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "916b6c67cd471fafa3e5e53ce8389c36749ed6f1", "tree": "72cc7d232c2d88d38d5475da41c7ae49826649f7", "parents": [ "a74e9a386f6e775f88061f7958b8b34c6742f926" ], "author": { "name": "Li Zefan", "email": "lizefan@huawei.com", "time": "Thu Jan 24 14:43:28 2013 +0800" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Mon Mar 04 06:06:44 2013 +0800" }, "message": "cgroup: fix exit() vs rmdir() race\n\ncommit 71b5707e119653039e6e95213f00479668c79b75 upstream.\n\nIn cgroup_exit() put_css_set_taskexit() is called without any lock,\nwhich might lead to accessing a freed cgroup:\n\nthread1 thread2\n---------------------------------------------\nexit()\n cgroup_exit()\n put_css_set_taskexit()\n atomic_dec(cgrp-\u003ecount);\n rmdir();\n /* not safe !! */\n check_for_release(cgrp);\n\nrcu_read_lock() can be used to make sure the cgroup is alive.\n\nSigned-off-by: Li Zefan \u003clizefan@huawei.com\u003e\nSigned-off-by: Tejun Heo \u003ctj@kernel.org\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "a74e9a386f6e775f88061f7958b8b34c6742f926", "tree": "a71c10ec1690efe570ec1236198f499faa9c661b", "parents": [ "68412b1718c488e58783d1c576d0aeb34012092d" ], "author": { "name": "Li Zefan", "email": "lizefan@huawei.com", "time": "Fri Jan 25 16:08:01 2013 +0800" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Mon Mar 04 06:06:44 2013 +0800" }, "message": "cpuset: fix cpuset_print_task_mems_allowed() vs rename() race\n\ncommit 63f43f55c9bbc14f76b582644019b8a07dc8219a upstream.\n\nrename() will change dentry-\u003ed_name. The result of this race can\nbe worse than seeing partially rewritten name, but we might access\na stale pointer because rename() will re-allocate memory to hold\na longer name.\n\nIt\u0027s safe in the protection of dentry-\u003ed_lock.\n\nv2: check NULL dentry before acquiring dentry lock.\n\nSigned-off-by: Li Zefan \u003clizefan@huawei.com\u003e\nSigned-off-by: Tejun Heo \u003ctj@kernel.org\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "68412b1718c488e58783d1c576d0aeb34012092d", "tree": "369e927a49f4b7a3e652783d83d8660fc7eca529", "parents": [ "06f924f163e4426ce6a8d4cf61b45f2fc8eaeecc" ], "author": { "name": "Seiji Aguchi", "email": "seiji.aguchi@hds.com", "time": "Fri Jan 11 18:09:41 2013 +0000" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Mon Mar 04 06:06:43 2013 +0800" }, "message": "pstore: Avoid deadlock in panic and emergency-restart path\n\ncommit 9f244e9cfd70c7c0f82d3c92ce772ab2a92d9f64 upstream.\n\n[Issue]\n\nWhen pstore is in panic and emergency-restart paths, it may be blocked\nin those paths because it simply takes spin_lock.\n\nThis is an example scenario which pstore may hang up in a panic path:\n\n - cpuA grabs psinfo-\u003ebuf_lock\n - cpuB panics and calls smp_send_stop\n - smp_send_stop sends IRQ to cpuA\n - after 1 second, cpuB gives up on cpuA and sends an NMI instead\n - cpuA is now in an NMI handler while still holding buf_lock\n - cpuB is deadlocked\n\nThis case may happen if a firmware has a bug and\ncpuA is stuck talking with it more than one second.\n\nAlso, this is a similar scenario in an emergency-restart path:\n\n - cpuA grabs psinfo-\u003ebuf_lock and stucks in a firmware\n - cpuB kicks emergency-restart via either sysrq-b or hangcheck timer.\n And then, cpuB is deadlocked by taking psinfo-\u003ebuf_lock again.\n\n[Solution]\n\nThis patch avoids the deadlocking issues in both panic and emergency_restart\npaths by introducing a function, is_non_blocking_path(), to check if a cpu\ncan be blocked in current path.\n\nWith this patch, pstore is not blocked even if another cpu has\ntaken a spin_lock, in those paths by changing from spin_lock_irqsave\nto spin_trylock_irqsave.\n\nIn addition, according to a comment of emergency_restart() in kernel/sys.c,\nspin_lock shouldn\u0027t be taken in an emergency_restart path to avoid\ndeadlock. This patch fits the comment below.\n\n\u003csnip\u003e\n/**\n * emergency_restart - reboot the system\n *\n * Without shutting down any hardware or taking any locks\n * reboot the system. This is called when we know we are in\n * trouble so this is our best effort to reboot. This is\n * safe to call in interrupt context.\n */\nvoid emergency_restart(void)\n\u003csnip\u003e\n\nSigned-off-by: Seiji Aguchi \u003cseiji.aguchi@hds.com\u003e\nAcked-by: Don Zickus \u003cdzickus@redhat.com\u003e\nSigned-off-by: Tony Luck \u003ctony.luck@intel.com\u003e\nCc: CAI Qian \u003ccaiqian@redhat.com\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "06f924f163e4426ce6a8d4cf61b45f2fc8eaeecc", "tree": "029fe0d34de98d68a64740439c72ec64dfecf29d", "parents": [ "57ef0d83d393b0f1f378a6b18a7394c62caadafa" ], "author": { "name": "Felix Fietkau", "email": "nbd@openwrt.org", "time": "Sun Jan 20 21:55:20 2013 +0100" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Mon Mar 04 06:06:43 2013 +0800" }, "message": "ath9k_hw: fix calibration issues on chainmask that don\u0027t include chain 0\n\ncommit 4a8f199508d79ff8a7d1e22f47b912baaf225336 upstream.\n\nSigned-off-by: Felix Fietkau \u003cnbd@openwrt.org\u003e\nSigned-off-by: John W. Linville \u003clinville@tuxdriver.com\u003e\nSigned-off-by: CAI Qian \u003ccaiqian@redhat.com\u003e\nReviewed-by: John W. Linville \u003clinville@tuxdriver.com\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "57ef0d83d393b0f1f378a6b18a7394c62caadafa", "tree": "ff6a2a11496d63cad0d9a0a5a2f9ead1e894c1fb", "parents": [ "146207bbadeb4578334d6e26b9b690df8aeb1a3d" ], "author": { "name": "Helge Deller", "email": "deller@gmx.de", "time": "Mon Feb 04 19:39:52 2013 +0000" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Mon Mar 04 06:06:43 2013 +0800" }, "message": "unbreak automounter support on 64-bit kernel with 32-bit userspace (v2)\n\ncommit 4f4ffc3a5398ef9bdbb32db04756d7d34e356fcf upstream.\n\nautomount-support is broken on the parisc architecture, because the existing\n#if list does not include a check for defined(__hppa__). The HPPA (parisc)\narchitecture is similiar to other 64bit Linux targets where we have to define\nautofs_wqt_t (which is passed back and forth to user space) as int type which\nhas a size of 32bit across 32 and 64bit kernels.\n\nDuring the discussion on the mailing list, H. Peter Anvin suggested to invert\nthe #if list since only specific platforms (specifically those who do not have\na 32bit userspace, like IA64 and Alpha) should have autofs_wqt_t as unsigned\nlong type.\n\nThis suggestion is probably the best way to go, since Arm64 (and maybe others?)\nseems to have a non-working automounter. So in the long run even for other new\nupcoming architectures this inverted check seem to be the best solution, since\nit will not require them to change this #if again (unless they are 64bit only).\n\nSigned-off-by: Helge Deller \u003cdeller@gmx.de\u003e\nAcked-by: H. Peter Anvin \u003chpa@zytor.com\u003e\nAcked-by: Ian Kent \u003craven@themaw.net\u003e\nAcked-by: Catalin Marinas \u003ccatalin.marinas@arm.com\u003e\nCC: James Bottomley \u003cJames.Bottomley@HansenPartnership.com\u003e\nCC: Rolf Eike Beer \u003ceike-kernel@sf-tec.de\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "146207bbadeb4578334d6e26b9b690df8aeb1a3d", "tree": "dbf8d2cbe783956cdd0310e28f6187f2e0e39186", "parents": [ "94dcb26bbbed1851e0a7fb16165207c2c61e545f" ], "author": { "name": "Miklos Szeredi", "email": "mszeredi@suse.cz", "time": "Mon Feb 04 15:57:42 2013 +0100" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Mon Mar 04 06:06:43 2013 +0800" }, "message": "fuse: don\u0027t WARN when nlink is zero\n\ncommit dfca7cebc2679f3d129f8e680a8f199a7ad16e38 upstream.\n\ndrop_nlink() warns if nlink is already zero. This is triggerable by a buggy\nuserspace filesystem. The cure, I think, is worse than the disease so disable\nthe warning.\n\nReported-by: Tero Roponen \u003ctero.roponen@gmail.com\u003e\nSigned-off-by: Miklos Szeredi \u003cmszeredi@suse.cz\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "94dcb26bbbed1851e0a7fb16165207c2c61e545f", "tree": "3bbf5cc7eb75e9cdb8f3c5763546767f5a4a9d28", "parents": [ "7e5e167c5c1b44f408fa8f8a8f062f234cd0f0d6" ], "author": { "name": "Michael S. Tsirkin", "email": "mst@redhat.com", "time": "Mon Nov 26 05:57:27 2012 +0000" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Mon Mar 04 06:06:43 2013 +0800" }, "message": "vhost: fix length for cross region descriptor\n\ncommit bd97120fc3d1a11f3124c7c9ba1d91f51829eb85 upstream.\n\nIf a single descriptor crosses a region, the\nsecond chunk length should be decremented\nby size translated so far, instead it includes\nthe full descriptor length.\n\nSigned-off-by: Michael S. Tsirkin \u003cmst@redhat.com\u003e\nAcked-by: Jason Wang \u003cjasowang@redhat.com\u003e\nSigned-off-by: David S. Miller \u003cdavem@davemloft.net\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "7e5e167c5c1b44f408fa8f8a8f062f234cd0f0d6", "tree": "4d07cc6f35b269d6ce80e678db56ba36dcb8e57f", "parents": [ "5623a7cc4e3f0f461586b10b78967bb5f53fa096" ], "author": { "name": "J. Bruce Fields", "email": "bfields@redhat.com", "time": "Sun Feb 10 11:33:48 2013 -0500" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Mon Mar 04 06:06:43 2013 +0800" }, "message": "svcrpc: make svc_age_temp_xprts enqueue under sv_lock\n\ncommit e75bafbff2270993926abcc31358361db74a9bc2 upstream.\n\nsvc_age_temp_xprts expires xprts in a two-step process: first it takes\nthe sv_lock and moves the xprts to expire off their server-wide list\n(sv_tempsocks or sv_permsocks) to a local list. Then it drops the\nsv_lock and enqueues and puts each one.\n\nI see no reason for this: svc_xprt_enqueue() will take sp_lock, but the\nsv_lock and sp_lock are not otherwise nested anywhere (and documentation\nat the top of this file claims it\u0027s correct to nest these with sp_lock\ninside.)\n\nTested-by: Jason Tibbitts \u003ctibbs@math.uh.edu\u003e\nTested-by: Paweł Sikora \u003cpawel.sikora@agmk.net\u003e\nSigned-off-by: J. Bruce Fields \u003cbfields@redhat.com\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "5623a7cc4e3f0f461586b10b78967bb5f53fa096", "tree": "31c046702f80af64ae7f5a5086337be12eeb492d", "parents": [ "4234fb29a8c0a5c5eaee6de38fe3cba674daecd0" ], "author": { "name": "majianpeng", "email": "majianpeng@gmail.com", "time": "Tue Jan 29 13:16:06 2013 +0800" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Mon Mar 04 06:06:42 2013 +0800" }, "message": "nfsd: Fix memleak\n\ncommit 2d32b29a1c2830f7c42caa8258c714acd983961f upstream.\n\nWhen free nfs-client, it must free the -\u003ecl_stateids.\n\nSigned-off-by: Jianpeng Ma \u003cmajianpeng@gmail.com\u003e\nSigned-off-by: J. Bruce Fields \u003cbfields@redhat.com\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "4234fb29a8c0a5c5eaee6de38fe3cba674daecd0", "tree": "1b18b671e4835dc38520726bedbb142bad6cfc86", "parents": [ "19c9740ba7362357bde91267a0aa5109a809cd3e" ], "author": { "name": "Lukas Czerner", "email": "lczerner@redhat.com", "time": "Fri Feb 22 15:27:52 2013 -0500" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Mon Mar 04 06:06:42 2013 +0800" }, "message": "ext4: fix free clusters calculation in bigalloc filesystem\n\ncommit 304e220f0879198b1f5309ad6f0be862b4009491 upstream.\n\next4_has_free_clusters() should tell us whether there is enough free\nclusters to allocate, however number of free clusters in the file system\nis converted to blocks using EXT4_C2B() which is not only wrong use of\nthe macro (we should have used EXT4_NUM_B2C) but it\u0027s also completely\nwrong concept since everything else is in cluster units.\n\nMoreover when calculating number of root clusters we should be using\nmacro EXT4_NUM_B2C() instead of EXT4_B2C() otherwise the result might be\noff by one. However r_blocks_count should always be a multiple of the\ncluster ratio so doing a plain bit shift should be enough here. We\navoid using EXT4_B2C() because it\u0027s confusing.\n\nAs a result of the first problem number of free clusters is much bigger\nthan it should have been and ext4_has_free_clusters() would return 1 even\nif there is really not enough free clusters available.\n\nFix this by removing the EXT4_C2B() conversion of free clusters and\nusing bit shift when calculating number of root clusters. This bug\naffects number of xfstests tests covering file system ENOSPC situation\nhandling. With this patch most of the ENOSPC problems with bigalloc file\nsystem disappear, especially the errors caused by delayed allocation not\nhaving enough space when the actual allocation is finally requested.\n\nSigned-off-by: Lukas Czerner \u003clczerner@redhat.com\u003e\nSigned-off-by: \"Theodore Ts\u0027o\" \u003ctytso@mit.edu\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "19c9740ba7362357bde91267a0aa5109a809cd3e", "tree": "3c1b86dff72d5b9f73584a42f70b6183c6a3ad36", "parents": [ "51e26006d1c9d5a2609d1bb6b7899cd86f92eed9" ], "author": { "name": "Lukas Czerner", "email": "lczerner@redhat.com", "time": "Mon Feb 18 12:12:07 2013 -0500" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Mon Mar 04 06:06:42 2013 +0800" }, "message": "ext4: fix xattr block allocation/release with bigalloc\n\ncommit 1231b3a1eb5740192aeebf5344dd6d6da000febf upstream.\n\nCurrently when new xattr block is created or released we we would call\ndquot_free_block() or dquot_alloc_block() respectively, among the else\ndecrementing or incrementing the number of blocks assigned to the\ninode by one block.\n\nThis however does not work for bigalloc file system because we always\nallocate/free the whole cluster so we have to count with that in\ndquot_free_block() and dquot_alloc_block() as well.\n\nUse the clusters-to-blocks conversion EXT4_C2B() when passing number of\nblocks to the dquot_alloc/free functions to fix the problem.\n\nThe problem has been revealed by xfstests #117 (and possibly others).\n\nSigned-off-by: Lukas Czerner \u003clczerner@redhat.com\u003e\nSigned-off-by: \"Theodore Ts\u0027o\" \u003ctytso@mit.edu\u003e\nReviewed-by: Eric Sandeen \u003csandeen@redhat.com\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" } ], "next": "51e26006d1c9d5a2609d1bb6b7899cd86f92eed9" }