On Fri, Oct 12, 2018 at 02:50:53PM -0700, Joe Stringer wrote:
> Dan Carpenter reports:
>
> The patch 6acc9b432e67: "bpf: Add helper to retrieve socket in BPF"
> from Oct 2, 2018, leads to the following Smatch complaint:
>
> net/core/filter.c:4893 bpf_sk_lookup()
> error: we previously ass
On 10/12/18 5:42 AM, Nikolay Aleksandrov wrote:
> This patch adds support for the new backup port option that can be set
> on a bridge port. If the port's carrier goes down all of the traffic
> gets redirected to the configured backup port. We add the following new
> arguments:
> $ ip link set dev
On 10/11/18 2:45 PM, Roopa Prabhu wrote:
> From: Roopa Prabhu
>
> Adds new option extern_learn to set NTF_EXT_LEARNED flag
> on neigh entries.
>
> Signed-off-by: Roopa Prabhu
> ---
> ip/ipneigh.c| 7 ++-
> man/man8/ip-neighbour.8 | 9 -
> 2 files changed, 14 insertions(
Hello
i need your help to invest in your region, please can you assist me?
On Fri, 2018-10-12 at 13:57 -0700, Cong Wang wrote:
> Why not just validate the fallback action in each action init()?
> For example, checking tcfg_paction in tcf_gact_init().
>
> I don't see the need of making it generic.
hello Cong, once again thanks for looking at this.
what you say is doable
the following script:
# tc f a dev v0 egress chain 4 matchall action simple sdata "A triumph!"
# tc f a dev v0 egress matchall action pass random determ goto chain 4 5
produces the following crash:
BUG: unable to handle kernel NULL pointer dereference at
PGD 0 P4D 0
Oops: 0
This is a fix for the port_set_speed method for the Topaz family.
Currently the same method is used as for the Peridot family, but
this is wrong for the SERDES port.
On Topaz, the SERDES port is port 5, not 9 and 10 as in Peridot.
Moreover setting alt_bit on Topaz only makes sense for port 0 (for
I, Mikhail Fridman have selected you specifically as one of my beneficiaries
for my Charitable Donation of $5 Million Dollars,
Check the link below for confirmation:
https://www.rt.com/business/343781-mikhail-fridman-will-charity/
I await your earliest response for further directives.
Best Reg
On 18/10/13 (土) 16:48, Jesper Dangaard Brouer wrote:
On Thu, 11 Oct 2018 18:36:48 +0900
Toshiaki Makita wrote:
Use existing atomic drop counter. Since drop path is really an
exceptional case here, I'm thinking atomic ops would not hurt the
performance.
Hmm... we try very hard not to add atom
On Thu, 11 Oct 2018 18:36:48 +0900
Toshiaki Makita wrote:
> Use existing atomic drop counter. Since drop path is really an
> exceptional case here, I'm thinking atomic ops would not hurt the
> performance.
Hmm... we try very hard not to add atomic ops to XDP code path. The
XDP_DROP case is also
10 matches
Mail list logo