08 Mar, 2020

1 commit

  • Merge Linux stable release v5.4.24 into imx_5.4.y

    * tag 'v5.4.24': (3306 commits)
    Linux 5.4.24
    blktrace: Protect q->blk_trace with RCU
    kvm: nVMX: VMWRITE checks unsupported field before read-only field
    ...

    Signed-off-by: Jason Liu

    Conflicts:
    arch/arm/boot/dts/imx6sll-evk.dts
    arch/arm/boot/dts/imx7ulp.dtsi
    arch/arm64/boot/dts/freescale/fsl-ls1028a.dtsi
    drivers/clk/imx/clk-composite-8m.c
    drivers/gpio/gpio-mxc.c
    drivers/irqchip/Kconfig
    drivers/mmc/host/sdhci-of-esdhc.c
    drivers/mtd/nand/raw/gpmi-nand/gpmi-nand.c
    drivers/net/can/flexcan.c
    drivers/net/ethernet/freescale/dpaa/dpaa_eth.c
    drivers/net/ethernet/mscc/ocelot.c
    drivers/net/ethernet/stmicro/stmmac/stmmac_main.c
    drivers/net/ethernet/stmicro/stmmac/stmmac_platform.c
    drivers/net/phy/realtek.c
    drivers/pci/controller/mobiveil/pcie-mobiveil-host.c
    drivers/perf/fsl_imx8_ddr_perf.c
    drivers/tee/optee/shm_pool.c
    drivers/usb/cdns3/gadget.c
    kernel/sched/cpufreq.c
    net/core/xdp.c
    sound/soc/fsl/fsl_esai.c
    sound/soc/fsl/fsl_sai.c
    sound/soc/sof/core.c
    sound/soc/sof/imx/Kconfig
    sound/soc/sof/loader.c

    Jason Liu
     

05 Mar, 2020

