linux-toradex.git, branch v3.9.4

Linux 3.9.4

2013-05-24T18:45:59+00:00

x86, vm86: fix VM86 syscalls: use SYSCALL_DEFINEx(...)

2013-05-24T18:36:06+00:00

commit 5522ddb3fc0dfd4a503c8278eafd88c9f2d3fada upstream.

Commit 49cb25e9290 x86: 'get rid of pt_regs argument in vm86/vm86old'
got rid of the pt_regs stub for sys_vm86old and sys_vm86. The functions
were, however, not changed to use the calling convention for syscalls.

[AV: killed asmlinkage_protect() - it's done automatically now]

Backported-by: Satoru Takeuchi 
Reported-and-tested-by: Hans de Bruin 
Signed-off-by: Alexander van Heukelum 
Signed-off-by: Al Viro 
Signed-off-by: Greg Kroah-Hartman

NTB: Multiple NTB client fix

2013-05-24T18:36:05+00:00

commit 8b19d450ad188d402a183ff4a4d40f31c3916fbf upstream.

Fix issue with adding multiple ntb client devices to the ntb virtual
bus.  Previously, multiple devices would be added with the same name,
resulting in crashes.  To get around this issue, add a unique number to
the device when it is added.

Signed-off-by: Jon Mason 
Signed-off-by: Greg Kroah-Hartman

ntb_netdev: remove from list on exit

2013-05-24T18:36:05+00:00

commit 904435cf76a9bdd5eb41b1c4e049d5a64f3a8400 upstream.

The ntb_netdev device is not removed from the global list of devices
upon device removal.  If the device is re-added, the removal code would
find the first instance and try to remove an already removed device.

Signed-off-by: Jon Mason 
Signed-off-by: Greg Kroah-Hartman

NTB: memcpy lockup workaround

2013-05-24T18:36:05+00:00

commit c336acd3331dcc191a97dbc66a557d47741657c7 upstream.

The system will appear to lockup for long periods of time due to the NTB
driver spending too much time in memcpy.  Avoid this by reducing the
number of packets that can be serviced on a given interrupt.

Signed-off-by: Jon Mason 
Signed-off-by: Greg Kroah-Hartman

NTB: Correctly handle receive buffers of the minimal size

2013-05-24T18:36:05+00:00

commit c9d534c8cbaedbb522a1d2cb037c6c394f610317 upstream.

The ring logic of the NTB receive buffer/transmit memory window requires
there to be at least 2 payload sized allotments.  For the minimal size
case, split the buffer into two and set the transport_mtu to the
appropriate size.

Signed-off-by: Jon Mason 
Signed-off-by: Greg Kroah-Hartman

NTB: reset tx_index on link toggle

2013-05-24T18:36:04+00:00

commit 90f9e934647e652a69396e18c779215a493271cf upstream.

If the NTB link toggles, the driver could stop receiving due to the
tx_index not being set to 0 on the transmitting size on a link-up event.
This is due to the driver expecting the incoming data to start at the
beginning of the receive buffer and not at a random place.

Signed-off-by: Jon Mason 
Signed-off-by: Greg Kroah-Hartman

NTB: Link toggle memory leak

2013-05-24T18:36:04+00:00

commit b77b2637b39ecc380bb08992380d7d48452b0872 upstream.

Each link-up will allocate a new NTB receive buffer when the NTB
properties are negotiated with the remote system.  These allocations did
not check for existing buffers and thus did not free them.  Now, the
driver will check for an existing buffer and free it if not of the
correct size, before trying to alloc a new one.

Signed-off-by: Jon Mason 
Signed-off-by: Greg Kroah-Hartman

NTB: Handle 64bit BAR sizes

2013-05-24T18:36:04+00:00

commit 113fc505b83b2d16e820ca74fa07f99a34877b1d upstream.

64bit BAR sizes are permissible with an NTB device.  To support them
various modifications and clean-ups were required, most significantly
using 2 32bit scratch pad registers for each BAR.

Also, modify the driver to allow more than 2 Memory Windows.

Signed-off-by: Jon Mason 
Signed-off-by: Greg Kroah-Hartman

NTB: fix pointer math issues

2013-05-24T18:36:04+00:00

commit cc0f868d8adef7bdc12cda132654870086d766bc upstream.

->remote_rx_info and ->rx_info are struct ntb_rx_info pointers.  If we
add sizeof(struct ntb_rx_info) then it goes too far.

Signed-off-by: Dan Carpenter 
Signed-off-by: Jon Mason 
Signed-off-by: Greg Kroah-Hartman