Eric Lee / smarc-fsl-linux-kernel

24 Jun, 2013

4 commits

30 Apr, 2013

1 commit

25 Apr, 2013

2 commits

  • 22ee3b57c   VSOCK: Drop bogus __init annotation from vsock_init_tables() ... Browse Code »

    If gcc (e.g. 4.1.2) decides not to inline vsock_init_tables(), this will
    cause a section mismatch:

    WARNING: net/vmw_vsock/vsock.o(.text+0x1bc): Section mismatch in reference from the function __vsock_core_init() to the function .init.text:vsock_init_tables()
    The function __vsock_core_init() references
    the function __init vsock_init_tables().
    This is often because __vsock_core_init lacks a __init
    annotation or the annotation of vsock_init_tables is wrong.

    This may cause crashes if VSOCKETS=y and VMWARE_VMCI_VSOCKETS=m.

    Signed-off-by: Geert Uytterhoeven
    Signed-off-by: David S. Miller

    Geert Uytterhoeven
     
  • 6ad0b2f7f   VSOCK: Fix misc device registration ... Browse Code »

    When we call vsock_core_init to init VSOCK the second time,
    vsock_device.minor still points to the old dynamically allocated minor
    number. misc_register will allocate it for us successfully as if we were
    asking for a static one. However, when other user call misc_register to
    allocate a dynamic minor number, it will give the one used by
    vsock_core_init(), causing this:

    [ 405.470687] WARNING: at fs/sysfs/dir.c:536 sysfs_add_one+0xcc/0xf0()
    [ 405.470689] Hardware name: OptiPlex 790
    [ 405.470690] sysfs: cannot create duplicate filename '/dev/char/10:54'

    Always set vsock_device.minor to MISC_DYNAMIC_MINOR before we
    register.

    Cc: "David S. Miller"
    Cc: Andy King
    Cc: Dmitry Torokhov
    Cc: Reilly Grant
    Cc: netdev@vger.kernel.org
    Cc: linux-kernel@vger.kernel.org
    Signed-off-by: Asias He
    Acked-by: Dmitry Torokhov
    Signed-off-by: David S. Miller

    Asias He
     

08 Apr, 2013

3 commits

03 Apr, 2013

2 commits

  • d66248326   Merge git://git.kernel.org/pub/scm/linux/kernel/git/davem/net ... Browse Code »

    Pull net into net-next to get the synchronize_net() bug fix in
    bonding.

    Signed-off-by: David S. Miller

    David S. Miller
     
  • 990454b5a   VSOCK: Handle changes to the VMCI context ID. ... Browse Code »

    The VMCI context ID of a virtual machine may change at any time. There
    is a VMCI event which signals this but datagrams may be processed before
    this is handled. It is therefore necessary to be flexible about the
    destination context ID of any datagrams received. (It can be assumed to
    be correct because it is provided by the hypervisor.) The context ID on
    existing sockets should be updated to reflect how the hypervisor is
    currently referring to the system.

    Signed-off-by: Reilly Grant
    Acked-by: Andy King
    Signed-off-by: David S. Miller

    Reilly Grant
     

15 Mar, 2013

1 commit

  • 2a89f9247   VSOCK: Support VM sockets connected to the hypervisor. ... Browse Code »

    The resource ID used for VM socket control packets (0) is already
    used for the VMCI_GET_CONTEXT_ID hypercall so a new ID (15) must be
    used when the guest sends these datagrams to the hypervisor.

    The hypervisor context ID must also be removed from the internal
    blacklist.

    Signed-off-by: Reilly Grant
    Acked-by: Andy King
    Signed-off-by: David S. Miller

    Reilly Grant
     

19 Feb, 2013

3 commits

11 Feb, 2013

1 commit

  • d021c3440   VSOCK: Introduce VM Sockets ... Browse Code »

    VM Sockets allows communication between virtual machines and the hypervisor.
    User level applications both in a virtual machine and on the host can use the
    VM Sockets API, which facilitates fast and efficient communication between
    guest virtual machines and their host. A socket address family, designed to be
    compatible with UDP and TCP at the interface level, is provided.

    Today, VM Sockets is used by various VMware Tools components inside the guest
    for zero-config, network-less access to VMware host services. In addition to
    this, VMware's users are using VM Sockets for various applications, where
    network access of the virtual machine is restricted or non-existent. Examples
    of this are VMs communicating with device proxies for proprietary hardware
    running as host applications and automated testing of applications running
    within virtual machines.

    The VMware VM Sockets are similar to other socket types, like Berkeley UNIX
    socket interface. The VM Sockets module supports both connection-oriented
    stream sockets like TCP, and connectionless datagram sockets like UDP. The VM
    Sockets protocol family is defined as "AF_VSOCK" and the socket operations
    split for SOCK_DGRAM and SOCK_STREAM.

    For additional information about the use of VM Sockets, please refer to the
    VM Sockets Programming Guide available at:

    https://www.vmware.com/support/developer/vmci-sdk/

    Signed-off-by: George Zhang
    Signed-off-by: Dmitry Torokhov
    Signed-off-by: Andy king
    Signed-off-by: David S. Miller

    Andy King