{"push_id":838409578,"size":205,"distinct_size":205,"ref":"refs/heads/rpi-4.1.y","head":"e9c356a2c18787d356567f24e7879875d7337efc","before":"b74df9228c27f55361c065bc5dbfba88861cc771","commits":[{"sha":"10e259a1ec2e4b39e1a9d49d51dbd152a8e5f3c3","author":{"email":"05c339d9f3779bdd0faff6d34f6b66b68983e570@tieto.com","name":"Marek Majtyka"},"message":"arm: KVM: Fix incorrect device to IPA mapping\n\ncommit ca09f02f122b2ecb0f5ddfc5fd47b29ed657d4fd upstream.\n\nA critical bug has been found in device memory stage1 translation for\nVMs with more then 4GB of address space. Once vm_pgoff size is smaller\nthen pa (which is true for LPAE case, u32 and u64 respectively) some\nmore significant bits of pa may be lost as a shift operation is performed\non u32 and later cast onto u64.\n\nExample: vm_pgoff(u32)=0x00210030, PAGE_SHIFT=12\n        expected pa(u64):   0x0000002010030000\n        produced pa(u64):   0x0000000010030000\n\nThe fix is to change the order of operations (casting first onto phys_addr_t\nand then shifting).\n\nReviewed-by: Marc Zyngier <marc.zyngier@arm.com>\n[maz: fixed changelog and patch formatting]\nSigned-off-by: Marek Majtyka <marek.majtyka@tieto.com>\nSigned-off-by: Marc Zyngier <marc.zyngier@arm.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/raspberrypi/linux/commits/10e259a1ec2e4b39e1a9d49d51dbd152a8e5f3c3"},{"sha":"35f5af9cb6994ee92e27b2cd5936142337983284","author":{"email":"bdcdf23be75b976d8e1ad9f82e6b264941889f50@hotmail.com","name":"Wanpeng Li"},"message":"KVM: vmx: fix VPID is 0000H in non-root operation\n\ncommit 04bb92e4b4cf06a66889d37b892b78f926faa9d4 upstream.\n\nReference SDM 28.1:\n\nThe current VPID is 0000H in the following situations:\n- Outside VMX operation. (This includes operation in system-management\n  mode under the default treatment of SMIs and SMM with VMX operation;\n  see Section 34.14.)\n- In VMX root operation.\n- In VMX non-root operation when the “enable VPID” VM-execution control\n  is 0.\n\nThe VPID should never be 0000H in non-root operation when \"enable VPID\"\nVM-execution control is 1. However, commit 34a1cd60 (\"kvm: x86: vmx:\nmove some vmx setting from vmx_init() to hardware_setup()\") remove the\ncodes which reserve 0000H for VMX root operation.\n\nThis patch fix it by again reserving 0000H for VMX root operation.\n\nFixes: 34a1cd60d17f62c1f077c1478a6c2ca8c3d17af4\nReported-by: Wincy Van <fanwenyi0529@gmail.com>\nSigned-off-by: Wanpeng Li <wanpeng.li@hotmail.com>\nSigned-off-by: Paolo Bonzini <pbonzini@redhat.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/raspberrypi/linux/commits/35f5af9cb6994ee92e27b2cd5936142337983284"},{"sha":"87f3ae1f34a06fb5296a4b0d763737171c3f2d65","author":{"email":"808efd45667dbd241e4e026b5673172419ecb43e@redhat.com","name":"Jason Wang"},"message":"kvm: don't try to register to KVM_FAST_MMIO_BUS for non mmio eventfd\n\ncommit 8453fecbecae26edb3f278627376caab05d9a88d upstream.\n\nWe only want zero length mmio eventfd to be registered on\nKVM_FAST_MMIO_BUS. So check this explicitly when arg->len is zero to\nmake sure this.\n\nCc: Gleb Natapov <gleb@kernel.org>\nCc: Paolo Bonzini <pbonzini@redhat.com>\nSigned-off-by: Jason Wang <jasowang@redhat.com>\nReviewed-by: Cornelia Huck <cornelia.huck@de.ibm.com>\nSigned-off-by: Paolo Bonzini <pbonzini@redhat.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/raspberrypi/linux/commits/87f3ae1f34a06fb5296a4b0d763737171c3f2d65"},{"sha":"989bbb3a4c25d9e21a791a4d23cf24610270db63","author":{"email":"808efd45667dbd241e4e026b5673172419ecb43e@redhat.com","name":"Jason Wang"},"message":"kvm: fix zero length mmio searching\n\ncommit 8f4216c7d28976f7ec1b2bcbfa0a9f787133c45e upstream.\n\nCurrently, if we had a zero length mmio eventfd assigned on\nKVM_MMIO_BUS. It will never be found by kvm_io_bus_cmp() since it\nalways compares the kvm_io_range() with the length that guest\nwrote. This will cause e.g for vhost, kick will be trapped by qemu\nuserspace instead of vhost. Fixing this by using zero length if an\niodevice is zero length.\n\nCc: Gleb Natapov <gleb@kernel.org>\nCc: Paolo Bonzini <pbonzini@redhat.com>\nSigned-off-by: Jason Wang <jasowang@redhat.com>\nReviewed-by: Cornelia Huck <cornelia.huck@de.ibm.com>\nSigned-off-by: Paolo Bonzini <pbonzini@redhat.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/raspberrypi/linux/commits/989bbb3a4c25d9e21a791a4d23cf24610270db63"},{"sha":"348a20a23f03953f1a0ab57b55cd9079084b14f4","author":{"email":"808efd45667dbd241e4e026b5673172419ecb43e@redhat.com","name":"Jason Wang"},"message":"kvm: factor out core eventfd assign/deassign logic\n\ncommit 85da11ca587c8eb73993a1b503052391a73586f9 upstream.\n\nThis patch factors out core eventfd assign/deassign logic and leaves\nthe argument checking and bus index selection to callers.\n\nCc: Gleb Natapov <gleb@kernel.org>\nCc: Paolo Bonzini <pbonzini@redhat.com>\nSigned-off-by: Jason Wang <jasowang@redhat.com>\nReviewed-by: Cornelia Huck <cornelia.huck@de.ibm.com>\nSigned-off-by: Paolo Bonzini <pbonzini@redhat.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/raspberrypi/linux/commits/348a20a23f03953f1a0ab57b55cd9079084b14f4"},{"sha":"c286128ffc7ffaeaf5cf8d7b0b64c9883160a636","author":{"email":"808efd45667dbd241e4e026b5673172419ecb43e@redhat.com","name":"Jason Wang"},"message":"kvm: fix double free for fast mmio eventfd\n\ncommit eefd6b06b17c5478e7c24bea6f64beaa2c431ca6 upstream.\n\nWe register wildcard mmio eventfd on two buses, once for KVM_MMIO_BUS\nand once on KVM_FAST_MMIO_BUS but with a single iodev\ninstance. This will lead to an issue: kvm_io_bus_destroy() knows\nnothing about the devices on two buses pointing to a single dev. Which\nwill lead to double free[1] during exit. Fix this by allocating two\ninstances of iodevs then registering one on KVM_MMIO_BUS and another\non KVM_FAST_MMIO_BUS.\n\nCPU: 1 PID: 2894 Comm: qemu-system-x86 Not tainted 3.19.0-26-generic #28-Ubuntu\nHardware name: LENOVO 2356BG6/2356BG6, BIOS G7ET96WW (2.56 ) 09/12/2013\ntask: ffff88009ae0c4b0 ti: ffff88020e7f0000 task.ti: ffff88020e7f0000\nRIP: 0010:[<ffffffffc07e25d8>]  [<ffffffffc07e25d8>] ioeventfd_release+0x28/0x60 [kvm]\nRSP: 0018:ffff88020e7f3bc8  EFLAGS: 00010292\nRAX: dead000000200200 RBX: ffff8801ec19c900 RCX: 000000018200016d\nRDX: ffff8801ec19cf80 RSI: ffffea0008bf1d40 RDI: ffff8801ec19c900\nRBP: ffff88020e7f3bd8 R08: 000000002fc75a01 R09: 000000018200016d\nR10: ffffffffc07df6ae R11: ffff88022fc75a98 R12: ffff88021e7cc000\nR13: ffff88021e7cca48 R14: ffff88021e7cca50 R15: ffff8801ec19c880\nFS:  00007fc1ee3e6700(0000) GS:ffff88023e240000(0000) knlGS:0000000000000000\nCS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\nCR2: 00007f8f389d8000 CR3: 000000023dc13000 CR4: 00000000001427e0\nStack:\nffff88021e7cc000 0000000000000000 ffff88020e7f3be8 ffffffffc07e2622\nffff88020e7f3c38 ffffffffc07df69a ffff880232524160 ffff88020e792d80\n 0000000000000000 ffff880219b78c00 0000000000000008 ffff8802321686a8\nCall Trace:\n[<ffffffffc07e2622>] ioeventfd_destructor+0x12/0x20 [kvm]\n[<ffffffffc07df69a>] kvm_put_kvm+0xca/0x210 [kvm]\n[<ffffffffc07df818>] kvm_vcpu_release+0x18/0x20 [kvm]\n[<ffffffff811f69f7>] __fput+0xe7/0x250\n[<ffffffff811f6bae>] ____fput+0xe/0x10\n[<ffffffff81093f04>] task_work_run+0xd4/0xf0\n[<ffffffff81079358>] do_exit+0x368/0xa50\n[<ffffffff81082c8f>] ? recalc_sigpending+0x1f/0x60\n[<ffffffff81079ad5>] do_group_exit+0x45/0xb0\n[<ffffffff81085c71>] get_signal+0x291/0x750\n[<ffffffff810144d8>] do_signal+0x28/0xab0\n[<ffffffff810f3a3b>] ? do_futex+0xdb/0x5d0\n[<ffffffff810b7028>] ? __wake_up_locked_key+0x18/0x20\n[<ffffffff810f3fa6>] ? SyS_futex+0x76/0x170\n[<ffffffff81014fc9>] do_notify_resume+0x69/0xb0\n[<ffffffff817cb9af>] int_signal+0x12/0x17\nCode: 5d c3 90 0f 1f 44 00 00 55 48 89 e5 53 48 89 fb 48 83 ec 08 48 8b 7f 20 e8 06 d6 a5 c0 48 8b 43 08 48 8b 13 48 89 df 48 89 42 08 <48> 89 10 48 b8 00 01 10 00 00\n RIP  [<ffffffffc07e25d8>] ioeventfd_release+0x28/0x60 [kvm]\n RSP <ffff88020e7f3bc8>\n\nCc: Gleb Natapov <gleb@kernel.org>\nCc: Paolo Bonzini <pbonzini@redhat.com>\nSigned-off-by: Jason Wang <jasowang@redhat.com>\nReviewed-by: Cornelia Huck <cornelia.huck@de.ibm.com>\nSigned-off-by: Paolo Bonzini <pbonzini@redhat.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/raspberrypi/linux/commits/c286128ffc7ffaeaf5cf8d7b0b64c9883160a636"},{"sha":"a5b48a8ed5004bc857cd15b4a5e4f93773251874","author":{"email":"a16cc0c82647c52d401177f8e50567df5499e36c@arm.com","name":"Marc Zyngier"},"message":"arm: KVM: Disable virtual timer even if the guest is not using it\n\ncommit 688bc577ac42ae3d07c889a1f0a72f0b23763d58 upstream.\n\nWhen running a guest with the architected timer disabled (with QEMU and\nthe kernel_irqchip=off option, for example), it is important to make\nsure the timer gets turned off. Otherwise, the guest may try to\nenable it anyway, leading to a screaming HW interrupt.\n\nThe fix is to unconditionally turn off the virtual timer on guest\nexit.\n\nSigned-off-by: Marc Zyngier <marc.zyngier@arm.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/raspberrypi/linux/commits/a5b48a8ed5004bc857cd15b4a5e4f93773251874"},{"sha":"ffd269ee140151a04f33731a7160b571186d5bba","author":{"email":"9e65be74847981e55b2564b6266c57d86d3bac05@redhat.com","name":"Thomas Huth"},"message":"KVM: PPC: Book3S: Take the kvm->srcu lock in kvmppc_h_logical_ci_load/store()\n\ncommit 3eb4ee68254235e4f47bc0410538fcdaede39589 upstream.\n\nAccess to the kvm->buses (like with the kvm_io_bus_read() and -write()\nfunctions) has to be protected via the kvm->srcu lock.\nThe kvmppc_h_logical_ci_load() and -store() functions are missing\nthis lock so far, so let's add it there, too.\nThis fixes the problem that the kernel reports \"suspicious RCU usage\"\nwhen lock debugging is enabled.\n\nFixes: 99342cf8044420eebdf9297ca03a14cb6a7085a1\nSigned-off-by: Thomas Huth <thuth@redhat.com>\nSigned-off-by: Paul Mackerras <paulus@samba.org>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/raspberrypi/linux/commits/ffd269ee140151a04f33731a7160b571186d5bba"},{"sha":"6d9cc6c15c8a1019263ab8a85eeb38dcf3c3c9d6","author":{"email":"c13571dbffa0eb89c7f8eebdce482897b0f5a685@linux.vnet.ibm.com","name":"Gautham R. Shenoy"},"message":"KVM: PPC: Book3S HV: Pass the correct trap argument to kvmhv_commence_exit\n\ncommit 7e022e717f54897e396504306d0c9b61452adf4e upstream.\n\nIn guest_exit_cont we call kvmhv_commence_exit which expects the trap\nnumber as the argument. However r3 doesn't contain the trap number at\nthis point and as a result we would be calling the function with a\nspurious trap number.\n\nFix this by copying r12 into r3 before calling kvmhv_commence_exit as\nr12 contains the trap number.\n\nFixes: eddb60fb1443\nSigned-off-by: Gautham R. Shenoy <ego@linux.vnet.ibm.com>\nSigned-off-by: Paul Mackerras <paulus@samba.org>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/raspberrypi/linux/commits/6d9cc6c15c8a1019263ab8a85eeb38dcf3c3c9d6"},{"sha":"a5428d82f04e051e9c0d1da2b353c21be01600c7","author":{"email":"33837adfb53316eae44aad04041e1240088d76fd@linaro.org","name":"John Stultz"},"message":"time: Fix timekeeping_freqadjust()'s incorrect use of abs() instead of abs64()\n\ncommit 2619d7e9c92d524cb155ec89fd72875321512e5b upstream.\n\nThe internal clocksteering done for fine-grained error\ncorrection uses a logarithmic approximation, so any time\nadjtimex() adjusts the clock steering, timekeeping_freqadjust()\nquickly approximates the correct clock frequency over a series\nof ticks.\n\nUnfortunately, the logic in timekeeping_freqadjust(), introduced\nin commit:\n\n  dc491596f639 (\"timekeeping: Rework frequency adjustments to work better w/ nohz\")\n\nused the abs() function with a s64 error value to calculate the\nsize of the approximated adjustment to be made.\n\nPer include/linux/kernel.h:\n\n  \"abs() should not be used for 64-bit types (s64, u64, long long) - use abs64()\".\n\nThus on 32-bit platforms, this resulted in the clocksteering to\ntake a quite dampended random walk trying to converge on the\nproper frequency, which caused the adjustments to be made much\nslower then intended (most easily observed when large\nadjustments are made).\n\nThis patch fixes the issue by using abs64() instead.\n\nReported-by: Nuno Gonçalves <nunojpg@gmail.com>\nTested-by: Nuno Goncalves <nunojpg@gmail.com>\nSigned-off-by: John Stultz <john.stultz@linaro.org>\nCc: Linus Torvalds <torvalds@linux-foundation.org>\nCc: Miroslav Lichvar <mlichvar@redhat.com>\nCc: Peter Zijlstra <peterz@infradead.org>\nCc: Prarit Bhargava <prarit@redhat.com>\nCc: Richard Cochran <richardcochran@gmail.com>\nCc: Thomas Gleixner <tglx@linutronix.de>\nLink: http://lkml.kernel.org/r/1441840051-20244-1-git-send-email-john.stultz@linaro.org\nSigned-off-by: Ingo Molnar <mingo@kernel.org>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/raspberrypi/linux/commits/a5428d82f04e051e9c0d1da2b353c21be01600c7"},{"sha":"e77fb714b612371276f733947ad776ccf1f7aefe","author":{"email":"b7d524d2f5cc5aebadb6b92b08d3ab26911cde33@redhat.com","name":"Andy Grover"},"message":"target/iscsi: Fix np_ip bracket issue by removing np_ip\n\ncommit 76c28f1fcfeb42b47f798fe498351ee1d60086ae upstream.\n\nRevert commit 1997e6259, which causes double brackets on ipv6\ninaddr_any addresses.\n\nSince we have np_sockaddr, if we need a textual representation we can\nuse \"%pISc\".\n\nChange iscsit_add_network_portal() and iscsit_add_np() signatures to remove\n*ip_str parameter.\n\nFix and extend some comments earlier in the function.\n\nTested to work for :: and ::1 via iscsiadm, previously :: failed, see\nhttps://bugzilla.redhat.com/show_bug.cgi?id=1249107 .\n\nSigned-off-by: Andy Grover <agrover@redhat.com>\nSigned-off-by: Nicholas Bellinger <nab@linux-iscsi.org>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/raspberrypi/linux/commits/e77fb714b612371276f733947ad776ccf1f7aefe"},{"sha":"4863a3f3a6fee85504d78254de97aea26e0c661c","author":{"email":"829500b200af6c2a0eca4dfd5c388e6b8fbe8dc6@suse.com","name":"Michal Hocko"},"message":"scsi: fix scsi_error_handler vs. scsi_host_dev_release race\n\ncommit 537b604c8b3aa8b96fe35f87dd085816552e294c upstream.\n\nb9d5c6b7ef57 (\"[SCSI] cleanup setting task state in\nscsi_error_handler()\") has introduced a race between scsi_error_handler\nand scsi_host_dev_release resulting in the hang when the device goes\naway because scsi_error_handler might miss a wake up:\n\nCPU0\t\t\t\t\tCPU1\nscsi_error_handler\t\t\tscsi_host_dev_release\n  \t\t\t\t\t  kthread_stop()\n  kthread_should_stop()\n    test_bit(KTHREAD_SHOULD_STOP)\n\t\t\t\t\t    set_bit(KTHREAD_SHOULD_STOP)\n\t\t\t\t\t    wake_up_process()\n\t\t\t\t\t    wait_for_completion()\n\n  set_current_state(TASK_INTERRUPTIBLE)\n  schedule()\n\nThe most straightforward solution seems to be to invert the ordering of\nthe set_current_state and kthread_should_stop.\n\nThe issue has been noticed during reboot test on a 3.0 based kernel but\nthe current code seems to be affected in the same way.\n\n[jejb: additional comment added]\nReported-and-debugged-by: Mike Mayer <Mike.Meyer@teradata.com>\nSigned-off-by: Michal Hocko <mhocko@suse.com>\nReviewed-by: Dan Williams <dan.j.williams@intel.com>\nReviewed-by: Hannes Reinecke <hare@suse.de>\nSigned-off-by: James Bottomley <JBottomley@Odin.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/raspberrypi/linux/commits/4863a3f3a6fee85504d78254de97aea26e0c661c"},{"sha":"57bc4a2d5be815c3b917fdf54a2013e8df565e42","author":{"email":"978acd1567d5598152161fdf8bf3ca568f950c9b@linux-iscsi.org","name":"Nicholas Bellinger"},"message":"target: Attach EXTENDED_COPY local I/O descriptors to xcopy_pt_sess\n\ncommit 4416f89b8cfcb794d040fc3b68e5fb159b7d8d02 upstream.\n\nThis patch is a >= v4.1 regression bug-fix where control CDB\nemulation logic in commit 38b57f82 now expects a se_cmd->se_sess\npointer to exist when determining T10-PI support is to be exposed\nfor initiator host ports.\n\nTo address this bug, go ahead and add locally generated se_cmd\ndescriptors for copy-offload block-copy to it's own stand-alone\nse_session nexus, while the parent EXTENDED_COPY se_cmd descriptor\nremains associated with it's originating se_cmd->se_sess nexus.\n\nNote a valid se_cmd->se_sess is also required for future support\nof WRITE_INSERT and READ_STRIP software emulation when submitting\nbackend I/O to se_device that exposes T10-PI suport.\n\nReported-by: Alex Gorbachev <ag@iss-integration.com>\nTested-by: Alex Gorbachev <ag@iss-integration.com>\nCc: \"Martin K. Petersen\" <martin.petersen@oracle.com>\nCc: Hannes Reinecke <hare@suse.de>\nCc: Christoph Hellwig <hch@lst.de>\nCc: Doug Gilbert <dgilbert@interlog.com>\nSigned-off-by: Nicholas Bellinger <nab@linux-iscsi.org>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/raspberrypi/linux/commits/57bc4a2d5be815c3b917fdf54a2013e8df565e42"},{"sha":"060f45157d2a43dffd51a10e9707336f58ae34b7","author":{"email":"274d60a4a21eeeaf59b30c36f9b7b6d5a585a612@mellanox.com","name":"Jenny Derzhavetz"},"message":"iser-target: remove command with state ISTATE_REMOVE\n\ncommit a4c15cd957cbd728f685645de7a150df5912591a upstream.\n\nAs documented in iscsit_sequence_cmd:\n/*\n * Existing callers for iscsit_sequence_cmd() will silently\n * ignore commands with CMDSN_LOWER_THAN_EXP, so force this\n * return for CMDSN_MAXCMDSN_OVERRUN as well..\n */\n\nWe need to silently finish a command when it's in ISTATE_REMOVE.\nThis fixes an teardown hang we were seeing where a mis-behaved\ninitiator (triggered by allocation error injections) sent us a\ncmdsn which was lower than expected.\n\nSigned-off-by: Jenny Derzhavetz <jennyf@mellanox.com>\nSigned-off-by: Sagi Grimberg <sagig@mellanox.com>\nSigned-off-by: Nicholas Bellinger <nab@linux-iscsi.org>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/raspberrypi/linux/commits/060f45157d2a43dffd51a10e9707336f58ae34b7"},{"sha":"b6ac3aee1c73d5b107ae6ec6e3715b39db782781","author":{"email":"274d60a4a21eeeaf59b30c36f9b7b6d5a585a612@mellanox.com","name":"Jenny Derzhavetz"},"message":"iser-target: Put the reference on commands waiting for unsol data\n\ncommit 3e03c4b01da3e6a5f3081eb0aa252490fe83e352 upstream.\n\nThe iscsi target core teardown sequence calls wait_conn for\nall active commands to finish gracefully by:\n- move the queue-pair to error state\n- drain all the completions\n- wait for the core to finish handling all session commands\n\nHowever, when tearing down a session while there are sequenced\ncommands that are still waiting for unsolicited data outs, we can\nblock forever as these are missing an extra reference put.\n\nWe basically need the equivalent of iscsit_free_queue_reqs_for_conn()\nwhich is called after wait_conn has returned. Address this by an\nexplicit walk on conn_cmd_list and put the extra reference.\n\nSigned-off-by: Jenny Derzhavetz <jennyf@mellanox.com>\nSigned-off-by: Sagi Grimberg <sagig@mellanox.com>\nSigned-off-by: Nicholas Bellinger <nab@linux-iscsi.org>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/raspberrypi/linux/commits/b6ac3aee1c73d5b107ae6ec6e3715b39db782781"},{"sha":"35afa65642a9a88c81913377b93a3a66220f8b9d","author":{"email":"978acd1567d5598152161fdf8bf3ca568f950c9b@linux-iscsi.org","name":"Nicholas Bellinger"},"message":"target: Fix v4.1 UNIT_ATTENTION se_node_acl->device_list[] NULL pointer\n\nThis patch fixes a v4.1 only regression bug as reported by Martin\nwhere UNIT_ATTENTION checking for pre v4.2-rc1 RCU conversion code\nlegacy se_node_acl->device_list[] was hitting a NULL pointer\ndereference in:\n\n[ 1858.639654] CPU: 2 PID: 1293 Comm: kworker/2:1 Tainted: G          I 4.1.6-fixxcopy+ #1\n[ 1858.639699] Hardware name: Dell Inc. PowerEdge R410/0N83VF, BIOS 1.11.0 07/20/2012\n[ 1858.639747] Workqueue: xcopy_wq target_xcopy_do_work [target_core_mod]\n[ 1858.639782] task: ffff880036f0cbe0 ti: ffff880317940000 task.ti: ffff880317940000\n[ 1858.639822] RIP: 0010:[<ffffffffa01d3774>]  [<ffffffffa01d3774>] target_scsi3_ua_check+0x24/0x60 [target_core_mod]\n[ 1858.639884] RSP: 0018:ffff880317943ce0  EFLAGS: 00010282\n[ 1858.639913] RAX: 0000000000000000 RBX: ffff880317943dc0 RCX: 0000000000000000\n[ 1858.639950] RDX: 0000000000000000 RSI: ffff880317943dd0 RDI: ffff88030eaee408\n[ 1858.639987] RBP: ffff88030eaee408 R08: 0000000000000001 R09: 0000000000000001\n[ 1858.640025] R10: 0000000000000000 R11: 00000000000706e0 R12: ffff880315e0a000\n[ 1858.640062] R13: ffff88030eaee408 R14: 0000000000000001 R15: ffff88030eaee408\n[ 1858.640100] FS:  0000000000000000(0000) GS:ffff880322e80000(0000) knlGS:0000000000000000\n[ 1858.640143] CS:  0010 DS: 0000 ES: 0000 CR0: 000000008005003b\n[ 1858.640173] CR2: 0000000000000000 CR3: 000000000180d000 CR4: 00000000000006e0\n[ 1858.640210] Stack:\n[ 1858.640223]  ffffffffa01cadfa ffff88030eaee400 ffff880318e7c340 ffff880315e0a000\n[ 1858.640267]  ffffffffa01d8c25 ffff8800cae809e0 0000000000000400 0000000000000400\n[ 1858.640310]  ffff880318e7c3d0 0000000006b75800 0000000000080000 ffff88030eaee400\n[ 1858.640354] Call Trace:\n[ 1858.640379]  [<ffffffffa01cadfa>] ? target_setup_cmd_from_cdb+0x13a/0x2c0 [target_core_mod]\n[ 1858.640429]  [<ffffffffa01d8c25>] ? target_xcopy_setup_pt_cmd+0x85/0x320 [target_core_mod]\n[ 1858.640479]  [<ffffffffa01d9424>] ? target_xcopy_do_work+0x264/0x700 [target_core_mod]\n[ 1858.640526]  [<ffffffff810ac3a0>] ? pick_next_task_fair+0x720/0x8f0\n[ 1858.640562]  [<ffffffff8108b3fb>] ? process_one_work+0x14b/0x430\n[ 1858.640595]  [<ffffffff8108bf5b>] ? worker_thread+0x6b/0x560\n[ 1858.640627]  [<ffffffff8108bef0>] ? rescuer_thread+0x390/0x390\n[ 1858.640661]  [<ffffffff810913b3>] ? kthread+0xd3/0xf0\n[ 1858.640689]  [<ffffffff810912e0>] ? kthread_create_on_node+0x180/0x180\n\nAlso, check for the same se_node_acl->device_list[] during EXTENDED_COPY\noperation as a non-holding persistent reservation port.\n\nReported-by: Martin Svec <martin,svec@zoner.cz>\nTested-by: Martin Svec <martin,svec@zoner.cz>\nCc: Martin Svec <martin,svec@zoner.cz>\nCc: Alex Gorbachev <ag@iss-integration.com>\nSigned-off-by: Nicholas Bellinger <nab@linux-iscsi.org>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/raspberrypi/linux/commits/35afa65642a9a88c81913377b93a3a66220f8b9d"},{"sha":"61be5a59622ab5b2c0152e3d32b0d8b18ca65875","author":{"email":"38200bb1bfd6b0890d2ad683bb8ab02214b08408@gmail.com","name":"Azael Avalos"},"message":"toshiba_acpi: Fix hotkeys registration on some toshiba models\n\ncommit 53147b6cabee5e8d1997b5682fcc0c3b72ddf9c2 upstream.\n\nCommit a2b3471b5b13 (\"toshiba_acpi: Use the Hotkey Event Type function\nfor keymap choosing\") changed the *setup_keyboard function to query for\nthe Hotkey Event Type to help choose the correct keymap, but turns out\nthat here are certain Toshiba models out there not implementing this\nfeature, and thus, failing to continue the input device registration and\nleaving such laptops without hotkey support.\n\nThis patch changes such check, and instead of returning an error if\nthe Hotkey Event Type is not present, we simply inform userspace about it,\nchanging the message printed from err to notice, making the function\nresponsible for registering the input device to continue.\n\nThis issue was found on a Toshiba Portege Z30-B, but there might be\nsome other models out there affected by this regression as well.\n\nSigned-off-by: Azael Avalos <coproscefalo@gmail.com>\nSigned-off-by: Darren Hart <dvhart@linux.intel.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/raspberrypi/linux/commits/61be5a59622ab5b2c0152e3d32b0d8b18ca65875"},{"sha":"37f70c3811230c2ee4a3a9eece54cf7ee5ba00f9","author":{"email":"3fddac958924aef220f202ca567388ddab3f14a8@infradead.org","name":"Peter Zijlstra"},"message":"perf/x86/intel: Fix constraint access\n\ncommit ebfb4988f0378e2ac3b4a0aa1ea20d724293f392 upstream.\n\nSasha reported that we can get here with .idx==-1, and\ncpuc->event_constraints unallocated.\n\nSuggested-by: Stephane Eranian <eranian@google.com>\nReported-by: Sasha Levin <sasha.levin@oracle.com>\nSigned-off-by: Peter Zijlstra (Intel) <peterz@infradead.org>\nCc: Linus Torvalds <torvalds@linux-foundation.org>\nCc: Peter Zijlstra <peterz@infradead.org>\nCc: Thomas Gleixner <tglx@linutronix.de>\nFixes: b371b5943178 (\"perf/x86: Fix event/group validation\")\nSigned-off-by: Ingo Molnar <mingo@kernel.org>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/raspberrypi/linux/commits/37f70c3811230c2ee4a3a9eece54cf7ee5ba00f9"},{"sha":"d4cb7d0fc447e6117c99e45f3f4f698017201f2d","author":{"email":"41bb5944f244750b7cf0394140496972a3f1bee3@intel.com","name":"Adrian Hunter"},"message":"perf tools: Fix copying of /proc/kcore\n\ncommit b5cabbcbd157a4bf5a92dfc85134999a3b55342d upstream.\n\nA copy of /proc/kcore containing the kernel text can be made to the\nbuildid cache. e.g.\n\n\tperf buildid-cache -v -k /proc/kcore\n\nTo workaround objdump limitations, a copy is also made when annotating\nagainst /proc/kcore.\n\nThe copying process stops working from libelf about v1.62 onwards (the\nproblem was found with v1.63).\n\nThe cause is that a call to gelf_getphdr() in kcore__add_phdr() fails\nbecause additional validation has been added to gelf_getphdr().\n\nThe use of gelf_getphdr() is a misguided attempt to get default\ninitialization of the Gelf_Phdr structure.  That should not be\nnecessary because every member of the Gelf_Phdr structure is\nsubsequently assigned.  So just remove the call to gelf_getphdr().\n\nSimilarly, a call to gelf_getehdr() in gelf_kcore__init() can be\nremoved also.\n\nCommitter notes:\n\nNote to stable@kernel.org, from Adrian in the cover letter for this\npatchkit:\n\nThe \"Fix copying of /proc/kcore\" problem goes back to v3.13 if you think\nit is important enough for stable.\n\nSigned-off-by: Adrian Hunter <adrian.hunter@intel.com>\nCc: Jiri Olsa <jolsa@redhat.com>\nLink: http://lkml.kernel.org/r/1443089122-19082-3-git-send-email-adrian.hunter@intel.com\nSigned-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/raspberrypi/linux/commits/d4cb7d0fc447e6117c99e45f3f4f698017201f2d"},{"sha":"5c23f8cd8a4a3ce31f65711f3b100055347b8751","author":{"email":"293abb6b76d7791c0732cc517d38c4b5c734b87f@redhat.com","name":"Arnaldo Carvalho de Melo"},"message":"perf hists: Update the column width for the \"srcline\" sort key\n\ncommit e8e6d37e73e6b950c891c780745460b87f4755b6 upstream.\n\nWhen we introduce a new sort key, we need to update the\nhists__calc_col_len() function accordingly, otherwise the width\nwill be limited to strlen(header).\n\nWe can't update it when obtaining a line value for a column (for\ninstance, in sort__srcline_cmp()), because we reset it all when doing a\nresort (see hists__output_recalc_col_len()), so we need to, from what is\nin the hist_entry fields, set each of the column widths.\n\nCc: Namhyung Kim <namhyung@kernel.org>\nCc: Andi Kleen <andi@firstfloor.org>\nCc: Jiri Olsa <jolsa@kernel.org>\nFixes: 409a8be61560 (\"perf tools: Add sort by src line/number\")\nLink: http://lkml.kernel.org/n/tip-jgbe0yx8v1gs89cslr93pvz2@git.kernel.org\nSigned-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/raspberrypi/linux/commits/5c23f8cd8a4a3ce31f65711f3b100055347b8751"}]}