1 commit

  • commit 78e06cf430934fc3768c342cbebdd1013dcd6fa7 upstream.

    In the flowtable documentation there is a missing semicolon, the command
    as is would give this error:

    nftables.conf:5:27-33: Error: syntax error, unexpected devices, expecting newline or semicolon
    hook ingress priority 0 devices = { br0, pppoe-data };
    ^^^^^^^
    nftables.conf:4:12-13: Error: invalid hook (null)
    flowtable ft {
    ^^

    Fixes: 19b351f16fd9 ("netfilter: add flowtable documentation")
    Signed-off-by: Matteo Croce
    Signed-off-by: Pablo Neira Ayuso
    Signed-off-by: Greg Kroah-Hartman

    Matteo Croce
     

26 Feb, 2020

1 commit

  • Some MAC PCS blocks are unable to provide interrupts when their status
    changes. As we already have support in phylink for polling status, use
    this to provide a hook for MACs to enable polling mode.

    The patch idea was picked up from Russell King's suggestion on the macb
    phylink patch thread here [0] but the implementation was changed.
    Instead of introducing a new phylink_start_poll() function, which would
    make the implementation cumbersome for common PHYLINK implementations
    for multiple types of devices, like DSA, just add a boolean property to
    the phylink_config structure, which is just as backwards-compatible.

    https://lkml.org/lkml/2019/12/16/603

    Suggested-by: Russell King
    Signed-off-by: Vladimir Oltean

    Conflicts:
    drivers/net/phy/phylink.c

    with upstream commit 24cf0e693bb5 ("net: phylink: split link_an_mode
    configured and current settings") submitted for net-next and merged
    during v5.5-rc1.

    (cherry picked from commit ac7420c5ede06ebe049c6bce8ba9e9d7d3a51d11)

    Vladimir Oltean
     

18 Jan, 2020

1 commit

  • commit 8ac9d71d601374222a230804e419cd40c4492e1c upstream.

    During development the define J1939_PGN_ADDRESS_REQUEST was renamed to
    J1939_PGN_REQUEST. It was forgotten to adjust the documentation
    accordingly.

    This patch fixes the name of the symbol.

    Reported-by: https://github.com/linux-can/can-utils/issues/159#issuecomment-556538798
    Fixes: 9d71dd0c7009 ("can: add support of SAE J1939 protocol")
    Cc: Oleksij Rempel
    Signed-off-by: Marc Kleine-Budde
    Signed-off-by: Greg Kroah-Hartman

    Marc Kleine-Budde
     

06 Nov, 2019

1 commit

  • Add TLS TX counter description for the handshake retransmitted
    packets that triggers the resync procedure then skip it, going
    into the regular transmit flow.

    Fixes: 46a3ea98074e ("net/mlx5e: kTLS, Enhance TX resync flow")
    Signed-off-by: Tariq Toukan
    Signed-off-by: Saeed Mahameed
    Acked-by: Jakub Kicinski
    Signed-off-by: David S. Miller

    Tariq Toukan
     

02 Nov, 2019

2 commits

  • Jeff Kirsher says:

    ====================
    Intel Wired LAN Driver Updates 2019-11-01

    This series contains updates to e1000, igb, igc, ixgbe, i40e and driver
    documentation.

    Lyude Paul fixes an issue where a fatal read error occurs when the
    device is unplugged from the machine. So change the read error into a
    warn while the device is still present.

    Manfred Rudigier found that the i350 device was not apart of the "Media
    Auto Sense" feature, yet the device supports it. So add the missing
    i350 device to the check and fix an issue where the media auto sense
    would flip/flop when no cable was connected to the port causing spurious
    kernel log messages.

    I fixed an issue where the fix to resolve receive buffer starvation was
    applied in more than one place in the driver, one being the incorrect
    location in the i40e driver.

    Wenwen Wang fixes a potential memory leak in e1000 where allocated
    memory is not properly cleaned up in one of the error paths.

    Jonathan Neuschäfer cleans up the driver documentation to be consistent
    and remove the footnote reference, since the footnote no longer exists in
    the documentation.

    Igor Pylypiv cleans up a duplicate clearing of a bit, no need to clear
    it twice.

    v2: Fixed alignment issue in patch 3 of the series based on community
    feedback.
    ====================

    Signed-off-by: David S. Miller

    David S. Miller
     
  • These asterisks were once references to a line that said:
    "* Other names and brands may be claimed as the property of others."
    But now, they serve no purpose; they can only irritate the reader.

    Fixes: de3edab4276c ("e1000: update README for e1000")
    Fixes: a3fb65680f65 ("e100.txt: Cleanup license info in kernel doc")
    Fixes: da8c01c4502a ("e1000e.txt: Add e1000e documentation")
    Fixes: f12a84a9f650 ("Documentation: fm10k: Add kernel documentation")
    Fixes: b55c52b1938c ("igb.txt: Add igb documentation")
    Fixes: c4e9b56e2442 ("igbvf.txt: Add igbvf Documentation")
    Fixes: d7064f4c192c ("Documentation/networking/: Update Intel wired LAN driver documentation")
    Fixes: c4b8c01112a1 ("ixgbevf.txt: Update ixgbevf documentation")
    Fixes: 1e06edcc2f22 ("Documentation: i40e: Prepare documentation for RST conversion")
    Fixes: 105bf2fe6b32 ("i40evf: add driver to kernel build system")
    Fixes: 1fae869bcf3d ("Documentation: ice: Prepare documentation for RST conversion")
    Fixes: df69ba43217d ("ionic: Add basic framework for IONIC Network device driver")
    Signed-off-by: Jonathan Neuschäfer
    Tested-by: Aaron Brown
    Signed-off-by: Jeff Kirsher

    Jonathan Neuschäfer
     

01 Nov, 2019

2 commits

  • tcp_max_syn_backlog default value depends on memory size
    and TCP ehash size. Before this patch, the max value
    was 2048 [1], which is considered too small nowadays.

    Increase it to 4096 to match the recent SOMAXCONN change.

    [1] This is with TCP ehash size being capped to 524288 buckets.

    Signed-off-by: Eric Dumazet
    Cc: Willy Tarreau
    Cc: Yue Cao
    Signed-off-by: David S. Miller

    Eric Dumazet
     
  • SOMAXCONN is /proc/sys/net/core/somaxconn default value.

    It has been defined as 128 more than 20 years ago.

    Since it caps the listen() backlog values, the very small value has
    caused numerous problems over the years, and many people had
    to raise it on their hosts after beeing hit by problems.

    Google has been using 1024 for at least 15 years, and we increased
    this to 4096 after TCP listener rework has been completed, more than
    4 years ago. We got no complain of this change breaking any
    legacy application.

    Many applications indeed setup a TCP listener with listen(fd, -1);
    meaning they let the system select the backlog.

    Raising SOMAXCONN lowers chance of the port being unavailable under
    even small SYNFLOOD attack, and reduces possibilities of side channel
    vulnerabilities.

    Signed-off-by: Eric Dumazet
    Cc: Willy Tarreau
    Cc: Yue Cao
    Signed-off-by: David S. Miller

    Eric Dumazet
     

11 Oct, 2019

1 commit

  • Commit 8960b38932be ("linux/dim: Rename externally used net_dim
    members") renamed the net_dim API, removing the "net_" prefix from the
    structures and functions. The patch didn't update the net_dim.txt
    documentation file.

    Fix the documentation so that its examples match the current code.

    Fixes: 8960b38932be ("linux/dim: Rename externally used net_dim members", 2019-06-25)
    Fixes: c002bd529d71 ("linux/dim: Rename externally exposed macros", 2019-06-25)
    Fixes: 4f75da3666c0 ("linux/dim: Move implementation to .c files")
    Cc: Tal Gilboa
    Signed-off-by: Jacob Keller
    Signed-off-by: Jakub Kicinski

    Jacob Keller
     

09 Oct, 2019

1 commit

  • Fix documentation build warnings for Pensando ionic:

    Documentation/networking/device_drivers/pensando/ionic.rst:39: WARNING: Unexpected indentation.
    Documentation/networking/device_drivers/pensando/ionic.rst:43: WARNING: Unexpected indentation.

    Fixes: df69ba43217d ("ionic: Add basic framework for IONIC Network device driver")
    Signed-off-by: Randy Dunlap
    Acked-by: Shannon Nelson
    Signed-off-by: Jakub Kicinski

    Randy Dunlap
     

02 Oct, 2019

1 commit


28 Sep, 2019

1 commit

  • Alex noted that the below description might not be obvious to all users.
    Clarify it by adding an example.

    Fixes: f3047ca01f12 ("Documentation: Add devlink-trap documentation")
    Reported-by: Alex Kushnarov
    Reviewed-by: Alex Kushnarov
    Acked-by: Jiri Pirko
    Signed-off-by: Ido Schimmel
    Signed-off-by: David S. Miller

    Ido Schimmel
     

19 Sep, 2019

1 commit

  • Pull networking updates from David Miller:

    1) Support IPV6 RA Captive Portal Identifier, from Maciej Żenczykowski.

    2) Use bio_vec in the networking instead of custom skb_frag_t, from
    Matthew Wilcox.

    3) Make use of xmit_more in r8169 driver, from Heiner Kallweit.

    4) Add devmap_hash to xdp, from Toke Høiland-Jørgensen.

    5) Support all variants of 5750X bnxt_en chips, from Michael Chan.

    6) More RTNL avoidance work in the core and mlx5 driver, from Vlad
    Buslov.

    7) Add TCP syn cookies bpf helper, from Petar Penkov.

    8) Add 'nettest' to selftests and use it, from David Ahern.

    9) Add extack support to drop_monitor, add packet alert mode and
    support for HW drops, from Ido Schimmel.

    10) Add VLAN offload to stmmac, from Jose Abreu.

    11) Lots of devm_platform_ioremap_resource() conversions, from
    YueHaibing.

    12) Add IONIC driver, from Shannon Nelson.

    13) Several kTLS cleanups, from Jakub Kicinski.

    * git://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next: (1930 commits)
    mlxsw: spectrum_buffers: Add the ability to query the CPU port's shared buffer
    mlxsw: spectrum: Register CPU port with devlink
    mlxsw: spectrum_buffers: Prevent changing CPU port's configuration
    net: ena: fix incorrect update of intr_delay_resolution
    net: ena: fix retrieval of nonadaptive interrupt moderation intervals
    net: ena: fix update of interrupt moderation register
    net: ena: remove all old adaptive rx interrupt moderation code from ena_com
    net: ena: remove ena_restore_ethtool_params() and relevant fields
    net: ena: remove old adaptive interrupt moderation code from ena_netdev
    net: ena: remove code duplication in ena_com_update_nonadaptive_moderation_interval _*()
    net: ena: enable the interrupt_moderation in driver_supported_features
    net: ena: reimplement set/get_coalesce()
    net: ena: switch to dim algorithm for rx adaptive interrupt moderation
    net: ena: add intr_moder_rx_interval to struct ena_com_dev and use it
    net: phy: adin: implement Energy Detect Powerdown mode via phy-tunable
    ethtool: implement Energy Detect Powerdown support via phy-tunable
    xen-netfront: do not assume sk_buff_head list is empty in error handling
    s390/ctcm: Delete unnecessary checks before the macro call “dev_kfree_skb”
    net: ena: don't wake up tx queue when down
    drop_monitor: Better sanitize notified packets
    ...

    Linus Torvalds
     

