GitHub PushEvent at 2014-02-24 21:06:50
Repository: linux-next
Actor: ddstreet
Payload: {"shas":[["88b5bdfda886e9774b03f02ffe4295be124124f6","b8f9cab8be13de37b9588aedad10a20fc3a68783@trendmicro.com.cn","ASoC: wm8993: drop regulator_bulk_free of devm_ allocated data\n\nIt's not necessary to free regulator consumers allocated with\ndevm_regulator_bulk_get.\n\nSigned-off-by: Wei Yongjun <yongjun_wei@trendmicro.com.cn>\nSigned-off-by: Mark Brown <broonie@linaro.org>","Wei Yongjun",false],["b80d5ccca3a012e91ca64a2a0b13049163a6a698","4120c558c4571c57657705e7ff90b3a92d2e70b1@huawei.com","NVMe: Avoid shift operation when writing cq head doorbell\n\nChanges the type of dev->db_stride to unsigned and changes the value\nstored there to be 1 << the current value. Then there is less\ncalculation to be done at completion time.\n\nSigned-off-by: Haiyan Hu <huhaiyan@huawei.com>\nSigned-off-by: Matthew Wilcox <matthew.r.wilcox@intel.com>","Haiyan Hu",false],["481e5bad84239b01415b888df2040c1860ae3cfd","7a431b534449ead06bb4128c8239bba232a2bf74@free-electrons.com","NVMe: remove deprecated IRQF_DISABLED\n\nThis patch proposes to remove the use of the IRQF_DISABLED flag\n\nIt's a NOOP since 2.6.35 and it will be removed one day.\n\nSigned-off-by: Michael Opdenacker <michael.opdenacker@free-electrons.com>\nSigned-off-by: Matthew Wilcox <matthew.r.wilcox@intel.com>","Michael Opdenacker",false],["1037d567fdfc7ab9d3e2328e27bdc1300d3fdb1e","679188261afeb60eb822cd934fd7b46a48ddd743@freescale.com","ASoC: wm8737: Use IS_ENABLED() macro\n\nUsing the IS_ENABLED() macro can make the code shorter and simpler.\n\nSigned-off-by: Fabio Estevam <fabio.estevam@freescale.com>\nSigned-off-by: Mark Brown <broonie@linaro.org>","Fabio Estevam",false],["060ec80a27bf7a00bafb0c7495bbeec92e7903d3","679188261afeb60eb822cd934fd7b46a48ddd743@freescale.com","ASoC: wm8983: Use IS_ENABLED() macro\n\nUsing the IS_ENABLED() macro can make the code shorter and simpler.\n\nSigned-off-by: Fabio Estevam <fabio.estevam@freescale.com>\nSigned-off-by: Mark Brown <broonie@linaro.org>","Fabio Estevam",false],["a6f089e95b1e08cdea9633d50ad20aa5d44ba64d","30ea2d6de7db423b663e964abd9bbdb7979e47a5@marvell.com","irqchip: armada-370-xp: fix IPI race condition\n\nIn the Armada 370/XP driver, when we receive an IRQ 0, we read the\nlist of doorbells that caused the interrupt from register\nARMADA_370_XP_IN_DRBEL_CAUSE_OFFS. This gives the list of IPIs that\nwere generated. However, instead of acknowledging only the IPIs that\nwere generated, we acknowledge *all* the IPIs, by writing\n~IPI_DOORBELL_MASK in the ARMADA_370_XP_IN_DRBEL_CAUSE_OFFS register.\n\nThis creates a race condition: if a new IPI that isn't part of the\nones read into the temporary \"ipimask\" variable is fired before we\nacknowledge all IPIs, then we will simply loose it. This is causing\nscheduling hangs on SMP intensive workloads.\n\nIt is important to mention that this ARMADA_370_XP_IN_DRBEL_CAUSE_OFFS\nregister has the following behavior: \"A CPU write of 0 clears the bits\nin this field. A CPU write of 1 has no effect\". This is what allows us\nto simply write ~ipimask to acknoledge the handled IPIs.\n\nNotice that the same problem is present in the MSI implementation, but\nit will be fixed as a separate patch, so that this IPI fix can be\npushed to older stable versions as appropriate (all the way to 3.8),\nwhile the MSI code only appeared in 3.13.\n\nSigned-off-by: Lior Amsalem <alior@marvell.com>\nSigned-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>\nCc: stable@vger.kernel.org # v3.8+\nFixes: 344e873e5657e8dc0 'arm: mvebu: Add IPI support via doorbells'\nCc: Thomas Gleixner <tglx@linutronix.de>\nSigned-off-by: Jason Cooper <jason@lakedaemon.net>","Lior Amsalem",false],["c7f7bd4a136e4b02dd2a66bf95aec545bd93e8db","30ea2d6de7db423b663e964abd9bbdb7979e47a5@marvell.com","irqchip: armada-370-xp: fix MSI race condition\n\nIn the Armada 370/XP driver, when we receive an IRQ 1, we read the\nlist of doorbells that caused the interrupt from register\nARMADA_370_XP_IN_DRBEL_CAUSE_OFFS. This gives the list of MSIs that\nwere generated. However, instead of acknowledging only the MSIs that\nwere generated, we acknowledge *all* the MSIs, by writing\n~MSI_DOORBELL_MASK in the ARMADA_370_XP_IN_DRBEL_CAUSE_OFFS register.\n\nThis creates a race condition: if a new MSI that isn't part of the\nones read into the temporary \"msimask\" variable is fired before we\nacknowledge all MSIs, then we will simply loose it.\n\nIt is important to mention that this ARMADA_370_XP_IN_DRBEL_CAUSE_OFFS\nregister has the following behavior: \"A CPU write of 0 clears the bits\nin this field. A CPU write of 1 has no effect\". This is what allows us\nto simply write ~msimask to acknoledge the handled MSIs.\n\nNotice that the same problem is present in the IPI implementation, but\nit is fixed as a separate patch, so that this IPI fix can be pushed to\nolder stable versions as appropriate (all the way to 3.8), while the\nMSI code only appeared in 3.13.\n\nSigned-off-by: Lior Amsalem <alior@marvell.com>\nSigned-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>\nCc: Thomas Gleixner <tglx@linutronix.de>\nSigned-off-by: Jason Cooper <jason@lakedaemon.net>","Lior Amsalem",false],["f36132a75aafd0086aeb0eacf348654138d56b49","65b3ccf850ea721688fb240d52a95019d85394b7@ubuntukylin.com","ceph: Clean up if error occurred in finish_read()\n\nClean up if error occurred rather than going through normal process\n\nSigned-off-by: Li Wang <liwang@ubuntukylin.com>\nSigned-off-by: Yunchuan Wen <yunchuanwen@ubuntukylin.com>\nSigned-off-by: Sage Weil <sage@inktank.com>","Li Wang",false],["37c89bde5d402c25211a9e31e3166067f85aa31b","65b3ccf850ea721688fb240d52a95019d85394b7@ubuntukylin.com","ceph: Add necessary clean up if invalid reply received in handle_reply()\n\nWake up possible waiters, invoke the call back if any, unregister the request\n\nSigned-off-by: Li Wang <liwang@ubuntukylin.com>\nSigned-off-by: Yunchuan Wen <yunchuanwen@ubuntukylin.com>\nSigned-off-by: Sage Weil <sage@inktank.com>","Li Wang",false],["aa8b60e077fa2a4383e79b092b65cd5455ea5ab2","3ddb76ce901f50183fdff8d1ff6862f91b38880c@huawei.com","fs: ceph: new helper: file_inode(file)\n\nSigned-off-by: Libo Chen <clbchenlibo.chen@huawei.com>\nSigned-off-by: Sage Weil <sage@inktank.com>","Libo Chen",false],["d29adb34a94715174c88ca93e8aba955850c9bde","51652c783f70f5b272ebd02f1fd20d3af7a2449f@inktank.com","libceph: block I/O when PAUSE or FULL osd map flags are set\n\nThe PAUSEWR and PAUSERD flags are meant to stop the cluster from\nprocessing writes and reads, respectively. The FULL flag is set when\nthe cluster determines that it is out of space, and will no longer\nprocess writes.  PAUSEWR and PAUSERD are purely client-side settings\nalready implemented in userspace clients. The osd does nothing special\nwith these flags.\n\nWhen the FULL flag is set, however, the osd responds to all writes\nwith -ENOSPC. For cephfs, this makes sense, but for rbd the block\nlayer translates this into EIO.  If a cluster goes from full to\nnon-full quickly, a filesystem on top of rbd will not behave well,\nsince some writes succeed while others get EIO.\n\nFix this by blocking any writes when the FULL flag is set in the osd\nclient. This is the same strategy used by userspace, so apply it by\ndefault.  A follow-on patch makes this configurable.\n\n__map_request() is called to re-target osd requests in case the\navailable osds changed.  Add a paused field to a ceph_osd_request, and\nset it whenever an appropriate osd map flag is set.  Avoid queueing\npaused requests in __map_request(), but force them to be resent if\nthey become unpaused.\n\nAlso subscribe to the next osd map from the monitor if any of these\nflags are set, so paused requests can be unblocked as soon as\npossible.\n\nFixes: http://tracker.ceph.com/issues/6079\n\nReviewed-by: Sage Weil <sage@inktank.com>\nSigned-off-by: Josh Durgin <josh.durgin@inktank.com>","Josh Durgin",false],["9a1ea2dbff11547a8e664f143c1ffefc586a577a","51652c783f70f5b272ebd02f1fd20d3af7a2449f@inktank.com","libceph: resend all writes after the osdmap loses the full flag\n\nWith the current full handling, there is a race between osds and\nclients getting the first map marked full. If the osd wins, it will\nreturn -ENOSPC to any writes, but the client may already have writes\nin flight. This results in the client getting the error and\npropagating it up the stack. For rbd, the block layer turns this into\nEIO, which can cause corruption in filesystems above it.\n\nTo avoid this race, osds are being changed to drop writes that came\nfrom clients with an osdmap older than the last osdmap marked full.\nIn order for this to work, clients must resend all writes after they\nencounter a full -> not full transition in the osdmap. osds will wait\nfor an updated map instead of processing a request from a client with\na newer map, so resent writes will not be dropped by the osd unless\nthere is another not full -> full transition.\n\nThis approach requires both osds and clients to be fixed to avoid the\nrace. Old clients talking to osds with this fix may hang instead of\nreturning EIO and potentially corrupting an fs. New clients talking to\nold osds have the same behavior as before if they encounter this race.\n\nFixes: http://tracker.ceph.com/issues/6938\n\nReviewed-by: Sage Weil <sage@inktank.com>\nSigned-off-by: Josh Durgin <josh.durgin@inktank.com>","Josh Durgin",false],["320a382746e0ab1304476ea7e986a8d416ab99db","695e2a2c1e39535baaa147c5eb4e5da14054d59f@intel.com","NVMe: compat SG_IO ioctl\n\nFor 32-bit versions of sg3-utils running on a 64-bit system. This is\nmostly a copy from the relevent portions of fs/compat_ioctl.c, with\nslight modifications for going through block_device_operations.\n\nSigned-off-by: Keith Busch <keith.busch@intel.com>\nReviewed-by: Vishal Verma <vishal.l.verma@linux.intel.com>\n[fixed up CONFIG_COMPAT=n build problems]\nSigned-off-by: Matthew Wilcox <matthew.r.wilcox@intel.com>","Keith Busch",false],["0a8d44cb33377969337fa6c1961b631605d5f453","990c37a323daf1549bdd24197927625080ee16b8@linux.intel.com","NVMe: Fix lockdep warnings\n\nDuring the initialisation path, the queue lock is taken without interrupt\nprotection.  It's perfectly safe to do so, because the interrupt handler\ncan't run at this point, but it confuses lockdep.\n\nSigned-off-by: Matthew Wilcox <matthew.r.wilcox@intel.com>","Matthew Wilcox",false],["68608c268bf265b039daeaafee6c902dfef32024","ed1245e46949b7b8f2bca25d41520ebc8aeefcf8@intel.com","NVMe: Cache dev->pci_dev in a local pointer\n\nHelps with line-length issues\n\nSigned-off-by: Matthew Wilcox <matthew.r.wilcox@intel.com>","Matthew Wilcox",false],["9a6b94584de1a0467d85b435df9c744c5c45a270","695e2a2c1e39535baaa147c5eb4e5da14054d59f@intel.com","NVMe: Device resume error handling\n\nAdds controller error handling on resume power management. If the device\nfails to initialize, the device is queued for a reset. If the reset fails,\na thread is spawned to remove the pci device.\n\nIf the device resumes as \"busy\", the device is responding to admin\ncommands but will not create IO queues. In this case, we need to remove\nthe gendisks and free the IO queues since they can't be used and may be\nholding bios in their lists.\n\nFrom testing, the dma pools require a pci device so this had to change\nthe pci driver 'remove' to release the dma resources in line with that\ncall instead of after all references to the device are released.\n\nSigned-off-by: Keith Busch <keith.busch@intel.com>\nSigned-off-by: Matthew Wilcox <matthew.r.wilcox@intel.com>","Keith Busch",false],["83d5f3246fc05a629278240c09688fd9960b97db","09f65b71b7655725897b2fd41a09a0cefe2e1ace@kernel.org","staging:iio:ad799x fix incorrect endianness specification for buffer elements\n\nDue to use of the IIO_ST macro, the endianness element of scan_type was\nnot being set.  The result is that it will default to the cpu endianness\nwhereas this driver will fill the buffer with big endian data.  Thus for\nlittle endian machines, userspace will miss interpret the data.\n\nSigned-off-by: Jonathan Cameron <jic23@kernel.org>\nAcked-by: Lars-Peter Clausen <lars@metafoo.de>","Jonathan Cameron",false],["e178f7057b81c87a7ceaae0ca204487b6f7eedcf","cf148a1c890adeeb4308e9e093ed95f3d05c8318@intel.com","drm/i915: Provide PDP updates via MMIO\n\nThe initial implementation of this function used MMIO to write the PDPs.\nUpon review it was determined (correctly) that the docs say to use LRI.\nThe issue is there are times where we want to do a synchronous write\n(GPU reset).\n\nI've tested this, and it works. I've verified with as many people as\npossible that it should work.\n\nThis should fix the failing reset problems.\n\nSigned-off-by: Ben Widawsky <ben@bwidawsk.net>\nSigned-off-by: Daniel Vetter <daniel.vetter@ffwll.ch>","Ben Widawsky",false],["6f425321e02a1b6c5e90b70f8fab7c140fcaeefb","cf148a1c890adeeb4308e9e093ed95f3d05c8318@intel.com","drm/i915: Don't unconditionally try to deref aliasing ppgtt\n\nSince the beginning, the functions which try to properly reference the\naliasing PPGTT have deferences a potentially null aliasing_ppgtt member.\nSince the accessors are meant to be global, this will not do.\n\nIntroduced originally in:\ncommit a70a3148b0c61cb7c588ea650db785b261b378a3\nAuthor: Ben Widawsky <ben@bwidawsk.net>\nDate:   Wed Jul 31 16:59:56 2013 -0700\n\n    drm/i915: Make proper functions for VMs\n\nSigned-off-by: Ben Widawsky <ben@bwidawsk.net>\nSigned-off-by: Daniel Vetter <daniel.vetter@ffwll.ch>","Ben Widawsky",false],["6e164c3382314a1f63526fa7a4322a17318d0e32","cf148a1c890adeeb4308e9e093ed95f3d05c8318@intel.com","drm/i915: Allow ggtt lookups to not WARN\n\nTo be able to effectively use the GGTT object lookup function, we don't\nwant to warn when there is no GGTT mapping. Let the caller deal with it\ninstead.\n\nOriginally, I had intended to have this behavior, and has not\nintroduced the WARN. It was introduced during review with the addition\nof the follow commit\n\ncommit 5c2abbeab798154166d42fce4f71790caa6dd9bc\nAuthor: Ben Widawsky <benjamin.widawsky@intel.com>\nDate:   Tue Sep 24 09:57:57 2013 -0700\n\n    drm/i915: Provide a cheap ggtt vma lookup\n\nSigned-off-by: Ben Widawsky <ben@bwidawsk.net>\nSigned-off-by: Daniel Vetter <daniel.vetter@ffwll.ch>","Ben Widawsky",false]],"size":6832,"ref":"refs/heads/master","head":"fd238d765d60ccae13e42e8072b3732f45de609b"}