{"push_id":659209823,"size":19,"distinct_size":19,"ref":"refs/heads/lollipop-caf","head":"09e7e13c7d500e61df13f2122eb4111538ece022","before":"0a3ded4a43527f9e28fe993bd99c1e971caaf977","commits":[{"sha":"b7865a4fc93e0dd64ea5f44aa25840c8d155b604","author":{"email":"8e4aa0015eb43ed5ca66aaca3fb498609e1e427c@opensource.wolfsonmicro.com","name":"Charles Keepax"},"message":"ALSA: compress: Pass through return value of open ops callback\n\ncommit 749d32237bf39e6576dd95bfdf24e4378e51716c upstream.\n\nThe snd_compr_open function would always return 0 even if the compressed\nops open function failed, obviously this is incorrect. Looks like this\nwas introduced by a small typo in:\n\ncommit a0830dbd4e42b38aefdf3fb61ba5019a1a99ea85\nALSA: Add a reference counter to card instance\n\nThis patch returns the value from the compressed op as it should.\n\nSigned-off-by: Charles Keepax <ckeepax@opensource.wolfsonmicro.com>\nAcked-by: Vinod Koul <vinod.koul@intel.com>\nSigned-off-by: Takashi Iwai <tiwai@suse.de>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/smac0628/android_kernel_htc_msm8974/commits/b7865a4fc93e0dd64ea5f44aa25840c8d155b604"},{"sha":"0dc49f45be23ad2e125d839dca83381b42d4db17","author":{"email":"51652c783f70f5b272ebd02f1fd20d3af7a2449f@inktank.com","name":"Josh Durgin"},"message":"libceph: resend all writes after the osdmap loses the full flag\n\ncommit 9a1ea2dbff11547a8e664f143c1ffefc586a577a upstream.\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>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/smac0628/android_kernel_htc_msm8974/commits/0dc49f45be23ad2e125d839dca83381b42d4db17"},{"sha":"4a93cc3818f6b6d8c70227993a75bc6602203323","author":{"email":"73675debcd8a436be48ec22211dcf44fe0df0a64@decadent.org.uk","name":"Ben Hutchings"},"message":"iwlwifi: Complete backport of \"iwlwifi: always copy first 16 bytes of commands\"\n\nLinux 3.4.83 included an incomplete backport of commit\n8a964f44e01ad3bbc208c3e80d931ba91b9ea786 ('iwlwifi: always copy first\n16 bytes of commands') which causes a regression for this driver.\nThis is the missing piece.\n\nReported-by: Andreas Sturmlechner <andreas.sturmlechner@gmail.com>\nCc: Johannes Berg <johannes.berg@intel.com>\nCc: Emmanuel Grumbach <emmanuel.grumbach@intel.com>\nCc: Jianguo Wu <wujianguo@huawei.com>\nCc: Andres Bertens <abertensu@yahoo.com>\nTested-by: Andreas Sturmlechner <andreas.sturmlechner@gmail.com>\nSigned-off-by: Ben Hutchings <ben@decadent.org.uk>","distinct":true,"url":"https://api.github.com/repos/smac0628/android_kernel_htc_msm8974/commits/4a93cc3818f6b6d8c70227993a75bc6602203323"},{"sha":"ae80127a4ef94d8dce4cbc9c1bcbda559c441b21","author":{"email":"c24c0248770ae98831f8a654310d4c2e07514c61@plumgrid.com","name":"Alexei Starovoitov"},"message":"x86: bpf_jit: support negative offsets\n\ncommit fdfaf64e75397567257e1051931f9a3377360665 upstream.\n\nCommit a998d4342337 claimed to introduce negative offset support to x86 jit,\nbut it couldn't be working, since at the time of the execution\nof LD+ABS or LD+IND instructions via call into\nbpf_internal_load_pointer_neg_helper() the %edx (3rd argument of this func)\nhad junk value instead of access size in bytes (1 or 2 or 4).\n\nStore size into %edx instead of %ecx (what original commit intended to do)\n\nFixes: a998d4342337 (\"bpf jit: Let the x86 jit handle negative offsets\")\nSigned-off-by: Alexei Starovoitov <ast@plumgrid.com>\nCc: Jan Seiffert <kaffeemonster@googlemail.com>\nCc: Eric Dumazet <edumazet@google.com>\nAcked-by: Eric Dumazet <edumazet@google.com>\nSigned-off-by: David S. Miller <davem@davemloft.net>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/smac0628/android_kernel_htc_msm8974/commits/ae80127a4ef94d8dce4cbc9c1bcbda559c441b21"},{"sha":"b59cba67985568de4edde9221caf9bb00a3c5470","author":{"email":"73675debcd8a436be48ec22211dcf44fe0df0a64@decadent.org.uk","name":"Ben Hutchings"},"message":"deb-pkg: Fix cross-building linux-headers package\n\ncommit f8ce239dfc7ba9add41d9ecdc5e7810738f839fa upstream.\n\nbuilddeb generates a control file that says the linux-headers package\ncan only be built for the build system primary architecture.  This\nbreaks cross-building configurations.  We should use $debarch for this\ninstead.\n\nSince $debarch is not yet set when generating the control file, set\nArchitecture: any and use control file variables to fill in the\ndescription.\n\nFixes: cd8d60a20a45 ('kbuild: create linux-headers package in deb-pkg')\nReported-and-tested-by: \"Niew, Sh.\" <shniew@gmail.com>\nSigned-off-by: Ben Hutchings <ben@decadent.org.uk>\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/smac0628/android_kernel_htc_msm8974/commits/b59cba67985568de4edde9221caf9bb00a3c5470"},{"sha":"a91a66e349cd1a626789806db1f6b4f2cc8a187c","author":{"email":"ff341aa343d564f9e53e9dcb6996be8c04859a66@oracle.com","name":"Dan Carpenter"},"message":"p54: clamp properly instead of just truncating\n\ncommit 608cfbe4abaf76e9d732efd7ed1cfa3998163d91 upstream.\n\nThe call to clamp_t() first truncates the variable signed 8 bit and as a\nresult, the actual clamp is a no-op.\n\nFixes: 0d78156eef1d ('p54: improve site survey')\nSigned-off-by: Dan Carpenter <dan.carpenter@oracle.com>\nSigned-off-by: John W. Linville <linville@tuxdriver.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/smac0628/android_kernel_htc_msm8974/commits/a91a66e349cd1a626789806db1f6b4f2cc8a187c"},{"sha":"fe669a2dd73bef21ea1ba59cc6e7f020b1d90cfd","author":{"email":"efca98801f3398ebd7eeff805a2c18e6c49e84d4@suse.de","name":"Jean Delvare"},"message":"i7300_edac: Fix device reference count\n\ncommit 75135da0d68419ef8a925f4c1d5f63d8046e314d upstream.\n\npci_get_device() decrements the reference count of \"from\" (last\nargument) so when we break off the loop successfully we have only one\ndevice reference - and we don't know which device we have. If we want\na reference to each device, we must take them explicitly and let\nthe pci_get_device() walk complete to avoid duplicate references.\n\nThis is serious, as over-putting device references will cause\nthe device to eventually disappear. Without this fix, the kernel\ncrashes after a few insmod/rmmod cycles.\n\nTested on an Intel S7000FC4UR system with a 7300 chipset.\n\nSigned-off-by: Jean Delvare <jdelvare@suse.de>\nLink: http://lkml.kernel.org/r/20140224111656.09bbb7ed@endymion.delvare\nCc: Mauro Carvalho Chehab <m.chehab@samsung.com>\nCc: Doug Thompson <dougthompson@xmission.com>\nCc: stable@vger.kernel.org\nSigned-off-by: Borislav Petkov <bp@suse.de>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/smac0628/android_kernel_htc_msm8974/commits/fe669a2dd73bef21ea1ba59cc6e7f020b1d90cfd"},{"sha":"bb64b3503549bbbc9dd316ec38d11c484034f3d9","author":{"email":"aa00819e304141d872f2e4b1c4be422ea3abbfe1@calxeda.com","name":"Rob Herring"},"message":"ARM: move outer_cache declaration out of ifdef\n\ncommit 0b53c11d533a8f6688d73fad0baf67dd08ec1b90 upstream.\n\nMove the outer_cache declaration of the CONFIG_OUTER_CACHE ifdef so that\nouter_cache can be used inside IS_ENABLED condition.\n\nSigned-off-by: Rob Herring <rob.herring@calxeda.com>\nCc: Russell King <linux@arm.linux.org.uk>\nSigned-off-by: Ian Campbell <ian.campbell@citrix.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/smac0628/android_kernel_htc_msm8974/commits/bb64b3503549bbbc9dd316ec38d11c484034f3d9"},{"sha":"f8e533d8113ea17903e80c342c45ac508d55c07f","author":{"email":"9fa1be1a5b5729e4c6b404f34c9ce49ff4882fd8@redhat.com","name":"Hans de Goede"},"message":"Input: elantech - improve clickpad detection\n\ncommit c15bdfd5b9831e4cab8cfc118243956e267dd30e upstream.\n\nThe current assumption in the elantech driver that hw version 3 touchpads\nare never clickpads and hw version 4 touchpads are always clickpads is\nwrong.\n\nThere are several bug reports for this, ie:\nhttps://bugzilla.redhat.com/show_bug.cgi?id=1030802\nhttp://superuser.com/questions/619582/right-elantech-touchpad-button-not-working-in-linux\n\nI've spend a couple of hours wading through various bugzillas, launchpads\nand forum posts to create a list of fw-versions and capabilities for\ndifferent laptop models to find a good method to differentiate between\nclickpads and versions with separate hardware buttons.\n\nWhich shows that a device being a clickpad is reliable indicated by bit 12\nbeing set in the fw_version. I've included the gathered list inside the\ndriver, so that we've this info at hand if we need to revisit this later.\n\nSigned-off-by: Hans de Goede <hdegoede@redhat.com>\nReviewed-by: Benjamin Tissoires <benjamin.tissoires@redhat.com>\nSigned-off-by: Dmitry Torokhov <dmitry.torokhov@gmail.com>\nCc: Josh Boyer <jwboyer@fedoraproject.org>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/smac0628/android_kernel_htc_msm8974/commits/f8e533d8113ea17903e80c342c45ac508d55c07f"},{"sha":"13b58723c04127986811f304ce99ff4fc1035514","author":{"email":"958bcd1f4a7a8c36dca09fe3fa9cb5f1483adf51@redhat.com","name":"Marcelo Tosatti"},"message":"KVM: MMU: handle invalid root_hpa at __direct_map\n\ncommit 989c6b34f6a9480e397b170cc62237e89bf4fdb9 upstream.\n\nIt is possible for __direct_map to be called on invalid root_hpa\n(-1), two examples:\n\n1) try_async_pf -> can_do_async_pf\n    -> vmx_interrupt_allowed -> nested_vmx_vmexit\n2) vmx_handle_exit -> vmx_interrupt_allowed -> nested_vmx_vmexit\n\nThen to load_vmcs12_host_state and kvm_mmu_reset_context.\n\nCheck for this possibility, let fault exception be regenerated.\n\nBZ: https://bugzilla.redhat.com/show_bug.cgi?id=924916\n\nSigned-off-by: Marcelo Tosatti <mtosatti@redhat.com>\nSigned-off-by: Paolo Bonzini <pbonzini@redhat.com>\nCc: Josh Boyer <jwboyer@fedoraproject.org>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/smac0628/android_kernel_htc_msm8974/commits/13b58723c04127986811f304ce99ff4fc1035514"},{"sha":"1b76c1f39e5a9297eb377cb110c7ef9034a30945","author":{"email":"958bcd1f4a7a8c36dca09fe3fa9cb5f1483adf51@redhat.com","name":"Marcelo Tosatti"},"message":"KVM: VMX: fix use after free of vmx->loaded_vmcs\n\ncommit 26a865f4aa8e66a6d94958de7656f7f1b03c6c56 upstream.\n\nAfter free_loaded_vmcs executes, the \"loaded_vmcs\" structure\nis kfreed, and now vmx->loaded_vmcs points to a kfreed area.\nSubsequent free_loaded_vmcs then attempts to manipulate\nvmx->loaded_vmcs.\n\nSwitch the order to avoid the problem.\n\nhttps://bugzilla.redhat.com/show_bug.cgi?id=1047892\n\nReviewed-by: Jan Kiszka <jan.kiszka@siemens.com>\nSigned-off-by: Marcelo Tosatti <mtosatti@redhat.com>\nCc: Josh Boyer <jwboyer@fedoraproject.org>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/smac0628/android_kernel_htc_msm8974/commits/1b76c1f39e5a9297eb377cb110c7ef9034a30945"},{"sha":"e854957ee29d00191c42510299da79b4a1f36ab2","author":{"email":"d4c4fc5069677be84f589aa6e14eedffef9ba12f@linux.intel.com","name":"Sarah Sharp"},"message":"xhci: Fix resume issues on Renesas chips in Samsung laptops\n\ncommit 1aa9578c1a9450fb21501c4f549f5b1edb557e6d upstream.\n\nDon Zickus <dzickus@redhat.com> writes:\n\nSome co-workers of mine bought Samsung laptops that had mostly usb3 ports.\nThose ports did not resume correctly (the driver would timeout communicating\nand fail).  This led to frustration as suspend/resume is a common use for\nlaptops.\n\nPoking around, I applied the reset on resume quirk to this chipset and the\nresume started working.  Reloading the xhci_hcd module had been the temporary\nworkaround.\n\nSigned-off-by: Sarah Sharp <sarah.a.sharp@linux.intel.com>\nReported-by: Don Zickus <dzickus@redhat.com>\nTested-by: Prarit Bhargava <prarit@redhat.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/smac0628/android_kernel_htc_msm8974/commits/e854957ee29d00191c42510299da79b4a1f36ab2"},{"sha":"42802e27a1158316202ff5940d92c17d7106fb62","author":{"email":"ab7bb06c5e68578ee974f52540e9229328f48a36@samsung.com","name":"Konstantin Khlebnikov"},"message":"ipc/msg: fix race around refcount\n\n[fixed differently in 6062a8dc0517bce23e3c2f7d2fea5e22411269a3 upstream.]\n\nIn older kernels (before v3.10) ipc_rcu_hdr->refcount was non-atomic int.\nThere was possuble double-free bug: do_msgsnd() calls ipc_rcu_putref() under\nmsq->q_perm->lock and RCU, while freequeue() calls it while it holds only\n'rw_mutex', so there is no sinchronization between them. Two function\ndecrements '2' non-atomically, they both can get '0' as result.\n\ndo_msgsnd()\t\t\t\t\tfreequeue()\n\nmsq = msg_lock_check(ns, msqid);\n...\nipc_rcu_getref(msq);\nmsg_unlock(msq);\nschedule();\n\t\t\t\t\t\t(caller locks spinlock)\n\t\t\t\t\t\texpunge_all(msq, -EIDRM);\n\t\t\t\t\t\tss_wakeup(&msq->q_senders, 1);\n\t\t\t\t\t\tmsg_rmid(ns, msq);\n\t\t\t\t\t\tmsg_unlock(msq);\nipc_lock_by_ptr(&msq->q_perm);\nipc_rcu_putref(msq);\t\t\t\tipc_rcu_putref(msq);\n< both may get get --(...)->refcount == 0 >\n\nThis patch locks ipc_lock and RCU around ipc_rcu_putref in freequeue.\n( RCU protects memory for spin_unlock() )\n\nSimilar bugs might be in other users of ipc_rcu_putref().\n\nIn the mainline this has been fixed in v3.10 indirectly in commmit\n6062a8dc0517bce23e3c2f7d2fea5e22411269a3\n(\"ipc,sem: fine grained locking for semtimedop\") by Rik van Riel.\nThat commit optimized locking and converted refcount into atomic.\n\nI'm not sure that anybody should care about this bug: it's very-very unlikely\nand no longer exists in actual mainline. I've found this just by looking into\nthe code, probably this never happens in real life.\n\nSigned-off-by: Konstantin Khlebnikov <k.khlebnikov@samsung.com>","distinct":true,"url":"https://api.github.com/repos/smac0628/android_kernel_htc_msm8974/commits/42802e27a1158316202ff5940d92c17d7106fb62"},{"sha":"a8b935e1247e59be78dbf49ec6148b90ad39d092","author":{"email":"4645f7897fd33786a2ee1264d590b3c400559d85@linuxfoundation.org","name":"Greg Kroah-Hartman"},"message":"Linux 3.4.85","distinct":true,"url":"https://api.github.com/repos/smac0628/android_kernel_htc_msm8974/commits/a8b935e1247e59be78dbf49ec6148b90ad39d092"},{"sha":"148e26a6de2ad00561184937188d4a51cffb35e2","author":{"email":"49a5ed162141aa1a2ad45c2f70540ac844521912@ens-lyon.org","name":"Samuel Thibault"},"message":"staging: speakup: Prefix externally-visible symbols\n\ncommit ca2beaf84d9678c12b17d92623f0e90829d6ca13 upstream.\n\nThis prefixes all externally-visible symbols of speakup with \"spk_\".\n\nSigned-off-by: Samuel Thibault <samuel.thibault@ens-lyon.org>\nCc: Kamal Mostafa <kamal@canonical.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/smac0628/android_kernel_htc_msm8974/commits/148e26a6de2ad00561184937188d4a51cffb35e2"},{"sha":"196290af4ea97b1ae9c0d525d29d485790dff0e8","author":{"email":"7a0e50e3f6a0939db82b6a8a423c08a163896f41@redhat.com","name":"Benjamin Tissoires"},"message":"Input: synaptics - add manual min/max quirk\n\ncommit 421e08c41fda1f0c2ff6af81a67b491389b653a5 upstream.\n\nThe new Lenovo Haswell series (-40's) contains a new Synaptics touchpad.\nHowever, these new Synaptics devices report bad axis ranges.\nUnder Windows, it is not a problem because the Windows driver uses RMI4\nover SMBus to talk to the device. Under Linux, we are using the PS/2\nfallback interface and it occurs the reported ranges are wrong.\n\nOf course, it would be too easy to have only one range for the whole\nseries, each touchpad seems to be calibrated in a different way.\n\nWe can not use SMBus to get the actual range because I suspect the firmware\nwill switch into the SMBus mode and stop talking through PS/2 (this is the\ncase for hybrid HID over I2C / PS/2 Synaptics touchpads).\n\nSo as a temporary solution (until RMI4 land into upstream), start a new\nlist of quirks with the min/max manually set.\n\nSigned-off-by: Benjamin Tissoires <benjamin.tissoires@redhat.com>\nSigned-off-by: Dmitry Torokhov <dmitry.torokhov@gmail.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/smac0628/android_kernel_htc_msm8974/commits/196290af4ea97b1ae9c0d525d29d485790dff0e8"},{"sha":"3c447ef89cf1bcb724af0b91972e15e7e8da1b6f","author":{"email":"9fa1be1a5b5729e4c6b404f34c9ce49ff4882fd8@redhat.com","name":"Hans de Goede"},"message":"Input: synaptics - add manual min/max quirk for ThinkPad X240\n\ncommit 8a0435d958fb36d93b8df610124a0e91e5675c82 upstream.\n\nThis extends Benjamin Tissoires manual min/max quirk table with support for\nthe ThinkPad X240.\n\nSigned-off-by: Hans de Goede <hdegoede@redhat.com>\nSigned-off-by: Dmitry Torokhov <dmitry.torokhov@gmail.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/smac0628/android_kernel_htc_msm8974/commits/3c447ef89cf1bcb724af0b91972e15e7e8da1b6f"},{"sha":"657ca0087f459e70f8d513ac692c3dc11f5092e4","author":{"email":"d6a1e509d1d5b0c4f1e9bb533f5fd95887612607@epam.com","name":"Artem Fetishev"},"message":"x86: fix boot on uniprocessor systems\n\ncommit 825600c0f20e595daaa7a6dd8970f84fa2a2ee57 upstream.\n\nOn x86 uniprocessor systems topology_physical_package_id() returns -1\nwhich causes rapl_cpu_prepare() to leave rapl_pmu variable uninitialized\nwhich leads to GPF in rapl_pmu_init().\n\nSee arch/x86/kernel/cpu/perf_event_intel_rapl.c.\n\nIt turns out that physical_package_id and core_id can actually be\nretreived for uniprocessor systems too.  Enabling them also fixes\nrapl_pmu code.\n\nSigned-off-by: Artem Fetishev <artem_fetishev@epam.com>\nCc: Stephane Eranian <eranian@google.com>\nCc: Ingo Molnar <mingo@elte.hu>\nCc: \"H. Peter Anvin\" <hpa@zytor.com>\nCc: Thomas Gleixner <tglx@linutronix.de>\nCc: Peter Zijlstra <a.p.zijlstra@chello.nl>\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/smac0628/android_kernel_htc_msm8974/commits/657ca0087f459e70f8d513ac692c3dc11f5092e4"},{"sha":"09e7e13c7d500e61df13f2122eb4111538ece022","author":{"email":"4645f7897fd33786a2ee1264d590b3c400559d85@linuxfoundation.org","name":"Greg Kroah-Hartman"},"message":"Linux 3.4.86","distinct":true,"url":"https://api.github.com/repos/smac0628/android_kernel_htc_msm8974/commits/09e7e13c7d500e61df13f2122eb4111538ece022"}]}