18 Sep, 2019

1 commit

  • Pull documentation updates from Jonathan Corbet:
    "It's a somewhat calmer cycle for docs this time, as the churn of the
    mass RST conversion is happily mostly behind us.

    - A new document on reproducible builds.

    - We finally got around to zapping the documentation for hardware
    support that was removed in 2004; one doesn't want to rush these
    things.

    - The usual assortment of fixes, typo corrections, etc"

    * tag 'docs-5.4' of git://git.lwn.net/linux: (67 commits)
    Documentation: kbuild: Add document about reproducible builds
    docs: printk-formats: Stop encouraging use of unnecessary %h[xudi] and %hh[xudi]
    Documentation: Add "earlycon=sbi" to the admin guide
    doc:lock: remove reference to clever use of read-write lock
    devices.txt: improve entry for comedi (char major 98)
    docs: mtd: Update spi nor reference driver
    doc: arm64: fix grammar dtb placed in no attributes region
    Documentation: sysrq: don't recommend 'S' 'U' before 'B'
    mailmap: Update email address for Quentin Perret
    docs: ftrace: clarify when tracing is disabled by the trace file
    docs: process: fix broken link
    Documentation/arm/samsung-s3c24xx: Remove stray U+FEFF character to fix title
    Documentation/arm/sa1100/assabet: Fix 'make assabet_defconfig' command
    Documentation/arm/sa1100: Remove some obsolete documentation
    docs/zh_CN: update Chinese howto.rst for latexdocs making
    Documentation: virt: Fix broken reference to virt tree's index
    docs: Fix typo on pull requests guide
    kernel-doc: Allow anonymous enum
    Documentation: sphinx: Don't parse socket() as identifier reference
    Documentation: sphinx: Add missing comma to list of strings
    ...

    Linus Torvalds
     

