payload: {"push_id":3808047058,"size":74,"distinct_size":0,"ref":"refs/heads/korg/stable/linux-4.4.y","head":"7bbf48947605d6ccef21a896c4b44dc356dc8726","before":"72d1ee93e9311c88809585a114c138bc6a43627a","commits":[{"sha":"fb7adf69e00dc08c3325a12f6cec3cd8ff53ebfc","author":{"name":"Jann Horn","email":"0fcb39c6619aeb747ed6898bfde644ba26b24452@google.com"},"message":"fs/binfmt_flat.c: make load_flat_shared_library() work\n\ncommit 867bfa4a5fcee66f2b25639acae718e8b28b25a5 upstream.\n\nload_flat_shared_library() is broken: It only calls load_flat_file() if\nprepare_binprm() returns zero, but prepare_binprm() returns the number of\nbytes read - so this only happens if the file is empty.\n\nInstead, call into load_flat_file() if the number of bytes read is\nnon-negative. (Even if the number of bytes is zero - in that case,\nload_flat_file() will see nullbytes and return a nice -ENOEXEC.)\n\nIn addition, remove the code related to bprm creds and stop using\nprepare_binprm() - this code is loading a library, not a main executable,\nand it only actually uses the members \"buf\", \"file\" and \"filename\" of the\nlinux_binprm struct. Instead, call kernel_read() directly.\n\nLink: http://lkml.kernel.org/r/20190524201817.16509-1-jannh@google.com\nFixes: 287980e49ffc (\"remove lots of IS_ERR_VALUE abuses\")\nSigned-off-by: Jann Horn <jannh@google.com>\nCc: Alexander Viro <viro@zeniv.linux.org.uk>\nCc: Kees Cook <keescook@chromium.org>\nCc: Nicolas Pitre <nicolas.pitre@linaro.org>\nCc: Arnd Bergmann <arnd@arndb.de>\nCc: Geert Uytterhoeven <geert@linux-m68k.org>\nCc: Russell King <linux@armlinux.org.uk>\nCc: Greg Ungerer <gerg@linux-m68k.org>\nCc: <stable@vger.kernel.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":false,"url":"https://api.github.com/repos/Jackeagle/kernel-msm-4.4/commits/fb7adf69e00dc08c3325a12f6cec3cd8ff53ebfc"},{"sha":"bd6042e9c3733f6fffc98ee88e239844d6f53a5d","author":{"name":"Colin Ian King","email":"d100aa70785e45ee8deab668147d941941915c21@canonical.com"},"message":"mm/page_idle.c: fix oops because end_pfn is larger than max_pfn\n\ncommit 7298e3b0a149c91323b3205d325e942c3b3b9ef6 upstream.\n\nCurrently the calcuation of end_pfn can round up the pfn number to more\nthan the actual maximum number of pfns, causing an Oops.  Fix this by\nensuring end_pfn is never more than max_pfn.\n\nThis can be easily triggered when on systems where the end_pfn gets\nrounded up to more than max_pfn using the idle-page stress-ng stress test:\n\nsudo stress-ng --idle-page 0\n\n  BUG: unable to handle kernel paging request at 00000000000020d8\n  #PF error: [normal kernel read fault]\n  PGD 0 P4D 0\n  Oops: 0000 [#1] SMP PTI\n  CPU: 1 PID: 11039 Comm: stress-ng-idle- Not tainted 5.0.0-5-generic #6-Ubuntu\n  Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.10.2-1ubuntu1 04/01/2014\n  RIP: 0010:page_idle_get_page+0xc8/0x1a0\n  Code: 0f b1 0a 75 7d 48 8b 03 48 89 c2 48 c1 e8 33 83 e0 07 48 c1 ea 36 48 8d 0c 40 4c 8d 24 88 49 c1 e4 07 4c 03 24 d5 00 89 c3 be <49> 8b 44 24 58 48 8d b8 80 a1 02 00 e8 07 d5 77 00 48 8b 53 08 48\n  RSP: 0018:ffffafd7c672fde8 EFLAGS: 00010202\n  RAX: 0000000000000005 RBX: ffffe36341fff700 RCX: 000000000000000f\n  RDX: 0000000000000284 RSI: 0000000000000275 RDI: 0000000001fff700\n  RBP: ffffafd7c672fe00 R08: ffffa0bc34056410 R09: 0000000000000276\n  R10: ffffa0bc754e9b40 R11: ffffa0bc330f6400 R12: 0000000000002080\n  R13: ffffe36341fff700 R14: 0000000000080000 R15: ffffa0bc330f6400\n  FS: 00007f0ec1ea5740(0000) GS:ffffa0bc7db00000(0000) knlGS:0000000000000000\n  CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033\n  CR2: 00000000000020d8 CR3: 0000000077d68000 CR4: 00000000000006e0\n  Call Trace:\n    page_idle_bitmap_write+0x8c/0x140\n    sysfs_kf_bin_write+0x5c/0x70\n    kernfs_fop_write+0x12e/0x1b0\n    __vfs_write+0x1b/0x40\n    vfs_write+0xab/0x1b0\n    ksys_write+0x55/0xc0\n    __x64_sys_write+0x1a/0x20\n    do_syscall_64+0x5a/0x110\n    entry_SYSCALL_64_after_hwframe+0x44/0xa9\n\nLink: http://lkml.kernel.org/r/20190618124352.28307-1-colin.king@canonical.com\nFixes: 33c3fc71c8cf (\"mm: introduce idle page tracking\")\nSigned-off-by: Colin Ian King <colin.king@canonical.com>\nReviewed-by: Andrew Morton <akpm@linux-foundation.org>\nAcked-by: Vladimir Davydov <vdavydov.dev@gmail.com>\nCc: Michal Hocko <mhocko@suse.com>\nCc: Mike Rapoport <rppt@linux.vnet.ibm.com>\nCc: Mel Gorman <mgorman@techsingularity.net>\nCc: Stephen Rothwell <sfr@canb.auug.org.au>\nCc: Andrey Ryabinin <aryabinin@virtuozzo.com>\nCc: <stable@vger.kernel.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":false,"url":"https://api.github.com/repos/Jackeagle/kernel-msm-4.4/commits/bd6042e9c3733f6fffc98ee88e239844d6f53a5d"},{"sha":"93709767272bf10f0244e2ca4d174c20668f5a54","author":{"name":"Jan Kara","email":"596727c8a0ea4db3ba2ceceedccbacd3d7b371b8@suse.cz"},"message":"scsi: vmw_pscsi: Fix use-after-free in pvscsi_queue_lck()\n\ncommit 240b4cc8fd5db138b675297d4226ec46594d9b3b upstream.\n\nOnce we unlock adapter->hw_lock in pvscsi_queue_lck() nothing prevents just\nqueued scsi_cmnd from completing and freeing the request. Thus cmd->cmnd[0]\ndereference can dereference already freed request leading to kernel crashes\nor other issues (which one of our customers observed). Store cmd->cmnd[0]\nin a local variable before unlocking adapter->hw_lock to fix the issue.\n\nCC: <stable@vger.kernel.org>\nSigned-off-by: Jan Kara <jack@suse.cz>\nReviewed-by: Ewan D. Milne <emilne@redhat.com>\nSigned-off-by: Martin K. Petersen <martin.petersen@oracle.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":false,"url":"https://api.github.com/repos/Jackeagle/kernel-msm-4.4/commits/93709767272bf10f0244e2ca4d174c20668f5a54"},{"sha":"f7247666a71ad147a5f2ecbd1b09cb3e6c7b6a32","author":{"name":"Miguel Ojeda","email":"f2cf57c66a360c31b77df33fc2c8f80a7e639e67@gmail.com"},"message":"tracing: Silence GCC 9 array bounds warning\n\ncommit 0c97bf863efce63d6ab7971dad811601e6171d2f upstream.\n\nStarting with GCC 9, -Warray-bounds detects cases when memset is called\nstarting on a member of a struct but the size to be cleared ends up\nwriting over further members.\n\nSuch a call happens in the trace code to clear, at once, all members\nafter and including `seq` on struct trace_iterator:\n\n    In function 'memset',\n        inlined from 'ftrace_dump' at kernel/trace/trace.c:8914:3:\n    ./include/linux/string.h:344:9: warning: '__builtin_memset' offset\n    [8505, 8560] from the object at 'iter' is out of the bounds of\n    referenced subobject 'seq' with type 'struct trace_seq' at offset\n    4368 [-Warray-bounds]\n      344 |  return __builtin_memset(p, c, size);\n          |         ^~~~~~~~~~~~~~~~~~~~~~~~~~~~\n\nIn order to avoid GCC complaining about it, we compute the address\nourselves by adding the offsetof distance instead of referring\ndirectly to the member.\n\nSince there are two places doing this clear (trace.c and trace_kdb.c),\ntake the chance to move the workaround into a single place in\nthe internal header.\n\nLink: http://lkml.kernel.org/r/20190523124535.GA12931@gmail.com\n\nSigned-off-by: Miguel Ojeda <miguel.ojeda.sandonis@gmail.com>\n[ Removed unnecessary parenthesis around \"iter\" ]\nSigned-off-by: Steven Rostedt (VMware) <rostedt@goodmis.org>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":false,"url":"https://api.github.com/repos/Jackeagle/kernel-msm-4.4/commits/f7247666a71ad147a5f2ecbd1b09cb3e6c7b6a32"},{"sha":"9efccd7745a1d659954cc5a0f6226cac2c4a1036","author":{"name":"Linus Torvalds","email":"69652caca27c8b940640ad396ab71f93cacec34f@linux-foundation.org"},"message":"gcc-9: silence 'address-of-packed-member' warning\n\ncommit 6f303d60534c46aa1a239f29c321f95c83dda748 upstream.\n\nWe already did this for clang, but now gcc has that warning too.  Yes,\nyes, the address may be unaligned.  And that's kind of the point.\n\nSigned-off-by: Linus Torvalds <torvalds@linux-foundation.org>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":false,"url":"https://api.github.com/repos/Jackeagle/kernel-msm-4.4/commits/9efccd7745a1d659954cc5a0f6226cac2c4a1036"},{"sha":"9a7435e1a5b94c8970a82254c27004dcaa8c440c","author":{"name":"Peter Chen","email":"c01a8c815a4ad165fff2d1c0d35ddf5b16bd3d7b@nxp.com"},"message":"usb: chipidea: udc: workaround for endpoint conflict issue\n\ncommit c19dffc0a9511a7d7493ec21019aefd97e9a111b upstream.\n\nAn endpoint conflict occurs when the USB is working in device mode\nduring an isochronous communication. When the endpointA IN direction\nis an isochronous IN endpoint, and the host sends an IN token to\nendpointA on another device, then the OUT transaction may be missed\nregardless the OUT endpoint number. Generally, this occurs when the\ndevice is connected to the host through a hub and other devices are\nconnected to the same hub.\n\nThe affected OUT endpoint can be either control, bulk, isochronous, or\nan interrupt endpoint. After the OUT endpoint is primed, if an IN token\nto the same endpoint number on another device is received, then the OUT\nendpoint may be unprimed (cannot be detected by software), which causes\nthis endpoint to no longer respond to the host OUT token, and thus, no\ncorresponding interrupt occurs.\n\nThere is no good workaround for this issue, the only thing the software\ncould do is numbering isochronous IN from the highest endpoint since we\nhave observed most of device number endpoint from the lowest.\n\nCc: <stable@vger.kernel.org> #v3.14+\nCc: Fabio Estevam <festevam@gmail.com>\nCc: Greg KH <gregkh@linuxfoundation.org>\nCc: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>\nCc: Jun Li <jun.li@nxp.com>\nSigned-off-by: Peter Chen <peter.chen@nxp.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":false,"url":"https://api.github.com/repos/Jackeagle/kernel-msm-4.4/commits/9a7435e1a5b94c8970a82254c27004dcaa8c440c"},{"sha":"4b6818e02588eb6eee0d741106dd71248e7a6c07","author":{"name":"Andrey Smirnov","email":"20184119c7e38269a48e5b46e687226abdf19908@gmail.com"},"message":"Input: uinput - add compat ioctl number translation for UI_*_FF_UPLOAD\n\ncommit 7c7da40da1640ce6814dab1e8031b44e19e5a3f6 upstream.\n\nIn the case of compat syscall ioctl numbers for UI_BEGIN_FF_UPLOAD and\nUI_END_FF_UPLOAD need to be adjusted before being passed on\nuinput_ioctl_handler() since code built with -m32 will be passing\nslightly different values. Extend the code already covering\nUI_SET_PHYS to cover UI_BEGIN_FF_UPLOAD and UI_END_FF_UPLOAD as well.\n\nReported-by: Pierre-Loup A. Griffais <pgriffais@valvesoftware.com>\nSigned-off-by: Andrey Smirnov <andrew.smirnov@gmail.com>\nCc: stable@vger.kernel.org\nSigned-off-by: Dmitry Torokhov <dmitry.torokhov@gmail.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":false,"url":"https://api.github.com/repos/Jackeagle/kernel-msm-4.4/commits/4b6818e02588eb6eee0d741106dd71248e7a6c07"},{"sha":"9617058178414c2ff32db0d55f060a35ec6f56ce","author":{"name":"Jann Horn","email":"0fcb39c6619aeb747ed6898bfde644ba26b24452@google.com"},"message":"apparmor: enforce nullbyte at end of tag string\n\ncommit 8404d7a674c49278607d19726e0acc0cae299357 upstream.\n\nA packed AppArmor policy contains null-terminated tag strings that are read\nby unpack_nameX(). However, unpack_nameX() uses string functions on them\nwithout ensuring that they are actually null-terminated, potentially\nleading to out-of-bounds accesses.\n\nMake sure that the tag string is null-terminated before passing it to\nstrcmp().\n\nCc: stable@vger.kernel.org\nFixes: 736ec752d95e (\"AppArmor: policy routines for loading and unpacking policy\")\nSigned-off-by: Jann Horn <jannh@google.com>\nSigned-off-by: John Johansen <john.johansen@canonical.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":false,"url":"https://api.github.com/repos/Jackeagle/kernel-msm-4.4/commits/9617058178414c2ff32db0d55f060a35ec6f56ce"},{"sha":"ececcbae0a3a915f241cfa7b8410bf63deef2dd3","author":{"name":"YueHaibing","email":"87ef4e6170d5e1d30adb7567acad1fcb98f93b6e@huawei.com"},"message":"parport: Fix mem leak in parport_register_dev_model\n\n[ Upstream commit 1c7ebeabc9e5ee12e42075a597de40fdb9059530 ]\n\nBUG: memory leak\nunreferenced object 0xffff8881df48cda0 (size 16):\n  comm \"syz-executor.0\", pid 5077, jiffies 4295994670 (age 22.280s)\n  hex dump (first 16 bytes):\n    00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................\n  backtrace:\n    [<00000000d2d0d5fe>] parport_register_dev_model+0x141/0x6e0 [parport]\n    [<00000000782f6dab>] 0xffffffffc15d1196\n    [<00000000d2ca6ae4>] platform_drv_probe+0x7e/0x100\n    [<00000000628c2a94>] really_probe+0x342/0x4d0\n    [<000000006874f5da>] driver_probe_device+0x8c/0x170\n    [<00000000424de37a>] __device_attach_driver+0xda/0x100\n    [<000000002acab09a>] bus_for_each_drv+0xfe/0x170\n    [<000000003d9e5f31>] __device_attach+0x190/0x230\n    [<0000000035d32f80>] bus_probe_device+0x123/0x140\n    [<00000000a05ba627>] device_add+0x7cc/0xce0\n    [<000000003f7560bf>] platform_device_add+0x230/0x3c0\n    [<000000002a0be07d>] 0xffffffffc15d0949\n    [<000000007361d8d2>] port_check+0x3b/0x50 [parport]\n    [<000000004d67200f>] bus_for_each_dev+0x115/0x180\n    [<000000003ccfd11c>] __parport_register_driver+0x1f0/0x210 [parport]\n    [<00000000987f06fc>] 0xffffffffc15d803e\n\nAfter commit 4e5a74f1db8d (\"parport: Revert \"parport: fix\nmemory leak\"\"), free_pardevice do not free par_dev->state,\nwe should free it in error path of parport_register_dev_model\nbefore return.\n\nReported-by: Hulk Robot <hulkci@huawei.com>\nFixes: 4e5a74f1db8d (\"parport: Revert \"parport: fix memory leak\"\")\nSigned-off-by: YueHaibing <yuehaibing@huawei.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>\nSigned-off-by: Sasha Levin <sashal@kernel.org>","distinct":false,"url":"https://api.github.com/repos/Jackeagle/kernel-msm-4.4/commits/ececcbae0a3a915f241cfa7b8410bf63deef2dd3"},{"sha":"96fdfe5665d4b4b8b5569abcd0903925edac5d34","author":{"name":"Helge Deller","email":"5b1e7895819cf7d6bc77091b09bbfd6d330a4e74@gmx.de"},"message":"parisc: Fix compiler warnings in float emulation code\n\n[ Upstream commit 6b98d9134e14f5ef4bcf64b27eedf484ed19a1ec ]\n\nAvoid such compiler warnings:\narch/parisc/math-emu/cnv_float.h:71:27: warning: ‘<<’ in boolean context, did you mean ‘<’ ? [-Wint-in-bool-context]\n     ((Dintp1(dint_valueA) << 33 - SGL_EXP_LENGTH) || Dintp2(dint_valueB))\narch/parisc/math-emu/fcnvxf.c:257:6: note: in expansion of macro ‘Dint_isinexact_to_sgl’\n  if (Dint_isinexact_to_sgl(srcp1,srcp2)) {\n\nSigned-off-by: Helge Deller <deller@gmx.de>\nSigned-off-by: Sasha Levin <sashal@kernel.org>","distinct":false,"url":"https://api.github.com/repos/Jackeagle/kernel-msm-4.4/commits/96fdfe5665d4b4b8b5569abcd0903925edac5d34"},{"sha":"a66d44b69a16ee43dfd82181345f1f24ec4ad201","author":{"name":"Mike Marciniszyn","email":"8b6671d72f65e2bb5dd5241f258fc1c5c815d085@intel.com"},"message":"IB/hfi1: Insure freeze_work work_struct is canceled on shutdown\n\n[ Upstream commit 6d517353c70bb0818b691ca003afdcb5ee5ea44e ]\n\nBy code inspection, the freeze_work is never canceled.\n\nFix by adding a cancel_work_sync in the shutdown path to insure it is no\nlonger running.\n\nFixes: 7724105686e7 (\"IB/hfi1: add driver files\")\nReviewed-by: Michael J. Ruhl <michael.j.ruhl@intel.com>\nReviewed-by: Dennis Dalessandro <dennis.dalessandro@intel.com>\nSigned-off-by: Mike Marciniszyn <mike.marciniszyn@intel.com>\nSigned-off-by: Dennis Dalessandro <dennis.dalessandro@intel.com>\nSigned-off-by: Jason Gunthorpe <jgg@mellanox.com>\nSigned-off-by: Sasha Levin <sashal@kernel.org>","distinct":false,"url":"https://api.github.com/repos/Jackeagle/kernel-msm-4.4/commits/a66d44b69a16ee43dfd82181345f1f24ec4ad201"},{"sha":"629877b5a33c92bc81e637090fb566017e3c2b33","author":{"name":"YueHaibing","email":"87ef4e6170d5e1d30adb7567acad1fcb98f93b6e@huawei.com"},"message":"MIPS: uprobes: remove set but not used variable 'epc'\n\n[ Upstream commit f532beeeff0c0a3586cc15538bc52d249eb19e7c ]\n\nFixes gcc '-Wunused-but-set-variable' warning:\n\narch/mips/kernel/uprobes.c: In function 'arch_uprobe_pre_xol':\narch/mips/kernel/uprobes.c:115:17: warning: variable 'epc' set but not used [-Wunused-but-set-variable]\n\nIt's never used since introduction in\ncommit 40e084a506eb (\"MIPS: Add uprobes support.\")\n\nSigned-off-by: YueHaibing <yuehaibing@huawei.com>\nSigned-off-by: Paul Burton <paul.burton@mips.com>\nCc: <ralf@linux-mips.org>\nCc: <jhogan@kernel.org>\nCc: <linux-kernel@vger.kernel.org>\nCc: <linux-mips@vger.kernel.org>\nSigned-off-by: Sasha Levin <sashal@kernel.org>","distinct":false,"url":"https://api.github.com/repos/Jackeagle/kernel-msm-4.4/commits/629877b5a33c92bc81e637090fb566017e3c2b33"},{"sha":"9df6837e2220c30af3ffd89f5b022f44af2e60c1","author":{"name":"Yonglong Liu","email":"f847115f96bccf66b9934bf1446b12bb39257442@huawei.com"},"message":"net: hns: Fix loopback test failed at copper ports\n\n[ Upstream commit 2e1f164861e500f4e068a9d909bbd3fcc7841483 ]\n\nWhen doing a loopback test at copper ports, the serdes loopback\nand the phy loopback will fail, because of the adjust link had\nnot finished, and phy not ready.\n\nAdds sleep between adjust link and test process to fix it.\n\nSigned-off-by: Yonglong Liu <liuyonglong@huawei.com>\nSigned-off-by: David S. Miller <davem@davemloft.net>\nSigned-off-by: Sasha Levin <sashal@kernel.org>","distinct":false,"url":"https://api.github.com/repos/Jackeagle/kernel-msm-4.4/commits/9df6837e2220c30af3ffd89f5b022f44af2e60c1"},{"sha":"37515df6b4885c72111683613cdc45dae215091b","author":{"name":"Young Xiao","email":"2edfd12f96379c82dda863b089b353f9bc5a3e2b@gmail.com"},"message":"sparc: perf: fix updated event period in response to PERF_EVENT_IOC_PERIOD\n\n[ Upstream commit 56cd0aefa475079e9613085b14a0f05037518fed ]\n\nThe PERF_EVENT_IOC_PERIOD ioctl command can be used to change the\nsample period of a running perf_event. Consequently, when calculating\nthe next event period, the new period will only be considered after the\nprevious one has overflowed.\n\nThis patch changes the calculation of the remaining event ticks so that\nthey are offset if the period has changed.\n\nSee commit 3581fe0ef37c (\"ARM: 7556/1: perf: fix updated event period in\nresponse to PERF_EVENT_IOC_PERIOD\") for details.\n\nSigned-off-by: Young Xiao <92siuyang@gmail.com>\nSigned-off-by: David S. Miller <davem@davemloft.net>\nSigned-off-by: Sasha Levin <sashal@kernel.org>","distinct":false,"url":"https://api.github.com/repos/Jackeagle/kernel-msm-4.4/commits/37515df6b4885c72111683613cdc45dae215091b"},{"sha":"d367346c5b43e3d5b1d2bf305e8e46cebda2000e","author":{"name":"George G. Davis","email":"d3601e2accd9d5fd5c9e7c6904cb6adcf94f9805@mentor.com"},"message":"scripts/checkstack.pl: Fix arm64 wrong or unknown architecture\n\n[ Upstream commit 4f45d62a52297b10ded963412a158685647ecdec ]\n\nThe following error occurs for the `make ARCH=arm64 checkstack` case:\n\naarch64-linux-gnu-objdump -d vmlinux $(find . -name '*.ko') | \\\nperl ./scripts/checkstack.pl arm64\nwrong or unknown architecture \"arm64\"\n\nAs suggested by Masahiro Yamada, fix the above error using regular\nexpressions in the same way it was fixed for the `ARCH=x86` case via\ncommit fda9f9903be6 (\"scripts/checkstack.pl: automatically handle\n32-bit and 64-bit mode for ARCH=x86\").\n\nSuggested-by: Masahiro Yamada <yamada.masahiro@socionext.com>\nSigned-off-by: George G. Davis <george_davis@mentor.com>\nSigned-off-by: Masahiro Yamada <yamada.masahiro@socionext.com>\nSigned-off-by: Sasha Levin <sashal@kernel.org>","distinct":false,"url":"https://api.github.com/repos/Jackeagle/kernel-msm-4.4/commits/d367346c5b43e3d5b1d2bf305e8e46cebda2000e"},{"sha":"3b63a2e8812a7bff8f4cbcbc1be33982911b1f93","author":{"name":"Avri Altman","email":"e1c753d62aa942f106c7c67eb1c33fa3803e3b75@wdc.com"},"message":"scsi: ufs: Check that space was properly alloced in copy_query_response\n\n[ Upstream commit 1c90836f70f9a8ef7b7ad9e1fdd8961903e6ced6 ]\n\nstruct ufs_dev_cmd is the main container that supports device management\ncommands. In the case of a read descriptor request, we assume that the\nproper space was allocated in dev_cmd to hold the returning descriptor.\n\nThis is no longer true, as there are flows that doesn't use dev_cmd for\ndevice management requests, and was wrong in the first place.\n\nFixes: d44a5f98bb49 (ufs: query descriptor API)\nSigned-off-by: Avri Altman <avri.altman@wdc.com>\nReviewed-by: Alim Akhtar <alim.akhtar@samsung.com>\nAcked-by: Bean Huo <beanhuo@micron.com>\nSigned-off-by: Martin K. Petersen <martin.petersen@oracle.com>\nSigned-off-by: Sasha Levin <sashal@kernel.org>","distinct":false,"url":"https://api.github.com/repos/Jackeagle/kernel-msm-4.4/commits/3b63a2e8812a7bff8f4cbcbc1be33982911b1f93"},{"sha":"4847348903fb41d5a3fb0eab58f4d766514fe877","author":{"name":"Alexandra Winter","email":"a912d7454c4891b9b8d8cc4de18203be0ba3d27a@linux.ibm.com"},"message":"s390/qeth: fix VLAN attribute in bridge_hostnotify udev event\n\n[ Upstream commit 335726195e460cb6b3f795b695bfd31f0ea70ef0 ]\n\nEnabling sysfs attribute bridge_hostnotify triggers a series of udev events\nfor the MAC addresses of all currently connected peers. In case no VLAN is\nset for a peer, the device reports the corresponding MAC addresses with\nVLAN ID 4096. This currently results in attribute VLAN=4096 for all\nnon-VLAN interfaces in the initial series of events after host-notify is\nenabled.\n\nInstead, no VLAN attribute should be reported in the udev event for\nnon-VLAN interfaces.\n\nOnly the initial events face this issue. For dynamic changes that are\nreported later, the device uses a validity flag.\n\nThis also changes the code so that it now sets the VLAN attribute for\nMAC addresses with VID 0. On Linux, no qeth interface will ever be\nregistered with VID 0: Linux kernel registers VID 0 on all network\ninterfaces initially, but qeth will drop .ndo_vlan_rx_add_vid for VID 0.\nPeers with other OSs could register MACs with VID 0.\n\nFixes: 9f48b9db9a22 (\"qeth: bridgeport support - address notifications\")\nSigned-off-by: Alexandra Winter <wintera@linux.ibm.com>\nSigned-off-by: Julian Wiedmann <jwi@linux.ibm.com>\nSigned-off-by: David S. Miller <davem@davemloft.net>\nSigned-off-by: Sasha Levin <sashal@kernel.org>","distinct":false,"url":"https://api.github.com/repos/Jackeagle/kernel-msm-4.4/commits/4847348903fb41d5a3fb0eab58f4d766514fe877"},{"sha":"66f0f0fdb9b96d931e479b5c9ea3305f68b3743b","author":{"name":"Robert Hancock","email":"1b69de4f4bc5496e5e8f15a80f675181dcd1fb58@sedsystems.ca"},"message":"hwmon: (pmbus/core) Treat parameters as paged if on multiple pages\n\n[ Upstream commit 4a60570dce658e3f8885bbcf852430b99f65aca5 ]\n\nSome chips have attributes which exist on more than one page but the\nattribute is not presently marked as paged. This causes the attributes\nto be generated with the same label, which makes it impossible for\nuserspace to tell them apart.\n\nMarking all such attributes as paged would result in the page suffix\nbeing added regardless of whether they were present on more than one\npage or not, which might break existing setups. Therefore, we add a\nsecond check which treats the attribute as paged, even if not marked as\nsuch, if it is present on multiple pages.\n\nFixes: b4ce237b7f7d (\"hwmon: (pmbus) Introduce infrastructure to detect sensors and limit registers\")\nSigned-off-by: Robert Hancock <hancock@sedsystems.ca>\nSigned-off-by: Guenter Roeck <linux@roeck-us.net>\nSigned-off-by: Sasha Levin <sashal@kernel.org>","distinct":false,"url":"https://api.github.com/repos/Jackeagle/kernel-msm-4.4/commits/66f0f0fdb9b96d931e479b5c9ea3305f68b3743b"},{"sha":"95c82386950c7a5e018ac02d795aa8782f52754b","author":{"name":"Filipe Manana","email":"e0fcd583df77ec6c08e6d1257619cc1216ddc994@suse.com"},"message":"Btrfs: fix race between readahead and device replace/removal\n\ncommit ce7791ffee1e1ee9f97193b817c7dd1fa6746aad upstream.\n\nThe list of devices is protected by the device_list_mutex and the device\nreplace code, in its finishing phase correctly takes that mutex before\nremoving the source device from that list. However the readahead code was\niterating that list without acquiring the respective mutex leading to\ncrashes later on due to invalid memory accesses:\n\n[125671.831036] general protection fault: 0000 [#1] PREEMPT SMP\n[125671.832129] Modules linked in: btrfs dm_flakey dm_mod crc32c_generic xor raid6_pq acpi_cpufreq tpm_tis tpm ppdev evdev parport_pc psmouse sg parport\nprocessor ser\n[125671.834973] CPU: 10 PID: 19603 Comm: kworker/u32:19 Tainted: G        W       4.6.0-rc7-btrfs-next-29+ #1\n[125671.834973] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS by qemu-project.org 04/01/2014\n[125671.834973] Workqueue: btrfs-readahead btrfs_readahead_helper [btrfs]\n[125671.834973] task: ffff8801ac520540 ti: ffff8801ac918000 task.ti: ffff8801ac918000\n[125671.834973] RIP: 0010:[<ffffffff81270479>]  [<ffffffff81270479>] __radix_tree_lookup+0x6a/0x105\n[125671.834973] RSP: 0018:ffff8801ac91bc28  EFLAGS: 00010206\n[125671.834973] RAX: 0000000000000000 RBX: 6b6b6b6b6b6b6b6a RCX: 0000000000000000\n[125671.834973] RDX: 0000000000000000 RSI: 00000000000c1bff RDI: ffff88002ebd62a8\n[125671.834973] RBP: ffff8801ac91bc70 R08: 0000000000000001 R09: 0000000000000000\n[125671.834973] R10: ffff8801ac91bc70 R11: 0000000000000000 R12: ffff88002ebd62a8\n[125671.834973] R13: 0000000000000000 R14: 0000000000000000 R15: 00000000000c1bff\n[125671.834973] FS:  0000000000000000(0000) GS:ffff88023fd40000(0000) knlGS:0000000000000000\n[125671.834973] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\n[125671.834973] CR2: 000000000073cae4 CR3: 00000000b7723000 CR4: 00000000000006e0\n[125671.834973] Stack:\n[125671.834973]  0000000000000000 ffff8801422d5600 ffff8802286bbc00 0000000000000000\n[125671.834973]  0000000000000001 ffff8802286bbc00 00000000000c1bff 0000000000000000\n[125671.834973]  ffff88002e639eb8 ffff8801ac91bc80 ffffffff81270541 ffff8801ac91bcb0\n[125671.834973] Call Trace:\n[125671.834973]  [<ffffffff81270541>] radix_tree_lookup+0xd/0xf\n[125671.834973]  [<ffffffffa04ae6a6>] reada_peer_zones_set_lock+0x3e/0x60 [btrfs]\n[125671.834973]  [<ffffffffa04ae8b9>] reada_pick_zone+0x29/0x103 [btrfs]\n[125671.834973]  [<ffffffffa04af42f>] reada_start_machine_worker+0x129/0x2d3 [btrfs]\n[125671.834973]  [<ffffffffa04880be>] btrfs_scrubparity_helper+0x185/0x3aa [btrfs]\n[125671.834973]  [<ffffffffa0488341>] btrfs_readahead_helper+0xe/0x10 [btrfs]\n[125671.834973]  [<ffffffff81069691>] process_one_work+0x271/0x4e9\n[125671.834973]  [<ffffffff81069dda>] worker_thread+0x1eb/0x2c9\n[125671.834973]  [<ffffffff81069bef>] ? rescuer_thread+0x2b3/0x2b3\n[125671.834973]  [<ffffffff8106f403>] kthread+0xd4/0xdc\n[125671.834973]  [<ffffffff8149e242>] ret_from_fork+0x22/0x40\n[125671.834973]  [<ffffffff8106f32f>] ? kthread_stop+0x286/0x286\n\nSo fix this by taking the device_list_mutex in the readahead code. We\ncan't use here the lighter approach of using a rcu_read_lock() and\nrcu_read_unlock() pair together with a list_for_each_entry_rcu() call\nbecause we end up doing calls to sleeping functions (kzalloc()) in the\nrespective code path.\n\nSigned-off-by: Filipe Manana <fdmanana@suse.com>\nReviewed-by: Josef Bacik <jbacik@fb.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":false,"url":"https://api.github.com/repos/Jackeagle/kernel-msm-4.4/commits/95c82386950c7a5e018ac02d795aa8782f52754b"},{"sha":"d38cac353bc5d3d056906c77ca27326b0b6c46bc","author":{"name":"Naohiro Aota","email":"8fe18c0c962c20cb6362a25e595e091afd482145@wdc.com"},"message":"btrfs: start readahead also in seed devices\n\ncommit c4e0540d0ad49c8ceab06cceed1de27c4fe29f6e upstream.\n\nCurrently, btrfs does not consult seed devices to start readahead. As a\nresult, if readahead zone is added to the seed devices, btrfs_reada_wait()\nindefinitely wait for the reada_ctl to finish.\n\nYou can reproduce the hung by modifying btrfs/163 to have larger initial\nfile size (e.g. xfs_io pwrite 4M instead of current 256K).\n\nFixes: 7414a03fbf9e (\"btrfs: initial readahead code and prototypes\")\nCc: stable@vger.kernel.org # 3.2+: ce7791ffee1e: Btrfs: fix race between readahead and device replace/removal\nCc: stable@vger.kernel.org # 3.2+\nReviewed-by: Filipe Manana <fdmanana@suse.com>\nSigned-off-by: Naohiro Aota <naohiro.aota@wdc.com>\nSigned-off-by: David Sterba <dsterba@suse.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":false,"url":"https://api.github.com/repos/Jackeagle/kernel-msm-4.4/commits/d38cac353bc5d3d056906c77ca27326b0b6c46bc"}]}
other: {"actor":{"display_login":"Jackeagle"}}