1. 07 3月, 2017 1 次提交
  2. 09 2月, 2017 1 次提交
    • L
      RDMA: Don't reference kernel private header from UAPI header · 646ebd41
      Leon Romanovsky 提交于
      Remove references to private kernel header and defines from exported
      ib_user_verb.h file.
      
      The code snippet below is used to reproduce the issue:
      
       #include <stdio.h>
       #include <rdma/ib_user_verb.h>
      
       int main(void)
       {
      	printf("IB_USER_VERBS_ABI_VERSION = %d\n", IB_USER_VERBS_ABI_VERSION);
      	return 0;
       }
      
      It fails during compilation phase with an error:
      ➜  /tmp gcc main.c
      main.c:2:31: fatal error: rdma/ib_user_verb.h: No such file or directory
       #include <rdma/ib_user_verb.h>
                                     ^
      compilation terminated.
      
      Fixes: 189aba99 ("IB/uverbs: Extend modify_qp and support packet pacing")
      CC: Bodong Wang <bodong@mellanox.com>
      CC: Matan Barak <matanb@mellanox.com>
      CC: Christoph Hellwig <hch@infradead.org>
      Tested-by: NSlava Shwartsman <slavash@mellanox.com>
      Signed-off-by: NLeon Romanovsky <leon@kernel.org>
      Signed-off-by: NDoug Ledford <dledford@redhat.com>
      646ebd41
  3. 04 2月, 2017 1 次提交
  4. 30 1月, 2017 1 次提交
  5. 25 1月, 2017 3 次提交
  6. 17 1月, 2017 1 次提交
    • D
      bpf: rework prog_digest into prog_tag · f1f7714e
      Daniel Borkmann 提交于
      Commit 7bd509e3 ("bpf: add prog_digest and expose it via
      fdinfo/netlink") was recently discussed, partially due to
      admittedly suboptimal name of "prog_digest" in combination
      with sha1 hash usage, thus inevitably and rightfully concerns
      about its security in terms of collision resistance were
      raised with regards to use-cases.
      
      The intended use cases are for debugging resp. introspection
      only for providing a stable "tag" over the instruction sequence
      that both kernel and user space can calculate independently.
      It's not usable at all for making a security relevant decision.
      So collisions where two different instruction sequences generate
      the same tag can happen, but ideally at a rather low rate. The
      "tag" will be dumped in hex and is short enough to introspect
      in tracepoints or kallsyms output along with other data such
      as stack trace, etc. Thus, this patch performs a rename into
      prog_tag and truncates the tag to a short output (64 bits) to
      make it obvious it's not collision-free.
      
      Should in future a hash or facility be needed with a security
      relevant focus, then we can think about requirements, constraints,
      etc that would fit to that situation. For now, rework the exposed
      parts for the current use cases as long as nothing has been
      released yet. Tested on x86_64 and s390x.
      
      Fixes: 7bd509e3 ("bpf: add prog_digest and expose it via fdinfo/netlink")
      Signed-off-by: NDaniel Borkmann <daniel@iogearbox.net>
      Acked-by: NAlexei Starovoitov <ast@kernel.org>
      Cc: Andy Lutomirski <luto@kernel.org>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      f1f7714e
  7. 16 1月, 2017 1 次提交
  8. 11 1月, 2017 2 次提交
  9. 02 1月, 2017 1 次提交
  10. 21 12月, 2016 1 次提交
    • H
      [media] cec: fix report_current_latency · f3854973
      Hans Verkuil 提交于
      In the (very) small print of the REPORT_CURRENT_LATENCY message there is a
      line that says that the last byte of the message (audio out delay) is only
      present if the 'audio out compensated' value is 3.
      
      I missed this, and so if this message was sent with a total length of 6 (i.e.
      without the audio out delay byte), then it was rejected by the framework
      since a minimum length of 7 was expected.
      
      Fix this minimum length check and update the wrappers in cec-funcs.h to do
      the right thing based on the message length.
      Signed-off-by: NHans Verkuil <hans.verkuil@cisco.com>
      Signed-off-by: NMauro Carvalho Chehab <mchehab@s-opensource.com>
      f3854973
  11. 16 12月, 2016 4 次提交
  12. 15 12月, 2016 2 次提交
    • A
      IB: Add vmw_pvrdma driver · 29c8d9eb
      Adit Ranadive 提交于
      This patch series adds a driver for a paravirtual RDMA device. The
      device is developed for VMware's Virtual Machines and allows existing RDMA
      applications to continue to use existing Verbs API when deployed in VMs
      on ESXi. We recently did a presentation in the OFA Workshop [1] regarding
      this device.
      
      Description and RDMA Support
      ============================
      The virtual device is exposed as a dual function PCIe device. One part
      is a virtual network device (VMXNet3) which provides networking properties
      like MAC, IP addresses to the RDMA part of the device. The networking
      properties are used to register GIDs required by RDMA applications to
      communicate.
      
      These patches add support and the all required infrastructure for
      letting applications use such a device. We support the mandatory Verbs API as
      well as the base memory management extensions (Local Inv, Send with Inv and
      Fast Register Work Requests). We currently support both Reliable Connected
      and Unreliable Datagram QPs but do not support Shared Receive Queues
      (SRQs).
      
      Also, we support the following types of Work Requests:
       o Send/Receive (with or without Immediate Data)
       o RDMA Write (with or without Immediate Data)
       o RDMA Read
       o Local Invalidate
       o Send with Invalidate
       o Fast Register Work Requests
      
      This version only adds support for version 1 of RoCE. We will add RoCEv2
      support in a future patch. We do support registration of both MAC-based
      and IP-based GIDs. I have also created a git tree for our user-level driver
      [2].
      
      Testing
      =======
      We have tested this internally for various types of Guest OS - Red Hat,
      Centos, Ubuntu 12.04/14.04/16.04, Oracle Enterprise Linux, SLES 12
      using backported versions of this driver. The tests included several
      runs of the performance tests (included with OFED), Intel MPI PingPong
      benchmark on OpenMPI, krping for FRWRs. Mellanox has been kind enough
      to test the backported version of the driver internally on their hardware
      using a VMware provided ESX build. I have also applied and tested this
      with Doug's k.o/for-4.9 branch (commit 5603910b). Note, that this patch
      series should be applied all together. I split out the commits so that
      it may be easier to review.
      
      PVRDMA Resources
      ================
      [1] OFA Workshop Presentation -
      https://openfabrics.org/images/eventpresos/2016presentations/102parardma.pdf
      
      [2] Libpvrdma User-level library -
      http://git.openfabrics.org/?p=~aditr/libpvrdma.git;a=summaryReviewed-by: NJorgen Hansen <jhansen@vmware.com>
      Reviewed-by: NGeorge Zhang <georgezhang@vmware.com>
      Reviewed-by: NAditya Sarwade <asarwade@vmware.com>
      Reviewed-by: NBryan Tan <bryantan@vmware.com>
      Reviewed-by: NLeon Romanovsky <leonro@mellanox.com>
      Signed-off-by: NAdit Ranadive <aditr@vmware.com>
      Signed-off-by: NDoug Ledford <dledford@redhat.com>
      29c8d9eb
    • J
      rdma UAPI: Use __kernel_sockaddr_storage · 35493294
      Jason Gunthorpe 提交于
      The kernel side is #ifdef'd to this type, and the UAPI header
      should use it directly. It has slightly different alignment
      requirments from the usual user space version.
      Signed-off-by: NJason Gunthorpe <jgunthorpe@obsidianresearch.com>
      Reviewed-by: NLeon Romanovsky <leonro@mellanox.com>
      Signed-off-by: NDoug Ledford <dledford@redhat.com>
      35493294
  13. 14 12月, 2016 8 次提交
  14. 13 12月, 2016 1 次提交
  15. 12 12月, 2016 2 次提交
  16. 11 12月, 2016 2 次提交
  17. 10 12月, 2016 1 次提交
  18. 09 12月, 2016 5 次提交
  19. 07 12月, 2016 2 次提交