17 Sep, 2019

1 commit


16 Sep, 2019

1 commit


11 Sep, 2019

5 commits

  • This adds the initial documentation for the NFP driver specific
    documentation.

    Right now, only basic information is provided about acquiring firmware
    and configuring device firmware loading.

    Original driver documentation can be found here:
    https://github.com/Netronome/nfp-drv-kmods/blob/master/README.md

    Signed-off-by: Dirk van der Merwe
    Signed-off-by: Jakub Kicinski
    Signed-off-by: Simon Horman
    Signed-off-by: David S. Miller

    Dirk van der Merwe
     
  • Add support for the 'reset_dev_on_drv_probe' devlink parameter. The
    reset control policy is controlled by the 'abi_drv_reset' hwinfo key.

    Signed-off-by: Dirk van der Merwe
    Signed-off-by: Jakub Kicinski
    Signed-off-by: Simon Horman
    Signed-off-by: David S. Miller

    Dirk van der Merwe
     
  • Add support for the 'fw_load_policy' devlink parameter. The FW load
    policy is controlled by the 'app_fw_from_flash' hwinfo key.

    Remap the values from devlink to the hwinfo key and back.

    Signed-off-by: Dirk van der Merwe
    Signed-off-by: Jakub Kicinski
    Signed-off-by: Simon Horman
    Signed-off-by: David S. Miller

    Dirk van der Merwe
     
  • Add the 'reset_dev_on_drv_probe' devlink parameter, controlling the
    device reset policy on driver probe.

    This parameter is useful in conjunction with the existing
    'fw_load_policy' parameter.

    Signed-off-by: Dirk van der Merwe
    Signed-off-by: Jakub Kicinski
    Signed-off-by: Simon Horman
    Signed-off-by: David S. Miller

    Dirk van der Merwe
     
  • Add the 'disk' value to the generic 'fw_load_policy' devlink parameter.
    This value indicates that firmware should always be loaded from disk
    only.

    Signed-off-by: Dirk van der Merwe
    Signed-off-by: Jakub Kicinski
    Signed-off-by: Simon Horman
    Signed-off-by: David S. Miller

    Dirk van der Merwe
     

