mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: syzbot <syzbot+57f410c9a4f8d7a441d6@syzkaller.appspotmail.com>
To: linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: Forwarded: test
Date: Mon, 28 Sep 2026 08:18:46 -0700	[thread overview]
Message-ID: <6aba8556.c41622c8.21b57.0001.GAE@google.com> (raw)
In-Reply-To: <6a8b1833.dbb3a75c.13dd47.0050.GAE@google.com>

For archival purposes, forwarding an incoming command email to
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com.

***

Subject: test
Author: idosch@nvidia.com

#syz test

diff --git a/net/ipv6/addrconf.c b/net/ipv6/addrconf.c
index c90ee6dd7446..e1e672ada7e7 100644
--- a/net/ipv6/addrconf.c
+++ b/net/ipv6/addrconf.c
@@ -3908,9 +3908,12 @@ static int addrconf_ifdown(struct net_device *dev, bool unregister)
 	}
 
 	/* combine the user config with event to determine if permanent
-	 * addresses are to be removed from address hash table
+	 * addresses are to be removed from address hash table. IPv6 cannot
+	 * operate below IPV6_MIN_MTU, so treat that like disable_ipv6 and do
+	 * not keep addresses without their host routes.
 	 */
-	if (!unregister && !idev->cnf.disable_ipv6) {
+	if (!unregister && !idev->cnf.disable_ipv6 &&
+	    dev->mtu >= IPV6_MIN_MTU) {
 		/* aggregate the system setting and interface setting */
 		int _keep_addr = READ_ONCE(net->ipv6.devconf_all->keep_addr_on_down);
 

  reply	other threads:[~2026-09-28 15:18 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-23 15:56 [syzbot] BUG: Address NUM::fb on device lo is missing its host route syzbot
2026-09-28 15:18 ` syzbot [this message]
  -- strict thread matches above, loose matches on Subject: below --
2026-08-07 12:56 [syzbot] BUG: Address fc00:: " syzbot
2026-09-28 15:18 ` Forwarded: test syzbot
2026-08-07 12:01 [syzbot] [kernel?] INFO: task hung in copy_ipcs syzbot
2026-08-11  5:59 ` Forwarded: test syzbot
2026-07-29  0:19 [syzbot] [fs?] general protection fault in start_dirop syzbot
2026-07-29 13:59 ` Forwarded: test syzbot
2026-07-29 14:59 ` syzbot
2026-07-28 13:31 [syzbot] [fs?] possible deadlock in configfs_rmdir syzbot
2026-07-31 10:51 ` Forwarded: test syzbot
2026-07-06 21:44 [syzbot] [netfs?] WARNING in netfs_writepages (3) syzbot
2026-07-07  5:34 ` Forwarded: test syzbot
2026-07-24  6:44 ` syzbot
2026-06-04 21:33 [syzbot] [overlayfs?] [ext4?] possible deadlock in lock_two_nondirectories (2) syzbot
2026-06-08 15:46 ` Forwarded: test syzbot
2026-05-31  1:20 [syzbot] [block?] general protection fault in ublk_queue_rq syzbot
2026-06-01 18:58 ` Forwarded: test syzbot
2026-05-19 18:53 [syzbot] [net?] possible deadlock in __sk_receive_skb syzbot
2026-05-20  2:05 ` Forwarded: test syzbot
2026-05-20  9:15 ` syzbot
2026-05-20 10:27 ` syzbot
2026-05-20 14:33 ` syzbot
2026-05-19 11:56 [syzbot] [net?] WARNING in netif_rx_mode_run syzbot
2026-05-19 12:49 ` Forwarded: test syzbot
2026-05-20  9:34 ` syzbot
2026-05-18  1:17 [syzbot] [media?] KASAN: slab-use-after-free Read in dvb_frontend_open syzbot
2026-05-18 11:19 ` Forwarded: test syzbot
2026-05-19  0:36 ` syzbot
2025-11-13  8:08 [syzbot] [ext4?] possible deadlock in ext4_xattr_set_handle (7) syzbot
2026-06-09  8:41 ` Forwarded: test syzbot
2025-11-07  7:29 [syzbot] [jfs?] general protection fault in txCommit (2) syzbot
2025-11-14 13:48 ` Forwarded: test syzbot
2025-11-14 14:36 ` syzbot
2025-11-01 17:24 [syzbot] [jfs?] stack segment fault in dbUpdatePMap syzbot
2025-11-10 11:30 ` Forwarded: test syzbot
2025-09-30 20:29 [syzbot] [rdma?] KMSAN: uninit-value in ib_nl_handle_ip_res_resp syzbot
2025-11-06 19:28 ` Forwarded: test syzbot
2025-04-30 21:08 [syzbot] [jfs?] UBSAN: shift-out-of-bounds in dbSplit (3) syzbot
2025-11-19  2:55 ` Forwarded: test syzbot
2025-04-30 13:26 [syzbot] [jfs?] UBSAN: shift-out-of-bounds in jfs_statfs (3) syzbot
2025-11-20 15:15 ` Forwarded: test syzbot
2024-10-03 19:10 [syzbot] [jfs?] UBSAN: array-index-out-of-bounds in dtInsertEntry syzbot
2025-11-18 14:11 ` Forwarded: test syzbot
2024-08-28  0:09 [syzbot] [nbd?] INFO: task hung in nbd_queue_rq syzbot
2026-07-07 11:25 ` Forwarded: test syzbot
2024-08-16  5:17 [syzbot] [xfs?] INFO: task hung in xfs_buf_item_unpin (2) syzbot
2026-07-13 14:52 ` Forwarded: test syzbot
2023-01-16 16:40 [syzbot] possible deadlock in br_multicast_rcv (3) syzbot
2026-04-23 16:10 ` Forwarded: test syzbot

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=6aba8556.c41622c8.21b57.0001.GAE@google.com \
    --to=syzbot+57f410c9a4f8d7a441d6@syzkaller.appspotmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=syzkaller-bugs@googlegroups.com \
    /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

all inboxes | Powered by JetHome®