1. 03 7月, 2021 2 次提交
  2. 03 6月, 2021 12 次提交
  3. 26 4月, 2021 3 次提交
    • K
      RDMA/qedr: Fix kernel panic when trying to access recv_cq · fb6cb308
      Kamal Heib 提交于
      stable inclusion
      from stable-5.10.30
      commit d8a0861e269d583f6420bed104866d2dc69c2711
      bugzilla: 51791
      
      --------------------------------
      
      [ Upstream commit e1ad897b ]
      
      As INI QP does not require a recv_cq, avoid the following null pointer
      dereference by checking if the qp_type is not INI before trying to extract
      the recv_cq.
      
      BUG: kernel NULL pointer dereference, address: 00000000000000e0
       #PF: supervisor read access in kernel mode
       #PF: error_code(0x0000) - not-present page
       PGD 0 P4D 0
       Oops: 0000 [#1] SMP PTI
       CPU: 0 PID: 54250 Comm: mpitests-IMB-MP Not tainted 5.12.0-rc5 #1
       Hardware name: Dell Inc. PowerEdge R320/0KM5PX, BIOS 2.7.0 08/19/2019
       RIP: 0010:qedr_create_qp+0x378/0x820 [qedr]
       Code: 02 00 00 50 e8 29 d4 a9 d1 48 83 c4 18 e9 65 fe ff ff 48 8b 53 10 48 8b 43 18 44 8b 82 e0 00 00 00 45 85 c0 0f 84 10 74 00 00 <8b> b8 e0 00 00 00 85 ff 0f 85 50 fd ff ff e9 fd 73 00 00 48 8d bd
       RSP: 0018:ffff9c8f056f7a70 EFLAGS: 00010202
       RAX: 0000000000000000 RBX: ffff9c8f056f7b58 RCX: 0000000000000009
       RDX: ffff8c41a9744c00 RSI: ffff9c8f056f7b58 RDI: ffff8c41c0dfa280
       RBP: ffff8c41c0dfa280 R08: 0000000000000002 R09: 0000000000000001
       R10: 0000000000000000 R11: ffff8c41e06fc608 R12: ffff8c4194052000
       R13: 0000000000000000 R14: ffff8c4191546070 R15: ffff8c41c0dfa280
       FS:  00007f78b2787b80(0000) GS:ffff8c43a3200000(0000) knlGS:0000000000000000
       CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
       CR2: 00000000000000e0 CR3: 00000001011d6002 CR4: 00000000001706f0
       Call Trace:
        ib_uverbs_handler_UVERBS_METHOD_QP_CREATE+0x4e4/0xb90 [ib_uverbs]
        ? ib_uverbs_cq_event_handler+0x30/0x30 [ib_uverbs]
        ib_uverbs_run_method+0x6f6/0x7a0 [ib_uverbs]
        ? ib_uverbs_handler_UVERBS_METHOD_QP_DESTROY+0x70/0x70 [ib_uverbs]
        ? __cond_resched+0x15/0x30
        ? __kmalloc+0x5a/0x440
        ib_uverbs_cmd_verbs+0x195/0x360 [ib_uverbs]
        ? xa_load+0x6e/0x90
        ? cred_has_capability+0x7c/0x130
        ? avc_has_extended_perms+0x17f/0x440
        ? vma_link+0xae/0xb0
        ? vma_set_page_prot+0x2a/0x60
        ? mmap_region+0x298/0x6c0
        ? do_mmap+0x373/0x520
        ? selinux_file_ioctl+0x17f/0x220
        ib_uverbs_ioctl+0xa7/0x110 [ib_uverbs]
        __x64_sys_ioctl+0x84/0xc0
        do_syscall_64+0x33/0x40
        entry_SYSCALL_64_after_hwframe+0x44/0xae
       RIP: 0033:0x7f78b120262b
      
      Fixes: 06e8d1df ("RDMA/qedr: Add support for user mode XRC-SRQ's")
      Link: https://lore.kernel.org/r/20210404125501.154789-1-kamalheib1@gmail.comSigned-off-by: NKamal Heib <kamalheib1@gmail.com>
      Signed-off-by: NJason Gunthorpe <jgg@nvidia.com>
      Signed-off-by: NSasha Levin <sashal@kernel.org>
      Signed-off-by: NChen Jun <chenjun102@huawei.com>
      Acked-by: N  Weilong Chen <chenweilong@huawei.com>
      Signed-off-by: NZheng Zengkai <zhengzengkai@huawei.com>
      fb6cb308
    • P
      RDMA/cxgb4: check for ipv6 address properly while destroying listener · 50f240d1
      Potnuri Bharat Teja 提交于
      stable inclusion
      from stable-5.10.30
      commit 7f40e93328989279fee7a718736c386c13d44aa8
      bugzilla: 51791
      
      --------------------------------
      
      [ Upstream commit 603c4690 ]
      
      ipv6 bit is wrongly set by the below which causes fatal adapter lookup
      engine errors for ipv4 connections while destroying a listener.  Fix it to
      properly check the local address for ipv6.
      
      Fixes: 3408be14 ("RDMA/cxgb4: Fix adapter LE hash errors while destroying ipv6 listening server")
      Link: https://lore.kernel.org/r/20210331135715.30072-1-bharat@chelsio.comSigned-off-by: NPotnuri Bharat Teja <bharat@chelsio.com>
      Signed-off-by: NJason Gunthorpe <jgg@nvidia.com>
      Signed-off-by: NSasha Levin <sashal@kernel.org>
      Signed-off-by: NChen Jun <chenjun102@huawei.com>
      Acked-by: N  Weilong Chen <chenweilong@huawei.com>
      Signed-off-by: NZheng Zengkai <zhengzengkai@huawei.com>
      50f240d1
    • M
      IB/hfi1: Fix probe time panic when AIP is enabled with a buggy BIOS · 561c3581
      Mike Marciniszyn 提交于
      stable inclusion
      from stable-5.10.30
      commit de427b662bfb23546cd0af4af86c8b945e780755
      bugzilla: 51791
      
      --------------------------------
      
      commit 5de61a47 upstream.
      
      A panic can result when AIP is enabled:
      
        BUG: unable to handle kernel NULL pointer dereference at 000000000000000
        PGD 0 P4D 0
        Oops: 0000 1 SMP PTI
        CPU: 70 PID: 981 Comm: systemd-udevd Tainted: G OE --------- - - 4.18.0-240.el8.x86_64 #1
        Hardware name: Intel Corporation S2600KP/S2600KP, BIOS SE5C610.86B.01.01.0005.101720141054 10/17/2014
        RIP: 0010:__bitmap_and+0x1b/0x70
        RSP: 0018:ffff99aa0845f9f0 EFLAGS: 00010246
        RAX: 0000000000000000 RBX: ffff8d5a6fc18000 RCX: 0000000000000048
        RDX: 0000000000000000 RSI: ffffffffc06336f0 RDI: ffff8d5a8fa67750
        RBP: 0000000000000079 R08: 0000000fffffffff R09: 0000000000000000
        R10: 0000000000000000 R11: 0000000000000001 R12: ffffffffc06336f0
        R13: 00000000000000a0 R14: ffff8d5a6fc18000 R15: 0000000000000003
        FS: 00007fec137a5980(0000) GS:ffff8d5a9fa80000(0000) knlGS:0000000000000000
        CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
        CR2: 0000000000000000 CR3: 0000000a04b48002 CR4: 00000000001606e0
        Call Trace:
        hfi1_num_netdev_contexts+0x7c/0x110 [hfi1]
        hfi1_init_dd+0xd7f/0x1a90 [hfi1]
        ? pci_bus_read_config_dword+0x49/0x70
        ? pci_mmcfg_read+0x3e/0xe0
        do_init_one.isra.18+0x336/0x640 [hfi1]
        local_pci_probe+0x41/0x90
        pci_device_probe+0x105/0x1c0
        really_probe+0x212/0x440
        driver_probe_device+0x49/0xc0
        device_driver_attach+0x50/0x60
        __driver_attach+0x61/0x130
        ? device_driver_attach+0x60/0x60
        bus_for_each_dev+0x77/0xc0
        ? klist_add_tail+0x3b/0x70
        bus_add_driver+0x14d/0x1e0
        ? dev_init+0x10b/0x10b [hfi1]
        driver_register+0x6b/0xb0
        ? dev_init+0x10b/0x10b [hfi1]
        hfi1_mod_init+0x1e6/0x20a [hfi1]
        do_one_initcall+0x46/0x1c3
        ? free_unref_page_commit+0x91/0x100
        ? _cond_resched+0x15/0x30
        ? kmem_cache_alloc_trace+0x140/0x1c0
        do_init_module+0x5a/0x220
        load_module+0x14b4/0x17e0
        ? __do_sys_finit_module+0xa8/0x110
        __do_sys_finit_module+0xa8/0x110
        do_syscall_64+0x5b/0x1a0
      
      The issue happens when pcibus_to_node() returns NO_NUMA_NODE.
      
      Fix this issue by moving the initialization of dd->node to hfi1_devdata
      allocation and remove the other pcibus_to_node() calls in the probe path
      and use dd->node instead.
      
      Affinity logic is adjusted to use a new field dd->affinity_entry as a
      guard instead of dd->node.
      
      Fixes: 4730f4a6 ("IB/hfi1: Activate the dummy netdev")
      Link: https://lore.kernel.org/r/1617025700-31865-4-git-send-email-dennis.dalessandro@cornelisnetworks.com
      Cc: stable@vger.kernel.org
      Signed-off-by: NMike Marciniszyn <mike.marciniszyn@cornelisnetworks.com>
      Signed-off-by: NDennis Dalessandro <dennis.dalessandro@cornelisnetworks.com>
      Signed-off-by: NJason Gunthorpe <jgg@nvidia.com>
      Signed-off-by: NGreg Kroah-Hartman <gregkh@linuxfoundation.org>
      Signed-off-by: NChen Jun <chenjun102@huawei.com>
      Acked-by: N  Weilong Chen <chenweilong@huawei.com>
      Signed-off-by: NZheng Zengkai <zhengzengkai@huawei.com>
      561c3581
  4. 19 4月, 2021 1 次提交
  5. 14 4月, 2021 1 次提交
  6. 13 4月, 2021 1 次提交
  7. 09 4月, 2021 8 次提交
  8. 09 2月, 2021 2 次提交
  9. 08 2月, 2021 1 次提交
  10. 28 1月, 2021 4 次提交
  11. 27 1月, 2021 1 次提交
  12. 12 1月, 2021 4 次提交