10 Sep, 2019

1 commit


06 Sep, 2019

1 commit

  • Daniel Borkmann says:

    ====================
    The following pull-request contains BPF updates for your *net-next* tree.

    The main changes are:

    1) Add the ability to use unaligned chunks in the AF_XDP umem. By
    relaxing where the chunks can be placed, it allows to use an
    arbitrary buffer size and place whenever there is a free
    address in the umem. Helps more seamless DPDK AF_XDP driver
    integration. Support for i40e, ixgbe and mlx5e, from Kevin and
    Maxim.

    2) Addition of a wakeup flag for AF_XDP tx and fill rings so the
    application can wake up the kernel for rx/tx processing which
    avoids busy-spinning of the latter, useful when app and driver
    is located on the same core. Support for i40e, ixgbe and mlx5e,
    from Magnus and Maxim.

    3) bpftool fixes for printf()-like functions so compiler can actually
    enforce checks, bpftool build system improvements for custom output
    directories, and addition of 'bpftool map freeze' command, from Quentin.

    4) Support attaching/detaching XDP programs from 'bpftool net' command,
    from Daniel.

    5) Automatic xskmap cleanup when AF_XDP socket is released, and several
    barrier/{read,write}_once fixes in AF_XDP code, from Björn.

    6) Relicense of bpf_helpers.h/bpf_endian.h for future libbpf
    inclusion as well as libbpf versioning improvements, from Andrii.

    7) Several new BPF kselftests for verifier precision tracking, from Alexei.

    8) Several BPF kselftest fixes wrt endianess to run on s390x, from Ilya.

    9) And more BPF kselftest improvements all over the place, from Stanislav.

    10) Add simple BPF map op cache for nfp driver to batch dumps, from Jakub.

    11) AF_XDP socket umem mapping improvements for 32bit archs, from Ivan.

    12) Add BPF-to-BPF call and BTF line info support for s390x JIT, from Yauheni.

    13) Small optimization in arm64 JIT to spare 1 insns for BPF_MOD, from Jerin.

    14) Fix an error check in bpf_tcp_gen_syncookie() helper, from Petar.

    15) Various minor fixes and cleanups, from Nathan, Masahiro, Masanari,
    Peter, Wei, Yue.
    ====================

    Signed-off-by: David S. Miller

    David S. Miller
     

05 Sep, 2019

3 commits

  • …x/kernel/git/mkl/linux-can-next

    Marc Kleine-Budde says:

    ====================
    pull-request: can-next 2019-09-04 j1939

    this is a pull request for net-next/master consisting of 21 patches.

    the first 12 patches are by me and target the CAN core infrastructure.
    They clean up the names of variables , structs and struct members,
    convert can_rx_register() to use max() instead of open coding it and
    remove unneeded code from the can_pernet_exit() callback.

    The next three patches are also by me and they introduce and make use of
    the CAN midlayer private structure. It is used to hold protocol specific
    per device data structures.

    The next patch is by Oleksij Rempel, switches the
    &net->can.rcvlists_lock from a spin_lock() to a spin_lock_bh(), so that
    it can be used from NAPI (soft IRQ) context.

    The next 4 patches are by Kurt Van Dijck, he first updates his email
    address via mailmap and then extends sockaddr_can to include j1939
    members.

    The final patch is the collective effort of many entities (The j1939
    authors: Oliver Hartkopp, Bastian Stender, Elenita Hinds, kbuild test
    robot, Kurt Van Dijck, Maxime Jayat, Robin van der Gracht, Oleksij
    Rempel, Marc Kleine-Budde). It adds support of SAE J1939 protocol to the
    CAN networking stack.

    SAE J1939 is the vehicle bus recommended practice used for communication
    and diagnostics among vehicle components. Originating in the car and
    heavy-duty truck industry in the United States, it is now widely used in
    other parts of the world.

    P.S.: This pull request doesn't invalidate my last pull request:
    "pull-request: can-next 2019-09-03".
    ====================

    Signed-off-by: David S. Miller <davem@davemloft.net>

    David S. Miller
     
  • This patch adds a basic driver framework for the Pensando IONIC
    network device. There is no functionality right now other than
    the ability to load and unload.

    Signed-off-by: Shannon Nelson
    Signed-off-by: David S. Miller

    Shannon Nelson
     
  • The current tag set is still rather small and needs a couple
    more tags to help with ASIC identification and to have a
    more generic FW version.

    Cc: Jiri Pirko
    Acked-by: Jakub Kicinski
    Signed-off-by: Shannon Nelson
    Signed-off-by: David S. Miller

    Shannon Nelson
     

