From: Leon Romanovsky
There is no value in checking ib_destroy_cq() result and skipping
to clear struct ic fields. This connection needs to be reinitialized
anyway.
Signed-off-by: Leon Romanovsky
---
net/rds/ib_cm.c | 8
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/ne
Hi Siva,
at 21:42, Siva Reddy Kallam wrote:
On Mon, Mar 11, 2019 at 9:23 AM Kai-Heng Feng
wrote:
[snipped]
Hi again,
Any update?
Kai-Heng
Sorry for the late reply. We will provide our feedback soon.
Any good news? It still happens on latest mainline kernel.
Kai-Heng
Ever since commit 3a06c7ac24f9 ("posix-clocks: Remove interval timer
facility and mmap/fasync callbacks") the possibility of PHC based
posix timers has been removed. In addition it will probably never
make sense to implement this functionality.
This patch removes the misleading example code which
As all the IPv4 testing addresses are in the same subnet and egress device ==
ingress device, to pass "from $SRC_IP iif $DEV" match test, we need enable
forwarding to get the route entry.
Hangbin Liu (2):
selftests: fib_rule_tests: fix local IPv4 address typo
selftests: fib_rule_tests: enable
The IPv4 testing address are all in 192.51.100.0 subnet. It doesn't make
sense to set a 198.51.100.1 local address. Should be a typo.
Fixes: 65b2b4939a64 ("selftests: net: initial fib rule tests")
Signed-off-by: Hangbin Liu
---
tools/testing/selftests/net/fib_rule_tests.sh | 2 +-
1 file changed
As all the testing addresses are in the same subnet and egress device ==
ingress device. We need enable forwarding to get the route entry.
Also disable rp_filer separately as some distributions enable it in
startup scripts.
Fixes: 65b2b4939a64 ("selftests: net: initial fib rule tests")
Signed-off
Hi,
After investigating this more, I am not positive why this fixes the
issue on sparc. I will continue to investigate as best I can, but would
like to request help from some sparc experts on evaluating my line of
thinking. I think the changes in this patch are still very worthwhile
generally thou
Hi Roi & Saeed,
I just test the mlx5e lag and mutipath feature. There are some suituation the
outgoing can't be offloaded.
ovs configureation as following.
# ovs-vsctl show
dfd71dfb-6e22-423e-b088-d2022103af6b
Bridge "br0"
Port "mlx_pf0vf0"
Interface "mlx_pf0vf0"
Bonjour
Je soussigné Mr ASSOGBA Aurel de nationalité béninoise. Je vous envoie ce
message pour vous proposer une affaire importante.
Je viens de bénéficier d’un important capital financier après la mort de mon
père qui était collaborateur d'un pétrolier libyen. Je désire investir ce
capital f
When a device is stacked like (team, bonding, failsafe or netvsc) the
XDP generic program for the parent device is not called. In these
cases, the rx handler changes skb->dev to its own in the receive
handler, and returns RX_HANDLER_ANOTHER. Fix this by calling
do_xdp_generic if necessary before
The netvsc VF skb handler should make sure that skb is not
shared. Similar logic already exists in bonding and team device
drivers.
This is not an issue in practice because the VF devicex
does not send up shared skb's. But the netvsc driver
should do the right thing if it did.
Fixes: 0c195567a8f6
This set of patches came about while investigating XDP
generic on Azure. The split brain nature of the accelerated
networking exposed issues with the stack device model.
The real fix is in the second patch which is a redo
of earlier patch from Jason Wang.
v2 - hold off the comment fixes for net-n
On Fri, May 17, 2019 at 12:45 PM wrote:
> From: wenxu
>
> The mlx5e support the lag mode. When add mlx_p0 and mlx_p1 to bond0.
> packet received from mlx_p0 or mlx_p1 and in the ingress tc flower
> forward to vf0. The tc rule can't be offloaded because there is
> no indr_register_block for the bo
From: Kurt Kanzenbach
On loaded systems with a preemptible kernel the mdio_wait() function may
report an error while everything is working fine:
xemaclite_mdio_wait():
xemaclite_readl() -> chip not ready
--> interrupt here (other work for some time / chip become ready)
if (time_before_eq(e
From: Kurt Kanzenbach
On loaded systems with a preemptible kernel the mdio_wait() function may
report an error while everything is working fine:
axienet_mdio_wait_until_ready():
axienet_ior() -> chip not ready
--> interrupt here (other work for some time / chip become ready)
if (time_befor
Hi,
On loaded systems with a preemptible kernel both functions
axienet_mdio_wait_until_ready() and xemaclite_mdio_wait() may report a
false positive error return.
Convert both functions to use readx_poll_timeout() to handle the
situation in a safe manner.
Regards
Benedikt Spranger
Kurt Kanze
Hi, I want to add some details:
On 5/18/19 11:07 AM, Octavio Alvarez wrote:
> PROBLEM: [2/2] Marvell 88E8040 (sky2) fails after hibernation
>
> It occurs since 4.14.
Sorry, 4.14 is the last known good version. Quoting section 5 of my report:
> [5.] Most recent kernel version which did not have
If the trace for read is larger than 4096,
the return value sz will be 4096.
This results in off-by-one error on buf.
static char buf[4096];
ssize_t sz;
sz = read(trace_fd, buf, sizeof(buf));
if (sz > 0) {
buf[sz] = 0;
puts(buf);
}
Signed-off-by: Chang-Hsien T
On 17/05/2019 11:21, we...@ucloud.cn wrote:
> From: wenxu
>
> The mlx5e support the lag mode. When add mlx_p0 and mlx_p1 to bond0.
> packet received from mlx_p0 or mlx_p1 and in the ingress tc flower
> forward to vf0. The tc rule can't be offloaded for the non indr
> rejistor block for the bond
From: Randy Dunlap
Date: Sat, 18 May 2019 21:23:07 -0700
> From: Randy Dunlap
>
> Fix kernel-doc warnings by moving the kernel-doc notation to be
> immediately above the functions that it describes.
>
> Fixes these warnings for sock_sendmsg() and sock_recvmsg():
>
> ../net/socket.c:658: warni
From: Patrick Talbert
Date: Fri, 17 May 2019 17:11:28 +0200
> Currently, procfs socket stats format sk_drops as a signed int (%d). For large
> values this will cause a negative number to be printed.
>
> We know the drop count can never be a negative so change the format specifier
> to
> %u.
>
On 18/05/2019 06:10, wenxu wrote:
> There will be multiple vlan device which maybe not belong to the uplink rep
> device, so wen can limit it
>
> 在 2019/5/18 4:30, Saeed Mahameed 写道:
>> On Wed, 2019-05-15 at 17:25 +0800, we...@ucloud.cn wrote:
>>> From: wenxu
>>>
>>> When register indr block f
On 15/05/2019 9:58, Gal Pressman wrote:
> Fix typo in usnic_udp node type and add a string for the unspecified
> node type.
>
> Signed-off-by: Gal Pressman
> ---
> rdma/dev.c | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/rdma/dev.c b/rdma/dev.c
> index 339625202200.
From: Randy Dunlap
Fix kernel-doc warnings by moving the kernel-doc notation to be
immediately above the functions that it describes.
Fixes these warnings for sock_sendmsg() and sock_recvmsg():
../net/socket.c:658: warning: Excess function parameter 'sock' description in
'INDIRECT_CALLABLE_DEC
On 5/16/2019 8:56 PM, Jakub Kicinski wrote:
> On Thu, 16 May 2019 09:08:52 +, Boris Pismenny wrote:
>>> diff --git a/Documentation/networking/tls-offload.rst
>>> b/Documentation/networking/tls-offload.rst
>>> new file mode 100644
>>> index ..32fecb3fbc4c
>>> --- /dev/null
>>> +++
25 matches
Mail list logo
