{"push_id":546134993,"size":121,"distinct_size":121,"ref":"refs/heads/android-msm-hammerhead-3.4-lollipop-release","head":"6b38e782672a9391e58268a8cd8f463f870ff841","before":"463a0150c0e676debc16d53fd678e6945a38bf1b","commits":[{"sha":"cce1df1df7326e37b2b3f5234c434dd6f50eab1e","author":{"email":"0da414d9d963da4039c2a0525b1844228075aa58@linux-m68k.org","name":"Geert Uytterhoeven"},"message":"mn10300: only add -mmem-funcs to KBUILD_CFLAGS if gcc supports it\n\ncommit 9957423f035c2071f6d1c5d2f095cdafbeb25ad7 upstream.\n\nIt seems the current (gcc 4.6.3) no longer provides this so make it\nconditional.\n\nAs reported by Tony before, the mn10300 architecture cross-compiles with\ngcc-4.6.3 if -mmem-funcs is not added to KBUILD_CFLAGS.\n\nReported-by: Tony Breeds <tony@bakeyournoodle.com>\nSigned-off-by: Geert Uytterhoeven <geert@linux-m68k.org>\nCc: David Howells <dhowells@redhat.com>\nCc: Koichi Yasutake <yasutake.koichi@jp.panasonic.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>","distinct":true,"url":"https://api.github.com/repos/Fagyi/kernel_msm_hammerhead/commits/cce1df1df7326e37b2b3f5234c434dd6f50eab1e"},{"sha":"32dd008a7c23b4f92bf7ac4eb6b86297f4ea0ba6","author":{"email":"c00cbc2b736c26791a3822db86f8796fe9efff67@pengutronix.de","name":"Sascha Hauer"},"message":"kbuild: make: fix if_changed when command contains backslashes\n\ncommit c353acba28fb3fa1fd05fd6b85a9fc7938330f9c upstream.\n\nThe call if_changed mechanism does not work when the command contains\nbackslashes.  This basically is an issue with lzo and bzip2 compressed\nkernels.  The compressed binaries do not contain the uncompressed image\nsize, so these use size_append to append the size.  This results in\nbackslashes in the executed command.  With this if_changed always\ndetects a change in the command and rebuilds the compressed image even\nif nothing has changed.\n\nFix this by escaping backslashes in make-cmd\n\nSigned-off-by: Sascha Hauer <s.hauer@pengutronix.de>\nSigned-off-by: Jan Luebbe <jlu@pengutronix.de>\nCc: Sam Ravnborg <sam@ravnborg.org>\nCc: Bernhard Walle <bernhard@bwalle.de>\nCc: Michal Marek <mmarek@suse.cz>\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>","distinct":true,"url":"https://api.github.com/repos/Fagyi/kernel_msm_hammerhead/commits/32dd008a7c23b4f92bf7ac4eb6b86297f4ea0ba6"},{"sha":"eab23dc2508d6132871aa4f56ef40a496b450971","author":{"email":"efca98801f3398ebd7eeff805a2c18e6c49e84d4@suse.de","name":"Jean Delvare"},"message":"kbuild: Fix gcc -x syntax\n\ncommit b1e0d8b70fa31821ebca3965f2ef8619d7c5e316 upstream.\n\nThe correct syntax for gcc -x is \"gcc -x assembler\", not\n\"gcc -xassembler\". Even though the latter happens to work, the former\nis what is documented in the manual page and thus what gcc wrappers\nsuch as icecream do expect.\n\nThis isn't a cosmetic change. The missing space prevents icecream from\nrecognizing compilation tasks it can't handle, leading to silent kernel\nmiscompilations.\n\nBesides me, credits go to Michael Matz and Dirk Mueller for\ninvestigating the miscompilation issue and tracking it down to this\nincorrect -x parameter syntax.\n\nSigned-off-by: Jean Delvare <jdelvare@suse.de>\nAcked-by: Ingo Molnar <mingo@kernel.org>\nCc: Bernhard Walle <bernhard@bwalle.de>\nCc: Michal Marek <mmarek@suse.cz>\nCc: Ralf Baechle <ralf@linux-mips.org>\nSigned-off-by: Michal Marek <mmarek@suse.cz>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/Fagyi/kernel_msm_hammerhead/commits/eab23dc2508d6132871aa4f56ef40a496b450971"},{"sha":"a34dfb26c1d191a16058a6b7234d3f5d1df5707c","author":{"email":"6affa2782fb8514898f88c7c4a087191fcbabb20@linux.vnet.ibm.com","name":"Michael Wang"},"message":"slab: fix the DEADLOCK issue on l3 alien lock\n\ncommit 947ca1856a7e60aa6d20536785e6a42dff25aa6e upstream.\n\nDEADLOCK will be report while running a kernel with NUMA and LOCKDEP enabled,\nthe process of this fake report is:\n\n\t   kmem_cache_free()\t//free obj in cachep\n\t-> cache_free_alien()\t//acquire cachep's l3 alien lock\n\t-> __drain_alien_cache()\n\t-> free_block()\n\t-> slab_destroy()\n\t-> kmem_cache_free()\t//free slab in cachep->slabp_cache\n\t-> cache_free_alien()\t//acquire cachep->slabp_cache's l3 alien lock\n\nSince the cachep and cachep->slabp_cache's l3 alien are in the same lock class,\nfake report generated.\n\nThis should not happen since we already have init_lock_keys() which will\nreassign the lock class for both l3 list and l3 alien.\n\nHowever, init_lock_keys() was invoked at a wrong position which is before we\ninvoke enable_cpucache() on each cache.\n\nSince until set slab_state to be FULL, we won't invoke enable_cpucache()\non caches to build their l3 alien while creating them, so although we invoked\ninit_lock_keys(), the l3 alien lock class won't change since we don't have\nthem until invoked enable_cpucache() later.\n\nThis patch will invoke init_lock_keys() after we done enable_cpucache()\ninstead of before to avoid the fake DEADLOCK report.\n\nMichael traced the problem back to a commit in release 3.0.0:\n\ncommit 30765b92ada267c5395fc788623cb15233276f5c\nAuthor: Peter Zijlstra <peterz@infradead.org>\nDate:   Thu Jul 28 23:22:56 2011 +0200\n\n    slab, lockdep: Annotate the locks before using them\n\n    Fernando found we hit the regular OFF_SLAB 'recursion' before we\n    annotate the locks, cure this.\n\n    The relevant portion of the stack-trace:\n\n    > [    0.000000]  [<c085e24f>] rt_spin_lock+0x50/0x56\n    > [    0.000000]  [<c04fb406>] __cache_free+0x43/0xc3\n    > [    0.000000]  [<c04fb23f>] kmem_cache_free+0x6c/0xdc\n    > [    0.000000]  [<c04fb2fe>] slab_destroy+0x4f/0x53\n    > [    0.000000]  [<c04fb396>] free_block+0x94/0xc1\n    > [    0.000000]  [<c04fc551>] do_tune_cpucache+0x10b/0x2bb\n    > [    0.000000]  [<c04fc8dc>] enable_cpucache+0x7b/0xa7\n    > [    0.000000]  [<c0bd9d3c>] kmem_cache_init_late+0x1f/0x61\n    > [    0.000000]  [<c0bba687>] start_kernel+0x24c/0x363\n    > [    0.000000]  [<c0bba0ba>] i386_start_kernel+0xa9/0xaf\n\n    Reported-by: Fernando Lopez-Lezcano <nando@ccrma.Stanford.EDU>\n    Acked-by: Pekka Enberg <penberg@kernel.org>\n    Signed-off-by: Peter Zijlstra <a.p.zijlstra@chello.nl>\n    Link: http://lkml.kernel.org/r/1311888176.2617.379.camel@laptop\n    Signed-off-by: Ingo Molnar <mingo@elte.hu>\n\nThe commit moved init_lock_keys() before we build up the alien, so we\nfailed to reclass it.\n\nAcked-by: Christoph Lameter <cl@linux.com>\nTested-by: Paul E. McKenney <paulmck@linux.vnet.ibm.com>\nSigned-off-by: Michael Wang <wangyun@linux.vnet.ibm.com>\nSigned-off-by: Pekka Enberg <penberg@kernel.org>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/Fagyi/kernel_msm_hammerhead/commits/a34dfb26c1d191a16058a6b7234d3f5d1df5707c"},{"sha":"cd7f24cd1f0d2f93c0a7cce67cd858d64b8cfb76","author":{"email":"7469de9b95ba379e2656fa9677689657c47a7690@redhat.com","name":"Alex Williamson"},"message":"intel-iommu: Default to non-coherent for domains unattached to iommus\n\ncommit 2e12bc29fc5a12242d68e11875db3dd58efad9ff upstream.\n\ndomain_update_iommu_coherency() currently defaults to setting domains\nas coherent when the domain is not attached to any iommus.  This\nallows for a window in domain_context_mapping_one() where such a\ndomain can update context entries non-coherently, and only after\nupdate the domain capability to clear iommu_coherency.\n\nThis can be seen using KVM device assignment on VT-d systems that\ndo not support coherency in the ecap register.  When a device is\nadded to a guest, a domain is created (iommu_coherency = 0), the\ndevice is attached, and ranges are mapped.  If we then hot unplug\nthe device, the coherency is updated and set to the default (1)\nsince no iommus are attached to the domain.  A subsequent attach\nof a device makes use of the same dmar domain (now marked coherent)\nupdates context entries with coherency enabled, and only disables\ncoherency as the last step in the process.\n\nTo fix this, switch domain_update_iommu_coherency() to use the\nsafer, non-coherent default for domains not attached to iommus.\n\nSigned-off-by: Alex Williamson <alex.williamson@redhat.com>\nTested-by: Donald Dutile <ddutile@redhat.com>\nAcked-by: Donald Dutile <ddutile@redhat.com>\nAcked-by: Chris Wright <chrisw@sous-sol.org>\nSigned-off-by: Joerg Roedel <joerg.roedel@amd.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/Fagyi/kernel_msm_hammerhead/commits/cd7f24cd1f0d2f93c0a7cce67cd858d64b8cfb76"},{"sha":"32582fcb5d96ef0d5eb1d1638f1612167b65fc2c","author":{"email":"73675debcd8a436be48ec22211dcf44fe0df0a64@decadent.org.uk","name":"Ben Hutchings"},"message":"media: rc: ite-cir: Initialise ite_dev::rdev earlier\n\ncommit 4b961180ef275035b1538317ffd0e21e80e63e77 upstream.\n\nite_dev::rdev is currently initialised in ite_probe() after\nrc_register_device() returns.  If a newly registered device is opened\nquickly enough, we may enable interrupts and try to use ite_dev::rdev\nbefore it has been initialised.  Move it up to the earliest point we\ncan, right after calling rc_allocate_device().\n\nReported-and-tested-by: YunQiang Su <wzssyqa@gmail.com>\n\nSigned-off-by: Ben Hutchings <ben@decadent.org.uk>\nSigned-off-by: Mauro Carvalho Chehab <mchehab@redhat.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/Fagyi/kernel_msm_hammerhead/commits/32582fcb5d96ef0d5eb1d1638f1612167b65fc2c"},{"sha":"601b13f8e4fab7cc8ba9e26c60753e059eb118d7","author":{"email":"27eadf8cc37a0b12407025a9e98c8c3dd8200904@googlemail.com","name":"Frank Schäfer"},"message":"media: gspca_pac7302: add support for device 1ae7:2001 Speedlink Snappy Microphone SL-6825-SBK\n\ncommit 97d2fbf501e3cf105ac957086c7e40e62e15cdf8 upstream.\n\nSigned-off-by: Frank Schäfer <fschaefer.oss@googlemail.com>\nSigned-off-by: Hans de Goede <hdegoede@redhat.com>\nSigned-off-by: Mauro Carvalho Chehab <mchehab@redhat.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/Fagyi/kernel_msm_hammerhead/commits/601b13f8e4fab7cc8ba9e26c60753e059eb118d7"},{"sha":"68f58ac6db1bba4a7a7f552ee0b7e6ca189f5d95","author":{"email":"d6f051473f553588884d51874952f6fb19ae8261@intel.com","name":"Lin Ming"},"message":"ACPI: run _OSC after ACPI_FULL_INITIALIZATION\n\ncommit fc54ab72959edbf229b65ac74b2f122d799ca002 upstream.\n\nThe _OSC method may exist in module level code,\nso it must be called after ACPI_FULL_INITIALIZATION\n\nOn some new platforms with Zero-Power-Optical-Disk-Drive (ZPODD)\nsupport, this fix is necessary to save power.\n\nSigned-off-by: Lin Ming <ming.m.lin@intel.com>\nTested-by: Aaron Lu <aaron.lu@intel.com>\nSigned-off-by: Len Brown <len.brown@intel.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/Fagyi/kernel_msm_hammerhead/commits/68f58ac6db1bba4a7a7f552ee0b7e6ca189f5d95"},{"sha":"949b65b4aa5eb524f2f97a8d50bfa054dfe0f4d1","author":{"email":"f10ec01be0c6b54271af5c550cd257810bdf3268@google.com","name":"Bjorn Helgaas"},"message":"PCI: acpiphp: check whether _ADR evaluation succeeded\n\ncommit dfb117b3e50c52c7b3416db4a4569224b8db80bb upstream.\n\nCheck whether we evaluated _ADR successfully.  Previously we ignored\nfailure, so we would have used garbage data from the stack as the device\nand function number.\n\nWe return AE_OK so that we ignore only this slot and continue looking\nfor other slots.\n\nFound by Coverity (CID 113981).\n\nSigned-off-by: Bjorn Helgaas <bhelgaas@google.com>\nSigned-off-by: Ben Hutchings <ben@decadent.org.uk>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/Fagyi/kernel_msm_hammerhead/commits/949b65b4aa5eb524f2f97a8d50bfa054dfe0f4d1"},{"sha":"89e06dca29912b4be61f01f8852268d2f44ea47c","author":{"email":"b51b9a92386687a9ac927cebfa0f978adeb8cea5@opensource.wolfsonmicro.com","name":"Mark Brown"},"message":"mfd: max8925: Move _IO resources out of ioport_ioresource\n\ncommit bee6e1fa617b1fb7f6f91033428410e05f5ab0ed upstream.\n\nThe removal of mach/io.h from most ARM platforms also set the range of\nvalid IO ports to be empty for most platforms when previously any 32\nbit integer had been valid. This makes it impossible to add IO resources\nas the added range is smaller than that of the root resource for IO ports.\n\nSince we're not really using IO memory at all fix this by defining our\nown root resource outside the normal tree and make that the parent of\nall IO resources. This also ensures we won't conflict with read IO ports\nif we ever run on a platform which happens to use them.\n\nSigned-off-by: Mark Brown <broonie@opensource.wolfsonmicro.com>\nAcked-by: Arnd Bergmann <arnd@arndb.de>\nAcked-by: Haojian Zhuang <haojian.zhuang@gmail.com>\nTested-by: Haojian Zhuang <haojian.zhuang@gmail.com>\nSigned-off-by: Samuel Ortiz <sameo@linux.intel.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/Fagyi/kernel_msm_hammerhead/commits/89e06dca29912b4be61f01f8852268d2f44ea47c"},{"sha":"db0c478ba676191a2b04f707b577c493dec4de72","author":{"email":"bfcdf3e6ca6cef45543bfbb57509c92aec9a39fb@gnu.org","name":"Davidlohr Bueso"},"message":"lib/gcd.c: prevent possible div by 0\n\ncommit e96875677fb2b7cb739c5d7769824dff7260d31d upstream.\n\nAccount for all properties when a and/or b are 0:\ngcd(0, 0) = 0\ngcd(a, 0) = a\ngcd(0, b) = b\n\nFixes no known problems in current kernels.\n\nSigned-off-by: Davidlohr Bueso <dave@gnu.org>\nCc: Eric Dumazet <eric.dumazet@gmail.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>","distinct":true,"url":"https://api.github.com/repos/Fagyi/kernel_msm_hammerhead/commits/db0c478ba676191a2b04f707b577c493dec4de72"},{"sha":"d1aa083ea4173f92701ea2166fb10da9d9723a03","author":{"email":"912cf7eb7d8018e2943586ae6657d21fd4e38239@linaro.org","name":"Shawn Guo"},"message":"kernel/sys.c: call disable_nonboot_cpus() in kernel_restart()\n\ncommit f96972f2dc6365421cf2366ebd61ee4cf060c8d5 upstream.\n\nAs kernel_power_off() calls disable_nonboot_cpus(), we may also want to\nhave kernel_restart() call disable_nonboot_cpus().  Doing so can help\nmachines that require boot cpu be the last alive cpu during reboot to\nsurvive with kernel restart.\n\nThis fixes one reboot issue seen on imx6q (Cortex-A9 Quad).  The machine\nrequires that the restart routine be run on the primary cpu rather than\nsecondary ones.  Otherwise, the secondary core running the restart\nroutine will fail to come to online after reboot.\n\nSigned-off-by: Shawn Guo <shawn.guo@linaro.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>","distinct":true,"url":"https://api.github.com/repos/Fagyi/kernel_msm_hammerhead/commits/d1aa083ea4173f92701ea2166fb10da9d9723a03"},{"sha":"d5c2a24bd3e0d457a34cf1a6f359b3202b4cb0ee","author":{"email":"204da078bb794ca7b065b3ff55e0f162ee76e3a2@cyrius.com","name":"Martin Michlmayr"},"message":"drivers/scsi/atp870u.c: fix bad use of udelay\n\ncommit 0f6d93aa9d96cc9022b51bd10d462b03296be146 upstream.\n\nThe ACARD driver calls udelay() with a value > 2000, which leads to to\nthe following compilation error on ARM:\n\n  ERROR: \"__bad_udelay\" [drivers/scsi/atp870u.ko] undefined!\n  make[1]: *** [__modpost] Error 1\n\nThis is because udelay is defined on ARM, roughly speaking, as\n\n\t#define udelay(n) ((n) > 2000 ? __bad_udelay() : \\\n\t\t__const_udelay((n) * ((2199023U*HZ)>>11)))\n\nThe argument to __const_udelay is the number of jiffies to wait divided\nby 4, but this does not work unless the multiplication does not\noverflow, and that is what the build error is designed to prevent.  The\nintended behavior can be achieved by using mdelay to call udelay\nmultiple times in a loop.\n\n[jrnieder@gmail.com: adding context]\nSigned-off-by: Martin Michlmayr <tbm@cyrius.com>\nSigned-off-by: Jonathan Nieder <jrnieder@gmail.com>\nCc: James Bottomley <James.Bottomley@HansenPartnership.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>","distinct":true,"url":"https://api.github.com/repos/Fagyi/kernel_msm_hammerhead/commits/d5c2a24bd3e0d457a34cf1a6f359b3202b4cb0ee"},{"sha":"9e0034214376ece1cfd710585242eea4cb0a6fc9","author":{"email":"679188261afeb60eb822cd934fd7b46a48ddd743@freescale.com","name":"Fabio Estevam"},"message":"drivers/dma/dmaengine.c: lower the priority of 'failed to get' dma channel message\n\ncommit 0eb5a35801df3c438ce3fc91310a415ea4452c00 upstream.\n\nDo the same as commit a03a202e95fd (\"dmaengine: failure to get a\nspecific DMA channel is not critical\") to get rid of the following\nmessages during kernel boot:\n\n  dmaengine_get: failed to get dma1chan0: (-22)\n  dmaengine_get: failed to get dma1chan1: (-22)\n  dmaengine_get: failed to get dma1chan2: (-22)\n  dmaengine_get: failed to get dma1chan3: (-22)\n  ..\n\nSigned-off-by: Fabio Estevam <fabio.estevam@freescale.com>\nCc: Vinod Koul <vinod.koul@intel.com>\nCc: Dan Williams <dan.j.williams@intel.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>","distinct":true,"url":"https://api.github.com/repos/Fagyi/kernel_msm_hammerhead/commits/9e0034214376ece1cfd710585242eea4cb0a6fc9"},{"sha":"38a655dba24882e24d279d0c5d12d3155080e43e","author":{"email":"df9728c9e5104131c08c7adb03af425394842596@rustcorp.com.au","name":"Rusty Russell"},"message":"lguest: fix occasional crash in example launcher.\n\ncommit ca16f580a5db7e60bfafe59a50bb133bd3347491 upstream.\n\nWe usually got away with ->next on the final entry being NULL, but it\nfinally bit me.\n\nSigned-off-by: Rusty Russell <rusty@rustcorp.com.au>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/Fagyi/kernel_msm_hammerhead/commits/38a655dba24882e24d279d0c5d12d3155080e43e"},{"sha":"31a251d0905dc11aae86e3ac9a92d1b4526ef91d","author":{"email":"4d6e32db2683aba4a3f3669c68ac02b37d1b91cd@linux.vnet.ibm.com","name":"Gavin Shan"},"message":"powerpc/eeh: Fix crash on converting OF node to edev\n\ncommit 1e38b7140185e384da216aff66a711df09b5afc9 upstream.\n\nThe kernel crash was reported by Alexy. He was testing some feature\nwith private kernel, in which Alexy added some code in pci_pm_reset()\nto read the CSR after writting it. The bug could be reproduced on\nFiber Channel card (Fibre Channel: Emulex Corporation Saturn-X:\nLightPulse Fibre Channel Host Adapter (rev 03)) by the following\ncommands.\n\n\t# echo 1 > /sys/devices/pci0004:01/0004:01:00.0/reset\n\t# rmmod lpfc\n\t# modprobe lpfc\n\nThe history behind the test case is that those additional config\nspace reading operations in pci_pm_reset() would cause EEH error,\nbut we didn't detect EEH error until \"modprobe lpfc\". For the case,\nall the PCI devices on PCI bus (0004:01) were removed and added after\nPE reset. Then the EEH devices would be figured out again based on\nthe OF nodes. Unfortunately, there were some child OF nodes under\nPCI device (0004:01:00.0), but they didn't have attached PCI_DN since\nthey're invisible from PCI domain. However, we were still trying to\nconvert OF node to EEH device without checking on the attached PCI_DN.\nEventually, it caused the kernel crash as follows:\n\nUnable to handle kernel paging request for data at address 0x00000030\nFaulting instruction address: 0xc00000000004d888\ncpu 0x0: Vector: 300 (Data Access) at [c000000fc797b950]\n    pc: c00000000004d888: .eeh_add_device_tree_early+0x78/0x140\n    lr: c00000000004d880: .eeh_add_device_tree_early+0x70/0x140\n    sp: c000000fc797bbd0\n   msr: 8000000000009032\n   dar: 30\n dsisr: 40000000\n  current = 0xc000000fc78d9f70\n  paca    = 0xc00000000edb0000   softe: 0        irq_happened: 0x00\n    pid   = 2951, comm = eehd\nenter ? for help\n[c000000fc797bc50] c00000000004d848 .eeh_add_device_tree_early+0x38/0x140\n[c000000fc797bcd0] c00000000004d848 .eeh_add_device_tree_early+0x38/0x140\n[c000000fc797bd50] c000000000051b54 .pcibios_add_pci_devices+0x34/0x190\n[c000000fc797bde0] c00000000004fb10 .eeh_reset_device+0x100/0x160\n[c000000fc797be70] c0000000000502dc .eeh_handle_event+0x19c/0x300\n[c000000fc797bf00] c000000000050570 .eeh_event_handler+0x130/0x1a0\n[c000000fc797bf90] c000000000020138 .kernel_thread+0x54/0x70\n\nThe patch changes of_node_to_eeh_dev() and just returns NULL if the\npassed OF node doesn't have attached PCI_DN.\n\nReported-by: Alexey Kardashevskiy <aik@ozlabs.ru>\nSigned-off-by: Gavin Shan <shangw@linux.vnet.ibm.com>\nSigned-off-by: Benjamin Herrenschmidt <benh@kernel.crashing.org>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/Fagyi/kernel_msm_hammerhead/commits/31a251d0905dc11aae86e3ac9a92d1b4526ef91d"},{"sha":"45cb2d550843ffa0e82f4ec0f58672c261ae3b1a","author":{"email":"4ee99b187650e6ea4b9259bc798eb76cfca96ee4@idt.com","name":"Alexandre Bounine"},"message":"rapidio/rionet: fix multicast packet transmit logic\n\ncommit 7c4a6106d6451fc03c491e61df37c044505d843a upstream.\n\nFix multicast packet transmit logic to account for repetitive transmission\nof single skb:\n- correct check for available buffers (this bug may produce NULL pointer\n  crash dump in case of heavy traffic);\n- update skb user count (incorrect user counter causes a warning dump from\n  net_tx_action routine during multicast transfers in systems with three or\n  more rionet participants).\n\nSigned-off-by: Alexandre Bounine <alexandre.bounine@idt.com>\nCc: Matt Porter <mporter@kernel.crashing.org>\nCc: David S. Miller <davem@davemloft.net>\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>","distinct":true,"url":"https://api.github.com/repos/Fagyi/kernel_msm_hammerhead/commits/45cb2d550843ffa0e82f4ec0f58672c261ae3b1a"},{"sha":"375db46c1ba54e1c0f39926e9854ddbb6f528056","author":{"email":"84756e775432b802ba0ac9377e5cc7a055de65f8@marvell.com","name":"Feng Hong"},"message":"PM / Sleep: use resume event when call dpm_resume_early\n\ncommit 997a031107ec962967ce36db9bc500f1fad491c1 upstream.\n\nWhen dpm_suspend_noirq fail, state is PMSG_SUSPEND,\nshould change to PMSG_RESUME when dpm_resume_early is called\n\nSigned-off-by: Feng Hong <hongfeng@marvell.com>\nSigned-off-by: Raul Xiong <xjian@marvell.com>\nSigned-off-by: Neil Zhang <zhangwm@marvell.com>\nSigned-off-by: Rafael J. Wysocki <rjw@sisk.pl>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/Fagyi/kernel_msm_hammerhead/commits/375db46c1ba54e1c0f39926e9854ddbb6f528056"},{"sha":"5f64b1723fc858ba47e97dac6218842d3e1dab56","author":{"email":"546b05909706652891a87f7bfe385ae147f61f91@kernel.org","name":"Tejun Heo"},"message":"workqueue: add missing smp_wmb() in process_one_work()\n\ncommit 959d1af8cffc8fd38ed53e8be1cf4ab8782f9c00 upstream.\n\nWORK_STRUCT_PENDING is used to claim ownership of a work item and\nprocess_one_work() releases it before starting execution.  When\nsomeone else grabs PENDING, all pre-release updates to the work item\nshould be visible and all updates made by the new owner should happen\nafterwards.\n\nGrabbing PENDING uses test_and_set_bit() and thus has a full barrier;\nhowever, clearing doesn't have a matching wmb.  Given the preceding\nspin_unlock and use of clear_bit, I don't believe this can be a\nproblem on an actual machine and there hasn't been any related report\nbut it still is theretically possible for clear_pending to permeate\nupwards and happen before work->entry update.\n\nAdd an explicit smp_wmb() before work_clear_pending().\n\nSigned-off-by: Tejun Heo <tj@kernel.org>\nCc: Oleg Nesterov <oleg@redhat.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/Fagyi/kernel_msm_hammerhead/commits/5f64b1723fc858ba47e97dac6218842d3e1dab56"},{"sha":"693c69e43518fa3782fd6e8e82873097d68fbc4b","author":{"email":"d55521028c14e0f378be5444e4ea388161c0d7e7@redhat.com","name":"Eric Sandeen"},"message":"jbd2: don't write superblock when if its empty\n\ncommit eeecef0af5ea4efd763c9554cf2bd80fc4a0efd3 upstream.\n\nThis sequence:\n\n# truncate --size=1g fsfile\n# mkfs.ext4 -F fsfile\n# mount -o loop,ro fsfile /mnt\n# umount /mnt\n# dmesg | tail\n\nresults in an IO error when unmounting the RO filesystem:\n\n[  318.020828] Buffer I/O error on device loop1, logical block 196608\n[  318.027024] lost page write due to I/O error on loop1\n[  318.032088] JBD2: Error -5 detected when updating journal superblock for loop1-8.\n\nThis was a regression introduced by commit 24bcc89c7e7c: \"jbd2: split\nupdating of journal superblock and marking journal empty\".\n\nSigned-off-by: Eric Sandeen <sandeen@redhat.com>\nSigned-off-by: \"Theodore Ts'o\" <tytso@mit.edu>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/Fagyi/kernel_msm_hammerhead/commits/693c69e43518fa3782fd6e8e82873097d68fbc4b"}]}