04 Sep, 2019

2 commits

  • SAE J1939 is the vehicle bus recommended practice used for communication
    and diagnostics among vehicle components. Originating in the car and
    heavy-duty truck industry in the United States, it is now widely used in
    other parts of the world.

    J1939, ISO 11783 and NMEA 2000 all share the same high level protocol.
    SAE J1939 can be considered the replacement for the older SAE J1708 and
    SAE J1587 specifications.

    Acked-by: Oliver Hartkopp
    Signed-off-by: Bastian Stender
    Signed-off-by: Elenita Hinds
    Signed-off-by: kbuild test robot
    Signed-off-by: Kurt Van Dijck
    Signed-off-by: Maxime Jayat
    Signed-off-by: Robin van der Gracht
    Signed-off-by: Oleksij Rempel
    Signed-off-by: Marc Kleine-Budde

    The j1939 authors
     
  • Add new parameter (flow_steering_mode) to control the flow steering
    mode of the driver.
    Two modes are supported:
    1. DMFS - Device managed flow steering
    2. SMFS - Software/Driver managed flow steering.

    In the DMFS mode, the HW steering entities are created through the
    FW. In the SMFS mode this entities are created though the driver
    directly.

    The driver will use the devlink steering mode only if the steering
    domain supports it, for now SMFS will manages only the switchdev eswitch
    steering domain.

    User command examples:
    - Set SMFS flow steering mode::

    $ devlink dev param set pci/0000:06:00.0 name flow_steering_mode value "smfs" cmode runtime

    - Read device flow steering mode::

    $ devlink dev param show pci/0000:06:00.0 name flow_steering_mode
    pci/0000:06:00.0:
    name flow_steering_mode type driver-specific
    values:
    cmode runtime value smfs

    Signed-off-by: Maor Gottlieb
    Signed-off-by: Saeed Mahameed

    Maor Gottlieb
     

31 Aug, 2019

1 commit

  • The addition of unaligned chunks mode, the documentation needs to be
    updated to indicate that the incoming addr to the fill ring will only be
    masked if the user application is run in the aligned chunk mode. This patch
    also adds a line to explicitly indicate that the incoming addr will not be
    masked if running the user application in the unaligned chunk mode.

    Signed-off-by: Kevin Laatz
    Acked-by: Jonathan Lemon
    Signed-off-by: Daniel Borkmann

    Kevin Laatz
     

22 Aug, 2019

3 commits

  • Allow tracing neigh state during neigh update task that is executed on
    workqueue and is scheduled by neigh state change event.

    Usage example:
    ># cd /sys/kernel/debug/tracing
    ># echo mlx5:mlx5e_rep_neigh_update >> set_event
    ># cat trace
    ...
    kworker/u48:7-2221 [009] ...1 1475.387435: mlx5e_rep_neigh_update:
    netdev: ens1f0 MAC: 24:8a:07:9a:17:9a IPv4: 1.1.1.10 IPv6: ::ffff:1.1.1.10 neigh_connected=1

    Added corresponding documentation in
    Documentation/networking/device-driver/mellanox/mlx5.rst

    Signed-off-by: Vlad Buslov
    Reviewed-by: Dmytro Linkin
    Signed-off-by: Saeed Mahameed

    Vlad Buslov
     
  • Allow tracing result of neigh used value update task that is executed
    periodically on workqueue.

    Usage example:
    ># cd /sys/kernel/debug/tracing
    ># echo mlx5:mlx5e_tc_update_neigh_used_value >> set_event
    ># cat trace
    ...
    kworker/u48:4-8806 [009] ...1 55117.882428: mlx5e_tc_update_neigh_used_value:
    netdev: ens1f0 IPv4: 1.1.1.10 IPv6: ::ffff:1.1.1.10 neigh_used=1

    Added corresponding documentation in
    Documentation/networking/device-driver/mellanox/mlx5.rst

    Signed-off-by: Vlad Buslov
    Reviewed-by: Dmytro Linkin
    Signed-off-by: Saeed Mahameed

    Vlad Buslov
     
  • Implemented following tracepoints:
    1. Configure flower (mlx5e_configure_flower)
    2. Delete flower (mlx5e_delete_flower)
    3. Stats flower (mlx5e_stats_flower)

    Usage example:
    ># cd /sys/kernel/debug/tracing
    ># echo mlx5:mlx5e_configure_flower >> set_event
    ># cat trace
    ...
    tc-6535 [019] ...1 2672.404466: mlx5e_configure_flower: cookie=0000000067874a55 actions= REDIRECT

    Added corresponding documentation in
    Documentation/networking/device-driver/mellanox/mlx5.rst

    Signed-off-by: Dmytro Linkin
    Reviewed-by: Vlad Buslov
    Signed-off-by: Saeed Mahameed

    Dmytro Linkin
     

