aboutsummaryrefslogtreecommitdiffstats
path: root/.mailmap
diff options
context:
space:
mode:
authorMark Zhang <markzhang@nvidia.com>2021-06-02 13:27:05 +0300
committerJason Gunthorpe <jgg@nvidia.com>2021-06-02 15:41:58 -0300
commit3595c398f6dbab79a38550ff26104c6ec1035cd3 (patch)
treed730a77b9948981cae1781d26fba96a001e3e4a5 /.mailmap
parentIB/cm: Tidy remaining cm_msg free paths (diff)
downloadlinux-dev-3595c398f6dbab79a38550ff26104c6ec1035cd3.tar.xz
linux-dev-3595c398f6dbab79a38550ff26104c6ec1035cd3.zip
Revert "IB/cm: Mark stale CM id's whenever the mad agent was unregistered"
This reverts commit 9db0ff53cb9b43ed75bacd42a89c1a0ab048b2b0, which wasn't a full fix and still causes to the following panic: panic @ time 1605623870.843, thread 0xfffffeb63b552000: vm_fault_lookup: fault on nofault entry, addr: 0xfffffe811a94e000 time = 1605623870 cpuid = 9, TSC = 0xb7937acc1b6 Panic occurred in module kernel loaded at 0xffffffff80200000:Stack: -------------------------------------------------- kernel:vm_fault+0x19da kernel:vm_fault_trap+0x6e kernel:trap_pfault+0x1f1 kernel:trap+0x31e kernel:cm_destroy_id+0x38c kernel:rdma_destroy_id+0x127 kernel:sdp_shutdown_task+0x3ae kernel:taskqueue_run_locked+0x10b kernel:taskqueue_thread_loop+0x87 kernel:fork_exit+0x83 Link: https://lore.kernel.org/r/4346449a7cdacc7a4eedc89cb1b42d8434ec9814.1622629024.git.leonro@nvidia.com Signed-off-by: Mark Zhang <markzhang@nvidia.com> Signed-off-by: Leon Romanovsky <leonro@nvidia.com> Signed-off-by: Jason Gunthorpe <jgg@nvidia.com>
Diffstat (limited to '.mailmap')
0 files changed, 0 insertions, 0 deletions