linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jakub Kicinski <kuba@kernel.org>
To: torvalds@linux-foundation.org
Cc: kuba@kernel.org, davem@davemloft.net, netdev@vger.kernel.org,
	linux-kernel@vger.kernel.org, pabeni@redhat.com
Subject: [PULL] Networking for v6.1 final / v6.1-rc9
Date: Thu,  8 Dec 2022 12:56:39 -0800	[thread overview]
Message-ID: <20221208205639.1799257-1-kuba@kernel.org> (raw)

Hi Linus!

Couple of "new code fixes" which is annoying this late, but neither
of those gives me pause.

We pooped it by merging a Xen patch too quickly, and Juergen ended
up sending you a different version via his tree, so you'll see
a conflict. Just keep what you have. Link to the linux-next conflict
report:
https://lore.kernel.org/all/20221208082301.5f7483e8@canb.auug.org.au/

There is an outstanding regression in BPF / Peter's static calls stuff,
you can probably judge this sort of stuff better than I can:
https://lore.kernel.org/all/CACkBjsYioeJLhJAZ=Sq4CAL2O_W+5uqcJynFgLSizWLqEjNrjw@mail.gmail.com/

No other known regressions.

The following changes since commit f8bac7f9fdb0017b32157957ffffd490f95faa07:

  net: dsa: sja1105: avoid out of bounds access in sja1105_init_l2_policing() (2022-12-08 09:38:31 -0800)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/netdev/net.git tags/net-6.1-rc9

for you to fetch changes up to f8bac7f9fdb0017b32157957ffffd490f95faa07:

  net: dsa: sja1105: avoid out of bounds access in sja1105_init_l2_policing() (2022-12-08 09:38:31 -0800)

----------------------------------------------------------------
Including fixes from bluetooth, can and netfilter.

Current release - new code bugs:

 - bonding: ipv6: correct address used in Neighbour Advertisement
   parsing (src vs dst typo)

 - fec: properly scope IRQ coalesce setup during link up to supported
   chips only

Previous releases - regressions:

 - Bluetooth fixes for fake CSR clones (knockoffs):
   - re-add ERR_DATA_REPORTING quirk
   - fix crash when device is replugged

 - Bluetooth:
   - silence a user-triggerable dmesg error message
   - L2CAP: fix u8 overflow, oob access
   - correct vendor codec definition
   - fix support for Read Local Supported Codecs V2

 - ti: am65-cpsw: fix RGMII configuration at SPEED_10

 - mana: fix race on per-CQ variable NAPI work_done

Previous releases - always broken:

 - af_unix: diag: fetch user_ns from in_skb in unix_diag_get_exact(),
   avoid null-deref

 - af_can: fix NULL pointer dereference in can_rcv_filter

 - can: slcan: fix UAF with a freed work

 - can: can327: flush TX_work on ldisc .close()

 - macsec: add missing attribute validation for offload

 - ipv6: avoid use-after-free in ip6_fragment()

 - nft_set_pipapo: actually validate intervals in fields
   after the first one

 - mvneta: prevent oob access in mvneta_config_rss()

 - ipv4: fix incorrect route flushing when table ID 0 is used,
   or when source address is deleted

 - phy: mxl-gpy: add workaround for IRQ bug on GPY215B and GPY215C

Signed-off-by: Jakub Kicinski <kuba@kernel.org>

----------------------------------------------------------------

             reply	other threads:[~2022-12-08 20:56 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-08 20:56 Jakub Kicinski [this message]
2022-12-08 21:00 ` [PULL] Networking for v6.1 final / v6.1-rc9 (with the diff stat :S) Jakub Kicinski
2022-12-09 18:25   ` Linus Torvalds
2022-12-09 21:00     ` Jakub Kicinski
2022-12-09 22:05       ` Jakub Kicinski
2022-12-10  1:27         ` Alexei Starovoitov
2022-12-08 23:57 ` [PULL] Networking for v6.1 final / v6.1-rc9 pr-tracker-bot

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=20221208205639.1799257-1-kuba@kernel.org \
    --to=kuba@kernel.org \
    --cc=davem@davemloft.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=torvalds@linux-foundation.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).