{"push_id":2760073679,"size":1000,"distinct_size":1724,"ref":"refs/heads/another","head":"df159cfdafe66f6ebdaad79dbbcc98c7e615d12b","before":"3180dc01dc9577ff3655aaa8af2faa312e4e85f3","commits":[{"sha":"04f31b0251c0ac1745c55167efd22f64e0492b11","author":{"name":"Guenter Roeck","email":"ba324ca7b1c77fc20bb970d5aff6eea9377918a5@roeck-us.net"},"message":"openrisc: fix the fix of copy_from_user()\n\n[ Upstream commit 8e4b72054f554967827e18be1de0e8122e6efc04 ]\n\nSince commit acb2505d0119 (\"openrisc: fix copy_from_user()\"),\ncopy_from_user() returns the number of bytes requested, not the\nnumber of bytes not copied.\n\nCc: Al Viro <viro@zeniv.linux.org.uk>\nFixes: acb2505d0119 (\"openrisc: fix copy_from_user()\")\nSigned-off-by: Guenter Roeck <linux@roeck-us.net>\nSigned-off-by: Sasha Levin <alexander.levin@verizon.com>","distinct":true,"url":"https://api.github.com/repos/MyProjectIsAwesome/android_kernel_xiaomi_msm8953/commits/04f31b0251c0ac1745c55167efd22f64e0492b11"},{"sha":"f7bc785f1b9a88f0223d5e486513a1e8ed097b5b","author":{"name":"Sasha Levin","email":"0efa6c98c4f0e10999dc97df2ede00683cc37722@verizon.com"},"message":"Linux 3.18.43\n\nSigned-off-by: Sasha Levin <alexander.levin@verizon.com>","distinct":true,"url":"https://api.github.com/repos/MyProjectIsAwesome/android_kernel_xiaomi_msm8953/commits/f7bc785f1b9a88f0223d5e486513a1e8ed097b5b"},{"sha":"77d015cd37cfee88e433edf160a208ff22ff39f5","author":{"name":"Andrew Cooper","email":"cb880bd9232cc23a76ddb35f95d96ed0ad981f23@citrix.com"},"message":"x86/cpu: Fix SMAP check in PVOPS environments\n\n[ Upstream commit 581b7f158fe0383b492acd1ce3fb4e99d4e57808 ]\n\nThere appears to be no formal statement of what pv_irq_ops.save_fl() is\nsupposed to return precisely.  Native returns the full flags, while lguest and\nXen only return the Interrupt Flag, and both have comments by the\nimplementations stating that only the Interrupt Flag is looked at.  This may\nhave been true when initially implemented, but no longer is.\n\nTo make matters worse, the Xen PVOP leaves the upper bits undefined, making\nthe BUG_ON() undefined behaviour.  Experimentally, this now trips for 32bit PV\nguests on Broadwell hardware.  The BUG_ON() is consistent for an individual\nbuild, but not consistent for all builds.  It has also been a sitting timebomb\nsince SMAP support was introduced.\n\nUse native_save_fl() instead, which will obtain an accurate view of the AC\nflag.\n\nSigned-off-by: Andrew Cooper <andrew.cooper3@citrix.com>\nReviewed-by: David Vrabel <david.vrabel@citrix.com>\nTested-by: Rusty Russell <rusty@rustcorp.com.au>\nCc: Rusty Russell <rusty@rustcorp.com.au>\nCc: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>\nCc: Boris Ostrovsky <boris.ostrovsky@oracle.com>\nCc: <lguest@lists.ozlabs.org>\nCc: Xen-devel <xen-devel@lists.xen.org>\nCC: stable@vger.kernel.org\nLink: http://lkml.kernel.org/r/1433323874-6927-1-git-send-email-andrew.cooper3@citrix.com\nSigned-off-by: Thomas Gleixner <tglx@linutronix.de>\nSigned-off-by: Sasha Levin <alexander.levin@verizon.com>","distinct":true,"url":"https://api.github.com/repos/MyProjectIsAwesome/android_kernel_xiaomi_msm8953/commits/77d015cd37cfee88e433edf160a208ff22ff39f5"},{"sha":"59f612df3f0388c6d2cc9e69eb08dde4778d19bc","author":{"name":"Mathias Nyman","email":"2d4473c5e67eb83655334d4e9a7757f781607241@linux.intel.com"},"message":"xhci: fix usb2 resume timing and races.\n\n[ Upstream commit f69115fdbc1ac0718e7d19ad3caa3da2ecfe1c96 ]\n\nAccording to USB 2 specs ports need to signal resume for at least 20ms,\nin practice even longer, before moving to U0 state.\nBoth host and devices can initiate resume.\n\nOn device initiated resume, a port status interrupt with the port in resume\nstate in issued. The interrupt handler tags a resume_done[port]\ntimestamp with current time + USB_RESUME_TIMEOUT, and kick roothub timer.\nRoot hub timer requests for port status, finds the port in resume state,\nchecks if resume_done[port] timestamp passed, and set port to U0 state.\n\nOn host initiated resume, current code sets the port to resume state,\nsleep 20ms, and finally sets the port to U0 state. This should also\nbe changed to work in a similar way as the device initiated resume, with\ntimestamp tagging, but that is not yet tested and will be a separate\nfix later.\n\nThere are a few issues with this approach\n\n1. A host initiated resume will also generate a resume event. The event\n   handler will find the port in resume state, believe it's a device\n   initiated resume, and act accordingly.\n\n2. A port status request might cut the resume signalling short if a\n   get_port_status request is handled during the host resume signalling.\n   The port will be found in resume state. The timestamp is not set leading\n   to time_after_eq(jiffies, timestamp) returning true, as timestamp = 0.\n   get_port_status will proceed with moving the port to U0.\n\n3. If an error, or anything else happens to the port during device\n   initiated resume signalling it will leave all the device resume\n   parameters hanging uncleared, preventing further suspend, returning\n   -EBUSY, and cause the pm thread to busyloop trying to enter suspend.\n\nFix this by using the existing resuming_ports bitfield to indicate that\nresume signalling timing is taken care of.\nCheck if the resume_done[port] is set before using it for timestamp\ncomparison, and also clear out any resume signalling related variables\nif port is not in U0 or Resume state\n\nThis issue was discovered when a PM thread busylooped, trying to runtime\nsuspend the xhci USB 2 roothub on a Dell XPS\n\nCc: stable <stable@vger.kernel.org>\nReported-by: Daniel J Blueman <daniel@quora.org>\nTested-by: Daniel J Blueman <daniel@quora.org>\nSigned-off-by: Mathias Nyman <mathias.nyman@linux.intel.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>\nSigned-off-by: Sasha Levin <alexander.levin@verizon.com>","distinct":true,"url":"https://api.github.com/repos/MyProjectIsAwesome/android_kernel_xiaomi_msm8953/commits/59f612df3f0388c6d2cc9e69eb08dde4778d19bc"},{"sha":"ad00cbc195325de42068d7443454e30e4f3b1146","author":{"name":"Sasha Levin","email":"0efa6c98c4f0e10999dc97df2ede00683cc37722@verizon.com"},"message":"Linux 3.18.44\n\nSigned-off-by: Sasha Levin <alexander.levin@verizon.com>","distinct":true,"url":"https://api.github.com/repos/MyProjectIsAwesome/android_kernel_xiaomi_msm8953/commits/ad00cbc195325de42068d7443454e30e4f3b1146"},{"sha":"a4a20b72170d5552fa6f1fbb7f99cf99b1f8c602","author":{"name":"Jiri Slaby","email":"dfbf39eb5bf303a3db5454d815cb8c8888cbadf9@suse.cz"},"message":"mmc: core: Annotate cmd_hdr as __le32\n\n[ Upstream commit 3f2d26643595973e835e8356ea90c7c15cb1b0f1 ]\n\nCommit f68381a70bb2 (mmc: block: fix packed command header endianness)\ncorrectly fixed endianness handling of packed_cmd_hdr in\nmmc_blk_packed_hdr_wrq_prep.\n\nBut now, sparse complains about incorrect types:\ndrivers/mmc/card/block.c:1613:27: sparse: incorrect type in assignment (different base types)\ndrivers/mmc/card/block.c:1613:27:    expected unsigned int [unsigned] [usertype] <noident>\ndrivers/mmc/card/block.c:1613:27:    got restricted __le32 [usertype] <noident>\n...\n\nSo annotate cmd_hdr properly using __le32 to make everyone happy.\n\nSigned-off-by: Jiri Slaby <jslaby@suse.cz>\nFixes: f68381a70bb2 (mmc: block: fix packed command header endianness)\nCc: stable@vger.kernel.org\nSigned-off-by: Ulf Hansson <ulf.hansson@linaro.org>\nSigned-off-by: Sasha Levin <alexander.levin@verizon.com>","distinct":true,"url":"https://api.github.com/repos/MyProjectIsAwesome/android_kernel_xiaomi_msm8953/commits/a4a20b72170d5552fa6f1fbb7f99cf99b1f8c602"},{"sha":"5f3cf0aa8314ecca8ab04f448b5b9c0a9036d75d","author":{"name":"Ming Lei","email":"572efd9047f12626ad5bcb995a452788646858f3@gmail.com"},"message":"scsi: Fix use-after-free\n\n[ Upstream commit bcd8f2e94808fcddf6ef3af5f060a36820dcc432 ]\n\nThis patch fixes one use-after-free report[1] by KASAN.\n\nIn __scsi_scan_target(), when a type 31 device is probed,\nSCSI_SCAN_TARGET_PRESENT is returned and the target will be scanned\nagain.\n\nInside the following scsi_report_lun_scan(), one new scsi_device\ninstance is allocated, and scsi_probe_and_add_lun() is called again to\nprobe the target and still see type 31 device, finally\n__scsi_remove_device() is called to remove & free the device at the end\nof scsi_probe_and_add_lun(), so cause use-after-free in\nscsi_report_lun_scan().\n\nAnd the following SCSI log can be observed:\n\n\tscsi 0:0:2:0: scsi scan: INQUIRY pass 1 length 36\n\tscsi 0:0:2:0: scsi scan: INQUIRY successful with code 0x0\n\tscsi 0:0:2:0: scsi scan: peripheral device type of 31, no device added\n\tscsi 0:0:2:0: scsi scan: Sending REPORT LUNS to (try 0)\n\tscsi 0:0:2:0: scsi scan: REPORT LUNS successful (try 0) result 0x0\n\tscsi 0:0:2:0: scsi scan: REPORT LUN scan\n\tscsi 0:0:2:0: scsi scan: INQUIRY pass 1 length 36\n\tscsi 0:0:2:0: scsi scan: INQUIRY successful with code 0x0\n\tscsi 0:0:2:0: scsi scan: peripheral device type of 31, no device added\n\tBUG: KASAN: use-after-free in __scsi_scan_target+0xbf8/0xe40 at addr ffff88007b44a104\n\nThis patch fixes the issue by moving the putting reference at\nthe end of scsi_report_lun_scan().\n\n[1] KASAN report\n==================================================================\n[    3.274597] PM: Adding info for serio:serio1\n[    3.275127] BUG: KASAN: use-after-free in __scsi_scan_target+0xd87/0xdf0 at addr ffff880254d8c304\n[    3.275653] Read of size 4 by task kworker/u10:0/27\n[    3.275903] CPU: 3 PID: 27 Comm: kworker/u10:0 Not tainted 4.8.0 #2121\n[    3.276258] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS Ubuntu-1.8.2-1ubuntu1 04/01/2014\n[    3.276797] Workqueue: events_unbound async_run_entry_fn\n[    3.277083]  ffff880254d8c380 ffff880259a37870 ffffffff94bbc6c1 ffff880078402d80\n[    3.277532]  ffff880254d8bb80 ffff880259a37898 ffffffff9459fec1 ffff880259a37930\n[    3.277989]  ffff880254d8bb80 ffff880078402d80 ffff880259a37920 ffffffff945a0165\n[    3.278436] Call Trace:\n[    3.278528]  [<ffffffff94bbc6c1>] dump_stack+0x65/0x84\n[    3.278797]  [<ffffffff9459fec1>] kasan_object_err+0x21/0x70\n[    3.279063] device: 'psaux': device_add\n[    3.279616]  [<ffffffff945a0165>] kasan_report_error+0x205/0x500\n[    3.279651] PM: Adding info for No Bus:psaux\n[    3.280202]  [<ffffffff944ecd22>] ? kfree_const+0x22/0x30\n[    3.280486]  [<ffffffff94bc2dc9>] ? kobject_release+0x119/0x370\n[    3.280805]  [<ffffffff945a0543>] __asan_report_load4_noabort+0x43/0x50\n[    3.281170]  [<ffffffff9507e1f7>] ? __scsi_scan_target+0xd87/0xdf0\n[    3.281506]  [<ffffffff9507e1f7>] __scsi_scan_target+0xd87/0xdf0\n[    3.281848]  [<ffffffff9507d470>] ? scsi_add_device+0x30/0x30\n[    3.282156]  [<ffffffff94f7f660>] ? pm_runtime_autosuspend_expiration+0x60/0x60\n[    3.282570]  [<ffffffff956ddb07>] ? _raw_spin_lock+0x17/0x40\n[    3.282880]  [<ffffffff9507e505>] scsi_scan_channel+0x105/0x160\n[    3.283200]  [<ffffffff9507e8a2>] scsi_scan_host_selected+0x212/0x2f0\n[    3.283563]  [<ffffffff9507eb3c>] do_scsi_scan_host+0x1bc/0x250\n[    3.283882]  [<ffffffff9507efc1>] do_scan_async+0x41/0x450\n[    3.284173]  [<ffffffff941c1fee>] async_run_entry_fn+0xfe/0x610\n[    3.284492]  [<ffffffff941a8954>] ? pwq_dec_nr_in_flight+0x124/0x2a0\n[    3.284876]  [<ffffffff941d1770>] ? preempt_count_add+0x130/0x160\n[    3.285207]  [<ffffffff941a9a84>] process_one_work+0x544/0x12d0\n[    3.285526]  [<ffffffff941aa8e9>] worker_thread+0xd9/0x12f0\n[    3.285844]  [<ffffffff941aa810>] ? process_one_work+0x12d0/0x12d0\n[    3.286182]  [<ffffffff941bb365>] kthread+0x1c5/0x260\n[    3.286443]  [<ffffffff940855cd>] ? __switch_to+0x88d/0x1430\n[    3.286745]  [<ffffffff941bb1a0>] ? kthread_worker_fn+0x5a0/0x5a0\n[    3.287085]  [<ffffffff956dde9f>] ret_from_fork+0x1f/0x40\n[    3.287368]  [<ffffffff941bb1a0>] ? kthread_worker_fn+0x5a0/0x5a0\n[    3.287697] Object at ffff880254d8bb80, in cache kmalloc-2048 size: 2048\n[    3.288064] Allocated:\n[    3.288147] PID = 27\n[    3.288218]  [<ffffffff940b27ab>] save_stack_trace+0x2b/0x50\n[    3.288531]  [<ffffffff9459f246>] save_stack+0x46/0xd0\n[    3.288806]  [<ffffffff9459f4bd>] kasan_kmalloc+0xad/0xe0\n[    3.289098]  [<ffffffff9459c07e>] __kmalloc+0x13e/0x250\n[    3.289378]  [<ffffffff95078e5a>] scsi_alloc_sdev+0xea/0xcf0\n[    3.289701]  [<ffffffff9507de76>] __scsi_scan_target+0xa06/0xdf0\n[    3.290034]  [<ffffffff9507e505>] scsi_scan_channel+0x105/0x160\n[    3.290362]  [<ffffffff9507e8a2>] scsi_scan_host_selected+0x212/0x2f0\n[    3.290724]  [<ffffffff9507eb3c>] do_scsi_scan_host+0x1bc/0x250\n[    3.291055]  [<ffffffff9507efc1>] do_scan_async+0x41/0x450\n[    3.291354]  [<ffffffff941c1fee>] async_run_entry_fn+0xfe/0x610\n[    3.291695]  [<ffffffff941a9a84>] process_one_work+0x544/0x12d0\n[    3.292022]  [<ffffffff941aa8e9>] worker_thread+0xd9/0x12f0\n[    3.292325]  [<ffffffff941bb365>] kthread+0x1c5/0x260\n[    3.292594]  [<ffffffff956dde9f>] ret_from_fork+0x1f/0x40\n[    3.292886] Freed:\n[    3.292945] PID = 27\n[    3.293016]  [<ffffffff940b27ab>] save_stack_trace+0x2b/0x50\n[    3.293327]  [<ffffffff9459f246>] save_stack+0x46/0xd0\n[    3.293600]  [<ffffffff9459fa61>] kasan_slab_free+0x71/0xb0\n[    3.293916]  [<ffffffff9459bac2>] kfree+0xa2/0x1f0\n[    3.294168]  [<ffffffff9508158a>] scsi_device_dev_release_usercontext+0x50a/0x730\n[    3.294598]  [<ffffffff941ace9a>] execute_in_process_context+0xda/0x130\n[    3.294974]  [<ffffffff9508107c>] scsi_device_dev_release+0x1c/0x20\n[    3.295322]  [<ffffffff94f566f6>] device_release+0x76/0x1e0\n[    3.295626]  [<ffffffff94bc2db7>] kobject_release+0x107/0x370\n[    3.295942]  [<ffffffff94bc29ce>] kobject_put+0x4e/0xa0\n[    3.296222]  [<ffffffff94f56e17>] put_device+0x17/0x20\n[    3.296497]  [<ffffffff9505201c>] scsi_device_put+0x7c/0xa0\n[    3.296801]  [<ffffffff9507e1bc>] __scsi_scan_target+0xd4c/0xdf0\n[    3.297132]  [<ffffffff9507e505>] scsi_scan_channel+0x105/0x160\n[    3.297458]  [<ffffffff9507e8a2>] scsi_scan_host_selected+0x212/0x2f0\n[    3.297829]  [<ffffffff9507eb3c>] do_scsi_scan_host+0x1bc/0x250\n[    3.298156]  [<ffffffff9507efc1>] do_scan_async+0x41/0x450\n[    3.298453]  [<ffffffff941c1fee>] async_run_entry_fn+0xfe/0x610\n[    3.298777]  [<ffffffff941a9a84>] process_one_work+0x544/0x12d0\n[    3.299105]  [<ffffffff941aa8e9>] worker_thread+0xd9/0x12f0\n[    3.299408]  [<ffffffff941bb365>] kthread+0x1c5/0x260\n[    3.299676]  [<ffffffff956dde9f>] ret_from_fork+0x1f/0x40\n[    3.299967] Memory state around the buggy address:\n[    3.300209]  ffff880254d8c200: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb\n[    3.300608]  ffff880254d8c280: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb\n[    3.300986] >ffff880254d8c300: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb\n[    3.301408]                    ^\n[    3.301550]  ffff880254d8c380: fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc\n[    3.301987]  ffff880254d8c400: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00\n[    3.302396]\n==================================================================\n\nCc: Christoph Hellwig <hch@lst.de>\nCc: stable@vger.kernel.org\nSigned-off-by: Ming Lei <tom.leiming@gmail.com>\nReviewed-by: Christoph Hellwig <hch@lst.de>\nSigned-off-by: Martin K. Petersen <martin.petersen@oracle.com>\nSigned-off-by: Sasha Levin <alexander.levin@verizon.com>","distinct":true,"url":"https://api.github.com/repos/MyProjectIsAwesome/android_kernel_xiaomi_msm8953/commits/5f3cf0aa8314ecca8ab04f448b5b9c0a9036d75d"},{"sha":"b586d993f4f00284cdbecaeb4bb684190c9fca7d","author":{"name":"Taesoo Kim","email":"faaf2a003e763d66b0832086106da1ab97ecac15@gmail.com"},"message":"jbd2: fix incorrect unlock on j_list_lock\n\n[ Upstream commit 559cce698eaf4ccecb2213b2519ea3a0413e5155 ]\n\nWhen 'jh->b_transaction == transaction' (asserted by below)\n\n  J_ASSERT_JH(jh, (jh->b_transaction == transaction || ...\n\n'journal->j_list_lock' will be incorrectly unlocked, since\nthe the lock is aquired only at the end of if / else-if\nstatements (missing the else case).\n\nSigned-off-by: Taesoo Kim <tsgatesv@gmail.com>\nSigned-off-by: Theodore Ts'o <tytso@mit.edu>\nReviewed-by: Andreas Dilger <adilger@dilger.ca>\nFixes: 6e4862a5bb9d12be87e4ea5d9a60836ebed71d28\nCc: stable@vger.kernel.org # 3.14+\nSigned-off-by: Sasha Levin <alexander.levin@verizon.com>","distinct":true,"url":"https://api.github.com/repos/MyProjectIsAwesome/android_kernel_xiaomi_msm8953/commits/b586d993f4f00284cdbecaeb4bb684190c9fca7d"},{"sha":"5716532611d0fa6c9e03b5e6119fda68d37dfbe0","author":{"name":"Alex Deucher","email":"08dc22c6156113f2deff178e35e3ed9b24d6af9e@amd.com"},"message":"drm/radeon: change vblank_time's calculation method to reduce computational error.\n\n[ Upstream commit 02cfb5fccb0f9f968f0e208d89d9769aa16267bc ]\n\nPorted from Rex's amdgpu change.\n\nSigned-off-by: Alex Deucher <alexander.deucher@amd.com>\nCc: stable@vger.kernel.org\nSigned-off-by: Sasha Levin <alexander.levin@verizon.com>","distinct":true,"url":"https://api.github.com/repos/MyProjectIsAwesome/android_kernel_xiaomi_msm8953/commits/5716532611d0fa6c9e03b5e6119fda68d37dfbe0"},{"sha":"d5ec3044325efc9783c2137a3354dcdd5cf64895","author":{"name":"Dan Carpenter","email":"ff341aa343d564f9e53e9dcb6996be8c04859a66@oracle.com"},"message":"irqchip/gicv3: Handle loop timeout proper\n\n[ Upstream commit d102eb5c1ac5e6743b1c6d145c06a25d98ad1375 ]\n\nThe timeout loop terminates when the loop count is zero, but the decrement\nof the count variable is post check. So count is -1 when we check for the\ntimeout and therefor the error message is supressed.\n\nChange it to predecrement, so the error message is emitted.\n\n[ tglx: Massaged changelog ]\n\nFixes: a2c225101234 (\"irqchip: gic-v3: Refactor gic_enable_redist to support both enabling and disabling\")\nSigned-off-by: Dan Carpenter <dan.carpenter@oracle.com>\nAcked-by: Sudeep Holla <sudeep.holla@arm.com>\nCc: Marc Zyngier <marc.zyngier@arm.com>\nCc: kernel-janitors@vger.kernel.org\nCc: Jason Cooper <jason@lakedaemon.net>\nCc: stable@vger.kernel.org\nLink: http://lkml.kernel.org/r/20161014072534.GA15168@mwanda\nSigned-off-by: Thomas Gleixner <tglx@linutronix.de>\nSigned-off-by: Sasha Levin <alexander.levin@verizon.com>","distinct":true,"url":"https://api.github.com/repos/MyProjectIsAwesome/android_kernel_xiaomi_msm8953/commits/d5ec3044325efc9783c2137a3354dcdd5cf64895"},{"sha":"5394406189711443e3474201969065a2f746ff2d","author":{"name":"Ulf Hansson","email":"fe47b31f388f85ce6ddf64bf3a0cf6b46077d0e6@linaro.org"},"message":"mmc: rtsx_usb_sdmmc: Avoid keeping the device runtime resumed when unused\n\n[ Upstream commit 31cf742f515c275d22843c4c756e048d2b6d716c ]\n\nThe rtsx_usb_sdmmc driver may bail out in its ->set_ios() callback when no\nSD card is inserted. This is wrong, as it could cause the device to remain\nruntime resumed when it's unused. Fix this behaviour.\n\nTested-by: Ritesh Raj Sarraf <rrs@researchut.com>\nCc: <stable@vger.kernel.org>\nCc: Alan Stern <stern@rowland.harvard.edu>\nSigned-off-by: Ulf Hansson <ulf.hansson@linaro.org>\nSigned-off-by: Sasha Levin <alexander.levin@verizon.com>","distinct":true,"url":"https://api.github.com/repos/MyProjectIsAwesome/android_kernel_xiaomi_msm8953/commits/5394406189711443e3474201969065a2f746ff2d"},{"sha":"db9ff5cb0a96314e74cde370fdf380c2d3ed8883","author":{"name":"Ulf Hansson","email":"fe47b31f388f85ce6ddf64bf3a0cf6b46077d0e6@linaro.org"},"message":"mmc: rtsx_usb_sdmmc: Handle runtime PM while changing the led\n\n[ Upstream commit 4f48aa7a11bfed9502a7c85a5b68cd40ea827f73 ]\n\nAccesses of the rtsx sdmmc's parent device, which is the rtsx usb device,\nmust be done when it's runtime resumed. Currently this isn't case when\nchanging the led, so let's fix this by adding a pm_runtime_get_sync() and\na pm_runtime_put() around those operations.\n\nReported-by: Ritesh Raj Sarraf <rrs@researchut.com>\nTested-by: Ritesh Raj Sarraf <rrs@researchut.com>\nCc: <stable@vger.kernel.org>\nCc: Alan Stern <stern@rowland.harvard.edu>\nSigned-off-by: Ulf Hansson <ulf.hansson@linaro.org>\nSigned-off-by: Sasha Levin <alexander.levin@verizon.com>","distinct":true,"url":"https://api.github.com/repos/MyProjectIsAwesome/android_kernel_xiaomi_msm8953/commits/db9ff5cb0a96314e74cde370fdf380c2d3ed8883"},{"sha":"b0f0b650f332cdf04b1d88911b0fce3207c52821","author":{"name":"Alan Stern","email":"75ea6bb7bfc1186f92d26164de5f9268c9a45b59@rowland.harvard.edu"},"message":"memstick: rtsx_usb_ms: Runtime resume the device when polling for cards\n\n[ Upstream commit 796aa46adf1d90eab36ae06a42e6d3f10b28a75c ]\n\nAccesses to the rtsx usb device, which is the parent of the rtsx memstick\ndevice, must not be done unless it's runtime resumed.\n\nTherefore when the rtsx_usb_ms driver polls for inserted memstick cards,\nlet's add pm_runtime_get|put*() to make sure accesses is done when the\nrtsx usb device is runtime resumed.\n\nReported-by: Ritesh Raj Sarraf <rrs@researchut.com>\nTested-by: Ritesh Raj Sarraf <rrs@researchut.com>\nSigned-off-by: Alan Stern <stern@rowland.harvard.edu>\nCc: <stable@vger.kernel.org>\nSigned-off-by: Ulf Hansson <ulf.hansson@linaro.org>\nSigned-off-by: Sasha Levin <alexander.levin@verizon.com>","distinct":true,"url":"https://api.github.com/repos/MyProjectIsAwesome/android_kernel_xiaomi_msm8953/commits/b0f0b650f332cdf04b1d88911b0fce3207c52821"},{"sha":"342f582f49e76a1bbe6cb390adf49ea510438be0","author":{"name":"Ulf Hansson","email":"fe47b31f388f85ce6ddf64bf3a0cf6b46077d0e6@linaro.org"},"message":"memstick: rtsx_usb_ms: Manage runtime PM when accessing the device\n\n[ Upstream commit 9158cb29e7c2f10dd325eb1589f0fe745a271257 ]\n\nAccesses to the rtsx usb device, which is the parent of the rtsx memstick\ndevice, must not be done unless it's runtime resumed. This is currently not\nthe case and it could trigger various errors.\n\nFix this by properly deal with runtime PM in this regards. This means\nmaking sure the device is runtime resumed, when serving requests via the\n->request() callback or changing settings via the ->set_param() callbacks.\n\nCc: <stable@vger.kernel.org>\nCc: Ritesh Raj Sarraf <rrs@researchut.com>\nCc: Alan Stern <stern@rowland.harvard.edu>\nSigned-off-by: Ulf Hansson <ulf.hansson@linaro.org>\nSigned-off-by: Sasha Levin <alexander.levin@verizon.com>","distinct":true,"url":"https://api.github.com/repos/MyProjectIsAwesome/android_kernel_xiaomi_msm8953/commits/342f582f49e76a1bbe6cb390adf49ea510438be0"},{"sha":"779066c92f395541bfcf8bb6f62a74592d9408e0","author":{"name":"Stefan Tauner","email":"61643f08f3033edc23814c85a8f0e8c5c553befa@technikum-wien.at"},"message":"USB: serial: ftdi_sio: add support for Infineon TriBoard TC2X7\n\n[ Upstream commit ca006f785fbfd7a5c901900bd3fe2b26e946a1ee ]\n\nThis adds support to ftdi_sio for the Infineon TriBoard TC2X7\nengineering board for first-generation Aurix SoCs with Tricore CPUs.\nMere addition of the device IDs does the job.\n\nSigned-off-by: Stefan Tauner <stefan.tauner@technikum-wien.at>\nCc: stable <stable@vger.kernel.org>\nSigned-off-by: Johan Hovold <johan@kernel.org>\nSigned-off-by: Sasha Levin <alexander.levin@verizon.com>","distinct":true,"url":"https://api.github.com/repos/MyProjectIsAwesome/android_kernel_xiaomi_msm8953/commits/779066c92f395541bfcf8bb6f62a74592d9408e0"},{"sha":"7a3f813379c1f388248d1c9e0f24ba5dbabf155c","author":{"name":"Jan Kara","email":"596727c8a0ea4db3ba2ceceedccbacd3d7b371b8@suse.cz"},"message":"isofs: Do not return EACCES for unknown filesystems\n\n[ Upstream commit a2ed0b391dd9c3ef1d64c7c3e370f4a5ffcd324a ]\n\nWhen isofs_mount() is called to mount a device read-write, it returns\nEACCES even before it checks that the device actually contains an isofs\nfilesystem. This may confuse mount(8) which then tries to mount all\nsubsequent filesystem types in read-only mode.\n\nFix the problem by returning EACCES only once we verify that the device\nindeed contains an iso9660 filesystem.\n\nCC: stable@vger.kernel.org\nFixes: 17b7f7cf58926844e1dd40f5eb5348d481deca6a\nReported-by: Kent Overstreet <kent.overstreet@gmail.com>\nReported-by: Karel Zak <kzak@redhat.com>\nSigned-off-by: Jan Kara <jack@suse.cz>\nSigned-off-by: Sasha Levin <alexander.levin@verizon.com>","distinct":true,"url":"https://api.github.com/repos/MyProjectIsAwesome/android_kernel_xiaomi_msm8953/commits/7a3f813379c1f388248d1c9e0f24ba5dbabf155c"},{"sha":"26508e9b3a3b764d9782c62f549032cd5ae3da41","author":{"name":"Frederic Barrat","email":"c90240987c583ac0802fbeb88cb1684edc683e18@linux.vnet.ibm.com"},"message":"powerpc/mm: Prevent unlikely crash in copro_calculate_slb()\n\n[ Upstream commit d2cf909cda5f8c5609cb7ed6cda816c3e15528c7 ]\n\nIf a cxl adapter faults on an invalid address for a kernel context, we\nmay enter copro_calculate_slb() with a NULL mm pointer (kernel\ncontext) and an effective address which looks like a user\naddress. Which will cause a crash when dereferencing mm. It is clearly\nan AFU bug, but there's no reason to crash either. So return an error,\nso that cxl can ack the interrupt with an address error.\n\nFixes: 73d16a6e0e51 (\"powerpc/cell: Move data segment faulting code out of cell platform\")\nCc: stable@vger.kernel.org # v3.18+\nSigned-off-by: Frederic Barrat <fbarrat@linux.vnet.ibm.com>\nAcked-by: Ian Munsie <imunsie@au1.ibm.com>\nSigned-off-by: Michael Ellerman <mpe@ellerman.id.au>\nSigned-off-by: Sasha Levin <alexander.levin@verizon.com>","distinct":true,"url":"https://api.github.com/repos/MyProjectIsAwesome/android_kernel_xiaomi_msm8953/commits/26508e9b3a3b764d9782c62f549032cd5ae3da41"},{"sha":"cb96477abc219e4885aea7c17a62b792c643d0f0","author":{"name":"Richard Weinberger","email":"320bca71fc381a4a025636043ca86e734e31cf8b@nod.at"},"message":"ubifs: Fix xattr_names length in exit paths\n\n[ Upstream commit 843741c5778398ea67055067f4cc65ae6c80ca0e ]\n\nWhen the operation fails we also have to undo the changes\nwe made to ->xattr_names. Otherwise listxattr() will report\nwrong lengths.\n\nCc: stable@vger.kernel.org\nSigned-off-by: Richard Weinberger <richard@nod.at>\nSigned-off-by: Sasha Levin <alexander.levin@verizon.com>","distinct":true,"url":"https://api.github.com/repos/MyProjectIsAwesome/android_kernel_xiaomi_msm8953/commits/cb96477abc219e4885aea7c17a62b792c643d0f0"},{"sha":"bfe4426d3050b7ad278d276e4fc71cfcfa58c3f8","author":{"name":"Dinesh Israni","email":"1802f06ecf7ae79f62f5a1f3aef332becdc5d8f5@datera.io"},"message":"target: Don't override EXTENDED_COPY xcopy_pt_cmd SCSI status code\n\n[ Upstream commit 926317de33998c112c5510301868ea9aa34097e2 ]\n\nThis patch addresses a bug where a local EXTENDED_COPY WRITE or READ\nbackend I/O request would always return SAM_STAT_CHECK_CONDITION,\neven if underlying xcopy_pt_cmd->se_cmd generated a different\nSCSI status code.\n\nESX host environments expect to hit SAM_STAT_RESERVATION_CONFLICT\nfor certain scenarios, and SAM_STAT_CHECK_CONDITION results in\nnon-retriable status for these cases.\n\nTested on v4.1.y with ESX v5.5u2+ with local IBLOCK backend copy.\n\nReported-by: Nixon Vincent <nixon.vincent@calsoftinc.com>\nTested-by: Nixon Vincent <nixon.vincent@calsoftinc.com>\nCc: Nixon Vincent <nixon.vincent@calsoftinc.com>\nTested-by: Dinesh Israni <ddi@datera.io>\nSigned-off-by: Dinesh Israni <ddi@datera.io>\nCc: Dinesh Israni <ddi@datera.io>\nCc: stable@vger.kernel.org # 3.14+\nSigned-off-by: Nicholas Bellinger <nab@linux-iscsi.org>\nSigned-off-by: Sasha Levin <alexander.levin@verizon.com>","distinct":true,"url":"https://api.github.com/repos/MyProjectIsAwesome/android_kernel_xiaomi_msm8953/commits/bfe4426d3050b7ad278d276e4fc71cfcfa58c3f8"},{"sha":"a622186586e2b11763cd47101648cbb56cfa001d","author":{"name":"Darrick J. Wong","email":"206af32863b9fd2fc412cf38757e7321a0f2bd37@oracle.com"},"message":"libxfs: clean up _calc_dquots_per_chunk\n\n[ Upstream commit 58d789678546d46d7bbd809dd7dab417c0f23655 ]\n\nThe function xfs_calc_dquots_per_chunk takes a parameter in units\nof basic blocks.  The kernel seems to get the units wrong, but\nuserspace got 'fixed' by commenting out the unnecessary conversion.\nFix both.\n\ncc: <stable@vger.kernel.org>\nSigned-off-by: Darrick J. Wong <darrick.wong@oracle.com>\nReviewed-by: Eric Sandeen <sandeen@redhat.com>\nSigned-off-by: Dave Chinner <david@fromorbit.com>\nSigned-off-by: Sasha Levin <alexander.levin@verizon.com>","distinct":true,"url":"https://api.github.com/repos/MyProjectIsAwesome/android_kernel_xiaomi_msm8953/commits/a622186586e2b11763cd47101648cbb56cfa001d"}]}
{"actor":{"display_login":"davidtrpcevski"}}