{"push_id":612793150,"size":24,"distinct_size":24,"ref":"refs/heads/korg/linux-3.2.y","head":"9b81446eab425805e9bf9be122373658cbbd39a4","before":"fd623507bdcee1f7a387ae86adb7a66b431dd056","commits":[{"sha":"3edc6373939d16ff2b4d54aa12059d004bf62884","author":{"email":"73675debcd8a436be48ec22211dcf44fe0df0a64@decadent.org.uk","name":"Ben Hutchings"},"message":"PCI: quirks: Fix backport of quirk_io()\n\nCommit 06cf35f903aa ('PCI: Handle read-only BARs on AMD CS553x\ndevices') added the function quirk_io() which calls\npcibios_bus_to_resource().\n\nPrior to Linux 3.14, pcibios_bus_to_resource() takes a pointer to\nstruct pci_dev and looks up the device's bus itself, so we need\nto pass dev not dev->bus.\n\nSigned-off-by: Ben Hutchings <ben@decadent.org.uk>","distinct":true,"url":"https://api.github.com/repos/mifl/android_kernel_qcom_msm/commits/3edc6373939d16ff2b4d54aa12059d004bf62884"},{"sha":"6749fd110bf44164782df9bba86c0327474446b9","author":{"email":"73675debcd8a436be48ec22211dcf44fe0df0a64@decadent.org.uk","name":"Ben Hutchings"},"message":"x86: mm/fault: Fix semaphore imbalance\n\nWhen backporting commit 33692f27597f ('vm: add VM_FAULT_SIGSEGV\nhandling support') I didn't notice that it depended on a recent change\nto the locking context of mm_fault_error() (commit 7fb08eca4527,\n'x86: mm: move mmap_sem unlock from mm_fault_error() to caller').\nThat isn't easily applicable to 3.2, so instead make sure we drop\nmm->mmap_sem on the new branch of mm_fault_error().\n\nSigned-off-by: Ben Hutchings <ben@decadent.org.uk>","distinct":true,"url":"https://api.github.com/repos/mifl/android_kernel_qcom_msm/commits/6749fd110bf44164782df9bba86c0327474446b9"},{"sha":"c5780dc7c2c76e76cfc20d4b5a6bb2a4540fa92d","author":{"email":"118ed6118e893d16e8c6e0776e0ebc290952c897@openwrt.org","name":"Felix Fietkau"},"message":"MIPS: IRQ: Fix disable_irq on CPU IRQs\n\ncommit a3e6c1eff54878506b2dddcc202df9cc8180facb upstream.\n\nIf the irq_chip does not define .irq_disable, any call to disable_irq\nwill defer disabling the IRQ until it fires while marked as disabled.\nThis assumes that the handler function checks for this condition, which\nhandle_percpu_irq does not. In this case, calling disable_irq leads to\nan IRQ storm, if the interrupt fires while disabled.\n\nThis optimization is only useful when disabling the IRQ is slow, which\nis not true for the MIPS CPU IRQ.\n\nDisable this optimization by implementing .irq_disable and .irq_enable\n\nSigned-off-by: Felix Fietkau <nbd@openwrt.org>\nCc: linux-mips@linux-mips.org\nPatchwork: https://patchwork.linux-mips.org/patch/8949/\nSigned-off-by: Ralf Baechle <ralf@linux-mips.org>\nSigned-off-by: Ben Hutchings <ben@decadent.org.uk>","distinct":true,"url":"https://api.github.com/repos/mifl/android_kernel_qcom_msm/commits/c5780dc7c2c76e76cfc20d4b5a6bb2a4540fa92d"},{"sha":"c024ef952a111ac8963bfc4edbec6e7a75fffd61","author":{"email":"b3e6a3251704a94eee1cf08e0adc382e6cb535ee@atmel.com","name":"Bo Shen"},"message":"ASoC: atmel_ssc_dai: fix start event for I2S mode\n\ncommit a43bd7e125143b875caae6d4f9938855b440faaf upstream.\n\nAccording to the I2S specification information as following:\n  - WS = 0, channel 1 (left)\n  - WS = 1, channel 2 (right)\nSo, the start event should be TF/RF falling edge.\n\nReported-by: Songjun Wu <songjun.wu@atmel.com>\nSigned-off-by: Bo Shen <voice.shen@atmel.com>\nSigned-off-by: Mark Brown <broonie@kernel.org>\nSigned-off-by: Ben Hutchings <ben@decadent.org.uk>","distinct":true,"url":"https://api.github.com/repos/mifl/android_kernel_qcom_msm/commits/c024ef952a111ac8963bfc4edbec6e7a75fffd61"},{"sha":"5c8edb8faee3068348fa040c22568f132e3643fa","author":{"email":"4596b3305151c7ee743192a95d394341e3d3b644@suse.de","name":"Takashi Iwai"},"message":"ALSA: ak411x: Fix stall in work callback\n\ncommit 4161b4505f1690358ac0a9ee59845a7887336b21 upstream.\n\nWhen ak4114 work calls its callback and the callback invokes\nak4114_reinit(), it stalls due to flush_delayed_work().  For avoiding\nthis, control the reentrance by introducing a refcount.  Also\nflush_delayed_work() is replaced with cancel_delayed_work_sync().\n\nThe exactly same bug is present in ak4113.c and fixed as well.\n\nReported-by: Pavel Hofman <pavel.hofman@ivitera.com>\nAcked-by: Jaroslav Kysela <perex@perex.cz>\nTested-by: Pavel Hofman <pavel.hofman@ivitera.com>\nSigned-off-by: Takashi Iwai <tiwai@suse.de>\n[bwh: Backported to 3.2: snd_ak411{3,4}_reinit were previously using\n flush_delayed_work_sync() rather than flush_delayed_work()]\nSigned-off-by: Ben Hutchings <ben@decadent.org.uk>","distinct":true,"url":"https://api.github.com/repos/mifl/android_kernel_qcom_msm/commits/5c8edb8faee3068348fa040c22568f132e3643fa"},{"sha":"c544b4bf9ad9f10d48ac0bd720a4c0124a9c6d41","author":{"email":"5c8455eb353959a2a7e266fcc4f76fb65342dc20@gmail.com","name":"karl beldan"},"message":"lib/checksum.c: fix carry in csum_tcpudp_nofold\n\ncommit 150ae0e94634714b23919f0c333fee28a5b199d5 upstream.\n\nThe carry from the 64->32bits folding was dropped, e.g with:\nsaddr=0xFFFFFFFF daddr=0xFF0000FF len=0xFFFF proto=0 sum=1,\ncsum_tcpudp_nofold returned 0 instead of 1.\n\nSigned-off-by: Karl Beldan <karl.beldan@rivierawaves.com>\nCc: Al Viro <viro@ZenIV.linux.org.uk>\nCc: Eric Dumazet <eric.dumazet@gmail.com>\nCc: Arnd Bergmann <arnd@arndb.de>\nCc: Mike Frysinger <vapier@gentoo.org>\nCc: netdev@vger.kernel.org\nCc: linux-kernel@vger.kernel.org\nSigned-off-by: Eric Dumazet <edumazet@google.com>\nSigned-off-by: David S. Miller <davem@davemloft.net>\nSigned-off-by: Ben Hutchings <ben@decadent.org.uk>","distinct":true,"url":"https://api.github.com/repos/mifl/android_kernel_qcom_msm/commits/c544b4bf9ad9f10d48ac0bd720a4c0124a9c6d41"},{"sha":"818fbf0b9ed36ab58405662d137ab27c5c82140b","author":{"email":"5c8455eb353959a2a7e266fcc4f76fb65342dc20@gmail.com","name":"karl beldan"},"message":"lib/checksum.c: fix build for generic csum_tcpudp_nofold\n\ncommit 9ce357795ef208faa0d59894d9d119a7434e37f3 upstream.\n\nFixed commit added from64to32 under _#ifndef do_csum_ but used it\nunder _#ifndef csum_tcpudp_nofold_, breaking some builds (Fengguang's\nrobot reported TILEGX's). Move from64to32 under the latter.\n\nFixes: 150ae0e94634 (\"lib/checksum.c: fix carry in csum_tcpudp_nofold\")\nReported-by: kbuild test robot <fengguang.wu@intel.com>\nSigned-off-by: Karl Beldan <karl.beldan@rivierawaves.com>\nCc: Eric Dumazet <edumazet@google.com>\nCc: David S. Miller <davem@davemloft.net>\nSigned-off-by: David S. Miller <davem@davemloft.net>\nSigned-off-by: Ben Hutchings <ben@decadent.org.uk>","distinct":true,"url":"https://api.github.com/repos/mifl/android_kernel_qcom_msm/commits/818fbf0b9ed36ab58405662d137ab27c5c82140b"},{"sha":"eac943e2197b01ae12dd1bbbcf1b7dfb5801f868","author":{"email":"7864bb1e0e12322ea18ea731d051b95b75140567@6wind.com","name":"Nicolas Dichtel"},"message":"caif: remove wrong dev_net_set() call\n\ncommit 8997c27ec41127bf57421cc0205413d525421ddc upstream.\n\nsrc_net points to the netns where the netlink message has been received. This\nnetns may be different from the netns where the interface is created (because\nthe user may add IFLA_NET_NS_[PID|FD]). In this case, src_net is the link netns.\n\nIt seems wrong to override the netns in the newlink() handler because if it\nwas not already src_net, it means that the user explicitly asks to create the\nnetdevice in another netns.\n\nCC: Sjur Brændeland <sjur.brandeland@stericsson.com>\nCC: Dmitry Tarnyagin <dmitry.tarnyagin@lockless.no>\nFixes: 8391c4aab1aa (\"caif: Bugfixes in CAIF netdevice for close and flow control\")\nFixes: c41254006377 (\"caif-hsi: Add rtnl support\")\nSigned-off-by: Nicolas Dichtel <nicolas.dichtel@6wind.com>\nSigned-off-by: David S. Miller <davem@davemloft.net>\n[bwh: Backported to 3.2: drop the change to caif_hsi change]\nSigned-off-by: Ben Hutchings <ben@decadent.org.uk>","distinct":true,"url":"https://api.github.com/repos/mifl/android_kernel_qcom_msm/commits/eac943e2197b01ae12dd1bbbcf1b7dfb5801f868"},{"sha":"7829c20e43e9f915231e8b7c97aaa1acc9133126","author":{"email":"7da9702eed642c2e82fcf6b2f4145d9c11c095ec@iki.fi","name":"Hemmo Nieminen"},"message":"MIPS: Fix kernel lockup or crash after CPU offline/online\n\ncommit c7754e75100ed5e3068ac5085747f2bfc386c8d6 upstream.\n\nAs printk() invocation can cause e.g. a TLB miss, printk() cannot be\ncalled before the exception handlers have been properly initialized.\nThis can happen e.g. when netconsole has been loaded as a kernel module\nand the TLB table has been cleared when a CPU was offline.\n\nCall cpu_report() in start_secondary() only after the exception handlers\nhave been initialized to fix this.\n\nWithout the patch the kernel will randomly either lockup or crash\nafter a CPU is onlined and the console driver is a module.\n\nSigned-off-by: Hemmo Nieminen <hemmo.nieminen@iki.fi>\nSigned-off-by: Aaro Koskinen <aaro.koskinen@iki.fi>\nCc: David Daney <david.daney@cavium.com>\nCc: linux-mips@linux-mips.org\nCc: linux-kernel@vger.kernel.org\nPatchwork: https://patchwork.linux-mips.org/patch/8953/\nSigned-off-by: Ralf Baechle <ralf@linux-mips.org>\n[bwh: Backported to 3.2: adjust context]\nSigned-off-by: Ben Hutchings <ben@decadent.org.uk>","distinct":true,"url":"https://api.github.com/repos/mifl/android_kernel_qcom_msm/commits/7829c20e43e9f915231e8b7c97aaa1acc9133126"},{"sha":"67cb64715f1edfa5e05812bf70913c18d065421c","author":{"email":"759412786bc533369b22377bf83fb9056c5b25b2@kernel.org","name":"Johan Hovold"},"message":"gpio: sysfs: fix memory leak in gpiod_export_link\n\ncommit 0f303db08df0df9bd0966443ad6001e63960af16 upstream.\n\nFix memory leak in the gpio sysfs interface due to failure to drop\nreference to device returned by class_find_device when creating a link.\n\nFixes: a4177ee7f1a8 (\"gpiolib: allow exported GPIO nodes to be named\nusing sysfs links\")\nSigned-off-by: Johan Hovold <johan@kernel.org>\nSigned-off-by: Linus Walleij <linus.walleij@linaro.org>\n[bwh: Backported to 3.2: adjust filename]\nSigned-off-by: Ben Hutchings <ben@decadent.org.uk>","distinct":true,"url":"https://api.github.com/repos/mifl/android_kernel_qcom_msm/commits/67cb64715f1edfa5e05812bf70913c18d065421c"},{"sha":"4a5233cccf2599f8ae122ae6327cb2a2dce8c429","author":{"email":"759412786bc533369b22377bf83fb9056c5b25b2@kernel.org","name":"Johan Hovold"},"message":"gpio: sysfs: fix memory leak in gpiod_sysfs_set_active_low\n\ncommit 49d2ca84e433dab854c7a866bc6add09cfab682d upstream.\n\nFix memory leak in the gpio sysfs interface due to failure to drop\nreference to device returned by class_find_device when setting the\ngpio-line polarity.\n\nFixes: 0769746183ca (\"gpiolib: add support for changing value polarity\nin sysfs\")\nSigned-off-by: Johan Hovold <johan@kernel.org>\nSigned-off-by: Linus Walleij <linus.walleij@linaro.org>\n[bwh: Backported to 3.2: adjust filename]\nSigned-off-by: Ben Hutchings <ben@decadent.org.uk>","distinct":true,"url":"https://api.github.com/repos/mifl/android_kernel_qcom_msm/commits/4a5233cccf2599f8ae122ae6327cb2a2dce8c429"},{"sha":"f093464e854a6d3515b7d3fee968e4cf64c14fd1","author":{"email":"849b7ce4f31c4b266d748dab7a8ca8f901d6a555@telus.com","name":"Saran Maruti Ramanara"},"message":"net: sctp: fix passing wrong parameter header to param_type2af in sctp_process_param\n\ncommit cfbf654efc6d78dc9812e030673b86f235bf677d upstream.\n\nWhen making use of RFC5061, section 4.2.4. for setting the primary IP\naddress, we're passing a wrong parameter header to param_type2af(),\nresulting always in NULL being returned.\n\nAt this point, param.p points to a sctp_addip_param struct, containing\na sctp_paramhdr (type = 0xc004, length = var), and crr_id as a correlation\nid. Followed by that, as also presented in RFC5061 section 4.2.4., comes\nthe actual sctp_addr_param, which also contains a sctp_paramhdr, but\nthis time with the correct type SCTP_PARAM_IPV{4,6}_ADDRESS that\nparam_type2af() can make use of. Since we already hold a pointer to\naddr_param from previous line, just reuse it for param_type2af().\n\nFixes: d6de3097592b (\"[SCTP]: Add the handling of \"Set Primary IP Address\" parameter to INIT\")\nSigned-off-by: Saran Maruti Ramanara <saran.neti@telus.com>\nSigned-off-by: Daniel Borkmann <dborkman@redhat.com>\nAcked-by: Vlad Yasevich <vyasevich@gmail.com>\nAcked-by: Neil Horman <nhorman@tuxdriver.com>\nSigned-off-by: David S. Miller <davem@davemloft.net>\nSigned-off-by: Ben Hutchings <ben@decadent.org.uk>","distinct":true,"url":"https://api.github.com/repos/mifl/android_kernel_qcom_msm/commits/f093464e854a6d3515b7d3fee968e4cf64c14fd1"},{"sha":"e2ce502043f0035eed7e3243d274012f43b94c9a","author":{"email":"a62d066fcbab732c2ebe9cb02e2d29694a514faf@codeaurora.org","name":"Shiraz Hashim"},"message":"mm: pagewalk: call pte_hole() for VM_PFNMAP during walk_page_range\n\ncommit 23aaed6659df9adfabe9c583e67a36b54e21df46 upstream.\n\nwalk_page_range() silently skips vma having VM_PFNMAP set, which leads\nto undesirable behaviour at client end (who called walk_page_range).\nUserspace applications get the wrong data, so the effect is like just\nconfusing users (if the applications just display the data) or sometimes\nkilling the processes (if the applications do something with\nmisunderstanding virtual addresses due to the wrong data.)\n\nFor example for pagemap_read, when no callbacks are called against\nVM_PFNMAP vma, pagemap_read may prepare pagemap data for next virtual\naddress range at wrong index.\n\nEventually userspace may get wrong pagemap data for a task.\nCorresponding to a VM_PFNMAP marked vma region, kernel may report\nmappings from subsequent vma regions.  User space in turn may account\nmore pages (than really are) to the task.\n\nIn my case I was using procmem, procrack (Android utility) which uses\npagemap interface to account RSS pages of a task.  Due to this bug it\nwas giving a wrong picture for vmas (with VM_PFNMAP set).\n\nFixes: a9ff785e4437 (\"mm/pagewalk.c: walk_page_range should avoid VM_PFNMAP areas\")\nSigned-off-by: Shiraz Hashim <shashim@codeaurora.org>\nAcked-by: Naoya Horiguchi <n-horiguchi@ah.jp.nec.com>\nSigned-off-by: Andrew Morton <akpm@linux-foundation.org>\nSigned-off-by: Linus Torvalds <torvalds@linux-foundation.org>\nSigned-off-by: Ben Hutchings <ben@decadent.org.uk>","distinct":true,"url":"https://api.github.com/repos/mifl/android_kernel_qcom_msm/commits/e2ce502043f0035eed7e3243d274012f43b94c9a"},{"sha":"c23f3a9fa7826af0465b9408b186f6b555991890","author":{"email":"f414f2bdd839fdc054376382fa67e9bc2fbf206f@lab.ntt.co.jp","name":"Ryusuke Konishi"},"message":"nilfs2: fix deadlock of segment constructor over I_SYNC flag\n\ncommit 7ef3ff2fea8bf5e4a21cef47ad87710a3d0fdb52 upstream.\n\nNilfs2 eventually hangs in a stress test with fsstress program.  This\nissue was caused by the following deadlock over I_SYNC flag between\nnilfs_segctor_thread() and writeback_sb_inodes():\n\n  nilfs_segctor_thread()\n    nilfs_segctor_thread_construct()\n      nilfs_segctor_unlock()\n        nilfs_dispose_list()\n          iput()\n            iput_final()\n              evict()\n                inode_wait_for_writeback()  * wait for I_SYNC flag\n\n  writeback_sb_inodes()\n     * set I_SYNC flag on inode->i_state\n    __writeback_single_inode()\n      do_writepages()\n        nilfs_writepages()\n          nilfs_construct_dsync_segment()\n            nilfs_segctor_sync()\n               * wait for completion of segment constructor\n    inode_sync_complete()\n       * clear I_SYNC flag after __writeback_single_inode() completed\n\nwriteback_sb_inodes() calls do_writepages() for dirty inodes after\nsetting I_SYNC flag on inode->i_state.  do_writepages() in turn calls\nnilfs_writepages(), which can run segment constructor and wait for its\ncompletion.  On the other hand, segment constructor calls iput(), which\ncan call evict() and wait for the I_SYNC flag on\ninode_wait_for_writeback().\n\nSince segment constructor doesn't know when I_SYNC will be set, it\ncannot know whether iput() will block or not unless inode->i_nlink has a\nnon-zero count.  We can prevent evict() from being called in iput() by\nimplementing sop->drop_inode(), but it's not preferable to leave inodes\nwith i_nlink == 0 for long periods because it even defers file\ntruncation and inode deallocation.  So, this instead resolves the\ndeadlock by calling iput() asynchronously with a workqueue for inodes\nwith i_nlink == 0.\n\nSigned-off-by: Ryusuke Konishi <konishi.ryusuke@lab.ntt.co.jp>\nCc: Al Viro <viro@zeniv.linux.org.uk>\nTested-by: Ryusuke Konishi <konishi.ryusuke@lab.ntt.co.jp>\nSigned-off-by: Andrew Morton <akpm@linux-foundation.org>\nSigned-off-by: Linus Torvalds <torvalds@linux-foundation.org>\nSigned-off-by: Ben Hutchings <ben@decadent.org.uk>","distinct":true,"url":"https://api.github.com/repos/mifl/android_kernel_qcom_msm/commits/c23f3a9fa7826af0465b9408b186f6b555991890"},{"sha":"01c4de7a34c024d06309b5607c0374ae9855d0d3","author":{"email":"4c90c9e8139d6b2f3cb8a873465ba96eecf7efe8@bluecatnetworks.com","name":"Fernando Soto"},"message":"Drivers: hv: vmbus: incorrect device name is printed when child device is unregistered\n\ncommit 84672369ffb98a51d4ddf74c20a23636da3ad615 upstream.\n\nWhenever a device is unregistered in vmbus_device_unregister (drivers/hv/vmbus_drv.c), the device name in the log message may contain garbage as the memory has already been freed by the time pr_info is called. Log example:\n [ 3149.170475] hv_vmbus: child device àõsèè0_5 unregistered\n\nBy logging the message just before calling device_unregister, the correct device name is printed:\n[ 3145.034652] hv_vmbus: child device vmbus_0_5 unregistered\n\nAlso changing register & unregister messages to debug to avoid unnecessarily cluttering the kernel log.\n\nSigned-off-by: Fernando M Soto <fsoto@bluecatnetworks.com>\nSigned-off-by: K. Y. Srinivasan <kys@microsoft.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>\nSigned-off-by: Ben Hutchings <ben@decadent.org.uk>","distinct":true,"url":"https://api.github.com/repos/mifl/android_kernel_qcom_msm/commits/01c4de7a34c024d06309b5607c0374ae9855d0d3"},{"sha":"1c41da27b53bca2b97b24653b55dd690e3bfd8bc","author":{"email":"9e6ba6483b6a3e14d61f7c987e72ecb5b46122d6@mev.co.uk","name":"Ian Abbott"},"message":"staging: comedi: cb_pcidas64: fix incorrect AI range code handling\n\ncommit be8e89087ec2d2c8a1ad1e3db64bf4efdfc3c298 upstream.\n\nThe hardware range code values and list of valid ranges for the AI\nsubdevice is incorrect for several supported boards.  The hardware range\ncode values for all boards except PCI-DAS4020/12 is determined by\ncalling `ai_range_bits_6xxx()` based on the maximum voltage of the range\nand whether it is bipolar or unipolar, however it only returns the\ncorrect hardware range code for the PCI-DAS60xx boards.  For\nPCI-DAS6402/16 (and /12) it returns the wrong code for the unipolar\nranges.  For PCI-DAS64/Mx/16 it returns the wrong code for all the\nranges and the comedi range table is incorrect.\n\nChange `ai_range_bits_6xxx()` to use a look-up table pointed to by new\nmember `ai_range_codes` of `struct pcidas64_board` to map the comedi\nrange table indices to the hardware range codes.  Use a new comedi range\ntable for the PCI-DAS64/Mx/16 boards (and the commented out variants).\n\nSigned-off-by: Ian Abbott <abbotti@mev.co.uk>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>\nSigned-off-by: Ben Hutchings <ben@decadent.org.uk>","distinct":true,"url":"https://api.github.com/repos/mifl/android_kernel_qcom_msm/commits/1c41da27b53bca2b97b24653b55dd690e3bfd8bc"},{"sha":"c0a74eb2b093cd781f216306cc5a1e5825835d74","author":{"email":"b79c083a3c07cc7a5a7055ad6af8240be896cb86@gmail.com","name":"Austin Lund"},"message":"media/rc: Send sync space information on the lirc device\n\ncommit a8f29e89f2b54fbf2c52be341f149bc195b63a8b upstream.\n\nUserspace expects to see a long space before the first pulse is sent on\nthe lirc device.  Currently, if a long time has passed and a new packet\nis started, the lirc codec just returns and doesn't send anything.  This\nmakes lircd ignore many perfectly valid signals unless they are sent in\nquick sucession.  When a reset event is delivered, we cannot know\nanything about the duration of the space.  But it should be safe to\nassume it has been a long time and we just set the duration to maximum.\n\nSigned-off-by: Austin Lund <austin.lund@gmail.com>\nSigned-off-by: Mauro Carvalho Chehab <mchehab@osg.samsung.com>\nSigned-off-by: Ben Hutchings <ben@decadent.org.uk>","distinct":true,"url":"https://api.github.com/repos/mifl/android_kernel_qcom_msm/commits/c0a74eb2b093cd781f216306cc5a1e5825835d74"},{"sha":"985504f71bb0ca24ac647c72446cc621980aef9f","author":{"email":"695db642e8bc2a781029b5690bc796db9446cc2f@linux.intel.com","name":"Tim Chen"},"message":"sched/rt: Reduce rq lock contention by eliminating locking of non-feasible target\n\ncommit 80e3d87b2c5582db0ab5e39610ce3707d97ba409 upstream.\n\nThis patch adds checks that prevens futile attempts to move rt tasks\nto a CPU with active tasks of equal or higher priority.\n\nThis reduces run queue lock contention and improves the performance of\na well known OLTP benchmark by 0.7%.\n\nSigned-off-by: Tim Chen <tim.c.chen@linux.intel.com>\nSigned-off-by: Peter Zijlstra (Intel) <peterz@infradead.org>\nCc: Shawn Bohrer <sbohrer@rgmadvisors.com>\nCc: Suruchi Kadu <suruchi.a.kadu@intel.com>\nCc: Doug Nelson<doug.nelson@intel.com>\nCc: Steven Rostedt <rostedt@goodmis.org>\nCc: Linus Torvalds <torvalds@linux-foundation.org>\nLink: http://lkml.kernel.org/r/1421430374.2399.27.camel@schen9-desk2.jf.intel.com\nSigned-off-by: Ingo Molnar <mingo@kernel.org>\n[bwh: Backported to 3.2: adjust filename]\nSigned-off-by: Ben Hutchings <ben@decadent.org.uk>","distinct":true,"url":"https://api.github.com/repos/mifl/android_kernel_qcom_msm/commits/985504f71bb0ca24ac647c72446cc621980aef9f"},{"sha":"f20f9084ff23d722a80511a2ce7dc2ea50eb79ad","author":{"email":"e642b69ed2fc111e09ffdc37feb733a52253340d@oracle.com","name":"Sasha Levin"},"message":"time: adjtimex: Validate the ADJ_FREQUENCY values\n\ncommit 5e5aeb4367b450a28f447f6d5ab57d8f2ab16a5f upstream.\n\nVerify that the frequency value from userspace is valid and makes sense.\n\nUnverified values can cause overflows later on.\n\nCc: Thomas Gleixner <tglx@linutronix.de>\nCc: Ingo Molnar <mingo@kernel.org>\nSigned-off-by: Sasha Levin <sasha.levin@oracle.com>\n[jstultz: Fix up bug for negative values and drop redunent cap check]\nSigned-off-by: John Stultz <john.stultz@linaro.org>\n[bwh: Backported to 3.2: adjust context]\nSigned-off-by: Ben Hutchings <ben@decadent.org.uk>","distinct":true,"url":"https://api.github.com/repos/mifl/android_kernel_qcom_msm/commits/f20f9084ff23d722a80511a2ce7dc2ea50eb79ad"},{"sha":"b2fcc089bcb64b2f1667eb3046cb72f9529ec2bc","author":{"email":"33837adfb53316eae44aad04041e1240088d76fd@linaro.org","name":"John Stultz"},"message":"ntp: Fixup adjtimex freq validation on 32-bit systems\n\ncommit 29183a70b0b828500816bd794b3fe192fce89f73 upstream.\n\nAdditional validation of adjtimex freq values to avoid\npotential multiplication overflows were added in commit\n5e5aeb4367b (time: adjtimex: Validate the ADJ_FREQUENCY values)\n\nUnfortunately the patch used LONG_MAX/MIN instead of\nLLONG_MAX/MIN, which was fine on 64-bit systems, but being\nmuch smaller on 32-bit systems caused false positives\nresulting in most direct frequency adjustments to fail w/\nEINVAL.\n\nntpd only does direct frequency adjustments at startup, so\nthe issue was not as easily observed there, but other time\nsync applications like ptpd and chrony were more effected by\nthe bug.\n\nSee bugs:\n\n  https://bugzilla.kernel.org/show_bug.cgi?id=92481\n  https://bugzilla.redhat.com/show_bug.cgi?id=1188074\n\nThis patch changes the checks to use LLONG_MAX for\nclarity, and additionally the checks are disabled\non 32-bit systems since LLONG_MAX/PPM_SCALE is always\nlarger then the 32-bit long freq value, so multiplication\noverflows aren't possible there.\n\nReported-by: Josh Boyer <jwboyer@fedoraproject.org>\nReported-by: George Joseph <george.joseph@fairview5.com>\nTested-by: George Joseph <george.joseph@fairview5.com>\nSigned-off-by: John Stultz <john.stultz@linaro.org>\nSigned-off-by: Peter Zijlstra (Intel) <peterz@infradead.org>\nCc: Linus Torvalds <torvalds@linux-foundation.org>\nCc: Sasha Levin <sasha.levin@oracle.com>\nLink: http://lkml.kernel.org/r/1423553436-29747-1-git-send-email-john.stultz@linaro.org\n[ Prettified the changelog and the comments a bit. ]\nSigned-off-by: Ingo Molnar <mingo@kernel.org>\nSigned-off-by: Ben Hutchings <ben@decadent.org.uk>","distinct":true,"url":"https://api.github.com/repos/mifl/android_kernel_qcom_msm/commits/b2fcc089bcb64b2f1667eb3046cb72f9529ec2bc"}]}