1. 24 8月, 2020 1 次提交
  2. 21 7月, 2020 1 次提交
  3. 07 7月, 2020 1 次提交
  4. 26 6月, 2020 1 次提交
  5. 14 6月, 2020 1 次提交
    • M
      treewide: replace '---help---' in Kconfig files with 'help' · a7f7f624
      Masahiro Yamada 提交于
      Since commit 84af7a61 ("checkpatch: kconfig: prefer 'help' over
      '---help---'"), the number of '---help---' has been gradually
      decreasing, but there are still more than 2400 instances.
      
      This commit finishes the conversion. While I touched the lines,
      I also fixed the indentation.
      
      There are a variety of indentation styles found.
      
        a) 4 spaces + '---help---'
        b) 7 spaces + '---help---'
        c) 8 spaces + '---help---'
        d) 1 space + 1 tab + '---help---'
        e) 1 tab + '---help---'    (correct indentation)
        f) 1 tab + 1 space + '---help---'
        g) 1 tab + 2 spaces + '---help---'
      
      In order to convert all of them to 1 tab + 'help', I ran the
      following commend:
      
        $ find . -name 'Kconfig*' | xargs sed -i 's/^[[:space:]]*---help---/\thelp/'
      Signed-off-by: NMasahiro Yamada <masahiroy@kernel.org>
      a7f7f624
  6. 03 6月, 2020 2 次提交
  7. 12 5月, 2020 1 次提交
    • D
      IB/i40iw: Remove bogus call to netdev_master_upper_dev_get() · 856ec7f6
      Denis V. Lunev 提交于
      Local variable netdev is not used in these calls.
      
      It should be noted, that this change is required to work in bonded mode.
      Otherwise we would get the following assert:
      
       "RTNL: assertion failed at net/core/dev.c (5665)"
      
      With the calltrace as follows:
      	dump_stack+0x19/0x1b
      	netdev_master_upper_dev_get+0x61/0x70
      	i40iw_addr_resolve_neigh+0x1e8/0x220
      	i40iw_make_cm_node+0x296/0x700
      	? i40iw_find_listener.isra.10+0xcc/0x110
      	i40iw_receive_ilq+0x3d4/0x810
      	i40iw_puda_poll_completion+0x341/0x420
      	i40iw_process_ceq+0xa5/0x280
      	i40iw_ceq_dpc+0x1e/0x40
      	tasklet_action+0x83/0x140
      	__do_softirq+0x125/0x2bb
      	call_softirq+0x1c/0x30
      	do_softirq+0x65/0xa0
      	irq_exit+0x105/0x110
      	do_IRQ+0x56/0xf0
      	common_interrupt+0x16a/0x16a
      	? cpuidle_enter_state+0x57/0xd0
      	cpuidle_idle_call+0xde/0x230
      	arch_cpu_idle+0xe/0xc0
      	cpu_startup_entry+0x14a/0x1e0
      	start_secondary+0x1f7/0x270
      	start_cpu+0x5/0x14
      
      Link: https://lore.kernel.org/r/20200428131511.11049-1-den@openvz.orgSigned-off-by: NDenis V. Lunev <den@openvz.org>
      Acked-by: NShiraz Saleem <shiraz.saleem@intel.com>
      Signed-off-by: NJason Gunthorpe <jgg@mellanox.com>
      856ec7f6
  8. 05 5月, 2020 1 次提交
  9. 15 4月, 2020 1 次提交
  10. 19 3月, 2020 1 次提交
  11. 05 3月, 2020 1 次提交
  12. 21 2月, 2020 1 次提交
  13. 12 2月, 2020 1 次提交
  14. 16 1月, 2020 2 次提交
    • M
      IB/core: Introduce ib_reg_user_mr · 33006bd4
      Moni Shoua 提交于
      Add ib_reg_user_mr() for kernel ULPs to register user MRs.
      
      The common use case that uses this function is a userspace application
      that allocates memory for HCA access but the responsibility to register
      the memory at the HCA is on an kernel ULP. This ULP that acts as an agent
      for the userspace application.
      
      This function is intended to be used without a user context so vendor
      drivers need to be aware of calling reg_user_mr() device operation with
      udata equal to NULL.
      
      Among all drivers, i40iw is the only driver which relies on presence
      of udata, so check udata existence for that driver.
      Signed-off-by: NMoni Shoua <monis@mellanox.com>
      Reviewed-by: NGuy Levi <guyle@mellanox.com>
      Signed-off-by: NLeon Romanovsky <leonro@mellanox.com>
      33006bd4
    • M
      IB: Allow calls to ib_umem_get from kernel ULPs · c320e527
      Moni Shoua 提交于
      So far the assumption was that ib_umem_get() and ib_umem_odp_get()
      are called from flows that start in UVERBS and therefore has a user
      context. This assumption restricts flows that are initiated by ULPs
      and need the service that ib_umem_get() provides.
      
      This patch changes ib_umem_get() and ib_umem_odp_get() to get IB device
      directly by relying on the fact that both UVERBS and ULPs sets that
      field correctly.
      Reviewed-by: NGuy Levi <guyle@mellanox.com>
      Signed-off-by: NMoni Shoua <monis@mellanox.com>
      Signed-off-by: NLeon Romanovsky <leonro@mellanox.com>
      c320e527
  15. 08 1月, 2020 1 次提交
    • S
      i40iw: Remove setting of VMA private data and use rdma_user_mmap_io · 9554de39
      Shiraz Saleem 提交于
      vm_ops is now initialized in ib_uverbs_mmap() with the recent rdma mmap
      API changes. Earlier it was done in rdma_umap_priv_init() which would not
      be called unless a driver called rdma_user_mmap_io() in its mmap.
      
      i40iw does not use the rdma_user_mmap_io API but sets the vma's
      vm_private_data to a driver object. This now conflicts with the vm_op
      rdma_umap_close as priv pointer points to the i40iw driver object instead
      of the private data setup by core when rdma_user_mmap_io is called.  This
      leads to a crash in rdma_umap_close with a mmap put being called when it
      should not have.
      
      Remove the redundant setting of the vma private_data in i40iw as it is not
      used. Also move i40iw over to use the rdma_user_mmap_io API. This gives
      the extra protection of having the mappings zapped when the context is
      detsroyed.
      
        BUG: unable to handle page fault for address: 0000000100000001
        #PF: supervisor write access in kernel mode
        #PF: error_code(0x0002) - not-present page
        PGD 0 P4D 0
        Oops: 0002 [#1] SMP PTI
        CPU: 6 PID: 9528 Comm: rping Kdump: loaded Not tainted 5.5.0-rc4+ #117
        Hardware name: Gigabyte Technology Co., Ltd. To be filled by O.E.M./Q87M-D2H, BIOS F7 01/17/2014
        RIP: 0010:rdma_user_mmap_entry_put+0xa/0x30 [ib_core]
        RSP: 0018:ffffb340c04c7c38 EFLAGS: 00010202
        RAX: 00000000ffffffff RBX: ffff9308e7be2a00 RCX: 000000000000cec0
        RDX: 0000000000000000 RSI: 0000000000000006 RDI: 0000000100000001
        RBP: ffff9308dc7641f0 R08: 0000000000000001 R09: 0000000000000000
        R10: 0000000000000001 R11: ffffffff8d4414d8 R12: ffff93075182c780
        R13: 0000000000000001 R14: ffff93075182d2a8 R15: ffff9308e2ddc840
        FS:  0000000000000000(0000) GS:ffff9308fdc00000(0000) knlGS:0000000000000000
        CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
        CR2: 0000000100000001 CR3: 00000002e0412004 CR4: 00000000001606e0
        Call Trace:
         rdma_umap_close+0x40/0x90 [ib_uverbs]
         remove_vma+0x43/0x80
         exit_mmap+0xfd/0x1b0
         mmput+0x6e/0x130
         do_exit+0x290/0xcc0
         ? get_signal+0x152/0xc40
         do_group_exit+0x46/0xc0
         get_signal+0x1bd/0xc40
         ? prepare_to_wait_event+0x97/0x190
         do_signal+0x36/0x630
         ? remove_wait_queue+0x60/0x60
         ? __audit_syscall_exit+0x1d9/0x290
         ? rcu_read_lock_sched_held+0x52/0x90
         ? kfree+0x21c/0x2e0
         exit_to_usermode_loop+0x4f/0xc3
         do_syscall_64+0x1ed/0x270
         entry_SYSCALL_64_after_hwframe+0x49/0xbe
        RIP: 0033:0x7fae715a81fd
        Code: Bad RIP value.
        RSP: 002b:00007fae6e163cb0 EFLAGS: 00000293 ORIG_RAX: 0000000000000001
        RAX: fffffffffffffe00 RBX: 00007fae6e163d30 RCX: 00007fae715a81fd
        RDX: 0000000000000010 RSI: 00007fae6e163cf0 RDI: 0000000000000003
        RBP: 00000000013413a0 R08: 00007fae68000000 R09: 0000000000000017
        R10: 0000000000000001 R11: 0000000000000293 R12: 00007fae680008c0
        R13: 00007fae6e163cf0 R14: 00007fae717c9804 R15: 00007fae6e163ed0
        CR2: 0000000100000001
        ---[ end trace b33d58d3a06782cb ]---
        RIP: 0010:rdma_user_mmap_entry_put+0xa/0x30 [ib_core]
      
      Fixes: b86deba9 ("RDMA/core: Move core content from ib_uverbs to ib_core")
      Link: https://lore.kernel.org/r/20200107162223.1745-1-shiraz.saleem@intel.comSigned-off-by: NShiraz Saleem <shiraz.saleem@intel.com>
      Signed-off-by: NJason Gunthorpe <jgg@mellanox.com>
      9554de39
  16. 04 1月, 2020 1 次提交
  17. 17 11月, 2019 1 次提交
  18. 14 11月, 2019 1 次提交
  19. 05 10月, 2019 1 次提交
  20. 12 8月, 2019 1 次提交
  21. 04 7月, 2019 2 次提交
  22. 21 6月, 2019 1 次提交
  23. 12 6月, 2019 2 次提交
  24. 11 6月, 2019 3 次提交
  25. 03 6月, 2019 2 次提交
  26. 22 5月, 2019 1 次提交
  27. 21 5月, 2019 1 次提交
  28. 07 5月, 2019 1 次提交
  29. 03 5月, 2019 1 次提交
  30. 08 4月, 2019 1 次提交
  31. 02 4月, 2019 3 次提交