netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jakub Kicinski <kuba@kernel.org>
To: davem@davemloft.net
Cc: netdev@vger.kernel.org, ralf@linux-mips.org, jreuter@yaina.de,
	yoshfuji@linux-ipv6.org, dsahern@kernel.org, jmaloy@redhat.com,
	ying.xue@windriver.com, linux-hams@vger.kernel.org,
	tipc-discussion@lists.sourceforge.net,
	Jakub Kicinski <kuba@kernel.org>
Subject: [PATCH net-next 0/6] net: constify dev_addr passing for protocols
Date: Tue, 12 Oct 2021 08:58:34 -0700	[thread overview]
Message-ID: <20211012155840.4151590-1-kuba@kernel.org> (raw)

Commit 406f42fa0d3c ("net-next: When a bond have a massive amount 
of VLANs...") introduced a rbtree for faster Ethernet address look
up. To maintain netdev->dev_addr in this tree we need to make all
the writes to it got through appropriate helpers.

netdev->dev_addr will be made const to prevent direct writes.
This set sprinkles const across variables and arguments in protocol
code which are used to hold references to netdev->dev_addr.

Jakub Kicinski (6):
  ax25: constify dev_addr passing
  rose: constify dev_addr passing
  llc/snap: constify dev_addr passing
  ipv6: constify dev_addr passing
  tipc: constify dev_addr passing
  decnet: constify dev_addr passing

 include/net/ax25.h     | 13 +++++++------
 include/net/datalink.h |  2 +-
 include/net/dn.h       |  2 +-
 include/net/llc.h      |  2 +-
 include/net/llc_if.h   |  3 ++-
 include/net/ndisc.h    |  2 +-
 include/net/rose.h     |  8 ++++----
 net/802/p8022.c        |  2 +-
 net/802/psnap.c        |  2 +-
 net/ax25/af_ax25.c     |  2 +-
 net/ax25/ax25_dev.c    |  2 +-
 net/ax25/ax25_iface.c  |  6 +++---
 net/ax25/ax25_in.c     |  4 ++--
 net/ax25/ax25_out.c    |  2 +-
 net/ipv6/addrconf.c    |  4 ++--
 net/ipv6/ndisc.c       |  4 ++--
 net/llc/llc_c_ac.c     |  2 +-
 net/llc/llc_if.c       |  2 +-
 net/llc/llc_output.c   |  2 +-
 net/llc/llc_proc.c     |  2 +-
 net/netrom/af_netrom.c |  4 ++--
 net/netrom/nr_dev.c    |  6 +++---
 net/netrom/nr_route.c  |  4 ++--
 net/rose/af_rose.c     |  5 +++--
 net/rose/rose_dev.c    |  6 +++---
 net/rose/rose_link.c   |  8 ++++----
 net/rose/rose_route.c  | 10 ++++++----
 net/tipc/bearer.c      |  4 ++--
 net/tipc/bearer.h      |  2 +-
 net/tipc/eth_media.c   |  2 +-
 net/tipc/ib_media.c    |  2 +-
 31 files changed, 63 insertions(+), 58 deletions(-)

-- 
2.31.1


             reply	other threads:[~2021-10-12 15:58 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-12 15:58 Jakub Kicinski [this message]
2021-10-12 15:58 ` [PATCH net-next 1/6] ax25: constify dev_addr passing Jakub Kicinski
2021-10-12 15:58 ` [PATCH net-next 2/6] rose: " Jakub Kicinski
2021-10-12 15:58 ` [PATCH net-next 3/6] llc/snap: " Jakub Kicinski
2021-10-12 15:58 ` [PATCH net-next 4/6] ipv6: " Jakub Kicinski
2021-10-12 15:58 ` [PATCH net-next 5/6] tipc: " Jakub Kicinski
2021-10-12 15:58 ` [PATCH net-next 6/6] decnet: " Jakub Kicinski
2021-10-13 17:50 ` [PATCH net-next 0/6] net: constify dev_addr passing for protocols patchwork-bot+netdevbpf

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20211012155840.4151590-1-kuba@kernel.org \
    --to=kuba@kernel.org \
    --cc=davem@davemloft.net \
    --cc=dsahern@kernel.org \
    --cc=jmaloy@redhat.com \
    --cc=jreuter@yaina.de \
    --cc=linux-hams@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=ralf@linux-mips.org \
    --cc=tipc-discussion@lists.sourceforge.net \
    --cc=ying.xue@windriver.com \
    --cc=yoshfuji@linux-ipv6.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).