{"push_id":581604047,"size":1000,"distinct_size":1469,"ref":"refs/heads/linux-upstream","head":"7cd2a187ab6dc6654282d2760c8bed83fb75ef9d","before":"72dfced5523fb843f835a8db02d15fd9f15a5fb1","commits":[{"sha":"7dad9fc0419ff8c3b342d6b0320308e3be6a0e53","author":{"email":"547fa85bb3888a0222eed8ec39e36708605c6d53@imgtec.com","name":"James Hogan"},"message":"serial: 8250_dw: Fix LCR workaround regression\n\ncommit 6979f8d28049879e6147767d93ba6732c8bd94f4 upstream.\n\nCommit c49436b657d0 (serial: 8250_dw: Improve unwritable LCR workaround)\ncaused a regression. It added a check that the LCR was written properly\nto detect and workaround the busy quirk, but the behaviour of bit 5\n(UART_LCR_SPAR) differs between IP versions 3.00a and 3.14c per the\ndocs. On older versions this caused the check to fail and it would\nrepeatedly force idle and rewrite the LCR register, causing delays and\npreventing any input from serial being received.\n\nThis is fixed by masking out UART_LCR_SPAR before making the comparison.\n\nSigned-off-by: James Hogan <james.hogan@imgtec.com>\nCc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>\nCc: Jiri Slaby <jslaby@suse.cz>\nCc: Tim Kryger <tim.kryger@linaro.org>\nCc: Ezequiel Garcia <ezequiel.garcia@free-electrons.com>\nCc: Matt Porter <matt.porter@linaro.org>\nCc: Markus Mayer <markus.mayer@linaro.org>\nTested-by: Tim Kryger <tim.kryger@linaro.org>\nTested-by: Ezequiel Garcia <ezequiel.garcia@free-electrons.com>\nTested-by: Heikki Krogerus <heikki.krogerus@linux.intel.com>\nCc: Wang Nan <wangnan0@huawei.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/MikeC84/android_kernel_moto_shamu/commits/7dad9fc0419ff8c3b342d6b0320308e3be6a0e53"},{"sha":"879a09a4537a674193dd3e199f655106f6423b9e","author":{"email":"c65a040f7f664378353fb65fc3553df208a14f68@canonical.com","name":"Tim Gardner"},"message":"ALSA: usb-audio: Suppress repetitive debug messages from retire_playback_urb()\n\ncommit a5065eb6da55b226661456e6a7435f605df98111 upstream.\n\nBugLink: http://bugs.launchpad.net/bugs/1305133\n\nMalfunctioning or slow devices can cause a flood of dmesg SPAM.\n\nI've ignored checkpatch.pl complaints about the use of printk_ratelimit() in favour\nof prior art in sound/usb/pcm.c.\n\nWARNING: Prefer printk_ratelimited or pr_<level>_ratelimited to printk_ratelimit\n+\tif (printk_ratelimit() &&\n\nCc: Jaroslav Kysela <perex@perex.cz>\nCc: Takashi Iwai <tiwai@suse.de>\nCc: Eldad Zack <eldad@fogrefinery.com>\nCc: Daniel Mack <zonque@gmail.com>\nCc: Clemens Ladisch <clemens@ladisch.de>\nSigned-off-by: Tim Gardner <tim.gardner@canonical.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/MikeC84/android_kernel_moto_shamu/commits/879a09a4537a674193dd3e199f655106f6423b9e"},{"sha":"3115820f094ef5364ae222f65646b38739967983","author":{"email":"ba324ca7b1c77fc20bb970d5aff6eea9377918a5@eikelenboom.it","name":"Sander Eikelenboom"},"message":"ALSA: usb-audio: Prevent printk ratelimiting from spamming kernel log while DEBUG not defined\n\ncommit b7a7723513dc89f83d6df13206df55d4dc26e825 upstream.\n\nThis (widely used) construction:\n\nif(printk_ratelimit())\n\tdev_dbg()\n\nCauses the ratelimiting to spam the kernel log with the \"callbacks suppressed\"\nmessage below, even while the dev_dbg it is supposed to rate limit wouldn't\nprint anything because DEBUG is not defined for this device.\n\n[  533.803964] retire_playback_urb: 852 callbacks suppressed\n[  538.807930] retire_playback_urb: 852 callbacks suppressed\n[  543.811897] retire_playback_urb: 852 callbacks suppressed\n[  548.815745] retire_playback_urb: 852 callbacks suppressed\n[  553.819826] retire_playback_urb: 852 callbacks suppressed\n\nSo use dev_dbg_ratelimited() instead of this construction.\n\nSigned-off-by: Sander Eikelenboom <linux@eikelenboom.it>\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/MikeC84/android_kernel_moto_shamu/commits/3115820f094ef5364ae222f65646b38739967983"},{"sha":"a9b6a5142c02b23818a4f5f4288f4f1d5491cae2","author":{"email":"080e0242401949f8c1dfb399e414be816846daae@gmail.com","name":"Chen Gang"},"message":"arch/unicore32/mm/alignment.c: include \"asm/pgtable.h\" to avoid compiling error\n\ncommit 1ff38c56cbd095c4c0dfa581a859ba3557830f78 upstream.\n\nNeed include \"asm/pgtable.h\" to include \"asm-generic/pgtable-nopmd.h\",\nso can let 'pmd_t' defined. The related error with allmodconfig:\n\n    CC      arch/unicore32/mm/alignment.o\n  In file included from arch/unicore32/mm/alignment.c:24:\n  arch/unicore32/include/asm/tlbflush.h:135: error: expected .). before .*. token\n  arch/unicore32/include/asm/tlbflush.h:154: error: expected .). before .*. token\n  In file included from arch/unicore32/mm/alignment.c:27:\n  arch/unicore32/mm/mm.h:15: error: expected .=., .,., .;., .sm. or ._attribute__. before .*. token\n  arch/unicore32/mm/mm.h:20: error: expected .=., .,., .;., .sm. or ._attribute__. before .*. token\n  arch/unicore32/mm/mm.h:25: error: expected .=., .,., .;., .sm. or ._attribute__. before .*. token\n  make[1]: *** [arch/unicore32/mm/alignment.o] Error 1\n  make: *** [arch/unicore32/mm] Error 2\n\nSigned-off-by: Chen Gang <gang.chen.5i5j@gmail.com>\nAcked-by: Xuetao Guan <gxt@mprc.pku.edu.cn>\nSigned-off-by: Xuetao Guan <gxt@mprc.pku.edu.cn>\nCc: Guenter Roeck <linux@roeck-us.net>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/MikeC84/android_kernel_moto_shamu/commits/a9b6a5142c02b23818a4f5f4288f4f1d5491cae2"},{"sha":"9233c1f2617329490b75c82b3110e5e5701e29d2","author":{"email":"cdbc88d3efc3f4d4e5e999ca6451151f17e7ed4d@gmail.com","name":"Zhichuang SUN"},"message":"drivers/video/fbdev/fb-puv3.c: Add header files for function unifb_mmap\n\ncommit fbc6c4a13bbfb420eedfdb26a0a859f9c07e8a7b upstream.\n\nFunction unifb_mmap calls functions which are defined in linux/mm.h\nand asm/pgtable.h\n\nThe related error (for unicore32 with unicore32_defconfig):\n\tCC      drivers/video/fbdev/fb-puv3.o\n\tdrivers/video/fbdev/fb-puv3.c: In function 'unifb_mmap':\n\tdrivers/video/fbdev/fb-puv3.c:646: error: implicit declaration of\n\t\t\t\t      function 'vm_iomap_memory'\n\tdrivers/video/fbdev/fb-puv3.c:646: error: implicit declaration of\n\t\t\t\t      function 'pgprot_noncached'\n\nSigned-off-by: Zhichuang Sun <sunzc522@gmail.com>\nCc: Jean-Christophe Plagniol-Villard <plagnioj@jcrosoft.com>\nCc: Tomi Valkeinen <tomi.valkeinen@ti.com>\nCc: Jingoo Han <jg1.han@samsung.com>\nCc: Daniel Vetter <daniel.vetter@ffwll.ch>\nCc: Joe Perches <joe@perches.com>\nCc: Laurent Pinchart <laurent.pinchart@ideasonboard.com>\nCc: linux-fbdev@vger.kernel.org\nAcked-by: Xuetao Guan <gxt@mprc.pku.edu.cn>\nSigned-off-by: Tomi Valkeinen <tomi.valkeinen@ti.com>\nCc: Guenter Roeck <linux@roeck-us.net>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/MikeC84/android_kernel_moto_shamu/commits/9233c1f2617329490b75c82b3110e5e5701e29d2"},{"sha":"cf1d3a4312b2b3999a841daae729652176906c14","author":{"email":"52f8f9962b7f38d8269c63c0859d68147c8d10f0@redhat.com","name":"Mikulas Patocka"},"message":"sym53c8xx_2: Set DID_REQUEUE return code when aborting squeue\n\ncommit fd1232b214af43a973443aec6a2808f16ee5bf70 upstream.\n\nThis patch fixes I/O errors with the sym53c8xx_2 driver when the disk\nreturns QUEUE FULL status.\n\nWhen the controller encounters an error (including QUEUE FULL or BUSY\nstatus), it aborts all not yet submitted requests in the function\nsym_dequeue_from_squeue.\n\nThis function aborts them with DID_SOFT_ERROR.\n\nIf the disk has full tag queue, the request that caused the overflow is\naborted with QUEUE FULL status (and the scsi midlayer properly retries\nit until it is accepted by the disk), but the sym53c8xx_2 driver aborts\nthe following requests with DID_SOFT_ERROR --- for them, the midlayer\ndoes just a few retries and then signals the error up to sd.\n\nThe result is that disk returning QUEUE FULL causes request failures.\n\nThe error was reproduced on 53c895 with COMPAQ BD03685A24 disk\n(rebranded ST336607LC) with command queue 48 or 64 tags.  The disk has\n64 tags, but under some access patterns it return QUEUE FULL when there\nare less than 64 pending tags.  The SCSI specification allows returning\nQUEUE FULL anytime and it is up to the host to retry.\n\nSigned-off-by: Mikulas Patocka <mpatocka@redhat.com>\nCc: Matthew Wilcox <matthew@wil.cx>\nCc: James Bottomley <JBottomley@Parallels.com>\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/MikeC84/android_kernel_moto_shamu/commits/cf1d3a4312b2b3999a841daae729652176906c14"},{"sha":"2ab96644e56bd57c249ac58e36c5a9171a16ce1c","author":{"email":"8e7a128cd0264d3269a891fb3e87507c2985f8af@ah.jp.nec.com","name":"Naoya Horiguchi"},"message":"hugetlb: fix copy_hugetlb_page_range() to handle migration/hwpoisoned entry\n\ncommit 4a705fef986231a3e7a6b1a6d3c37025f021f49f upstream.\n\nThere's a race between fork() and hugepage migration, as a result we try\nto \"dereference\" a swap entry as a normal pte, causing kernel panic.\nThe cause of the problem is that copy_hugetlb_page_range() can't handle\n\"swap entry\" family (migration entry and hwpoisoned entry) so let's fix\nit.\n\n[akpm@linux-foundation.org: coding-style fixes]\nSigned-off-by: Naoya Horiguchi <n-horiguchi@ah.jp.nec.com>\nAcked-by: Hugh Dickins <hughd@google.com>\nCc: Christoph Lameter <cl@linux.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/MikeC84/android_kernel_moto_shamu/commits/2ab96644e56bd57c249ac58e36c5a9171a16ce1c"},{"sha":"d819c44bfecefea0ac65c161eedeea9cf2db7ce8","author":{"email":"d3abdf3e2800e6cb849f11b81e6eb50b34d96431@google.com","name":"Hugh Dickins"},"message":"mm: fix crashes from mbind() merging vmas\n\ncommit d05f0cdcbe6388723f1900c549b4850360545201 upstream.\n\nIn v2.6.34 commit 9d8cebd4bcd7 (\"mm: fix mbind vma merge problem\")\nintroduced vma merging to mbind(), but it should have also changed the\nconvention of passing start vma from queue_pages_range() (formerly\ncheck_range()) to new_vma_page(): vma merging may have already freed\nthat structure, resulting in BUG at mm/mempolicy.c:1738 and probably\nworse crashes.\n\nFixes: 9d8cebd4bcd7 (\"mm: fix mbind vma merge problem\")\nReported-by: Naoya Horiguchi <n-horiguchi@ah.jp.nec.com>\nTested-by: Naoya Horiguchi <n-horiguchi@ah.jp.nec.com>\nSigned-off-by: Hugh Dickins <hughd@google.com>\nAcked-by: Christoph Lameter <cl@linux.com>\nCc: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>\nCc: Minchan Kim <minchan.kim@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/MikeC84/android_kernel_moto_shamu/commits/d819c44bfecefea0ac65c161eedeea9cf2db7ce8"},{"sha":"3a4191750f5f7f04011aed7f7af6c2069aabb5ee","author":{"email":"4645f7897fd33786a2ee1264d590b3c400559d85@linuxfoundation.org","name":"Greg Kroah-Hartman"},"message":"Linux 3.10.48","distinct":true,"url":"https://api.github.com/repos/MikeC84/android_kernel_moto_shamu/commits/3a4191750f5f7f04011aed7f7af6c2069aabb5ee"},{"sha":"71783b9db938f562c38f7f01963a12c5a873560d","author":{"email":"074b2cdaa8e1d86c6f3b980bb2e4f33bac054903@jolla.com","name":"Bernd Wachter"},"message":"usb: option: Add ID for Telewell TW-LTE 4G v2\n\ncommit 3d28bd840b2d3981cd28caf5fe1df38f1344dd60 upstream.\n\nAdd ID of the Telewell 4G v2 hardware to option driver to get legacy\nserial interface working\n\nSigned-off-by: Bernd Wachter <bernd.wachter@jolla.com>\nSigned-off-by: Johan Hovold <johan@kernel.org>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/MikeC84/android_kernel_moto_shamu/commits/71783b9db938f562c38f7f01963a12c5a873560d"},{"sha":"9d5a2953383634b0c35a712c3a51fe88492bebf3","author":{"email":"08a2fc565a1389a511ab9206b9a1e6b4b433486a@sth.sze.hu","name":"Andras Kovacs"},"message":"USB: cp210x: add support for Corsair usb dongle\n\ncommit b9326057a3d8447f5d2e74a7b521ccf21add2ec0 upstream.\n\nCorsair USB Dongles are shipped with Corsair AXi series PSUs.\nThese are cp210x serial usb devices, so make driver detect these.\nI have a program, that can get information from these PSUs.\n\nTested with 2 different dongles shipped with Corsair AX860i and\nAX1200i units.\n\nSigned-off-by: Andras Kovacs <andras@sth.sze.hu>\nSigned-off-by: Johan Hovold <johan@kernel.org>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/MikeC84/android_kernel_moto_shamu/commits/9d5a2953383634b0c35a712c3a51fe88492bebf3"},{"sha":"e23df0c02b9a2a3f164d11a3477fd016e1363975","author":{"email":"7b964cd933b2cc9106deabd4641111826cfbc094@biot.com","name":"Bert Vermeulen"},"message":"USB: ftdi_sio: Add extra PID.\n\ncommit 5a7fbe7e9ea0b1b9d7ffdba64db1faa3a259164c upstream.\n\nThis patch adds PID 0x0003 to the VID 0x128d (Testo). At least the\nTesto 435-4 uses this, likely other gear as well.\n\nSigned-off-by: Bert Vermeulen <bert@biot.com>\nCc: Johan Hovold <johan@kernel.org>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/MikeC84/android_kernel_moto_shamu/commits/e23df0c02b9a2a3f164d11a3477fd016e1363975"},{"sha":"d50a7c593886f7a0dff827686dbef1d00b2627dc","author":{"email":"aec3f085754bb5d2a19ac140444250fd25fbaed4@fel.cvut.cz","name":"Michal Sojka"},"message":"USB: serial: ftdi_sio: Add Infineon Triboard\n\ncommit d8279a40e50ad55539780aa617a32a53d7f0953e upstream.\n\nThis adds support for Infineon TriBoard TC1798 [1]. Only interface 1\nis used as serial line (see [2], Figure 8-6).\n\n[1] http://www.infineon.com/cms/de/product/microcontroller/development-tools-software-and-kits/tricore-tm-development-tools-software-and-kits/starterkits-and-evaluation-boards/starter-kit-tc1798/channel.html?channel=db3a304333b8a7ca0133cfa3d73e4268\n[2] http://www.infineon.com/dgdl/TriBoardManual-TC1798-V10.pdf?folderId=db3a304412b407950112b409ae7c0343&fileId=db3a304333b8a7ca0133cfae99fe426a\n\nSigned-off-by: Michal Sojka <sojkam1@fel.cvut.cz>\nCc: Johan Hovold <johan@kernel.org>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/MikeC84/android_kernel_moto_shamu/commits/d50a7c593886f7a0dff827686dbef1d00b2627dc"},{"sha":"2a89dd283e6a335b9b0639681f650098769d4a33","author":{"email":"5b1e7895819cf7d6bc77091b09bbfd6d330a4e74@gmx.de","name":"Helge Deller"},"message":"parisc: add serial ports of C8000/1GHz machine to hardware database\n\ncommit eadcc7208a2237016be7bdff4551ba7614da85c8 upstream.\n\nSigned-off-by: Helge Deller <deller@gmx.de>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/MikeC84/android_kernel_moto_shamu/commits/2a89dd283e6a335b9b0639681f650098769d4a33"},{"sha":"9282c4164af40377c80f327213bdc5390e417916","author":{"email":"f76ce1f46e3863a1d2d6b7e849385982e002f716@freebox.fr","name":"Maxime Bizon"},"message":"workqueue: fix dev_set_uevent_suppress() imbalance\n\ncommit bddbceb688c6d0decaabc7884fede319d02f96c8 upstream.\n\nUevents are suppressed during attributes registration, but never\nrestored, so kobject_uevent() does nothing.\n\nSigned-off-by: Maxime Bizon <mbizon@freebox.fr>\nSigned-off-by: Tejun Heo <tj@kernel.org>\nFixes: 226223ab3c4118ddd10688cc2c131135848371ab\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/MikeC84/android_kernel_moto_shamu/commits/9282c4164af40377c80f327213bdc5390e417916"},{"sha":"2f0f4c6816177b0b76ae937c71c11b26df0f9d62","author":{"email":"9eae2d327ddc4c2ff66f290d0aa6288f14fc5928@cn.fujitsu.com","name":"Gu Zheng"},"message":"cpuset,mempolicy: fix sleeping function called from invalid context\n\ncommit 391acf970d21219a2a5446282d3b20eace0c0d7a upstream.\n\nWhen runing with the kernel(3.15-rc7+), the follow bug occurs:\n[ 9969.258987] BUG: sleeping function called from invalid context at kernel/locking/mutex.c:586\n[ 9969.359906] in_atomic(): 1, irqs_disabled(): 0, pid: 160655, name: python\n[ 9969.441175] INFO: lockdep is turned off.\n[ 9969.488184] CPU: 26 PID: 160655 Comm: python Tainted: G       A      3.15.0-rc7+ #85\n[ 9969.581032] Hardware name: FUJITSU-SV PRIMEQUEST 1800E/SB, BIOS PRIMEQUEST 1000 Series BIOS Version 1.39 11/16/2012\n[ 9969.706052]  ffffffff81a20e60 ffff8803e941fbd0 ffffffff8162f523 ffff8803e941fd18\n[ 9969.795323]  ffff8803e941fbe0 ffffffff8109995a ffff8803e941fc58 ffffffff81633e6c\n[ 9969.884710]  ffffffff811ba5dc ffff880405c6b480 ffff88041fdd90a0 0000000000002000\n[ 9969.974071] Call Trace:\n[ 9970.003403]  [<ffffffff8162f523>] dump_stack+0x4d/0x66\n[ 9970.065074]  [<ffffffff8109995a>] __might_sleep+0xfa/0x130\n[ 9970.130743]  [<ffffffff81633e6c>] mutex_lock_nested+0x3c/0x4f0\n[ 9970.200638]  [<ffffffff811ba5dc>] ? kmem_cache_alloc+0x1bc/0x210\n[ 9970.272610]  [<ffffffff81105807>] cpuset_mems_allowed+0x27/0x140\n[ 9970.344584]  [<ffffffff811b1303>] ? __mpol_dup+0x63/0x150\n[ 9970.409282]  [<ffffffff811b1385>] __mpol_dup+0xe5/0x150\n[ 9970.471897]  [<ffffffff811b1303>] ? __mpol_dup+0x63/0x150\n[ 9970.536585]  [<ffffffff81068c86>] ? copy_process.part.23+0x606/0x1d40\n[ 9970.613763]  [<ffffffff810bf28d>] ? trace_hardirqs_on+0xd/0x10\n[ 9970.683660]  [<ffffffff810ddddf>] ? monotonic_to_bootbased+0x2f/0x50\n[ 9970.759795]  [<ffffffff81068cf0>] copy_process.part.23+0x670/0x1d40\n[ 9970.834885]  [<ffffffff8106a598>] do_fork+0xd8/0x380\n[ 9970.894375]  [<ffffffff81110e4c>] ? __audit_syscall_entry+0x9c/0xf0\n[ 9970.969470]  [<ffffffff8106a8c6>] SyS_clone+0x16/0x20\n[ 9971.030011]  [<ffffffff81642009>] stub_clone+0x69/0x90\n[ 9971.091573]  [<ffffffff81641c29>] ? system_call_fastpath+0x16/0x1b\n\nThe cause is that cpuset_mems_allowed() try to take\nmutex_lock(&callback_mutex) under the rcu_read_lock(which was hold in\n__mpol_dup()). And in cpuset_mems_allowed(), the access to cpuset is\nunder rcu_read_lock, so in __mpol_dup, we can reduce the rcu_read_lock\nprotection region to protect the access to cpuset only in\ncurrent_cpuset_is_being_rebound(). So that we can avoid this bug.\n\nThis patch is a temporary solution that just addresses the bug\nmentioned above, can not fix the long-standing issue about cpuset.mems\nrebinding on fork():\n\n\"When the forker's task_struct is duplicated (which includes\n ->mems_allowed) and it races with an update to cpuset_being_rebound\n in update_tasks_nodemask() then the task's mems_allowed doesn't get\n updated. And the child task's mems_allowed can be wrong if the\n cpuset's nodemask changes before the child has been added to the\n cgroup's tasklist.\"\n\nSigned-off-by: Gu Zheng <guz.fnst@cn.fujitsu.com>\nAcked-by: Li Zefan <lizefan@huawei.com>\nSigned-off-by: Tejun Heo <tj@kernel.org>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/MikeC84/android_kernel_moto_shamu/commits/2f0f4c6816177b0b76ae937c71c11b26df0f9d62"},{"sha":"802d799bcefb2cef672a7994d1520887613d458d","author":{"email":"9b26f769475fafc2d25107053b1bdd774d49438a@jp.fujitsu.com","name":"Yasuaki Ishimatsu"},"message":"workqueue: zero cpumask of wq_numa_possible_cpumask on init\n\ncommit 5a6024f1604eef119cf3a6fa413fe0261a81a8f3 upstream.\n\nWhen hot-adding and onlining CPU, kernel panic occurs, showing following\ncall trace.\n\n  BUG: unable to handle kernel paging request at 0000000000001d08\n  IP: [<ffffffff8114acfd>] __alloc_pages_nodemask+0x9d/0xb10\n  PGD 0\n  Oops: 0000 [#1] SMP\n  ...\n  Call Trace:\n   [<ffffffff812b8745>] ? cpumask_next_and+0x35/0x50\n   [<ffffffff810a3283>] ? find_busiest_group+0x113/0x8f0\n   [<ffffffff81193bc9>] ? deactivate_slab+0x349/0x3c0\n   [<ffffffff811926f1>] new_slab+0x91/0x300\n   [<ffffffff815de95a>] __slab_alloc+0x2bb/0x482\n   [<ffffffff8105bc1c>] ? copy_process.part.25+0xfc/0x14c0\n   [<ffffffff810a3c78>] ? load_balance+0x218/0x890\n   [<ffffffff8101a679>] ? sched_clock+0x9/0x10\n   [<ffffffff81105ba9>] ? trace_clock_local+0x9/0x10\n   [<ffffffff81193d1c>] kmem_cache_alloc_node+0x8c/0x200\n   [<ffffffff8105bc1c>] copy_process.part.25+0xfc/0x14c0\n   [<ffffffff81114d0d>] ? trace_buffer_unlock_commit+0x4d/0x60\n   [<ffffffff81085a80>] ? kthread_create_on_node+0x140/0x140\n   [<ffffffff8105d0ec>] do_fork+0xbc/0x360\n   [<ffffffff8105d3b6>] kernel_thread+0x26/0x30\n   [<ffffffff81086652>] kthreadd+0x2c2/0x300\n   [<ffffffff81086390>] ? kthread_create_on_cpu+0x60/0x60\n   [<ffffffff815f20ec>] ret_from_fork+0x7c/0xb0\n   [<ffffffff81086390>] ? kthread_create_on_cpu+0x60/0x60\n\nIn my investigation, I found the root cause is wq_numa_possible_cpumask.\nAll entries of wq_numa_possible_cpumask is allocated by\nalloc_cpumask_var_node(). And these entries are used without initializing.\nSo these entries have wrong value.\n\nWhen hot-adding and onlining CPU, wq_update_unbound_numa() is called.\nwq_update_unbound_numa() calls alloc_unbound_pwq(). And alloc_unbound_pwq()\ncalls get_unbound_pool(). In get_unbound_pool(), worker_pool->node is set\nas follow:\n\n3592         /* if cpumask is contained inside a NUMA node, we belong to that node */\n3593         if (wq_numa_enabled) {\n3594                 for_each_node(node) {\n3595                         if (cpumask_subset(pool->attrs->cpumask,\n3596                                            wq_numa_possible_cpumask[node])) {\n3597                                 pool->node = node;\n3598                                 break;\n3599                         }\n3600                 }\n3601         }\n\nBut wq_numa_possible_cpumask[node] does not have correct cpumask. So, wrong\nnode is selected. As a result, kernel panic occurs.\n\nBy this patch, all entries of wq_numa_possible_cpumask are allocated by\nzalloc_cpumask_var_node to initialize them. And the panic disappeared.\n\nSigned-off-by: Yasuaki Ishimatsu <isimatu.yasuaki@jp.fujitsu.com>\nReviewed-by: Lai Jiangshan <laijs@cn.fujitsu.com>\nSigned-off-by: Tejun Heo <tj@kernel.org>\nFixes: bce903809ab3 (\"workqueue: add wq_numa_tbl_len and wq_numa_possible_cpumask[]\")\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/MikeC84/android_kernel_moto_shamu/commits/802d799bcefb2cef672a7994d1520887613d458d"},{"sha":"e855586a876e60f1b196c57bfe937b6ca0280562","author":{"email":"b6ffd6973e972cb999e8e535ab74da7fee0c035f@ingics.com","name":"Axel Lin"},"message":"hwmon: (amc6821) Fix permissions for temp2_input\n\ncommit df86754b746e9a0ff6f863f690b1c01d408e3cdc upstream.\n\ntemp2_input should not be writable, fix it.\n\nReported-by: Guenter Roeck <linux@roeck-us.net>\nSigned-off-by: Axel Lin <axel.lin@ingics.com>\nSigned-off-by: Guenter Roeck <linux@roeck-us.net>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/MikeC84/android_kernel_moto_shamu/commits/e855586a876e60f1b196c57bfe937b6ca0280562"},{"sha":"687a85e82150967da55edc94bc7c170c75f41052","author":{"email":"ba324ca7b1c77fc20bb970d5aff6eea9377918a5@roeck-us.net","name":"Guenter Roeck"},"message":"hwmon: (adm1031) Fix writes to limit registers\n\ncommit 145e74a4e5022225adb84f4e5d4fff7938475c35 upstream.\n\nUpper limit for write operations to temperature limit registers\nwas clamped to a fractional value. However, limit registers do\nnot support fractional values. As a result, upper limits of 127.5\ndegrees C or higher resulted in a rounded limit of 128 degrees C.\nSince limit registers are signed, this was stored as -128 degrees C.\nClamp limits to (-55, +127) degrees C to solve the problem.\n\nValue on writes to auto_temp[12]_min and auto_temp[12]_max were not\nclamped at all, but masked. As a result, out-of-range writes resulted\nin a more or less arbitrary limit. Clamp those attributes to (0, 127)\ndegrees C for more predictable results.\n\nCc: Axel Lin <axel.lin@ingics.com>\nReviewed-by: Jean Delvare <jdelvare@suse.de>\nSigned-off-by: Guenter Roeck <linux@roeck-us.net>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/MikeC84/android_kernel_moto_shamu/commits/687a85e82150967da55edc94bc7c170c75f41052"},{"sha":"b36db304bfa9c4ec5b89ab5e74e47a928f335f93","author":{"email":"b6ffd6973e972cb999e8e535ab74da7fee0c035f@ingics.com","name":"Axel Lin"},"message":"hwmon: (adm1029) Ensure the fan_div cache is updated in set_fan_div\n\ncommit 1035a9e3e9c76b64a860a774f5b867d28d34acc2 upstream.\n\nWriting to fanX_div does not clear the cache. As a result, reading\nfrom fanX_div may return the old value for up to two seconds\nafter writing a new value.\n\nThis patch ensures the fan_div cache is updated in set_fan_div().\n\nReported-by: Guenter Roeck <linux@roeck-us.net>\nSigned-off-by: Axel Lin <axel.lin@ingics.com>\nSigned-off-by: Guenter Roeck <linux@roeck-us.net>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/MikeC84/android_kernel_moto_shamu/commits/b36db304bfa9c4ec5b89ab5e74e47a928f335f93"}]}