1. Mar 25, 2023
  2. Mar 24, 2023
  3. Mar 23, 2023
    • Pedro Tammela's avatar
      net/sched: act_api: use the correct TCA_ACT attributes in dump · fcb3a465
      Pedro Tammela authored
      
      
      4 places in the act api code are using 'TCA_' definitions where they
      should be using 'TCA_ACT_', which is confusing for the reader, although
      functionally they are equivalent.
      
      Cc: Hangbin Liu <haliu@redhat.com>
      Reviewed-by: default avatarJamal Hadi Salim <jhs@mojatatu.com>
      Reviewed-by: default avatarSimon Horman <simon.horman@corigine.com>
      Signed-off-by: default avatarPedro Tammela <pctammela@mojatatu.com>
      Acked-by: default avatarHangbin Liu <haliu@redhat.com>
      Signed-off-by: default avatarDavid S. Miller <davem@davemloft.net>
      fcb3a465
    • David S. Miller's avatar
      Merge branch '1GbE' of git://git.kernel.org/pub/scm/linux/kernel/git/tnguy/next-queue · d0e43912
      David S. Miller authored
      
      
      Tony Nguyen says:
      
      ====================
      Intel Wired LAN Driver Updates 2023-03-21 (igb, igbvf, igc)
      
      This series contains updates to igb, igbvf, and igc drivers.
      
      Andrii changes igb driver to utilize diff_by_scaled_ppm() implementation
      over an open-coded version.
      
      Dawid adds pci_error_handlers for reset_prepare and reset_done for
      igbvf.
      
      Sasha removes unnecessary code in igc.
      ====================
      
      Signed-off-by: default avatarDavid S. Miller <davem@davemloft.net>
      d0e43912
    • David S. Miller's avatar
      Merge branch 'ipv4-address-protocol' · c5cf13fb
      David S. Miller authored
      Petr Machata says:
      
      ====================
      net: Allow changing IPv4 address protocol
      
      IPv4 and IPv6 addresses can be assigned a protocol value that indicates the
      provenance of the IP address. The attribute is modeled after ip route
      protocols, and essentially allows the administrator or userspace stack to
      tag addresses in some way that makes sense to the actor in question.
      
      When IP address protocol field was added in commit 47f0bd50
      
       ("net: Add
      new protocol attribute to IP addresses"), the semantics included the
      ability to change the protocol for IPv6 addresses, but not for IPv4
      addresses. It seems this was not deliberate, but rather by accident.
      
      One particular use case is tagging the addresses differently depending on
      whether the routing stack should advertise them or not. Without support for
      protocol replacement, this can not be done.
      
      In this patchset, extend IPv4 to allow changing the protocol defined at an
      address (in patch #1). Then in patches #2 and #3 add selftest coverage for
      ip address protocols.
      
      Currently the kernel simply ignores the new value. Thus allowing the
      replacement changes the observable behavior. However, since IPv6 already
      behaves like this anyway, and since the feature as such is relatively new,
      it seems like the change is safe to make.
      
      An example session with the feature in action:
      
      	bash-5.2# ip address add dev d 192.0.2.1/28 proto 0xab
      	bash-5.2# ip address show dev d
      	4: d: <BROADCAST,NOARP> mtu 1500 qdisc noop state DOWN group default qlen 1000
      	    link/ether 06:29:74:fd:1f:eb brd ff:ff:ff:ff:ff:ff
      	    inet 192.0.2.1/28 scope global proto 0xab d
      	       valid_lft forever preferred_lft forever
      
      	bash-5.2# ip address replace dev d 192.0.2.1/28 proto 0x11
      	bash-5.2# ip address show dev d
      	4: d: <BROADCAST,NOARP> mtu 1500 qdisc noop state DOWN group default qlen 1000
      	    link/ether 06:29:74:fd:1f:eb brd ff:ff:ff:ff:ff:ff
      	    inet 192.0.2.1/28 scope global proto 0x11 d
      	       valid_lft forever preferred_lft forever
      ====================
      
      Signed-off-by: default avatarDavid S. Miller <davem@davemloft.net>
      c5cf13fb
    • Petr Machata's avatar
      selftests: rtnetlink: Add an address proto test · 6a414fd7
      Petr Machata authored
      
      
      Add coverage of "ip address {add,replace} ... proto" support.
      
      Signed-off-by: default avatarPetr Machata <petrm@nvidia.com>
      Reviewed-by: default avatarIdo Schimmel <idosch@nvidia.com>
      Reviewed-by: default avatarDavid Ahern <dsahern@kernel.org>
      Signed-off-by: default avatarDavid S. Miller <davem@davemloft.net>
      6a414fd7
    • Petr Machata's avatar
      selftests: rtnetlink: Make the set of tests to run configurable · ecb3c1e6
      Petr Machata authored
      
      
      Extract the list of all tests into a variable, ALL_TESTS. Then assume the
      environment variable TESTS holds the list of tests to actually run, falling
      back to ALL_TESTS if TESTS is empty. This is the same interface that
      forwarding selftests use to make the set of tests to run configurable.
      In addition to this, allow setting the value explicitly through a command
      line option "-t" along the lines of what fib_nexthops.sh does.
      
      Signed-off-by: default avatarPetr Machata <petrm@nvidia.com>
      Reviewed-by: default avatarIdo Schimmel <idosch@nvidia.com>
      Signed-off-by: default avatarDavid S. Miller <davem@davemloft.net>
      ecb3c1e6
    • Petr Machata's avatar
      net: ipv4: Allow changing IPv4 address protocol · 5c4a9aa8
      Petr Machata authored
      When IP address protocol field was added in commit 47f0bd50
      
       ("net: Add
      new protocol attribute to IP addresses"), the semantics included the
      ability to change the protocol for IPv6 addresses, but not for IPv4
      addresses. It seems this was not deliberate, but rather by accident.
      
      A userspace that wants to change the protocol of an address might drop and
      recreate the address, but that disrupts routing and is just impractical.
      
      So in this patch, when an IPv4 address is replaced (through RTM_NEWADDR
      request with NLM_F_REPLACE flag), update the proto at the address to the
      one given in the request, or zero if none is given. This matches the
      behavior of IPv6. Previously, any new value given was simply ignored.
      
      Signed-off-by: default avatarPetr Machata <petrm@nvidia.com>
      Reviewed-by: default avatarIdo Schimmel <idosch@nvidia.com>
      Reviewed-by: default avatarDavid Ahern <dsahern@kernel.org>
      Signed-off-by: default avatarDavid S. Miller <davem@davemloft.net>
      5c4a9aa8
    • Jakub Kicinski's avatar
      Merge branch 'net-ipa-fully-support-ipa-v5-0' · 90bf6610
      Jakub Kicinski authored
      Alex Elder says:
      
      ====================
      net: ipa: fully support IPA v5.0
      
      At long last, add the IPA and GSI register definitions, and the
      configuration data required to support IPA v5.0.  This enables IPA
      support for the Qualcomm SDX65 SoC.
      
      The first version of this series had build errors due to a
      non-existent source file being required.  This version addresses
      that by changing how required files are specified in the Makefile.
      
      Note that the second patch has some warnings about lines starting
      with spaces; those spaces align text with the open parenthesis on
      the previous line.
      ====================
      
      Link: https://lore.kernel.org/r/20230321182644.2143990-1-elder@linaro.org
      
      
      Signed-off-by: default avatarJakub Kicinski <kuba@kernel.org>
      90bf6610
    • Alex Elder's avatar
      net: ipa: add IPA v5.0 configuration data · cb7550b4
      Alex Elder authored
      
      
      Add the configuration data required for IPA v5.0, which is used in
      the SDX65 SoC.
      
      Signed-off-by: default avatarAlex Elder <elder@linaro.org>
      Signed-off-by: default avatarJakub Kicinski <kuba@kernel.org>
      cb7550b4