GitHub PushEvent at 2014-02-10 04:43:33
Repository: linux
Actor: gregkh
Payload: {"shas":[["1b8c5f8b4b57c574f6cf2047e80e1565b2a07f09","0c71a8c45d1c28c49aceef3749b4faa9d3c35c54@redhat.com","GFS2: Increase i_writecount during gfs2_setattr_chown\n\ncommit 62e96cf81988101fe9e086b2877307b6adda5197 upstream.\n\nThis patch calls get_write_access in function gfs2_setattr_chown,\nwhich merely increases inode->i_writecount for the duration of the\nfunction. That will ensure that any file closes won't delete the\ninode's multi-block reservation while the function is running.\nIt also ensures that a multi-block reservation exists when needed\nfor quota change operations during the chown.\n\nSigned-off-by: Bob Peterson <rpeterso@redhat.com>\nSigned-off-by: Steven Whitehouse <swhiteho@redhat.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","Bob Peterson",false],["af7b2d49ef7b4171ef416b7ca2810834993afbca","1d6e1cf70ec6f9ab28d3ea4b27a49a77654d370e@berndporr.me.uk","staging: comedi: fix result of memdup_user for user chanlist\n\ncommit e56b1401056288a725d50942ef300dcbed5e519a upstream.\n\nIf the channel list is not set in userspace we get an error at\nPTR_ERR(async->cmd.chanlist). However, do_become_nonbusy(dev, s) cleans\nup this pointer which causes a kernel ooops. Setting the channel list in\nasync to NULL and checking this in do_become_nonbusy prevents the oops.\n\n[Ian Abbott] Also do the same for the chanlist allocated in\ndo_cmdtest_ioctl().\n\nSigned-off-by: Bernd Porr <mail@berndporr.me.uk>\nSigned-off-by: Ian Abbott <abbotti@mev.co.uk>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","Bernd Porr",false],["323a088a4d9905415825e451372ad7b71fe256fc","382ff55d8e07d1082d179e669636cd1552da4f36@visionengravers.com","staging: comedi: addi_apci_1032: fix subdevice type/flags bug\n\ncommit 90daf69a7a3f1d1a41018c799968a0bb896d65e0 upstream.\n\nThe SDF_CMD_READ should be one of the s->subdev_flags not part of\nthe s->type.\n\nSigned-off-by: H Hartley Sweeten <hsweeten@visionengravers.com>\nReviewed-by: Ian Abbott <abbotti@mev.co.uk>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","H Hartley Sweeten",false],["924678c5d32e2259e6b261bcd45007bae9349ad4","382ff55d8e07d1082d179e669636cd1552da4f36@visionengravers.com","staging: comedi: adl_pci9111: fix incorrect irq passed to request_irq()\n\ncommit 48108fe3daa0d142f9b97178fdb23704ea3a407b upstream.\n\nThe dev->irq passed to request_irq() will always be 0 when the auto_attach\nfunction is called. The pcidev->irq should be used instead to get the correct\nirq number.\n\nSigned-off-by: H Hartley Sweeten <hsweeten@visionengravers.com>\nReviewed-by: Ian Abbott <abbotti@mev.co.uk>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","H Hartley Sweeten",false],["c6e23916a2d35a4236b43d9ac6c19c0359148b11","0da414d9d963da4039c2a0525b1844228075aa58@linux-m68k.org","mm: Make {,set}page_address() static inline if WANT_PAGE_VIRTUAL\n\ncommit f92f455f67fef27929e6043499414605b0c94872 upstream.\n\n{,set}page_address() are macros if WANT_PAGE_VIRTUAL.  If\n!WANT_PAGE_VIRTUAL, they're plain C functions.\n\nIf someone calls them with a void *, this pointer is auto-converted to\nstruct page * if !WANT_PAGE_VIRTUAL, but causes a build failure on\narchitectures using WANT_PAGE_VIRTUAL (arc, m68k and sparc64):\n\n  drivers/md/bcache/bset.c: In function `__btree_sort':\n  drivers/md/bcache/bset.c:1190: warning: dereferencing `void *' pointer\n  drivers/md/bcache/bset.c:1190: error: request for member `virtual' in something not a structure or union\n\nConvert them to static inline functions to fix this.  There are already\nplenty of users of struct page members inside <linux/mm.h>, so there's\nno reason to keep them as macros.\n\nSigned-off-by: Geert Uytterhoeven <geert@linux-m68k.org>\nAcked-by: Michael S. Tsirkin <mst@redhat.com>\nTested-by: Guenter Roeck <linux@roeck-us.net>\nTested-by: David Rientjes <rientjes@google.com>\nSigned-off-by: Andrew Morton <akpm@linux-foundation.org>\nSigned-off-by: Linus Torvalds <torvalds@linux-foundation.org>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","Geert Uytterhoeven",false],["bfb158e133d338823eec0c55dbe2be9f685f9739","90cd1a2bf502062a09a1a38db4b5d470886df04b@linaro.org","serial: amba-pl011: use port lock to guard control register access\n\ncommit fe43390702a1b5741fdf217063b05c7612b38303 upstream.\n\nWhen the pl011 is being used for a console, pl011_console_write forces\nthe control register (CR) to enable the UART for transmission and then\nrestores this to the original value afterwards. It does this while\nholding the port lock.\n\nUnfortunately, when the uart is started or shutdown - say in response to\nuserland using the serial device for a terminal - then this updates the\ncontrol register without any locking.\n\nThis means we can have\n\n  pl011_console_write   Save CR\n  pl011_startup         Initialise CR, e.g. enable receive\n  pl011_console_write   Restore old CR with receive not enabled\n\nthis result is a serial port which doesn't respond to any input.\n\nA similar race in reverse could happen when the device is shutdown.\n\nWe can fix these problems by taking the port lock when updating CR.\n\nSigned-off-by: Jon Medhurst <tixy@linaro.org>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","Jon Medhurst",false],["f4d566d8de432c1bf94f8f26dd99871601775203","ba324ca7b1c77fc20bb970d5aff6eea9377918a5@roeck-us.net","extcon: gpio: Request gpio pin before modifying its state\n\ncommit 4288d9b8edcec7289e00eecdad44f14c9ea1ba0e upstream.\n\nCommit 338de0ca (extcon: gpio: Use gpio driver/chip debounce if supported)\nintroduced a call to gpio_set_debounce() before actually requesting the\nrespective gpio pin from the gpio subsystem.\n\nThe gpio subsystem expects that a gpio pin was requested before modifying its\nstate. Not doing so results in a warning from gpiolib, and the gpio pin is\nauto-requested. This in turn causes the subsequent devm_gpio_request_one()\nto fail. So devm_gpio_request_one() must be called prior to calling\ngpio_set_debounce().\n\nSigned-off-by: Guenter Roeck <linux@roeck-us.net>\nAcked-by: MyungJoo Ham <myungjoo.ham@samsung.com>\nSigned-off-by: Chanwoo Choi <cw00.choi@samsung.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","Guenter Roeck",false],["d112bace4521ff50b40b68bf1375fb5e8feed217","9fb354e0a5603a0331399c18f4aa5aab2f9d9c5b@canonical.com","ALSA: hda - Explicitly keep codec powered up in hdmi_present_sense\n\ncommit da4a7a3926d09c13ae052ede67feb7285e01e3f5 upstream.\n\nThis should help us avoid the following mutex deadlock:\n\n[] mutex_lock+0x2a/0x50\n[] hdmi_present_sense+0x53/0x3a0 [snd_hda_codec_hdmi]\n[] generic_hdmi_resume+0x5a/0x70 [snd_hda_codec_hdmi]\n[] hda_call_codec_resume+0xec/0x1d0 [snd_hda_codec]\n[] snd_hda_power_save+0x1e4/0x280 [snd_hda_codec]\n[] codec_exec_verb+0x5f/0x290 [snd_hda_codec]\n[] snd_hda_codec_read+0x5b/0x90 [snd_hda_codec]\n[] snd_hdmi_get_eld_size+0x1e/0x20 [snd_hda_codec_hdmi]\n[] snd_hdmi_get_eld+0x2c/0xd0 [snd_hda_codec_hdmi]\n[] hdmi_present_sense+0x9a/0x3a0 [snd_hda_codec_hdmi]\n[] hdmi_repoll_eld+0x34/0x50 [snd_hda_codec_hdmi]\n\nSigned-off-by: David Henningsson <david.henningsson@canonical.com>\nFixes: cbbaa603a03c ('ALSA: hda - Fix possible races in HDMI driver')\nSigned-off-by: Takashi Iwai <tiwai@suse.de>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","David Henningsson",false],["34fa7e82ec661cf54f21b1677d2e05173e5a812c","1c00aa603bb92d594c03cff60ecf8e63b2a5bcb1@suse.de","md/raid5: fix long-standing problem with bitmap handling on write failure.\n\ncommit 9f97e4b128d2ea90a5f5063ea0ee3b0911f4c669 upstream.\n\nBefore a write starts we set a bit in the write-intent bitmap.\nWhen the write completes we clear that bit if the write was successful\nto all devices.  However if the write wasn't fully successful we\nshould not clear the bit.  If the faulty drive is subsequently\nre-added, the fact that the bit is still set ensure that we will\nre-write the data that is missing.\n\nThis logic is mediated by the STRIPE_DEGRADED flag - we only clear the\nbitmap bit when this flag is not set.\nCurrently we correctly set the flag if a write starts when some\ndevices are failed or missing.  But we do *not* set the flag if some\ndevice failed during the write attempt.\nThis is wrong and can result in clearing the bit inappropriately.\n\nSo: set the flag when a write fails.\n\nThis bug has been present since bitmaps were introduces, so the fix is\nsuitable for any -stable kernel.\n\nReported-by: Ethan Wilson <ethan.wilson@shiftmail.org>\nSigned-off-by: NeilBrown <neilb@suse.de>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","NeilBrown",false],["e4e80e0bec9e03b6e323857e9bb2820f5bbe6287","1c00aa603bb92d594c03cff60ecf8e63b2a5bcb1@suse.de","md/raid5: close recently introduced race in stripe_head management.\n\ncommit 7da9d450ab2843bf1db378c156acc6304dbc1c2b upstream.\n\nAs release_stripe and __release_stripe decrement ->count and then\nmanipulate ->lru both under ->device_lock, it is important that\nget_active_stripe() increments ->count and clears ->lru also under\n->device_lock.\n\nHowever we currently list_del_init ->lru under the lock, but increment\nthe ->count outside the lock.  This can lead to races and list\ncorruption.\n\nSo move the atomic_inc(&sh->count) up inside the ->device_lock\nprotected region.\n\nNote that we still increment ->count without device lock in the case\nwhere get_free_stripe() was called, and in fact don't take\n->device_lock at all in that path.\nThis is safe because if the stripe_head can be found by\nget_free_stripe, then the hash lock assures us the no-one else could\npossibly be calling release_stripe() at the same time.\n\nFixes: 566c09c53455d7c4f1130928ef8071da1a24ea65\nReported-and-tested-by: Ian Kumlien <ian.kumlien@gmail.com>\nSigned-off-by: NeilBrown <neilb@suse.de>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","NeilBrown",false],["07ecf16297bbec8d94012f2dd9d615f98093fbbe","4645f7897fd33786a2ee1264d590b3c400559d85@linuxfoundation.org","Linux 3.13.1","Greg Kroah-Hartman",false],["4a466742d28b10d696e79b1c77996e2f72536ba7","78e305742ac743ecf22d8139502576ac8709e0ad@redhat.com","e752x_edac: Fix pci_dev usage count\n\ncommit 90ed4988b8c030d65b41b7d13140e9376dc6ec5a upstream.\n\nIn case the device 0, function 1 is not found using pci_get_device(),\npci_scan_single_device() will be used but, differently than\npci_get_device(), it allocates a pci_dev but doesn't does bump the usage\ncount on the pci_dev and after few module removals and loads the pci_dev\nwill be freed.\n\nSigned-off-by: Aristeu Rozanski <aris@redhat.com>\nReviewed-by: mark gross <mark.gross@intel.com>\nLink: http://lkml.kernel.org/r/20131205153755.GL4545@redhat.com\nSigned-off-by: Borislav Petkov <bp@suse.de>\nCc: Jean Delvare <jdelvare@suse.de>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","Aristeu Rozanski",false],["41d3f491c9cf265f757bcbab663ec34ff84748fa","d8cd2994e15bc61ddb2b113030bda55eebc3a0fe@google.com","mm/mempolicy.c: fix mempolicy printing in numa_maps\n\ncommit 8790c71a18e5d2d93532ae250bcf5eddbba729cd upstream.\n\nAs a result of commit 5606e3877ad8 (\"mm: numa: Migrate on reference\npolicy\"), /proc/<pid>/numa_maps prints the mempolicy for any <pid> as\n\"prefer:N\" for the local node, N, of the process reading the file.\n\nThis should only be printed when the mempolicy of <pid> is\nMPOL_PREFERRED for node N.\n\nIf the process is actually only using the default mempolicy for local\nnode allocation, make sure \"default\" is printed as expected.\n\nSigned-off-by: David Rientjes <rientjes@google.com>\nReported-by: Robert Lippert <rlippert@google.com>\nCc: Peter Zijlstra <peterz@infradead.org>\nAcked-by: Mel Gorman <mgorman@suse.de>\nCc: Ingo Molnar <mingo@kernel.org>\nSigned-off-by: Andrew Morton <akpm@linux-foundation.org>\nSigned-off-by: Linus Torvalds <torvalds@linux-foundation.org>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","David Rientjes",false],["921ce180818a8a3b52fbe02e747695d51a46f5e1","79082de0c93349f717971d409a005388d1854a7c@freemail.hu","x86, x32: Correct invalid use of user timespec in the kernel\n\ncommit 2def2ef2ae5f3990aabdbe8a755911902707d268 upstream.\n\nThe x32 case for the recvmsg() timout handling is broken:\n\n  asmlinkage long compat_sys_recvmmsg(int fd, struct compat_mmsghdr __user *mmsg,\n                                      unsigned int vlen, unsigned int flags,\n                                      struct compat_timespec __user *timeout)\n  {\n          int datagrams;\n          struct timespec ktspec;\n\n          if (flags & MSG_CMSG_COMPAT)\n                  return -EINVAL;\n\n          if (COMPAT_USE_64BIT_TIME)\n                  return __sys_recvmmsg(fd, (struct mmsghdr __user *)mmsg, vlen,\n                                        flags | MSG_CMSG_COMPAT,\n                                        (struct timespec *) timeout);\n          ...\n\nThe timeout pointer parameter is provided by userland (hence the __user\nannotation) but for x32 syscalls it's simply cast to a kernel pointer\nand is passed to __sys_recvmmsg which will eventually directly\ndereference it for both reading and writing.  Other callers to\n__sys_recvmmsg properly copy from userland to the kernel first.\n\nThe bug was introduced by commit ee4fa23c4bfc (\"compat: Use\nCOMPAT_USE_64BIT_TIME in net/compat.c\") and should affect all kernels\nsince 3.4 (and perhaps vendor kernels if they backported x32 support\nalong with this code).\n\nNote that CONFIG_X86_X32_ABI gets enabled at build time and only if\nCONFIG_X86_X32 is enabled and ld can build x32 executables.\n\nOther uses of COMPAT_USE_64BIT_TIME seem fine.\n\nThis addresses CVE-2014-0038.\n\nSigned-off-by: PaX Team <pageexec@freemail.hu>\nSigned-off-by: H. Peter Anvin <hpa@linux.intel.com>\nSigned-off-by: Linus Torvalds <torvalds@linux-foundation.org>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","PaX Team",false],["0c51097273237d079ef67aa819e904e484e382ca","73675debcd8a436be48ec22211dcf44fe0df0a64@decadent.org.uk","xen/pci: Fix build on non-x86\n\ncommit b7ef4a6dd35d1b47db72fbd1a31c8fd0da7a74f3 upstream.\n\nWe can't include <asm/pci_x86.h> if this isn't x86, and we only need\nit if CONFIG_PCI_MMCONFIG is enabled.\n\nFixes: 8deb3eb1461e ('xen/mcfg: Call PHYSDEVOP_pci_mmcfg_reserved for MCFG areas.')\nSigned-off-by: Ben Hutchings <ben@decadent.org.uk>\nSigned-off-by: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>\nReviewed-by: David Vrabel <david.vrabel@citrix.com>\nAcked-by: Ian Campbell <ian.campbell@citrix.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","Ben Hutchings",false],["965918eb863be707d548683b5165cfb30deb8d1c","5716cc40769303914dac486db0fc6ac4cba9419e@redhat.com","x86/efi: Fix off-by-one bug in EFI Boot Services reservation\n\ncommit a7f84f03f660d93574ac88835d056c0d6468aebe upstream.\n\nCurrent code check boot service region with kernel text region by:\nstart+size >= __pa_symbol(_text)\nThe end of the above region should be start + size - 1 instead.\n\nI see this problem in ovmf + Fedora 19 grub boot:\ntext start: 1000000 md start: 800000 md size: 800000\n\nSigned-off-by: Dave Young <dyoung@redhat.com>\nAcked-by: Borislav Petkov <bp@suse.de>\nAcked-by: Toshi Kani <toshi.kani@hp.com>\nTested-by: Toshi Kani <toshi.kani@hp.com>\nSigned-off-by: Matt Fleming <matt.fleming@intel.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","Dave Young",false],["7581173b4e52437936ed39d20b48418b1cdecd31","958bcd1f4a7a8c36dca09fe3fa9cb5f1483adf51@redhat.com","KVM: x86: limit PIT timer frequency\n\ncommit 9ed96e87c5748de4c2807ef17e81287c7304186c upstream.\n\nLimit PIT timer frequency similarly to the limit applied by\nLAPIC timer.\n\nReviewed-by: Jan Kiszka <jan.kiszka@siemens.com>\nSigned-off-by: Marcelo Tosatti <mtosatti@redhat.com>\nSigned-off-by: Paolo Bonzini <pbonzini@redhat.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","Marcelo Tosatti",false],["b94c2ba692234e31150b025ad270e8220d4b03a4","69d3ebcf5ee4e7f05a50dc23cd96655b730804b4@redhat.com","x86, kvm: cache the base of the KVM cpuid leaves\n\ncommit 1c300a40772dae829b91dad634999a6a522c0829 upstream.\n\nIt is unnecessary to go through hypervisor_cpuid_base every time\na leaf is found (which will be every time a feature is requested\nafter the next patch).\n\nFixes: 1085ba7f552d84aa8ac0ae903fa8d0cc2ff9f79d\nCc: mtosatti@redhat.com\nSigned-off-by: Paolo Bonzini <pbonzini@redhat.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","Paolo Bonzini",false],["4ba10fc2d81a087e69fb782e4c8a0fc54f5084df","69d3ebcf5ee4e7f05a50dc23cd96655b730804b4@redhat.com","x86, kvm: correctly access the KVM_CPUID_FEATURES leaf at 0x40000101\n\ncommit 77f01bdfa5e55dc19d3eb747181d2730a9bb3ca8 upstream.\n\nWhen Hyper-V hypervisor leaves are present, KVM must relocate\nits own leaves at 0x40000100, because Windows does not look for\nHyper-V leaves at indices other than 0x40000000.  In this case,\nthe KVM features are at 0x40000101, but the old code would always\nlook at 0x40000001.\n\nFix by using kvm_cpuid_base().  This also requires making the\nfunction non-inline, since kvm_cpuid_base() is static.\n\nFixes: 1085ba7f552d84aa8ac0ae903fa8d0cc2ff9f79d\nCc: mtosatti@redhat.com\nSigned-off-by: Paolo Bonzini <pbonzini@redhat.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","Paolo Bonzini",false],["1d503f1a90538a068b0efd62757af9c11e119b36","c01a8c815a4ad165fff2d1c0d35ddf5b16bd3d7b@freescale.com","usb: chipidea: add freescale imx28 special write register method\n\ncommit ed8f8318d2ef3e5f9e4ddf79349508c116b68d7f upstream.\n\nAccording to Freescale imx28 Errata, \"ENGR119653 USB: ARM to USB\nregister error issue\", All USB register write operations must\nuse the ARM SWP instruction. So, we implement special hw_write\nand hw_test_and_clear for imx28.\n\nDiscussion for it at below:\nhttp://marc.info/?l=linux-usb&m=137996395529294&w=2\n\nThis patch is needed for stable tree 3.11+.\n\nCc: robert.hodaszi@digi.com\nSigned-off-by: Peter Chen <peter.chen@freescale.com>\nSigned-off-by: Marc Kleine-Budde <mkl@pengutronix.de>\nTested-by: Marc Kleine-Budde <mkl@pengutronix.de>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","Peter Chen",false]],"size":152,"ref":"refs/heads/coreos/master","head":"8f7338b0cf7426b5f76743e2e7aaa667b0255e21"}