21 Aug, 2019

1 commit


20 Aug, 2019

1 commit


18 Aug, 2019

3 commits


10 Aug, 2019

1 commit

  • The current implementation of TCP MTU probing can considerably
    underestimate the MTU on lossy connections allowing the MSS to get down to
    48. We have found that in almost all of these cases on our networks these
    paths can handle much larger MTUs meaning the connections are being
    artificially limited. Even though TCP MTU probing can raise the MSS back up
    we have seen this not to be the case causing connections to be "stuck" with
    an MSS of 48 when heavy loss is present.

    Prior to pushing out this change we could not keep TCP MTU probing enabled
    b/c of the above reasons. Now with a reasonble floor set we've had it
    enabled for the past 6 months.

    The new sysctl will still default to TCP_MIN_SND_MSS (48), but gives
    administrators the ability to control the floor of MSS probing.

    Signed-off-by: Josh Hunt
    Signed-off-by: Eric Dumazet
    Acked-by: Neal Cardwell
    Signed-off-by: David S. Miller

    Josh Hunt
     

09 Aug, 2019

1 commit

  • sk_validate_xmit_skb() and drivers depend on the sk member of
    struct sk_buff to identify segments requiring encryption.
    Any operation which removes or does not preserve the original TLS
    socket such as skb_orphan() or skb_clone() will cause clear text
    leaks.

    Make the TCP socket underlying an offloaded TLS connection
    mark all skbs as decrypted, if TLS TX is in offload mode.
    Then in sk_validate_xmit_skb() catch skbs which have no socket
    (or a socket with no validation) and decrypted flag set.

    Note that CONFIG_SOCK_VALIDATE_XMIT, CONFIG_TLS_DEVICE and
    sk->sk_validate_xmit_skb are slightly interchangeable right now,
    they all imply TLS offload. The new checks are guarded by
    CONFIG_TLS_DEVICE because that's the option guarding the
    sk_buff->decrypted member.

    Second, smaller issue with orphaning is that it breaks
    the guarantee that packets will be delivered to device
    queues in-order. All TLS offload drivers depend on that
    scheduling property. This means skb_orphan_partial()'s
    trick of preserving partial socket references will cause
    issues in the drivers. We need a full orphan, and as a
    result netem delay/throttling will cause all TLS offload
    skbs to be dropped.

    Reusing the sk_buff->decrypted flag also protects from
    leaking clear text when incoming, decrypted skb is redirected
    (e.g. by TC).

    See commit 0608c69c9a80 ("bpf: sk_msg, sock{map|hash} redirect
    through ULP") for justification why the internal flag is safe.
    The only location which could leak the flag in is tcp_bpf_sendmsg(),
    which is taken care of by clearing the previously unused bit.

    v2:
    - remove superfluous decrypted mark copy (Willem);
    - remove the stale doc entry (Boris);
    - rely entirely on EOR marking to prevent coalescing (Boris);
    - use an internal sendpages flag instead of marking the socket
    (Boris).
    v3 (Willem):
    - reorganize the can_skb_orphan_partial() condition;
    - fix the flag leak-in through tcp_bpf_sendmsg.

    Signed-off-by: Jakub Kicinski
    Acked-by: Willem de Bruijn
    Reviewed-by: Boris Pismenny
    Signed-off-by: David S. Miller

    Jakub Kicinski