Re: [PATCH mlx5-next 0/5] Mellanox, mlx5 next updates 2019-09-29

On Thu, 2019-08-29 at 23:42 +, Saeed Mahameed wrote: > Hi All, > > This series includes misc updates for mlx5-next shared branch > required > for upcoming software steering feature. > > 1) Alex adds HW bits and definitions required for SW steering > 2) Ariel moves device memory management to

RE: Proposal: r8152 firmware patching framework

Prashant Malani > > > > (Adding a few more Realtek folks) > > > > Friendly ping. Any thoughts / feedback, Realtek folks (and others) ? > > > >> On Thu, Aug 29, 2019 at 11:40 AM Prashant Malani > wrote: > >> > >> Hi, > >> > >> The r8152 driver source code distributed by Realtek (on > >> www.realt

Re: [PATCH net-next 3/3] net: phy: realtek: add support for the 2.5Gbps PHY in RTL8125

On 02.09.2019 04:07, Florian Fainelli wrote: > > > On 8/8/2019 1:24 PM, Heiner Kallweit wrote: >> On 08.08.2019 22:20, Andrew Lunn wrote: I have a contact in Realtek who provided the information about the vendor-specific registers used in the patch. I also asked for a method to aut

Re: [PATCH v3] tun: fix use-after-free when register netdev failed

On 2019/8/23 下午5:36, Yang Yingliang wrote: On 2019/8/23 11:05, Jason Wang wrote: - Original Message - On 2019/8/22 14:07, Yang Yingliang wrote: On 2019/8/22 10:13, Jason Wang wrote: On 2019/8/20 上午10:28, Jason Wang wrote: On 2019/8/20 上午9:25, David Miller wrote: From: Yang Yin

Re: [bpf-next, v2] samples: bpf: add max_pckt_size option at xdp_adjust_tail

On Fri, Aug 30, 2019 at 3:23 AM Daniel T. Lee wrote: > > On Fri, Aug 30, 2019 at 5:42 AM Song Liu wrote: > > > > On Mon, Aug 26, 2019 at 9:52 AM Daniel T. Lee > > wrote: > > > > > > Currently, at xdp_adjust_tail_kern.c, MAX_PCKT_SIZE is limited > > > to 600. To make this size flexible, a new ma

Re: [PATCH] net-ipv6: fix excessive RTF_ADDRCONF flag on ::1/128 local route (and others)

On Mon, Sep 2, 2019 at 2:55 AM Maciej Żenczykowski wrote: > It's not immediately clear to me what is the better approach as I'm > not immediately certain what RTF_ADDRCONF truly means. > However the in kernel header file comment does explicitly mention this > being used to flag routes derived from

Re: [PATCH net-next 3/3] net: phy: realtek: add support for the 2.5Gbps PHY in RTL8125

On 8/8/2019 1:24 PM, Heiner Kallweit wrote: > On 08.08.2019 22:20, Andrew Lunn wrote: >>> I have a contact in Realtek who provided the information about >>> the vendor-specific registers used in the patch. I also asked for >>> a method to auto-detect 2.5Gbps support but have no feedback so far.

Re: [PATCH 0/4 net-next] flow_offload: update mangle action representation

On Sat, 31 Aug 2019 16:22:17 +0200, Pablo Neira Ayuso wrote: > On Fri, Aug 30, 2019 at 03:33:51PM -0700, Jakub Kicinski wrote: > > On Fri, 30 Aug 2019 11:07:10 +0200, Pablo Neira Ayuso wrote: > > > > > * The front-end coalesces consecutive pedit actions into one single > > > > > word, so driver

Re: BUG_ON in skb_segment, after bpf_skb_change_proto was applied

On Thu, Aug 29, 2019 at 8:22 AM Shmulik Ladkani wrote: > > On Tue, 27 Aug 2019 14:10:35 +0200 > Daniel Borkmann wrote: > > > Given first point above wrt hitting rarely, it would be good to first get a > > better understanding for writing a reproducer. Back then Yonghong added one > > to the BPF k

Re: [PATCH v6 net-next 14/19] ionic: Add initial ethtool support

On Fri, Aug 30, 2019 at 03:16:41PM -0700, Jakub Kicinski wrote: > On Fri, 30 Aug 2019 14:25:12 -0700, Shannon Nelson wrote: > > On 8/29/19 4:10 PM, Jakub Kicinski wrote: > > > On Thu, 29 Aug 2019 11:27:15 -0700, Shannon Nelson wrote: > > >> +static int ionic_get_module_eeprom(struct net_device *n

Re: [PATCH net-next 00/10] net: dsa: mv88e6xxx: centralize SERDES IRQ handling

From: Vivien Didelot Date: Sat, 31 Aug 2019 16:18:26 -0400 > Following Marek's work on the abstraction of the SERDES lanes mapping, this > series trades the .serdes_irq_setup and .serdes_irq_free callbacks for new > .serdes_irq_mapping, .serdes_irq_enable and .serdes_irq_status operations. > > T

Re: [PATCH net-next] net: hns3: remove set but not used variable 'qos'

From: YueHaibing Date: Sat, 31 Aug 2019 12:29:11 + > Fixes gcc '-Wunused-but-set-variable' warning: > > drivers/net/ethernet/hisilicon/hns3/hns3pf/hclge_main.c: In function > 'hclge_restore_vlan_table': > drivers/net/ethernet/hisilicon/hns3/hns3pf/hclge_main.c:8016:18: warning: > variable

RT and PTP system timestamping

Hello people of netdev, linux-rt-users and linux-spi, Apologies in advance for asking a question about something I know nothing about. I am playing with a device driver of a SPI-controlled PTP timer. For my particular application it is important that the value of the PTP timer can be retrieved wi

Re: [PATCH net] isdn/capi: check message length in capi_write()

From: Eric Biggers Date: Sun, 1 Sep 2019 09:32:39 -0500 > From: Eric Biggers > > syzbot reported: > > BUG: KMSAN: uninit-value in capi_write+0x791/0xa90 > drivers/isdn/capi/capi.c:700 > CPU: 0 PID: 10025 Comm: syz-executor379 Not tainted 4.20.0-rc7+ #2 > Hardware name: Google Goo

Re: [PATCH net-next] r8169: don't set bit RxVlan on RTL8125

From: Heiner Kallweit Date: Sun, 1 Sep 2019 10:42:44 +0200 > RTL8125 uses a different register for VLAN offloading config, > therefore don't set bit RxVlan. > > Fixes: f1bce4ad2f1c ("r8169: add support for RTL8125") > Signed-off-by: Heiner Kallweit Applied.

Re: [PATCH] net-ipv6: fix excessive RTF_ADDRCONF flag on ::1/128 local route (and others)

Some background: This was found due to bad interactions with one of the few remaining Android common kernel networking patches. (The one that makes it possible for RA's to create routes in interface specific tables) The cleanup portion of it scours all tables and deletes all relevant ADDRCONF rou

[PATCH] net-ipv6: fix excessive RTF_ADDRCONF flag on ::1/128 local route (and others)

From: Maciej Żenczykowski There is a subtle change in behaviour introduced by: commit c7a1ce397adacaf5d4bb2eab0a738b5f80dc3e43 'ipv6: Change addrconf_f6i_alloc to use ip6_route_info_create' Before that patch /proc/net/ipv6_route includes: 0001 80 0

[PATCH net] isdn/capi: check message length in capi_write()

From: Eric Biggers syzbot reported: BUG: KMSAN: uninit-value in capi_write+0x791/0xa90 drivers/isdn/capi/capi.c:700 CPU: 0 PID: 10025 Comm: syz-executor379 Not tainted 4.20.0-rc7+ #2 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011 Call

[PATCH net-next] r8169: don't set bit RxVlan on RTL8125

RTL8125 uses a different register for VLAN offloading config, therefore don't set bit RxVlan. Fixes: f1bce4ad2f1c ("r8169: add support for RTL8125") Signed-off-by: Heiner Kallweit --- drivers/net/ethernet/realtek/r8169_main.c | 6 -- 1 file changed, 4 insertions(+), 2 deletions(-) diff --gi

Re: [patch net-next v2] mlx5: Add missing init_net check in FIB notifier

On 2019-08-30 11:25 AM, Jiri Pirko wrote: > From: Jiri Pirko > > Take only FIB events that are happening in init_net into account. No other > namespaces are supported. > > Signed-off-by: Jiri Pirko > --- > v1->v2: > - no change, just cced maintainers (fat finger made me avoid them in v1) > --

[PATCHv2 1/1] forcedeth: use per cpu to collect xmit/recv statistics

When testing with a background iperf pushing 1Gbit/sec traffic and running both ifconfig and netstat to collect statistics, some deadlocks occurred. Ifconfig and netstat will call nv_get_stats64 to get software xmit/recv statistics. In the commit f5d827aece36 ("forcedeth: implement ndo_get_stats64

[PATCHv2 0/1] Fix deadlock problem and make performance better

When running with about 1Gbit/ses for very long time, running ifconfig and netstat causes dead lock. These symptoms are similar to the commit 5f6b4e14cada ("net: dsa: User per-cpu 64-bit statistics"). After replacing network devices statistics with per-cpu 64-bit statistics, the dead locks disappea