From nobody Sun Dec 31 18:34:45 2023 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4T38bF0Swkz557pG for ; Sun, 31 Dec 2023 19:40:09 +0000 (UTC) (envelope-from pi@freebsd.org) Received: from fc.opsec.eu (fc.opsec.eu [IPv6:2001:14f8:200:4::4]) by mx1.freebsd.org (Postfix) with ESMTP id 4T38bD08Gtz3P8p for ; Sun, 31 Dec 2023 19:40:07 +0000 (UTC) (envelope-from pi@freebsd.org) Authentication-Results: mx1.freebsd.org; dkim=none; spf=softfail (mx1.freebsd.org: 2001:14f8:200:4::4 is neither permitted nor denied by domain of pi@freebsd.org) smtp.mailfrom=pi@freebsd.org; dmarc=none Received: from pi (uid 104) (envelope-from pi@freebsd.org) id 18a9f by fc.opsec.eu (DragonFly Mail Agent v0.13+ on fc.opsec.eu); Sun, 31 Dec 2023 19:34:45 +0100 Date: Sun, 31 Dec 2023 19:34:45 +0100 From: Kurt Jaeger To: freebsd-current@freebsd.org Subject: ZFS problems since recently ? Message-ID: List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-Spamd-Result: default: False [2.78 / 15.00]; VIOLATED_DIRECT_SPF(3.50)[]; SUBJECT_ENDS_QUESTION(1.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_SPAM_SHORT(0.18)[0.184]; RCVD_NO_TLS_LAST(0.10)[]; MIME_GOOD(-0.10)[text/plain]; ONCE_RECEIVED(0.10)[]; DMARC_NA(0.00)[freebsd.org]; ARC_NA(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; FREEFALL_USER(0.00)[pi]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:12502, ipnet:2001:14f8::/32, country:DE]; TO_DN_NONE(0.00)[]; RCVD_COUNT_ONE(0.00)[1]; FROM_HAS_DN(0.00)[]; R_SPF_SOFTFAIL(0.00)[~all]; MLMMJ_DEST(0.00)[freebsd-current@freebsd.org]; RCPT_COUNT_ONE(0.00)[1]; TO_MATCH_ENVRCPT_ALL(0.00)[]; GREYLIST(0.00)[pass,body]; TO_DOM_EQ_FROM_DOM(0.00)[] X-Rspamd-Queue-Id: 4T38bD08Gtz3P8p X-Spamd-Bar: ++ Hi! Short overview: - Had CURRENT system from around September - Upgrade on the 23th of December - crashes in ZFS, see https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=261538 for details - Reinstalled from scratch with new SSDs drives from https://download.freebsd.org/snapshots/amd64/amd64/ISO-IMAGES/15.0/ freebsd-openzfs-amd64-2020081900-memstick.img.xz - Had one crash with sysctl -a https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=276039 - Still see crashes with ZFS (and other) when using poudriere to build ports. Problem: I happen to run in several cases of crashes in ZFS, some of them fatal (zpool non-recoverable). The latest was: panic: VERIFY(BP_GET_DEDUP(bp)) failed cpuid = 29 time = 1704050745 KDB: stack backtrace: db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame 0xfffffe02def538c0 vpanic() at vpanic+0x131/frame 0xfffffe02def539f0 spl_panic() at spl_panic+0x3a/frame 0xfffffe02def53a50 dsl_livelist_iterate() at dsl_livelist_iterate+0x2de/frame 0xfffffe02def53b30 bpobj_iterate_blkptrs() at bpobj_iterate_blkptrs+0x235/frame 0xfffffe02def53bf0 bpobj_iterate_impl() at bpobj_iterate_impl+0x16e/frame 0xfffffe02def53c80 dsl_process_sub_livelist() at dsl_process_sub_livelist+0x5c/frame 0xfffffe02def53d00 spa_livelist_delete_cb() at spa_livelist_delete_cb+0xf6/frame 0xfffffe02def53ea0 zthr_procedure() at zthr_procedure+0xa5/frame 0xfffffe02def53ef0 fork_exit() at fork_exit+0x82/frame 0xfffffe02def53f30 fork_trampoline() at fork_trampoline+0xe/frame 0xfffffe02def53f30 --- trap 0x85baac33, rip = 0xdfda59b01bda59f, rsp = 0xaaca3ed7a68a3ed3, rbp = 0x16f512f91ab512fd --- before I had to nuke that pool and restart... I already have vfs.zfs.dmu_offset_next_sync=0 which is supposed to disable block-cloning. Does anyone else see this with recent versions or is it just me ? -- pi@FreeBSD.org +49 171 3101372 Now what ? From nobody Sun Dec 31 23:16:48 2023 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4T3FRP6jhPz55Xmt for ; Sun, 31 Dec 2023 23:18:41 +0000 (UTC) (envelope-from warlock@phouka1.phouka.net) Received: from phouka1.phouka.net (phouka1.phouka.net [107.170.196.116]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "phouka.net", Issuer "Go Daddy Secure Certificate Authority - G2" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 4T3FRP4BRBz4LwJ; Sun, 31 Dec 2023 23:18:41 +0000 (UTC) (envelope-from warlock@phouka1.phouka.net) Authentication-Results: mx1.freebsd.org; none Received: from phouka1.phouka.net (localhost [127.0.0.1]) by phouka1.phouka.net (8.17.1/8.17.1) with ESMTPS id 3BVNGn0K071241 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO); Sun, 31 Dec 2023 15:16:49 -0800 (PST) (envelope-from warlock@phouka1.phouka.net) Received: (from warlock@localhost) by phouka1.phouka.net (8.17.1/8.17.1/Submit) id 3BVNGnfq071240; Sun, 31 Dec 2023 15:16:49 -0800 (PST) (envelope-from warlock) Date: Sun, 31 Dec 2023 15:16:48 -0800 From: John Kennedy To: Kurt Jaeger Cc: freebsd-current@freebsd.org Subject: Re: ZFS problems since recently ? Message-ID: References: List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:14061, ipnet:107.170.192.0/18, country:US] X-Spamd-Bar: ---- X-Rspamd-Queue-Id: 4T3FRP4BRBz4LwJ On Sun, Dec 31, 2023 at 07:34:45PM +0100, Kurt Jaeger wrote: > Hi! > > Short overview: > - Had CURRENT system from around September > - Upgrade on the 23th of December > - crashes in ZFS, see > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=261538 > for details > - Reinstalled from scratch with new SSDs drives from > https://download.freebsd.org/snapshots/amd64/amd64/ISO-IMAGES/15.0/ > freebsd-openzfs-amd64-2020081900-memstick.img.xz > - Had one crash with > sysctl -a > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=276039 > - Still see crashes with ZFS (and other) when using poudriere to > build ports. > > Problem: > > I happen to run in several cases of crashes in ZFS, some of > them fatal (zpool non-recoverable). I can crash mine with "sysctl -a" as well. I seeded my bhyve with: FreeBSD-15.0-CURRENT-amd64-20231228-fb03f7f8e30d-267242-disc1.iso Rebuilt the kernel (so now at main-n267320-4d08b569a01) and started crunching through poudriere package builds. Sorta stock install of encrypted ZFS. I didn't get it to crash with poudriere (yet). Mine lives in bhyve, so maybe less possible destruction via crashes. KDB: stack backtrace: db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame 0xfffffe00fa5f3960 vpanic() at vpanic+0x131/frame 0xfffffe00fa5f3a90 panic() at panic+0x43/frame 0xfffffe00fa5f3af0 sbuf_clear() at sbuf_clear+0xa8/frame 0xfffffe00fa5f3b00 sbuf_cpy() at sbuf_cpy+0x56/frame 0xfffffe00fa5f3b20 spa_taskq_write_param() at spa_taskq_write_param+0x85/frame 0xfffffe00fa5f3bd0 sysctl_root_handler_locked() at sysctl_root_handler_locked+0x9c/frame 0xfffffe00fa5f3c20 sysctl_root() at sysctl_root+0x21e/frame 0xfffffe00fa5f3ca0 userland_sysctl() at userland_sysctl+0x184/frame 0xfffffe00fa5f3d50 sys___sysctl() at sys___sysctl+0x60/frame 0xfffffe00fa5f3e00 amd64_syscall() at amd64_syscall+0x153/frame 0xfffffe00fa5f3f30 fast_syscall_common() at fast_syscall_common+0xf8/frame 0xfffffe00fa5f3f30 --- syscall (202, FreeBSD ELF64, __sysctl), rip = 0x22e42167019a, rsp = 0x22e41ee72518, rbp = 0x22e41ee72550 --- KDB: enter: panic The sysctl died at this point, but who knows if it had pending buffered output or anything... ... vfs.zfs.zio.deadman_log_all: 0 vfs.zfs.zio.dva_throttle_enabled: 1 vfs.zfs.zio.requeue_io_start_cut_in_line: 1 vfs.zfs.zio.slow_io_ms: 30000 vfs.zfs.zio.taskq_wr_iss_ncpus: 0 From nobody Mon Jan 1 01:03:31 2024 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4T3HpY05rnz55lBN for ; Mon, 1 Jan 2024 01:05:25 +0000 (UTC) (envelope-from warlock@phouka1.phouka.net) Received: from phouka1.phouka.net (phouka1.phouka.net [107.170.196.116]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "phouka.net", Issuer "Go Daddy Secure Certificate Authority - G2" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 4T3HpW651dz4WnW; Mon, 1 Jan 2024 01:05:23 +0000 (UTC) (envelope-from warlock@phouka1.phouka.net) Authentication-Results: mx1.freebsd.org; dkim=none; spf=none (mx1.freebsd.org: domain of warlock@phouka1.phouka.net has no SPF policy when checking 107.170.196.116) smtp.mailfrom=warlock@phouka1.phouka.net; dmarc=none Received: from phouka1.phouka.net (localhost [127.0.0.1]) by phouka1.phouka.net (8.17.1/8.17.1) with ESMTPS id 40113Vkf071391 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO); Sun, 31 Dec 2023 17:03:31 -0800 (PST) (envelope-from warlock@phouka1.phouka.net) Received: (from warlock@localhost) by phouka1.phouka.net (8.17.1/8.17.1/Submit) id 40113V8i071390; Sun, 31 Dec 2023 17:03:31 -0800 (PST) (envelope-from warlock) Date: Sun, 31 Dec 2023 17:03:31 -0800 From: John Kennedy To: Kurt Jaeger Cc: freebsd-current@freebsd.org Subject: Re: ZFS problems since recently ? Message-ID: References: List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Spamd-Result: default: False [-0.57 / 15.00]; AUTH_NA(1.00)[]; SUBJECT_ENDS_QUESTION(1.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_SHORT(-0.77)[-0.772]; FORGED_SENDER(0.30)[warlock@phouka.net,warlock@phouka1.phouka.net]; MIME_GOOD(-0.10)[text/plain]; MLMMJ_DEST(0.00)[freebsd-current@freebsd.org]; R_DKIM_NA(0.00)[]; RCPT_COUNT_TWO(0.00)[2]; ASN(0.00)[asn:14061, ipnet:107.170.192.0/18, country:US]; R_SPF_NA(0.00)[no SPF record]; MIME_TRACE(0.00)[0:+]; FROM_NEQ_ENVFROM(0.00)[warlock@phouka.net,warlock@phouka1.phouka.net]; FROM_HAS_DN(0.00)[]; ARC_NA(0.00)[]; MID_RHS_MATCH_FROMTLD(0.00)[]; TO_DN_SOME(0.00)[]; RCVD_TLS_LAST(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; DMARC_NA(0.00)[phouka.net]; RCVD_COUNT_TWO(0.00)[2] X-Rspamd-Queue-Id: 4T3HpW651dz4WnW X-Spamd-Bar: / > I can crash mine with "sysctl -a" as well. Smaller test, this is sufficient to crash things: root@bsd15:~ # sysctl vfs.zfs.zio vfs.zfs.zio.deadman_log_all: 0 vfs.zfs.zio.dva_throttle_enabled: 1 vfs.zfs.ziopanic: sbuf_clear makes no sense on sbuf 0xfffff8002c8dc300 with drain cpuid = 3 time = 1704069514 KDB: stack backtrace: db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame 0xfffffe00fa502960 vpanic() at vpanic+0x131/frame 0xfffffe00fa502a90 panic() at panic+0x43/frame 0xfffffe00fa502af0 sbuf_clear() at sbuf_clear+0xa8/frame 0xfffffe00fa502b00 sbuf_cpy() at sbuf_cpy+0x56/frame 0xfffffe00fa502b20 spa_taskq_write_param() at spa_taskq_write_param+0x85/frame 0xfffffe00fa502bd0 sysctl_root_handler_locked() at sysctl_root_handler_locked+0x9c/frame 0xfffffe00fa502c20 sysctl_root() at sysctl_root+0x21e/frame 0xfffffe00fa502ca0 userland_sysctl() at userland_sysctl+0x184/frame 0xfffffe00fa502d50 sys___sysctl() at sys___sysctl+0x60/frame 0xfffffe00fa502e00 amd64_syscall() at amd64_syscall+0x153/frame 0xfffffe00fa502f30 fast_syscall_common() at fast_syscall_common+0xf8/frame 0xfffffe00fa502f30 --- syscall (202, FreeBSD ELF64, __sysctl), rip = 0x3733c1e5619a, rsp = 0x3733bf494538, rbp = 0x3733bf494570 --- KDB: enter: panic [ thread pid 780 tid 100237 ] Stopped at kdb_enter+0x33: movq $0,0xe3a582(%rip) db> From nobody Mon Jan 1 05:43:58 2024 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4T3RKF4789z566WP for ; Mon, 1 Jan 2024 06:44:01 +0000 (UTC) (envelope-from pi@freebsd.org) Received: from fc.opsec.eu (fc.opsec.eu [IPv6:2001:14f8:200:4::4]) by mx1.freebsd.org (Postfix) with ESMTP id 4T3RKC6YY9z3YdX for ; Mon, 1 Jan 2024 06:43:59 +0000 (UTC) (envelope-from pi@freebsd.org) Authentication-Results: mx1.freebsd.org; none Received: from pi (uid 104) (envelope-from pi@freebsd.org) id 18416 by fc.opsec.eu (DragonFly Mail Agent v0.13+ on fc.opsec.eu); Mon, 01 Jan 2024 06:43:58 +0100 Date: Mon, 1 Jan 2024 06:43:58 +0100 From: Kurt Jaeger To: John Kennedy Cc: freebsd-current@freebsd.org Subject: Re: ZFS problems since recently ? Message-ID: References: List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:12502, ipnet:2001:14f8::/32, country:DE] X-Spamd-Bar: ---- X-Rspamd-Queue-Id: 4T3RKC6YY9z3YdX Hi! > > I can crash mine with "sysctl -a" as well. markj@ pointed me in https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=276039 to https://github.com/openzfs/zfs/pull/15719 So it will probably be fixed sooner or later. The other ZFS crashes I've seen are still an issue. -- pi@FreeBSD.org +49 171 3101372 Now what ? From nobody Mon Jan 1 13:59:29 2024 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4T3d1w42gBz56nPc for ; Mon, 1 Jan 2024 14:01:24 +0000 (UTC) (envelope-from warlock@phouka1.phouka.net) Received: from phouka1.phouka.net (phouka1.phouka.net [107.170.196.116]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "phouka.net", Issuer "Go Daddy Secure Certificate Authority - G2" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 4T3d1w1ZJBz4fgg; Mon, 1 Jan 2024 14:01:24 +0000 (UTC) (envelope-from warlock@phouka1.phouka.net) Authentication-Results: mx1.freebsd.org; none Received: from phouka1.phouka.net (localhost [127.0.0.1]) by phouka1.phouka.net (8.17.1/8.17.1) with ESMTPS id 401DxU5n073090 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO); Mon, 1 Jan 2024 05:59:30 -0800 (PST) (envelope-from warlock@phouka1.phouka.net) Received: (from warlock@localhost) by phouka1.phouka.net (8.17.1/8.17.1/Submit) id 401DxTvL073089; Mon, 1 Jan 2024 05:59:29 -0800 (PST) (envelope-from warlock) Date: Mon, 1 Jan 2024 05:59:29 -0800 From: John Kennedy To: Kurt Jaeger Cc: freebsd-current@freebsd.org Subject: Re: ZFS problems since recently ? Message-ID: References: List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:14061, ipnet:107.170.192.0/18, country:US] X-Spamd-Bar: ---- X-Rspamd-Queue-Id: 4T3d1w1ZJBz4fgg On Mon, Jan 01, 2024 at 06:43:58AM +0100, Kurt Jaeger wrote: > markj@ pointed me in > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=276039 > to > https://github.com/openzfs/zfs/pull/15719 > > So it will probably be fixed sooner or later. > > The other ZFS crashes I've seen are still an issue. My poudriere build did eventually fail as well: ... [05:40:24] [01] [00:17:20] Finished devel/gdb@py39 | gdb-13.2_1: Success [05:40:24] Stopping 2 builders panic: VERIFY(BP_GET_DEDUP(bp)) failed cpuid = 2 time = 1704091946 KDB: stack backtrace: db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame 0xfffffe00f62898c0 vpanic() at vpanic+0x131/frame 0xfffffe00f62899f0 spl_panic() at spl_panic+0x3a/frame 0xfffffe00f6289a50 dsl_livelist_iterate() at dsl_livelist_iterate+0x2de/frame 0xfffffe00f6289b30 bpobj_iterate_blkptrs() at bpobj_iterate_blkptrs+0x235/frame 0xfffffe00f6289bf0 bpobj_iterate_impl() at bpobj_iterate_impl+0x16e/frame 0xfffffe00f6289c80 dsl_process_sub_livelist() at dsl_process_sub_livelist+0x5c/frame 0xfffffe00f6289d00 spa_livelist_delete_cb() at spa_livelist_delete_cb+0xf6/frame 0xfffffe00f6289ea0 zthr_procedure() at zthr_procedure+0xa5/frame 0xfffffe00f6289ef0 fork_exit() at fork_exit+0x82/frame 0xfffffe00f6289f30 fork_trampoline() at fork_trampoline+0xe/frame 0xfffffe00f6289f30 --- trap 0, rip = 0, rsp = 0, rbp = 0 --- KDB: enter: panic [ thread pid 9 tid 100223 ] Stopped at kdb_enter+0x33: movq $0,0xe3a582(%rip) db> Trying to do another poudriere build fails almost immediatly with that verify error. Your verify errors don't match up exactly. I've got snapshots from before I started freaking it out with the sysctl calls and possibly inducing corruption. I didn't tweak this system off defaults for block-cloning. I haven't been following that issue 100%. From nobody Mon Jan 1 13:27:17 2024 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4T3dbx22ZZz56qtZ for ; Mon, 1 Jan 2024 14:27:25 +0000 (UTC) (envelope-from pi@freebsd.org) Received: from fc.opsec.eu (fc.opsec.eu [193.105.105.132]) by mx1.freebsd.org (Postfix) with ESMTP id 4T3dbw3z2Nz4kS9 for ; Mon, 1 Jan 2024 14:27:24 +0000 (UTC) (envelope-from pi@freebsd.org) Authentication-Results: mx1.freebsd.org; none Received: from pi (uid 104) (envelope-from pi@freebsd.org) id 18002 by fc.opsec.eu (DragonFly Mail Agent v0.13+ on fc.opsec.eu); Mon, 01 Jan 2024 14:27:17 +0100 Date: Mon, 1 Jan 2024 14:27:17 +0100 From: Kurt Jaeger To: John Kennedy Cc: freebsd-current@freebsd.org Subject: Re: ZFS problems since recently ? Message-ID: References: List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:12502, ipnet:193.105.105.0/24, country:DE] X-Spamd-Bar: ---- X-Rspamd-Queue-Id: 4T3dbw3z2Nz4kS9 Hi! > On Mon, Jan 01, 2024 at 06:43:58AM +0100, Kurt Jaeger wrote: > > markj@ pointed me in > > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=276039 > > to > > https://github.com/openzfs/zfs/pull/15719 > > > > So it will probably be fixed sooner or later. > > > > The other ZFS crashes I've seen are still an issue. > > My poudriere build did eventually fail as well: > ... > [05:40:24] [01] [00:17:20] Finished devel/gdb@py39 | gdb-13.2_1: Success > [05:40:24] Stopping 2 builders > panic: VERIFY(BP_GET_DEDUP(bp)) failed That's one of the panic messages I had as well. See https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=276051 for additional crashes and dumps. > I didn't tweak this system off defaults for block-cloning. I haven't been following > that issue 100%. Do you have vfs.zfs.dmu_offset_next_sync=0 ? -- pi@FreeBSD.org +49 171 3101372 Now what ? From nobody Mon Jan 1 15:17:51 2024 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4T3fmK1xy9z56vmK for ; Mon, 1 Jan 2024 15:19:45 +0000 (UTC) (envelope-from warlock@phouka1.phouka.net) Received: from phouka1.phouka.net (phouka1.phouka.net [107.170.196.116]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "phouka.net", Issuer "Go Daddy Secure Certificate Authority - G2" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 4T3fmJ6LfTz4pPK; Mon, 1 Jan 2024 15:19:44 +0000 (UTC) (envelope-from warlock@phouka1.phouka.net) Authentication-Results: mx1.freebsd.org; none Received: from phouka1.phouka.net (localhost [127.0.0.1]) by phouka1.phouka.net (8.17.1/8.17.1) with ESMTPS id 401FHpPY073225 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO); Mon, 1 Jan 2024 07:17:51 -0800 (PST) (envelope-from warlock@phouka1.phouka.net) Received: (from warlock@localhost) by phouka1.phouka.net (8.17.1/8.17.1/Submit) id 401FHpLM073224; Mon, 1 Jan 2024 07:17:51 -0800 (PST) (envelope-from warlock) Date: Mon, 1 Jan 2024 07:17:51 -0800 From: John Kennedy To: Kurt Jaeger Cc: freebsd-current@freebsd.org Subject: Re: ZFS problems since recently ? Message-ID: References: List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:14061, ipnet:107.170.192.0/18, country:US] X-Spamd-Bar: ---- X-Rspamd-Queue-Id: 4T3fmJ6LfTz4pPK On Mon, Jan 01, 2024 at 02:27:17PM +0100, Kurt Jaeger wrote: > Do you have > vfs.zfs.dmu_offset_next_sync=0 I didn't initially, I do now. Like I said, I haven't been following that one 100%. I know it isn't block-clone per say, so much as some underlying problem it pokes with a pointy stick. Small chance multiplied by a bunch of ZFS IOPS. Seems like I'd have to revert it all the way back to fresh install if I want to get rid of all potential corruption unrelated to sysctl panic. But I'll do myh busy-work cycle (*) with that one and maybe another with it off and see what happens. * full kernel+world, plus my local poudriere package build, currenly wedged a bit with the heimdall build issue. From nobody Mon Jan 1 16:42:26 2024 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4T3hdx5zK3z5741M for ; Mon, 1 Jan 2024 16:44:21 +0000 (UTC) (envelope-from warlock@phouka1.phouka.net) Received: from phouka1.phouka.net (phouka1.phouka.net [107.170.196.116]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "phouka.net", Issuer "Go Daddy Secure Certificate Authority - G2" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 4T3hdx2tYfz3GT8; Mon, 1 Jan 2024 16:44:21 +0000 (UTC) (envelope-from warlock@phouka1.phouka.net) Authentication-Results: mx1.freebsd.org; none Received: from phouka1.phouka.net (localhost [127.0.0.1]) by phouka1.phouka.net (8.17.1/8.17.1) with ESMTPS id 401GgQEQ073370 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO); Mon, 1 Jan 2024 08:42:26 -0800 (PST) (envelope-from warlock@phouka1.phouka.net) Received: (from warlock@localhost) by phouka1.phouka.net (8.17.1/8.17.1/Submit) id 401GgQgF073369; Mon, 1 Jan 2024 08:42:26 -0800 (PST) (envelope-from warlock) Date: Mon, 1 Jan 2024 08:42:26 -0800 From: John Kennedy To: Kurt Jaeger Cc: freebsd-current@freebsd.org Subject: Re: ZFS problems since recently ? Message-ID: References: List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:14061, ipnet:107.170.192.0/18, country:US] X-Spamd-Bar: ---- X-Rspamd-Queue-Id: 4T3hdx2tYfz3GT8 On Mon, Jan 01, 2024 at 06:43:58AM +0100, Kurt Jaeger wrote: > > > I can crash mine with "sysctl -a" as well. > > markj@ pointed me in > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=276039 > to > https://github.com/openzfs/zfs/pull/15719 > > So it will probably be fixed sooner or later. > > The other ZFS crashes I've seen are still an issue. Applying the two ZFS kernel patches fixes that issue: root@bsd15:~ # sysctl -a | grep vfs.zfs.zio vfs.zfs.zio.deadman_log_all: 0 vfs.zfs.zio.dva_throttle_enabled: 1 vfs.zfs.zio.requeue_io_start_cut_in_line: 1 vfs.zfs.zio.slow_io_ms: 30000 vfs.zfs.zio.taskq_wr_iss_ncpus: 0 vfs.zfs.zio.taskq_write: sync fixed,1,5 scale fixed,1,5 vfs.zfs.zio.taskq_read: fixed,1,8 null scale null vfs.zfs.zio.taskq_batch_tpq: 0 vfs.zfs.zio.taskq_batch_pct: 80 vfs.zfs.zio.exclude_metadata: 0 root@bsd15:~ # uname -aUK FreeBSD bsd15 15.0-CURRENT FreeBSD 15.0-CURRENT #2 main-n267335-499e84e16f5-dirty: Mon Jan 1 08:04:59 PST 2024 warlock@bsd15:/usr/obj/usr/src/amd64.amd64/sys/GENERIC amd64 1500008 1500008 From nobody Mon Jan 1 20:27:29 2024 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4T3ndm63bvz55VJs for ; Mon, 1 Jan 2024 20:29:32 +0000 (UTC) (envelope-from warlock@phouka1.phouka.net) Received: from phouka1.phouka.net (phouka1.phouka.net [107.170.196.116]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "phouka.net", Issuer "Go Daddy Secure Certificate Authority - G2" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 4T3ndl4KqZz3f4G; Mon, 1 Jan 2024 20:29:31 +0000 (UTC) (envelope-from warlock@phouka1.phouka.net) Authentication-Results: mx1.freebsd.org; dkim=none; spf=none (mx1.freebsd.org: domain of warlock@phouka1.phouka.net has no SPF policy when checking 107.170.196.116) smtp.mailfrom=warlock@phouka1.phouka.net; dmarc=none Received: from phouka1.phouka.net (localhost [127.0.0.1]) by phouka1.phouka.net (8.17.1/8.17.1) with ESMTPS id 401KRUET075172 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO); Mon, 1 Jan 2024 12:27:31 -0800 (PST) (envelope-from warlock@phouka1.phouka.net) Received: (from warlock@localhost) by phouka1.phouka.net (8.17.1/8.17.1/Submit) id 401KRUSo075170; Mon, 1 Jan 2024 12:27:30 -0800 (PST) (envelope-from warlock) Date: Mon, 1 Jan 2024 12:27:29 -0800 From: John Kennedy To: Kurt Jaeger Cc: freebsd-current@freebsd.org Subject: Re: ZFS problems since recently ? Message-ID: References: List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Spamd-Result: default: False [-0.80 / 15.00]; AUTH_NA(1.00)[]; SUBJECT_ENDS_QUESTION(1.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_SHORT(-1.00)[-0.998]; FORGED_SENDER(0.30)[warlock@phouka.net,warlock@phouka1.phouka.net]; MIME_GOOD(-0.10)[text/plain]; MLMMJ_DEST(0.00)[freebsd-current@freebsd.org]; R_DKIM_NA(0.00)[]; RCPT_COUNT_TWO(0.00)[2]; ASN(0.00)[asn:14061, ipnet:107.170.192.0/18, country:US]; R_SPF_NA(0.00)[no SPF record]; MIME_TRACE(0.00)[0:+]; FROM_NEQ_ENVFROM(0.00)[warlock@phouka.net,warlock@phouka1.phouka.net]; FROM_HAS_DN(0.00)[]; ARC_NA(0.00)[]; MID_RHS_MATCH_FROMTLD(0.00)[]; TO_DN_SOME(0.00)[]; RCVD_TLS_LAST(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; DMARC_NA(0.00)[phouka.net]; RCVD_COUNT_TWO(0.00)[2] X-Rspamd-Queue-Id: 4T3ndl4KqZz3f4G X-Spamd-Bar: / On Mon, Jan 01, 2024 at 08:42:26AM -0800, John Kennedy wrote: > Applying the two ZFS kernel patches fixes that issue: commit 09af4bf2c987f6f57804162cef8aeee05575ad1d (zfs: Fix SPA sysctl handlers) landed too. root@bsd15:~ # sysctl -a | grep vfs.zfs.zio vfs.zfs.zio.deadman_log_all: 0 vfs.zfs.zio.dva_throttle_enabled: 1 vfs.zfs.zio.requeue_io_start_cut_in_line: 1 vfs.zfs.zio.slow_io_ms: 30000 vfs.zfs.zio.taskq_wr_iss_ncpus: 0 vfs.zfs.zio.taskq_write: sync fixed,1,5 scale fixed,1,5 vfs.zfs.zio.taskq_read: fixed,1,8 null scale null vfs.zfs.zio.taskq_batch_tpq: 0 vfs.zfs.zio.taskq_batch_pct: 80 vfs.zfs.zio.exclude_metadata: 0 root@bsd15:~ # uname -aUK FreeBSD bsd15 15.0-CURRENT FreeBSD 15.0-CURRENT #1 main-n267336-09af4bf2c98: Mon Jan 1 12:04:15 PST 2024 warlock@bsd15:/usr/obj/usr/src/amd64.amd64/sys/GENERIC amd64 1500008 1500008 From nobody Mon Jan 1 23:40:36 2024 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4T3stP2mSkz55rmv for ; Mon, 1 Jan 2024 23:40:45 +0000 (UTC) (envelope-from lexi@le-fay.org) Received: from thyme.eden.le-Fay.ORG (THYME.EDEN.LE-FAY.ORG [81.187.47.194]) by mx1.freebsd.org (Postfix) with ESMTP id 4T3stN1tJZz4cWV for ; Mon, 1 Jan 2024 23:40:44 +0000 (UTC) (envelope-from lexi@le-fay.org) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=le-fay.org header.s=thyme header.b="ARyjSnK/"; spf=pass (mx1.freebsd.org: domain of lexi@le-fay.org designates 81.187.47.194 as permitted sender) smtp.mailfrom=lexi@le-fay.org; dmarc=none Received: from iris.eden.le-Fay.ORG (IRIS.EDEN.LE-FAY.ORG [IPv6:2001:8b0:aab5:106::18]) by thyme.eden.le-Fay.ORG (Postfix) with ESMTP id DBDD7185 for ; Mon, 1 Jan 2024 23:40:36 +0000 (GMT) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=le-fay.org; s=thyme; t=1704152436; bh=mpP+XO5TfNJdERWYyDjcV6JUkHcJRc/F5D/NpQ68VnY=; h=Date:From:To:Subject; b=ARyjSnK/lnlrTTkiS2mzo68NPfl5Wg9Lw8wvjYWOuuXGhPDe6g2mVGpshpG3Bzr9l 0CAn1G4DsdlMFsW5q8BWalxC/3CU2bRwdqCyvT1OERowTQ/jA6HpuhCDAGNuSBSsfd pRinkn9n/lA9V0RxovRLRC9CjY7USzLiSM0F5tzY= Received: from ilythia.eden.le-fay.org (ILYTHIA.EDEN.LE-FAY.ORG [IPv6:2001:8b0:aab5:104:3::101]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (secp384r1) server-digest SHA384) (No client certificate requested) by iris.eden.le-Fay.ORG (Postfix) with ESMTPSA id C2C1110015 for ; Mon, 1 Jan 2024 23:40:36 +0000 (GMT) Date: Mon, 1 Jan 2024 23:40:36 +0000 From: Lexi Winter To: freebsd-current@freebsd.org Subject: bridge(4) and IPv6 broken? Message-ID: List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="KOhs/Fnhyb9mSIqR" Content-Disposition: inline X-Spamd-Result: default: False [-4.46 / 15.00]; SIGNED_PGP(-2.00)[]; SUBJECT_ENDS_QUESTION(1.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_SHORT(-0.96)[-0.965]; R_SPF_ALLOW(-0.20)[+ip4:81.187.47.194]; MIME_GOOD(-0.20)[multipart/signed,text/plain]; R_DKIM_ALLOW(-0.20)[le-fay.org:s=thyme]; RCVD_NO_TLS_LAST(0.10)[]; ASN(0.00)[asn:20712, ipnet:81.187.0.0/16, country:GB]; DMARC_NA(0.00)[le-fay.org]; MLMMJ_DEST(0.00)[freebsd-current@freebsd.org]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+,1:+,2:~]; RCVD_VIA_SMTP_AUTH(0.00)[]; MID_RHS_MATCH_FROMTLD(0.00)[]; RCVD_COUNT_TWO(0.00)[2]; FROM_HAS_DN(0.00)[]; ARC_NA(0.00)[]; DKIM_TRACE(0.00)[le-fay.org:+]; TO_MATCH_ENVRCPT_ALL(0.00)[]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; TO_DN_NONE(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; DWL_DNSWL_NONE(0.00)[le-fay.org:dkim] X-Rspamd-Queue-Id: 4T3stN1tJZz4cWV X-Spamd-Bar: ---- --KOhs/Fnhyb9mSIqR Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable hello, i'm having an issue with bridge(4) and IPv6, with a configuration which=20 is essentially identical to a working system running releng/14.0. ifconfig: lo0: flags=3D1008049 metric 0 mtu 1= 6384 options=3D680003 inet 127.0.0.1 netmask 0xff000000 inet6 ::1 prefixlen 128 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x1 groups: lo nd6 options=3D21 pflog0: flags=3D1000141 metric 0 mtu 33152 options=3D0 groups: pflog alc0: flags=3D1008943 metric 0 mtu 1500 options=3Dc3098 ether 30:9c:23:a8:89:a0 inet6 fe80::329c:23ff:fea8:89a0%alc0 prefixlen 64 scopeid 0x3 media: Ethernet autoselect (1000baseT ) status: active nd6 options=3D1 wg0: flags=3D10080c1 metric 0 mtu 1420 options=3D80000 inet 172.16.145.21 netmask 0xffffffff inet6 fd00:0:1337:cafe:1111:1111:829a:595e prefixlen 128 groups: wg tunnelfib: 1 nd6 options=3D101 bridge0: flags=3D1008843 m= etric 0 mtu 1500 options=3D0 ether 58:9c:fc:10:ff:b6 inet 10.1.4.101 netmask 0xffffff00 broadcast 10.1.4.255 inet6 2001:8b0:aab5:104:3::101 prefixlen 64 id 00:00:00:00:00:00 priority 32768 hellotime 2 fwddelay 15 maxage 20 holdcnt 6 proto rstp maxaddr 2000 timeout 1200 root id 00:00:00:00:00:00 priority 32768 ifcost 0 port 0 member: tap0 flags=3D143 ifmaxaddr 0 port 6 priority 128 path cost 2000000 member: alc0 flags=3D143 ifmaxaddr 0 port 3 priority 128 path cost 55 groups: bridge nd6 options=3D1 tap0: flags=3D9903 metric 0 m= tu 1500 options=3D80000 ether 58:9c:fc:10:ff:89 groups: tap media: Ethernet 1000baseT status: no carrier nd6 options=3D29 the issue is that the bridge doesn't seem to respond to IPv6 ICMP Neighbour Solicitation. for example, while running ping, tcpdump shows this: 23:30:16.567071 58:9c:fc:10:ff:b6 > 1e:ab:48:c1:f6:62, ethertype IPv6 (0x86= dd), length 70: 2001:8b0:aab5:104:3::101 > 2001:8b0:aab5:106::12: ICMP6, ec= ho request, id 34603, seq 13, length 16 23:30:16.634860 1e:ab:48:c1:f6:62 > 33:33:ff:00:01:01, ethertype IPv6 (0x86= dd), length 86: fe80::1cab:48ff:fec1:f662 > ff02::1:ff00:101: ICMP6, neighb= or solicitation, who has 2001:8b0:aab5:104:3::101, length 32 23:30:17.567080 58:9c:fc:10:ff:b6 > 1e:ab:48:c1:f6:62, ethertype IPv6 (0x86= dd), length 70: 2001:8b0:aab5:104:3::101 > 2001:8b0:aab5:106::12: ICMP6, ec= ho request, id 34603, seq 14, length 16 23:30:17.674842 1e:ab:48:c1:f6:62 > 33:33:ff:00:01:01, ethertype IPv6 (0x86= dd), length 86: fe80::1cab:48ff:fec1:f662 > ff02::1:ff00:101: ICMP6, neighb= or solicitation, who has 2001:8b0:aab5:104:3::101, length 32 23:30:17.936956 1e:ab:48:c1:f6:62 > 33:33:00:00:00:01, ethertype IPv6 (0x86= dd), length 166: fe80::1cab:48ff:fec1:f662 > ff02::1: ICMP6, router adverti= sement, length 112 23:30:18.567093 58:9c:fc:10:ff:b6 > 1e:ab:48:c1:f6:62, ethertype IPv6 (0x86= dd), length 70: 2001:8b0:aab5:104:3::101 > 2001:8b0:aab5:106::12: ICMP6, ec= ho request, id 34603, seq 15, length 16 23:30:19.567104 58:9c:fc:10:ff:b6 > 1e:ab:48:c1:f6:62, ethertype IPv6 (0x86= dd), length 70: 2001:8b0:aab5:104:3::101 > 2001:8b0:aab5:106::12: ICMP6, ec= ho request, id 34603, seq 16, length 16 23:30:19.567529 1e:ab:48:c1:f6:62 > 33:33:ff:00:01:01, ethertype IPv6 (0x86= dd), length 86: fe80::1cab:48ff:fec1:f662 > ff02::1:ff00:101: ICMP6, neighb= or solicitation, who has 2001:8b0:aab5:104:3::101, length 32 fe80::1cab:48ff:fec1:f662 is the subnet router; it's sending solicitations but FreeBSD doesn't send a response, if i remove alc0 from the bridge and configure the IPv6 address directly on alc0 instead, everything works fine. i'm testing without any packet filter (ipfw/pf) in the kernel. it's possible i'm missing something obvious here; does anyone have an idea? kernel is: FreeBSD ilythia.eden.le-fay.org 15.0-CURRENT FreeBSD 15.0-CURRENT #3 main-n267318-1b8d70b2eb71: Sat Dec 30 11:36:42 GMT 2023 lexi@ilythia.eden.le-fay.org:/src/main/sys/amd64/compile/ILYTHIA amd64 thanks, lexi. --KOhs/Fnhyb9mSIqR Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQGzBAABCAAdFiEEuwt6MaPcv/+Mo+ftDHqbqZ41x5kFAmWTTXEACgkQDHqbqZ41 x5lH7wwAkwFAL1vtBMwdVWK2mR5UoMuXpIohHxhkZn5h+va+YPgWyUtYVnsf60Vn m+D4fuGqM1UPTAJvZzzZWSU92B4X4gOrsyWamTh5G3wXsu5NYmlmTjXSixLgogS3 onsICLUj4BO1mwTqcwSSQoPtVNtktGNnIxSnALCpo5yCC4dCxQXqIet1JZrM3T// 75t+5GgzxIxUdB9WRKqWYJg+Lba8Fz7UMKirkwkKZcqraGHmtMHELVsoiFmonb0a E3JbZLK0v23g5qCKKaVEUp/WY+N1uXpwqc76o/yi9gTyYpFA/LrPhYXwVrVac+lk riKTPiTSx4HBCCHPoy+CUMGtyVuTfbZyGKR3I/8Pt3ePDeibZQO34V9sjVEnNesg 4kN31JPs8JpdCx3uf46G/FGHfAPOq6WdMfwvkDqtm7yMZB2Io6CbzOxpXweIbPCt qDbjRJldwRp+cT7sW2pM16gBgcd38oCEaJ+FdkTxeexIKZXvJ174RF9/l4NuPcug VVtjc/sl =yhHT -----END PGP SIGNATURE----- --KOhs/Fnhyb9mSIqR-- From nobody Tue Jan 2 03:42:21 2024 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4T3zHP5WShz566Zr for ; Tue, 2 Jan 2024 03:44:17 +0000 (UTC) (envelope-from warlock@phouka1.phouka.net) Received: from phouka1.phouka.net (phouka1.phouka.net [107.170.196.116]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "phouka.net", Issuer "Go Daddy Secure Certificate Authority - G2" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 4T3zHP2x49z4XyZ; Tue, 2 Jan 2024 03:44:17 +0000 (UTC) (envelope-from warlock@phouka1.phouka.net) Authentication-Results: mx1.freebsd.org; none Received: from phouka1.phouka.net (localhost [127.0.0.1]) by phouka1.phouka.net (8.17.1/8.17.1) with ESMTPS id 4023gLT2088491 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO); Mon, 1 Jan 2024 19:42:21 -0800 (PST) (envelope-from warlock@phouka1.phouka.net) Received: (from warlock@localhost) by phouka1.phouka.net (8.17.1/8.17.1/Submit) id 4023gLue088490; Mon, 1 Jan 2024 19:42:21 -0800 (PST) (envelope-from warlock) Date: Mon, 1 Jan 2024 19:42:21 -0800 From: John Kennedy To: Kurt Jaeger Cc: freebsd-current@freebsd.org Subject: Re: ZFS problems since recently ? Message-ID: References: List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:14061, ipnet:107.170.192.0/18, country:US] X-Spamd-Bar: ---- X-Rspamd-Queue-Id: 4T3zHP2x49z4XyZ On Mon, Jan 01, 2024 at 02:27:17PM +0100, Kurt Jaeger wrote: > > On Mon, Jan 01, 2024 at 06:43:58AM +0100, Kurt Jaeger wrote: > > > markj@ pointed me in > > > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=276039 > > > to > > > https://github.com/openzfs/zfs/pull/15719 > > > > > > So it will probably be fixed sooner or later. > > > > > > The other ZFS crashes I've seen are still an issue. > > > > My poudriere build did eventually fail as well: > > ... > > [05:40:24] [01] [00:17:20] Finished devel/gdb@py39 | gdb-13.2_1: Success > > [05:40:24] Stopping 2 builders > > panic: VERIFY(BP_GET_DEDUP(bp)) failed > > That's one of the panic messages I had as well. > > See > > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=276051 > > for additional crashes and dumps. > > > I didn't tweak this system off defaults for block-cloning. I haven't been following > > that issue 100%. > > Do you have > vfs.zfs.dmu_offset_next_sync=0 > ? I reverted everything and reinstalled. The VERIFY(BP_GET_DEDUP(bp)) panic hasn't reoccurred (tended to happen on poudriere-build cleanup), which may lean it more towards corruption, or maybe I just haven't been "lucky" with my small random chance of corruption. I did set vfs.zfs.dmu_offset_next_sync=0 after the bsdinstall was complete (maybe I could have loaded the zfs kernel module from the shell and set it before things kicked off). From nobody Tue Jan 2 07:28:48 2024 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4T44H44Jj2z56VG6 for ; Tue, 2 Jan 2024 07:29:20 +0000 (UTC) (envelope-from Alexander@Leidinger.net) Received: from mailgate.Leidinger.net (bastille.leidinger.net [89.238.82.207]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature ECDSA (P-256) client-digest SHA256) (Client CN "mailgate.leidinger.net", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4T44H32BYkz3ThV; Tue, 2 Jan 2024 07:29:19 +0000 (UTC) (envelope-from Alexander@Leidinger.net) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=leidinger.net header.s=outgoing-alex header.b=K2EO4t9m; spf=pass (mx1.freebsd.org: domain of Alexander@Leidinger.net designates 89.238.82.207 as permitted sender) smtp.mailfrom=Alexander@Leidinger.net; dmarc=pass (policy=quarantine) header.from=leidinger.net List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=leidinger.net; s=outgoing-alex; t=1704180550; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=bNMopP1xqffyC/uf2hB7e/E5nfN4swbTX3oKGwY+1E0=; b=K2EO4t9mLOHo6BWaBAo5/udIBsLTl42gtLIVGFoWkPw447gdbTOzGxvOkvUUbyqHlNK+GN 7tM0u50PxlthRHnFt5CmlUER8hiG3kiM1FDE1uqSbchBKJpB6Aa0Qjv6vJjTjh9X5IHaYA +RLpCJD03vkMLI8rznXQxj/kokcJV+MdWtOKs1cUn6Q9PN37uLyyp0rDohvPV3TLBesiAL bWHNmS/cr0hC31Ybj4u3wdNvEi2nanjRs1YRbJuXF8tEyhn4szN0sqahwUjqfaEynj5hV/ lqzZnUKGIp1+zEKV/xf5oN9FbbeTzkBh0ZzBL2ife4tmI3VrRCbdMcQHE4mccA== Date: Tue, 02 Jan 2024 08:28:48 +0100 From: Alexander Leidinger To: Kurt Jaeger Cc: freebsd-current@freebsd.org Subject: Re: ZFS problems since recently ? In-Reply-To: References: Message-ID: <5210dd54acbaa8d7705aa4f756e21d1a@Leidinger.net> Organization: No organization, this is a private message. Content-Type: multipart/signed; protocol="application/pgp-signature"; boundary="=_9361e29c39098c5b19f86bb32c7ffe37"; micalg=pgp-sha256 X-Spamd-Result: default: False [-4.31 / 15.00]; SIGNED_PGP(-2.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; SUBJECT_ENDS_QUESTION(1.00)[]; DMARC_POLICY_ALLOW(-0.50)[leidinger.net,quarantine]; NEURAL_HAM_SHORT(-0.21)[-0.213]; MIME_GOOD(-0.20)[multipart/signed,text/plain]; R_SPF_ALLOW(-0.20)[+mx]; R_DKIM_ALLOW(-0.20)[leidinger.net:s=outgoing-alex]; FROM_EQ_ENVFROM(0.00)[]; RCVD_COUNT_ZERO(0.00)[0]; MLMMJ_DEST(0.00)[freebsd-current@freebsd.org]; MIME_TRACE(0.00)[0:+,1:+,2:~]; ARC_NA(0.00)[]; DKIM_TRACE(0.00)[leidinger.net:+]; ASN(0.00)[asn:34240, ipnet:89.238.64.0/18, country:DE]; TO_DN_SOME(0.00)[]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_TWO(0.00)[2]; TO_MATCH_ENVRCPT_ALL(0.00)[]; HAS_ORG_HEADER(0.00)[]; HAS_ATTACHMENT(0.00)[]; MID_RHS_MATCH_FROM(0.00)[] X-Rspamd-Queue-Id: 4T44H32BYkz3ThV X-Spamd-Bar: ---- This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --=_9361e29c39098c5b19f86bb32c7ffe37 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII; format=flowed Am 2023-12-31 19:34, schrieb Kurt Jaeger: > I already have > > vfs.zfs.dmu_offset_next_sync=0 > > which is supposed to disable block-cloning. It isn't. This one is supposed to fix an issue which is unrelated to block cloning (but can be amplified by block cloning). This issue is fixed since some weeks, your Dec 23 build should not need it (when the issues happens, you have files with zero as parts of the data instead of the real data, and only if you copy files at the same time as those files are modified, and then only if you happen to get the timing right). The sysctl for block cloning is vfs.zfs.bclone_enabled. To check if a pool has made use of block cloning: zpool get all poolname | grep bclone Bye, Alexander. -- http://www.Leidinger.net Alexander@Leidinger.net: PGP 0x8F31830F9F2772BF http://www.FreeBSD.org netchild@FreeBSD.org : PGP 0x8F31830F9F2772BF --=_9361e29c39098c5b19f86bb32c7ffe37 Content-Type: application/pgp-signature; name=signature.asc Content-Disposition: attachment; filename=signature.asc; size=833 Content-Description: OpenPGP digital signature -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEER9UlYXp1PSd08nWXEg2wmwP42IYFAmWTu0EACgkQEg2wmwP4 2IajCQ//QbH+PlqywDSbQHnUaZjl9GsuxsgppKzQNGv7mWgomDB+lSlfR0KZMdDz dSWh5UtUkDl2x1ZQPQUTNWo/HC4F9b7n6EMdI/2N2vanptnaWq49+UZ2a2bNUfs5 q7ocNODRXQbcf/O8wfcFo+6rJhogXNv8gURfZQkjc7lh+inzB7iNc9uXzIR0TPex PKadi6CtWYV0LGromJZ8ZPxJXXzqMTaKoPBtkzIjDhQ9opJzNBRgViqXaoWjkNJi aYxgqQOYPC7oAIcMO5/IM6LfNrDdiFAnE6OkeCHTRgTxTlnosMsjQNES86UeEkNA V5RZVb0ghbSVinWgHNHOu4gFrJIAIxRW4OnUA+yaVJ+T/mAjLOQcVS20Z0GK9QW5 giw24+lXQZCG/G5INZgTe3IfpG7uIRUyJDpuVQrangE1u31xJB+X071SQAeSvrOp cn3PrQsDRNtnqE636Y3g+eU697+u7+N3MVYsdLaBmnoXAXqPzHPNU2HkbCo8ZpQE 9PodopAoHt2SxvLxx+0GN1TRPgfyS6L5dB2LNoPhzi5Ve7TgjiZPdyVWnz/JeEwp REdFvQtUKqnIp6WQP29gA6O0EwULqef5HgszX4g9x3ujAB+I8+FX55XiLGTYwZnm LplwKs7GzEzcxcJfiTEfXPJI1sf6zIU8XjuIKFUArAEkAN7MR6w= =9Xnj -----END PGP SIGNATURE----- --=_9361e29c39098c5b19f86bb32c7ffe37-- From nobody Tue Jan 2 06:49:13 2024 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4T44k36Qysz56X4N for ; Tue, 2 Jan 2024 07:49:15 +0000 (UTC) (envelope-from pi@freebsd.org) Received: from fc.opsec.eu (fc.opsec.eu [IPv6:2001:14f8:200:4::4]) by mx1.freebsd.org (Postfix) with ESMTP id 4T44k31xnTz3WkM for ; Tue, 2 Jan 2024 07:49:15 +0000 (UTC) (envelope-from pi@freebsd.org) Authentication-Results: mx1.freebsd.org; none Received: from pi (uid 104) (envelope-from pi@freebsd.org) id 1879e by fc.opsec.eu (DragonFly Mail Agent v0.13+ on fc.opsec.eu); Tue, 02 Jan 2024 07:49:13 +0100 Date: Tue, 2 Jan 2024 07:49:13 +0100 From: Kurt Jaeger To: Alexander Leidinger Cc: freebsd-current@freebsd.org Subject: Re: ZFS problems since recently ? Message-ID: References: <5210dd54acbaa8d7705aa4f756e21d1a@Leidinger.net> List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <5210dd54acbaa8d7705aa4f756e21d1a@Leidinger.net> X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:12502, ipnet:2001:14f8::/32, country:DE] X-Spamd-Bar: ---- X-Rspamd-Queue-Id: 4T44k31xnTz3WkM Hi! > Am 2023-12-31 19:34, schrieb Kurt Jaeger: > > I already have > > > > vfs.zfs.dmu_offset_next_sync=0 > > > > which is supposed to disable block-cloning. > > It isn't. This one is supposed to fix an issue which is unrelated to block > cloning (but can be amplified by block cloning). This issue is fixed since > some weeks, your Dec 23 build should not need it (when the issues happens, > you have files with zero as parts of the data instead of the real data, > and only if you copy files at the same time as those files are modified, > and then only if you happen to get the timing right). > > The sysctl for block cloning is vfs.zfs.bclone_enabled. > To check if a pool has made use of block cloning: > zpool get all poolname | grep bclone Thanks. I now used that sysctl and my testcase (testbuild of shells/bash) and it did not crash. -- pi@FreeBSD.org +49 171 3101372 Now what ? From nobody Tue Jan 2 07:51:34 2024 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4T44np6znjz56XJ6 for ; Tue, 2 Jan 2024 07:52:30 +0000 (UTC) (envelope-from Alexander@Leidinger.net) Received: from mailgate.Leidinger.net (bastille.leidinger.net [89.238.82.207]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) client-signature ECDSA (P-256)) (Client CN "mailgate.leidinger.net", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4T44np59c6z3Xxl for ; Tue, 2 Jan 2024 07:52:30 +0000 (UTC) (envelope-from Alexander@Leidinger.net) Authentication-Results: mx1.freebsd.org; none List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=leidinger.net; s=outgoing-alex; t=1704181944; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=F/P9zMUN5PaqJi8OOQwR85BBpf+rpe38h/sBCwvhoMA=; b=o7Mp8iVnoOdp3oLqHLwp6SIJ9Kj6xLCR7irilpnf+r9ykSwYJpnJkc8ZqAr3BUDQY258nb ZNQZ1D/zpiNJRblbO1RNGpmzvjnJWSo63duekdEIW+FrGiOtV1UYbJuJhFuVoKwK2ad2QO TWF86iJfp6JT3YHR8ttxK6N3aCFjp2BtUBz+Ooxmxqie2p9yIvkv3NPCf8J7p4kSRb3B/T FyFiAY9FhETaTAKB45cQQttfyla1kQK7m1fPjYoofcJz22A6BytWIy6oRpSmA+/7dEOXdy WCGNaW35k7iDWPre6YiHRdKtFq94/ZjiZ0iTD1rZkmVOZhbSBcOr/laL/9i51w== Date: Tue, 02 Jan 2024 08:51:34 +0100 From: Alexander Leidinger To: Lexi Winter Cc: freebsd-current@freebsd.org Subject: Re: bridge(4) and IPv6 broken? In-Reply-To: References: Message-ID: Organization: No organization, this is a private message. Content-Type: multipart/signed; protocol="application/pgp-signature"; boundary="=_8cbf11b68ead8080bbdc8cbe667837d8"; micalg=pgp-sha256 X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:34240, ipnet:89.238.64.0/18, country:DE] X-Spamd-Bar: ---- X-Rspamd-Queue-Id: 4T44np59c6z3Xxl This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --=_8cbf11b68ead8080bbdc8cbe667837d8 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII; format=flowed Am 2024-01-02 00:40, schrieb Lexi Winter: > hello, > > i'm having an issue with bridge(4) and IPv6, with a configuration which > is essentially identical to a working system running releng/14.0. > > ifconfig: > > lo0: flags=1008049 metric 0 mtu > 16384 > options=680003 > inet 127.0.0.1 netmask 0xff000000 > inet6 ::1 prefixlen 128 > inet6 fe80::1%lo0 prefixlen 64 scopeid 0x1 > groups: lo > nd6 options=21 > pflog0: flags=1000141 metric 0 mtu 33152 > options=0 > groups: pflog > alc0: > flags=1008943 > metric 0 mtu 1500 > options=c3098 > ether 30:9c:23:a8:89:a0 > inet6 fe80::329c:23ff:fea8:89a0%alc0 prefixlen 64 scopeid 0x3 > media: Ethernet autoselect (1000baseT ) > status: active > nd6 options=1 > wg0: flags=10080c1 metric 0 mtu > 1420 > options=80000 > inet 172.16.145.21 netmask 0xffffffff > inet6 fd00:0:1337:cafe:1111:1111:829a:595e prefixlen 128 > groups: wg > tunnelfib: 1 > nd6 options=101 > bridge0: flags=1008843 > metric 0 mtu 1500 > options=0 > ether 58:9c:fc:10:ff:b6 > inet 10.1.4.101 netmask 0xffffff00 broadcast 10.1.4.255 > inet6 2001:8b0:aab5:104:3::101 prefixlen 64 > id 00:00:00:00:00:00 priority 32768 hellotime 2 fwddelay 15 > maxage 20 holdcnt 6 proto rstp maxaddr 2000 timeout 1200 > root id 00:00:00:00:00:00 priority 32768 ifcost 0 port 0 > member: tap0 flags=143 > ifmaxaddr 0 port 6 priority 128 path cost 2000000 > member: alc0 flags=143 > ifmaxaddr 0 port 3 priority 128 path cost 55 > groups: bridge > nd6 options=1 > tap0: flags=9903 metric 0 > mtu 1500 > options=80000 > ether 58:9c:fc:10:ff:89 > groups: tap > media: Ethernet 1000baseT > status: no carrier > nd6 options=29 > > the issue is that the bridge doesn't seem to respond to IPv6 ICMP > Neighbour Solicitation. for example, while running ping, tcpdump shows > this: > > 23:30:16.567071 58:9c:fc:10:ff:b6 > 1e:ab:48:c1:f6:62, ethertype IPv6 > (0x86dd), length 70: 2001:8b0:aab5:104:3::101 > 2001:8b0:aab5:106::12: > ICMP6, echo request, id 34603, seq 13, length 16 > 23:30:16.634860 1e:ab:48:c1:f6:62 > 33:33:ff:00:01:01, ethertype IPv6 > (0x86dd), length 86: fe80::1cab:48ff:fec1:f662 > ff02::1:ff00:101: > ICMP6, neighbor solicitation, who has 2001:8b0:aab5:104:3::101, length > 32 > 23:30:17.567080 58:9c:fc:10:ff:b6 > 1e:ab:48:c1:f6:62, ethertype IPv6 > (0x86dd), length 70: 2001:8b0:aab5:104:3::101 > 2001:8b0:aab5:106::12: > ICMP6, echo request, id 34603, seq 14, length 16 > 23:30:17.674842 1e:ab:48:c1:f6:62 > 33:33:ff:00:01:01, ethertype IPv6 > (0x86dd), length 86: fe80::1cab:48ff:fec1:f662 > ff02::1:ff00:101: > ICMP6, neighbor solicitation, who has 2001:8b0:aab5:104:3::101, length > 32 > 23:30:17.936956 1e:ab:48:c1:f6:62 > 33:33:00:00:00:01, ethertype IPv6 > (0x86dd), length 166: fe80::1cab:48ff:fec1:f662 > ff02::1: ICMP6, > router advertisement, length 112 > 23:30:18.567093 58:9c:fc:10:ff:b6 > 1e:ab:48:c1:f6:62, ethertype IPv6 > (0x86dd), length 70: 2001:8b0:aab5:104:3::101 > 2001:8b0:aab5:106::12: > ICMP6, echo request, id 34603, seq 15, length 16 > 23:30:19.567104 58:9c:fc:10:ff:b6 > 1e:ab:48:c1:f6:62, ethertype IPv6 > (0x86dd), length 70: 2001:8b0:aab5:104:3::101 > 2001:8b0:aab5:106::12: > ICMP6, echo request, id 34603, seq 16, length 16 > 23:30:19.567529 1e:ab:48:c1:f6:62 > 33:33:ff:00:01:01, ethertype IPv6 > (0x86dd), length 86: fe80::1cab:48ff:fec1:f662 > ff02::1:ff00:101: > ICMP6, neighbor solicitation, who has 2001:8b0:aab5:104:3::101, length > 32 > > fe80::1cab:48ff:fec1:f662 is the subnet router; it's sending > solicitations but FreeBSD doesn't send a response, > > if i remove alc0 from the bridge and configure the IPv6 address > directly > on alc0 instead, everything works fine. > > i'm testing without any packet filter (ipfw/pf) in the kernel. > > it's possible i'm missing something obvious here; does anyone have an > idea? Just an idea. I'm not sure if it is the right track... There is code in the kernel which is ignoring NS stuff from "non-valid" sources (security / spoofing reasons). The NS request is from a link local address. Your bridge has no link local address (and your tap has the auto linklocal flag set which I would have expected to be on the bridge instead). I'm not sure but I would guess it could be because of this. If my guess is not too far off, I would suggest to try: - remove auto linklocal from tap0 (like for alc0) - add auto linklocal to bridge0 If this doesn't help, there is the sysctl net.inet6.icmp6.nd6_onlink_ns_rfc4861 which you could try to set to 1. Please read https://www.freebsd.org/security/advisories/FreeBSD-SA-08:10.nd6.asc before you do that. Bye, Alexander. -- http://www.Leidinger.net Alexander@Leidinger.net: PGP 0x8F31830F9F2772BF http://www.FreeBSD.org netchild@FreeBSD.org : PGP 0x8F31830F9F2772BF --=_8cbf11b68ead8080bbdc8cbe667837d8 Content-Type: application/pgp-signature; name=signature.asc Content-Disposition: attachment; filename=signature.asc; size=833 Content-Description: OpenPGP digital signature -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEER9UlYXp1PSd08nWXEg2wmwP42IYFAmWTwJYACgkQEg2wmwP4 2IazGg/8DArWfskxI9N175ADM3IIzb//ggHsRGqMwlkPfZNq/kH3P1fItv4W/dGZ EPQx70vlHVbFgl7HkmWGkyvaG77Sp1zkB/TRT+a1408GsixRuqz4wO8z9hmh7Z8P 28OUCdSGose6EjVifE7ba9H3kl9UVFvHaXHxuIzqwGf/3QfEf9ZNF9m9f/I0xerB NItX3SzsHJX8jBaM073uWCEccjKqQrhOzeN0mLJpCuNMAoFyKSCJWQWuYqwtYwEX /Bki8nuR4YcHStIJn0Se5Ti196CqasL/KCBdwXa2GzXu7PUGEoF57wg39/CgEmR2 mTYrbzMV+DKoW1NIsWzVfiIwUqI+nQd8Vt08+uYBbLG/vssIxINarmJmvaugLv+A XIsEw+7764oQxEQCZFJm+/kWVosboob2x+MdzkENnUucmbo29kKYudW6z3T6b6U9 N/HKc9YGOW89LAnmBCMZ7qZ/OWDMsI3GfkzudJDMtJaxGghYJ9m7b/jCbVgZosNz D9OCXiF3jTd/lnZtYh3J3/CnMGlVV/UAPSWbCEx/TlVeOKMsHU0FhdbMAT4/R0+l mU7i6rE847GoRsqymDgSsH8J/cKMs5v6pqQFzG3++eI4qX8/dsZd7aErCLocB7Bj t4851WUv4l3taJFXBJEa2sc+tpkHSa3rF9SKWD6fPqziPGeffNw= =KiUa -----END PGP SIGNATURE----- --=_8cbf11b68ead8080bbdc8cbe667837d8-- From nobody Tue Jan 2 07:22:13 2024 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4T45S50Kvpz56ZbM for ; Tue, 2 Jan 2024 08:22:13 +0000 (UTC) (envelope-from pi@freebsd.org) Received: from fc.opsec.eu (fc.opsec.eu [IPv6:2001:14f8:200:4::4]) by mx1.freebsd.org (Postfix) with ESMTP id 4T45S43X2vz3dCR for ; Tue, 2 Jan 2024 08:22:12 +0000 (UTC) (envelope-from pi@freebsd.org) Authentication-Results: mx1.freebsd.org; none Received: from pi (uid 104) (envelope-from pi@freebsd.org) id 19046 by fc.opsec.eu (DragonFly Mail Agent v0.13+ on fc.opsec.eu); Tue, 02 Jan 2024 08:22:13 +0100 Date: Tue, 2 Jan 2024 08:22:13 +0100 From: Kurt Jaeger To: Alexander Leidinger Cc: freebsd-current@freebsd.org Subject: Re: ZFS problems since recently ? Message-ID: References: <5210dd54acbaa8d7705aa4f756e21d1a@Leidinger.net> List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <5210dd54acbaa8d7705aa4f756e21d1a@Leidinger.net> X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:12502, ipnet:2001:14f8::/32, country:DE] X-Spamd-Bar: ---- X-Rspamd-Queue-Id: 4T45S43X2vz3dCR Hi! > The sysctl for block cloning is vfs.zfs.bclone_enabled. > To check if a pool has made use of block cloning: > zpool get all poolname | grep bclone One more thing: I have two pools on that box, and one of them has some bclone files: # zpool get all ref | grep bclone ref bcloneused 21.8M - ref bclonesaved 24.4M - ref bcloneratio 2.12x - # zpool get all pou | grep bclone pou bcloneused 0 - pou bclonesaved 0 - pou bcloneratio 1.00x - The ref pool contains the system and some files. The pou pool is for poudriere only. How do I find which files on ref are bcloned and how can I remove the bcloning from them ? -- pi@FreeBSD.org +49 171 3101372 Now what ? From nobody Tue Jan 2 08:34:38 2024 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4T45lW2qyrz56bsT for ; Tue, 2 Jan 2024 08:35:35 +0000 (UTC) (envelope-from Alexander@Leidinger.net) Received: from mailgate.Leidinger.net (bastille.leidinger.net [89.238.82.207]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) client-signature ECDSA (P-256)) (Client CN "mailgate.leidinger.net", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4T45lV5NXnz3g1r; Tue, 2 Jan 2024 08:35:34 +0000 (UTC) (envelope-from Alexander@Leidinger.net) Authentication-Results: mx1.freebsd.org; none List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=leidinger.net; s=outgoing-alex; t=1704184528; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=xqEUhApMs4Wc6/4jrW9oERP+dtmQ8mN03vlFsq0/gUY=; b=BKotRwNnwg4tXQEqXXwK4xCFV0tJhZ1F9AzCRCVxgfn4lYFfG3Ab6Hp8A3WJ4dCelicyFc nkNCdLyBLVE+LXlCfGzVadJKMnkgg9VHFFRDLEu3MUVG5/Zk6N+fqNwFpz2Yj37Db6J/1P g84TqUHCkIDC46CnvJEOseK4InnIbW+YzQjHrrCcsuw8huNdZvt7p0nJ9GUVBvwG7Qp+X5 Ycu9AdPwe0CcQvdSdc935ynsvg3zGNMaKeXogfrCnkHmj6PwN+udXxUlIwzui7MAc0OYpg OTKsaVzNnBZswK41n0BBSsALPdZr9pcH0s9qJrquAJiVdTRtdzW4QaK8jmv2Sg== Date: Tue, 02 Jan 2024 09:34:38 +0100 From: Alexander Leidinger To: Kurt Jaeger Cc: freebsd-current@freebsd.org Subject: Re: ZFS problems since recently ? In-Reply-To: References: <5210dd54acbaa8d7705aa4f756e21d1a@Leidinger.net> Message-ID: Organization: No organization, this is a private message. Content-Type: multipart/signed; protocol="application/pgp-signature"; boundary="=_2cd57a592242f8fd641657a1aa46689f"; micalg=pgp-sha256 X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:34240, ipnet:89.238.64.0/18, country:DE] X-Spamd-Bar: ---- X-Rspamd-Queue-Id: 4T45lV5NXnz3g1r This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --=_2cd57a592242f8fd641657a1aa46689f Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII; format=flowed Am 2024-01-02 08:22, schrieb Kurt Jaeger: > Hi! > >> The sysctl for block cloning is vfs.zfs.bclone_enabled. >> To check if a pool has made use of block cloning: >> zpool get all poolname | grep bclone > > One more thing: > > I have two pools on that box, and one of them has some bclone files: > > # zpool get all ref | grep bclone > ref bcloneused 21.8M - > ref bclonesaved 24.4M - > ref bcloneratio 2.12x - > # zpool get all pou | grep bclone > pou bcloneused 0 - > pou bclonesaved 0 - > pou bcloneratio 1.00x - > > The ref pool contains the system and some files. > The pou pool is for poudriere only. > > How do I find which files on ref are bcloned and how can I remove the > bcloning from them ? No idea about the detection (I don't expect an easy way), but the answer to the second part is to copy the files after disabling block cloning. As this is system stuff, I would expect it is not much data, and you could copy everything and then move back to the original place. I would also assume original log files are not affected, and only files which were copied (installworld or installkernel or backup files or manual copies or port install (not sure about pkg install)) are possible targets. Bye, Alexander. -- http://www.Leidinger.net Alexander@Leidinger.net: PGP 0x8F31830F9F2772BF http://www.FreeBSD.org netchild@FreeBSD.org : PGP 0x8F31830F9F2772BF --=_2cd57a592242f8fd641657a1aa46689f Content-Type: application/pgp-signature; name=signature.asc Content-Disposition: attachment; filename=signature.asc; size=833 Content-Description: OpenPGP digital signature -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEER9UlYXp1PSd08nWXEg2wmwP42IYFAmWTyq4ACgkQEg2wmwP4 2IY/iRAAgRgMdp3gPHwUrHvaoaeXJfHokjhaFMmlcZi0QlyDo74PfikLWLIbIcE3 XXdHFb3UoiM29zPHT/PRf+EMUmZUiVl10FOhgAMLrJ4vhWvCTBMXDXyGuSNeWl5J mk40ELjL2CnE7vPvJ9e/8cwh8PVYm0hhmQ83OS9OfoI34Dm0hhsHZxHu4Yv2uJdP ojTypAKREhElW8qe04DQX8qDLOcyJFZvhqwUKqqS9laSQSWLL6SSjUw7Ap/4AUle AzX7jJFJcXZeTIPnkfR1XVvwZSrmCYGBfm2/HYSR0K4gbi0NdXB3KrF3qlkOoLFo 3VHqTaHGUGuCNvwtkKk07rhtM1pXFgDdIXGPUpekMKUMdKU5sbTNg/sYkrU/7ZYt lRyI7jgayDocigQ7x7ifjlpibXxML3Np8rEkYuWZ6SRY5iQU9IHddppUHiM8+4ZK 9wLheJQzb3rlWOrP1yytrkhMHiDd76OtEj2ykQE/LAmoMt7H6RnRdOE2mviVIvWY 2MmubYbKxP7/3iOtqu8eZY2xfWZoTw3Br73filgqLR55bH1pi6RVcAmir2ntW1pP p0TL5i8hr3xEEDqELsu2KlPenfiPeixuCTFrGK9klV9vdqPGlsVsB2fd8/iRxxng jEt6mzvmIZH6MdLndJxEJEAXFViYIhktVkaYeEBxLPKO0ltuDz8= =OHJH -----END PGP SIGNATURE----- --=_2cd57a592242f8fd641657a1aa46689f-- From nobody Tue Jan 2 12:56:51 2024 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4T4CYF6319z55M94 for ; Tue, 2 Jan 2024 12:57:05 +0000 (UTC) (envelope-from crest@rlwinm.de) Received: from mail.rlwinm.de (mail.rlwinm.de [IPv6:2a01:4f8:171:f902::5]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4T4CYF0rBXz4YF1 for ; Tue, 2 Jan 2024 12:57:04 +0000 (UTC) (envelope-from crest@rlwinm.de) Authentication-Results: mx1.freebsd.org; dkim=none; spf=pass (mx1.freebsd.org: domain of crest@rlwinm.de designates 2a01:4f8:171:f902::5 as permitted sender) smtp.mailfrom=crest@rlwinm.de; dmarc=none Received: from [IPV6:2003:d7:1f0b:3800:6cd3:a690:af2f:b47f] (p200300d71f0b38006cd3a690af2fb47f.dip0.t-ipconnect.de [IPv6:2003:d7:1f0b:3800:6cd3:a690:af2f:b47f]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-384) server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by mail.rlwinm.de (Postfix) with ESMTPSA id BB96234E6B for ; Tue, 2 Jan 2024 12:56:52 +0000 (UTC) Message-ID: <91dfe3b4-11ff-435e-b8c3-b4e3c9ee81fd@rlwinm.de> Date: Tue, 2 Jan 2024 13:56:51 +0100 List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: bridge(4) and IPv6 broken? To: freebsd-current@freebsd.org References: Content-Language: en-US From: Jan Bramkamp In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Spamd-Result: default: False [-2.28 / 15.00]; SUBJECT_ENDS_QUESTION(1.00)[]; NEURAL_HAM_SHORT(-1.00)[-0.999]; NEURAL_HAM_LONG(-1.00)[-0.996]; NEURAL_HAM_MEDIUM(-0.99)[-0.992]; R_SPF_ALLOW(-0.20)[+mx]; MIME_GOOD(-0.10)[text/plain]; XM_UA_NO_VERSION(0.01)[]; ASN(0.00)[asn:24940, ipnet:2a01:4f8::/32, country:DE]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; RCVD_COUNT_ONE(0.00)[1]; MLMMJ_DEST(0.00)[freebsd-current@freebsd.org]; RCVD_VIA_SMTP_AUTH(0.00)[]; DMARC_NA(0.00)[rlwinm.de]; RCPT_COUNT_ONE(0.00)[1]; FROM_HAS_DN(0.00)[]; ARC_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; TO_MATCH_ENVRCPT_ALL(0.00)[]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; MID_RHS_MATCH_FROM(0.00)[]; TO_DN_NONE(0.00)[]; RCVD_TLS_ALL(0.00)[] X-Rspamd-Queue-Id: 4T4CYF0rBXz4YF1 X-Spamd-Bar: -- On 02.01.24 00:40, Lexi Winter wrote: > hello, > > i'm having an issue with bridge(4) and IPv6, with a configuration which > is essentially identical to a working system running releng/14.0. > > ifconfig: > > lo0: flags=1008049 metric 0 mtu 16384 > options=680003 > inet 127.0.0.1 netmask 0xff000000 > inet6 ::1 prefixlen 128 > inet6 fe80::1%lo0 prefixlen 64 scopeid 0x1 > groups: lo > nd6 options=21 > pflog0: flags=1000141 metric 0 mtu 33152 > options=0 > groups: pflog > alc0: flags=1008943 metric 0 mtu 1500 > options=c3098 > ether 30:9c:23:a8:89:a0 > inet6 fe80::329c:23ff:fea8:89a0%alc0 prefixlen 64 scopeid 0x3 > media: Ethernet autoselect (1000baseT ) > status: active > nd6 options=1 > wg0: flags=10080c1 metric 0 mtu 1420 > options=80000 > inet 172.16.145.21 netmask 0xffffffff > inet6 fd00:0:1337:cafe:1111:1111:829a:595e prefixlen 128 > groups: wg > tunnelfib: 1 > nd6 options=101 > bridge0: flags=1008843 metric 0 mtu 1500 > options=0 > ether 58:9c:fc:10:ff:b6 > inet 10.1.4.101 netmask 0xffffff00 broadcast 10.1.4.255 > inet6 2001:8b0:aab5:104:3::101 prefixlen 64 > id 00:00:00:00:00:00 priority 32768 hellotime 2 fwddelay 15 > maxage 20 holdcnt 6 proto rstp maxaddr 2000 timeout 1200 > root id 00:00:00:00:00:00 priority 32768 ifcost 0 port 0 > member: tap0 flags=143 > ifmaxaddr 0 port 6 priority 128 path cost 2000000 > member: alc0 flags=143 > ifmaxaddr 0 port 3 priority 128 path cost 55 > groups: bridge > nd6 options=1 > tap0: flags=9903 metric 0 mtu 1500 > options=80000 > ether 58:9c:fc:10:ff:89 > groups: tap > media: Ethernet 1000baseT > status: no carrier > nd6 options=29 IPv6 enabled interfaces need a link-local address for normal operation. Please set the auto-linklocal flag on the bridge and try again. From nobody Tue Jan 2 13:50:58 2024 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4T4Dlp1kqHz55SQs for ; Tue, 2 Jan 2024 13:51:18 +0000 (UTC) (envelope-from pmh@hausen.com) Received: from mail2.pluspunkthosting.de (mail2.pluspunkthosting.de [217.29.33.228]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4T4Dln1gKDz4gLN for ; Tue, 2 Jan 2024 13:51:17 +0000 (UTC) (envelope-from pmh@hausen.com) Authentication-Results: mx1.freebsd.org; dkim=none; spf=pass (mx1.freebsd.org: domain of pmh@hausen.com designates 217.29.33.228 as permitted sender) smtp.mailfrom=pmh@hausen.com; dmarc=none Received: from smtpclient.apple (87.138.185.145) by mail2.pluspunkthosting.de (Axigen) with (ECDHE-RSA-AES256-GCM-SHA384 encrypted) ESMTPSA id 327DC1; Tue, 2 Jan 2024 14:51:08 +0100 From: "Patrick M. Hausen" Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3774.300.61.1.2\)) Subject: Re: bridge(4) and IPv6 broken? Date: Tue, 2 Jan 2024 14:50:58 +0100 References: <91dfe3b4-11ff-435e-b8c3-b4e3c9ee81fd@rlwinm.de> To: Current FreeBSD In-Reply-To: <91dfe3b4-11ff-435e-b8c3-b4e3c9ee81fd@rlwinm.de> Message-Id: <1897E648-156B-46F5-B954-67A6F8DDC6BC@hausen.com> X-Mailer: Apple Mail (2.3774.300.61.1.2) X-Spamd-Result: default: False [-1.80 / 15.00]; SUBJECT_ENDS_QUESTION(1.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-1.00)[-0.999]; NEURAL_HAM_SHORT(-1.00)[-0.998]; MV_CASE(0.50)[]; R_SPF_ALLOW(-0.20)[+a:mail2.pluspunkthosting.de]; MIME_GOOD(-0.10)[text/plain]; R_DKIM_NA(0.00)[]; ASN(0.00)[asn:16188, ipnet:217.29.32.0/20, country:DE]; FROM_EQ_ENVFROM(0.00)[]; RCVD_COUNT_ONE(0.00)[1]; MLMMJ_DEST(0.00)[freebsd-current@freebsd.org]; TO_DN_ALL(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; MID_RHS_MATCH_FROM(0.00)[]; ARC_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; FROM_HAS_DN(0.00)[]; DMARC_NA(0.00)[hausen.com]; TO_MATCH_ENVRCPT_ALL(0.00)[]; RCVD_TLS_ALL(0.00)[] X-Rspamd-Queue-Id: 4T4Dln1gKDz4gLN X-Spamd-Bar: - Hi all, > Am 02.01.2024 um 13:56 schrieb Jan Bramkamp : >=20 > IPv6 enabled interfaces need a link-local address for normal = operation. Please set the auto-linklocal flag on the bridge and try = again. And remove the link-local address from alc0. A bridge member must not = have any layer 3 addresses configured. If you are using the standard rc.conf = variables just use: ifconfig_alc0=3D"up" Kind regards, Patrick= From nobody Tue Jan 2 22:51:32 2024 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4T4SlW51VFz562y6 for ; Tue, 2 Jan 2024 22:51:51 +0000 (UTC) (envelope-from mavbsd@gmail.com) Received: from mail-oo1-xc34.google.com (mail-oo1-xc34.google.com [IPv6:2607:f8b0:4864:20::c34]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1D4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4T4SlV6FKDz3NXY; Tue, 2 Jan 2024 22:51:50 +0000 (UTC) (envelope-from mavbsd@gmail.com) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20230601 header.b=gqnqGTBL; spf=pass (mx1.freebsd.org: domain of mavbsd@gmail.com designates 2607:f8b0:4864:20::c34 as permitted sender) smtp.mailfrom=mavbsd@gmail.com; dmarc=none Received: by mail-oo1-xc34.google.com with SMTP id 006d021491bc7-595507627c8so1042704eaf.1; Tue, 02 Jan 2024 14:51:50 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1704235908; x=1704840708; darn=freebsd.org; h=content-transfer-encoding:in-reply-to:from:references:cc:to :content-language:subject:user-agent:mime-version:date:message-id :sender:from:to:cc:subject:date:message-id:reply-to; bh=eGePjWc9KKhgJWW+187z0zLAKhY9SWmThdGCfCDrGz8=; b=gqnqGTBLg7T5Jj46PsE5z4pOlLSY9vDPmrUPLSYW51sruQfa6krlEogNkj/hHCIE1w DNH2QYzB+nfhvXrFINM3CEjTFzVZ6+8fbX9blP7QNOWY9kGaIZiXGolpbMgBQVNbvINL oBdHg7E/DhRPrvbGmSA9+B/WIxtFmfSWdSl6YOpHkGJqWwFFG+vQ3wh/HSS6C0psjfCZ CjmAzF5tBqA5MEuR7HE8+fgP2EHuFrP/8sFiC9YdUGiY66dZ51lEcyWaUaDHGp3P1tcd lWJfrZGOLNhyfM8vouHJFw1HSf6TOsm9kK/KbREi6ZIujelvfzQNPlg+8BLcNdSic7jq FdlA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1704235908; x=1704840708; h=content-transfer-encoding:in-reply-to:from:references:cc:to :content-language:subject:user-agent:mime-version:date:message-id :sender:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=eGePjWc9KKhgJWW+187z0zLAKhY9SWmThdGCfCDrGz8=; b=s2ZsbN+ZpOweBXj9Ws3uNjRd0kL5SM0frveQZuAloXb/RZsOy3V6Sx9n4zUV19s5Wl NtoRqxGetNuggjvLztCbR5fojmCqZra/fMnoKguT5xvZjTdNcO6DmsYdGdv9A/37ELnJ z67nUZzd8abRM8eFjfzP2l/SP5PkZ/3rF62ggBb7Ai2LRBFsWL8//SSkFhqLjOO0LhRz neLB8re6DompI46yg5sh/wSeKZtxpPvKT3y2y4bc2U7YVZ31YOMq8dqwL0AuxH3pZf80 H8KHmZ/JvgKhtWo3JXMNsmEQGi/HJ3QfALTMjHz4cXGfaJcN4AqvSBjof0/SHcGU13Ka JsJA== X-Gm-Message-State: AOJu0Yy+802N/Hb7l1BidivHWM18iZ4h5HjMaxRUl/Cc3ShY6V5Qd/rX znTGwwT4HhlpbbPR4kuvQGo= X-Google-Smtp-Source: AGHT+IGf95pJneIVoMTWOvQ3HTPitu6x2RWigDwJarpVifxB48po2Nacd2xRZAG/CZ88DRC+yBLfjQ== X-Received: by 2002:a05:6808:16a0:b0:3bb:edef:478 with SMTP id bb32-20020a05680816a000b003bbedef0478mr65154oib.36.1704235908530; Tue, 02 Jan 2024 14:51:48 -0800 (PST) Received: from [10.230.45.5] ([38.32.73.2]) by smtp.gmail.com with ESMTPSA id f11-20020a05680807cb00b003bbcee00b2bsm1651155oij.18.2024.01.02.14.51.47 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Tue, 02 Jan 2024 14:51:47 -0800 (PST) Message-ID: Date: Tue, 2 Jan 2024 17:51:32 -0500 List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:102.0) Gecko/20100101 Thunderbird/102.11.0 Subject: Re: ZFS problems since recently ? Content-Language: en-US To: John Kennedy , Kurt Jaeger Cc: freebsd-current@freebsd.org, Alexander Leidinger References: From: Alexander Motin In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Spamd-Result: default: False [-2.20 / 15.00]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; SUBJECT_ENDS_QUESTION(1.00)[]; NEURAL_HAM_SHORT(-1.00)[-0.998]; FORGED_SENDER(0.30)[mav@FreeBSD.org,mavbsd@gmail.com]; R_SPF_ALLOW(-0.20)[+ip6:2607:f8b0:4000::/36]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20230601]; MIME_GOOD(-0.10)[text/plain]; DMARC_NA(0.00)[freebsd.org]; FROM_HAS_DN(0.00)[]; MID_RHS_MATCH_FROM(0.00)[]; RCPT_COUNT_THREE(0.00)[4]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCVD_IN_DNSWL_NONE(0.00)[2607:f8b0:4864:20::c34:from]; RCVD_VIA_SMTP_AUTH(0.00)[]; FROM_NEQ_ENVFROM(0.00)[mav@FreeBSD.org,mavbsd@gmail.com]; MLMMJ_DEST(0.00)[freebsd-current@freebsd.org]; RCVD_TLS_LAST(0.00)[]; DKIM_TRACE(0.00)[gmail.com:+]; TO_DN_SOME(0.00)[]; ARC_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; FREEMAIL_ENVFROM(0.00)[gmail.com]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US]; DWL_DNSWL_NONE(0.00)[gmail.com:dkim]; RCVD_COUNT_TWO(0.00)[2] X-Rspamd-Queue-Id: 4T4SlV6FKDz3NXY X-Spamd-Bar: -- On 01.01.2024 08:59, John Kennedy wrote: > On Mon, Jan 01, 2024 at 06:43:58AM +0100, Kurt Jaeger wrote: >> markj@ pointed me in >> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=276039 >> to >> https://github.com/openzfs/zfs/pull/15719 >> >> So it will probably be fixed sooner or later. >> >> The other ZFS crashes I've seen are still an issue. > > My poudriere build did eventually fail as well: > > ... > [05:40:24] [01] [00:17:20] Finished devel/gdb@py39 | gdb-13.2_1: Success > [05:40:24] Stopping 2 builders > panic: VERIFY(BP_GET_DEDUP(bp)) failed Please see/test: https://github.com/openzfs/zfs/pull/15732 . -- Alexander Motin From nobody Wed Jan 3 04:02:04 2024 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4T4bgt704Mz56bsx for ; Wed, 3 Jan 2024 04:04:10 +0000 (UTC) (envelope-from warlock@phouka1.phouka.net) Received: from phouka1.phouka.net (phouka1.phouka.net [107.170.196.116]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "phouka.net", Issuer "Go Daddy Secure Certificate Authority - G2" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 4T4bgt49GXz4SHW; Wed, 3 Jan 2024 04:04:10 +0000 (UTC) (envelope-from warlock@phouka1.phouka.net) Authentication-Results: mx1.freebsd.org; none Received: from phouka1.phouka.net (localhost [127.0.0.1]) by phouka1.phouka.net (8.17.1/8.17.1) with ESMTPS id 403425YY034243 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO); Tue, 2 Jan 2024 20:02:05 -0800 (PST) (envelope-from warlock@phouka1.phouka.net) Received: (from warlock@localhost) by phouka1.phouka.net (8.17.1/8.17.1/Submit) id 403425iE034242; Tue, 2 Jan 2024 20:02:05 -0800 (PST) (envelope-from warlock) Date: Tue, 2 Jan 2024 20:02:04 -0800 From: John Kennedy To: Alexander Motin Cc: Kurt Jaeger , freebsd-current@freebsd.org, Alexander Leidinger Subject: Re: ZFS problems since recently ? Message-ID: References: List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:14061, ipnet:107.170.192.0/18, country:US] X-Spamd-Bar: ---- X-Rspamd-Queue-Id: 4T4bgt49GXz4SHW On Tue, Jan 02, 2024 at 05:51:32PM -0500, Alexander Motin wrote: > On 01.01.2024 08:59, John Kennedy wrote: > > ... > > My poudriere build did eventually fail as well: > > ... > > [05:40:24] [01] [00:17:20] Finished devel/gdb@py39 | gdb-13.2_1: Success > > [05:40:24] Stopping 2 builders > > panic: VERIFY(BP_GET_DEDUP(bp)) failed > > Please see/test: https://github.com/openzfs/zfs/pull/15732 . It came back today at the end of my poudriere build. Your patch has fixed it, so far at least. From nobody Wed Jan 3 13:10:10 2024 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4T4qp24JgFz55qYM for ; Wed, 3 Jan 2024 13:10:18 +0000 (UTC) (envelope-from lexi@le-fay.org) Received: from thyme.eden.le-Fay.ORG (THYME.EDEN.LE-FAY.ORG [IPv6:2001:8b0:aab5:107::10]) by mx1.freebsd.org (Postfix) with ESMTP id 4T4qp21WvFz4FVk for ; Wed, 3 Jan 2024 13:10:18 +0000 (UTC) (envelope-from lexi@le-fay.org) Authentication-Results: mx1.freebsd.org; none Received: from iris.eden.le-Fay.ORG (IRIS.EDEN.LE-FAY.ORG [IPv6:2001:8b0:aab5:106::18]) by thyme.eden.le-Fay.ORG (Postfix) with ESMTP id 73198199; Wed, 3 Jan 2024 13:10:10 +0000 (GMT) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=le-fay.org; s=thyme; t=1704287410; bh=gxtQ5jAf5M/FxC2SdQEtch/Sbj8GLftwR6kShSd/Hic=; h=Date:From:To:Cc:Subject:References:In-Reply-To; b=QlJm70moxFTCUSeDFRkSlSS1Y3T6rXkLkmt+1f/Lk6eAniPH+rJFUr+E6Sisbctov plr90BvO11LuB2B6vztzWatPfVw2lbDb30AZotaVAHIgfhW3ILExeAuD+NhhuoU3d+ n5pcKqYfIAaipm4k4ryeC7Y1LryO+6eqxJ7AXQQU= Received: from ilythia.eden.le-fay.org (ILYTHIA.EDEN.LE-FAY.ORG [IPv6:2001:8b0:aab5:104:3::101]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (secp384r1) server-digest SHA384) (No client certificate requested) by iris.eden.le-Fay.ORG (Postfix) with ESMTPSA id 464761020A; Wed, 3 Jan 2024 13:10:10 +0000 (GMT) Date: Wed, 3 Jan 2024 13:10:10 +0000 From: Lexi Winter To: "Patrick M. Hausen" Cc: Current FreeBSD Subject: Re: bridge(4) and IPv6 broken? Message-ID: References: <91dfe3b4-11ff-435e-b8c3-b4e3c9ee81fd@rlwinm.de> <1897E648-156B-46F5-B954-67A6F8DDC6BC@hausen.com> List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="Mdo0qEarLe9tImW1" Content-Disposition: inline In-Reply-To: <1897E648-156B-46F5-B954-67A6F8DDC6BC@hausen.com> X-Rspamd-Queue-Id: 4T4qp21WvFz4FVk X-Spamd-Bar: ---- X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:20712, ipnet:2001:8b0::/32, country:GB] --Mdo0qEarLe9tImW1 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Patrick M. Hausen: > > Am 02.01.2024 um 13:56 schrieb Jan Bramkamp : > > IPv6 enabled interfaces need a link-local address for normal > > operation. Please set the auto-linklocal flag on the bridge and try > > again. >=20 > And remove the link-local address from alc0. A bridge member must not have > any layer 3 addresses configured. If you are using the standard rc.conf v= ariables > just use: > > ifconfig_alc0=3D"up" thanks both, i did try removing the lladdr from alc0 but i missed that the bridge doesn't have one by default. all working now. regards, lexi. --Mdo0qEarLe9tImW1 Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQGzBAABCAAdFiEEuwt6MaPcv/+Mo+ftDHqbqZ41x5kFAmWVXK8ACgkQDHqbqZ41 x5nhpwv9EiamtdEGtSnM3MPsrED6M6x2cmgyYd5kI7Xjx27nAj26cuDNMw7n/Itb eXQrvjdBwkgIElXKWcIU6iMoFx2SqspmAAEyhn9EjnwWTQc57ctPZ9FlNO58saGt X9uUFh1mQ/i/OfjOyM+lOEylPHLldXV8KWhUWi0yWSuN/8jfntz2/XSTj7BCOJIl /rTcPWcLKxSXRt3YBvZtsbwVl87KmW9z4cgxScfhf3RJbho3zZAKbWrPdz/WlN/N 41kl2E4iIdYTrtDQuMh86gmQhC7Wt5XNtXgXKnJASlCLeDnet39D17UVP3CKO8/P sDFCeQP8kQL74QwkgnRMXB1qPu7Nz+rxTEaW3+WWOifcLTwILICawyWkzb1CeZ6h t8iyDPUY7Egp6fA+Qjl7sg8O1tKSmzz3fOmLkqnUsqS0mRFl+RwNR6qpNGw2qjOQ YdUVkgwsZgGRz+TEHz2A/V7C+jQAgv0Ywwp/d1IwF948gzyk2GsSd/iSvCghjhAL 9MdfNdzY =kOYd -----END PGP SIGNATURE----- --Mdo0qEarLe9tImW1-- From nobody Wed Jan 3 19:13:35 2024 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4T4zsD64dqz56W6p for ; Wed, 3 Jan 2024 19:13:36 +0000 (UTC) (envelope-from jamie@catflap.org) Received: from donotpassgo.dyslexicfish.net (donotpassgo.dyslexicfish.net [IPv6:2001:19f0:7400:8808:123::1]) by mx1.freebsd.org (Postfix) with ESMTP id 4T4zsD0gLYz47vY; Wed, 3 Jan 2024 19:13:36 +0000 (UTC) (envelope-from jamie@catflap.org) Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=pass (policy=none) header.from=catflap.org; spf=pass (mx1.freebsd.org: domain of jamie@catflap.org designates 2001:19f0:7400:8808:123::1 as permitted sender) smtp.mailfrom=jamie@catflap.org X-Catflap-Envelope-From: X-Catflap-Envelope-To: freebsd-current@freebsd.org Received: from donotpassgo.dyslexicfish.net (donotpassgo.dyslexicfish.net [209.250.224.51]) by donotpassgo.dyslexicfish.net (8.14.5/8.14.5) with ESMTP id 403JDZwH028037; Wed, 3 Jan 2024 19:13:35 GMT (envelope-from jamie@donotpassgo.dyslexicfish.net) Received: (from jamie@localhost) by donotpassgo.dyslexicfish.net (8.14.5/8.14.5/Submit) id 403JDZBt028036; Wed, 3 Jan 2024 19:13:35 GMT (envelope-from jamie) From: Jamie Landeg-Jones Message-Id: <202401031913.403JDZBt028036@donotpassgo.dyslexicfish.net> Date: Wed, 03 Jan 2024 19:13:35 +0000 Organization: Dyslexic Fish To: freebsd-current@freebsd.org Cc: yuri@freebsd.org Subject: git repo port issues? User-Agent: Heirloom mailx 12.4 7/29/08 List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Greylist: Sender passed SPF test, not delayed by milter-greylist-4.2.7 (donotpassgo.dyslexicfish.net [209.250.224.51]); Wed, 03 Jan 2024 19:13:35 +0000 (GMT) X-Spamd-Bar: + X-Spamd-Result: default: False [1.24 / 15.00]; SUBJECT_ENDS_QUESTION(1.00)[]; NEURAL_SPAM_SHORT(0.94)[0.936]; DMARC_POLICY_ALLOW(-0.50)[catflap.org,none]; R_SPF_ALLOW(-0.20)[+mx:dyslexicfish.net:c]; MIME_GOOD(-0.10)[text/plain]; RCVD_NO_TLS_LAST(0.10)[]; TO_DN_NONE(0.00)[]; ASN(0.00)[asn:20473, ipnet:2001:19f0:7400::/38, country:US]; ARC_NA(0.00)[]; HAS_ORG_HEADER(0.00)[]; FREEFALL_USER(0.00)[jamie]; TO_MATCH_ENVRCPT_ALL(0.00)[]; FROM_HAS_DN(0.00)[]; R_DKIM_NA(0.00)[]; RCVD_COUNT_TWO(0.00)[2]; RCPT_COUNT_TWO(0.00)[2]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; MLMMJ_DEST(0.00)[freebsd-current@freebsd.org] X-Rspamd-Queue-Id: 4T4zsD0gLYz47vY https://cgit.freebsd.org/ports/ The latest update to "main" is : author Yuri Victorovich 2023-01-03 14:49:38 +0000 committer Yuri Victorovich 2023-01-03 14:49:38 +0000 I.e. A year old. Reading the commit message, it does appear to be a wrong clock, rather than an old message, but whilst the author date is local to the author, I thought the commit date was centralised. If nothing else, this does seem to bugger up "commits since " within git itself. Cheers, Jamie From nobody Wed Jan 3 19:18:19 2024 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4T4zyh5tdlz56WWV for ; Wed, 3 Jan 2024 19:18:20 +0000 (UTC) (envelope-from jamie@catflap.org) Received: from donotpassgo.dyslexicfish.net (donotpassgo.dyslexicfish.net [IPv6:2001:19f0:7400:8808:123::1]) by mx1.freebsd.org (Postfix) with ESMTP id 4T4zyg75djz4Dnb for ; Wed, 3 Jan 2024 19:18:19 +0000 (UTC) (envelope-from jamie@catflap.org) Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=pass (policy=none) header.from=catflap.org; spf=pass (mx1.freebsd.org: domain of jamie@catflap.org designates 2001:19f0:7400:8808:123::1 as permitted sender) smtp.mailfrom=jamie@catflap.org X-Catflap-Envelope-From: Received: from donotpassgo.dyslexicfish.net (donotpassgo.dyslexicfish.net [209.250.224.51]) by donotpassgo.dyslexicfish.net (8.14.5/8.14.5) with ESMTP id 403JIJtI028096; Wed, 3 Jan 2024 19:18:19 GMT (envelope-from jamie@donotpassgo.dyslexicfish.net) Received: (from jamie@localhost) by donotpassgo.dyslexicfish.net (8.14.5/8.14.5/Submit) id 403JIJD3028095; Wed, 3 Jan 2024 19:18:19 GMT (envelope-from jamie) From: Jamie Landeg-Jones Message-Id: <202401031918.403JIJD3028095@donotpassgo.dyslexicfish.net> Date: Wed, 03 Jan 2024 19:18:19 +0000 Organization: Dyslexic Fish To: yuri@rawbw.com, jamie@catflap.org, freebsd-current@freebsd.org Subject: Re: git repo ports issues? References: <202401031909.403J9iWe027978@donotpassgo.dyslexicfish.net> <94e30cab-dad8-4a6c-86dd-5ae7261ac12d@rawbw.com> In-Reply-To: <94e30cab-dad8-4a6c-86dd-5ae7261ac12d@rawbw.com> User-Agent: Heirloom mailx 12.4 7/29/08 List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Greylist: Sender passed SPF test, not delayed by milter-greylist-4.2.7 (donotpassgo.dyslexicfish.net [209.250.224.51]); Wed, 03 Jan 2024 19:18:19 +0000 (GMT) X-Spamd-Bar: / X-Spamd-Result: default: False [0.60 / 15.00]; SUBJECT_ENDS_QUESTION(1.00)[]; DMARC_POLICY_ALLOW(-0.50)[catflap.org,none]; NEURAL_SPAM_SHORT(0.30)[0.297]; R_SPF_ALLOW(-0.20)[+mx:dyslexicfish.net:c]; RCVD_NO_TLS_LAST(0.10)[]; MIME_GOOD(-0.10)[text/plain]; ASN(0.00)[asn:20473, ipnet:2001:19f0:7400::/38, country:US]; HAS_ORG_HEADER(0.00)[]; MIME_TRACE(0.00)[0:+]; FREEFALL_USER(0.00)[jamie]; ARC_NA(0.00)[]; MLMMJ_DEST(0.00)[freebsd-current@freebsd.org]; TO_MATCH_ENVRCPT_SOME(0.00)[]; FROM_HAS_DN(0.00)[]; R_DKIM_NA(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; TO_DN_NONE(0.00)[]; RCVD_COUNT_TWO(0.00)[2]; RCPT_COUNT_THREE(0.00)[3] X-Rspamd-Queue-Id: 4T4zyg75djz4Dnb Yuri wrote: > Hi Jamie, > > > This was a faulty script where 2023 wasn't changed to 2024. > > Thanks for the notice. Ahh, ok, I did think it was probably a bit more than coincidence that it was exactly 1 year to the day! Cheers for the quick reply, Jamie From nobody Wed Jan 3 19:22:35 2024 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4T503l09Vdz56WqC for ; Wed, 3 Jan 2024 19:22:43 +0000 (UTC) (envelope-from brooks@spindle.one-eyed-alien.net) Received: from spindle.one-eyed-alien.net (spindle.one-eyed-alien.net [199.48.129.229]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4T503k544tz4GLj; Wed, 3 Jan 2024 19:22:42 +0000 (UTC) (envelope-from brooks@spindle.one-eyed-alien.net) Authentication-Results: mx1.freebsd.org; none Received: by spindle.one-eyed-alien.net (Postfix, from userid 3001) id 48FF53C019A; Wed, 3 Jan 2024 19:22:35 +0000 (UTC) Date: Wed, 3 Jan 2024 19:22:35 +0000 From: Brooks Davis To: Jamie Landeg-Jones Cc: freebsd-current@freebsd.org, yuri@freebsd.org Subject: Re: git repo port issues? Message-ID: References: <202401031913.403JDZBt028036@donotpassgo.dyslexicfish.net> List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <202401031913.403JDZBt028036@donotpassgo.dyslexicfish.net> X-Rspamd-Queue-Id: 4T503k544tz4GLj X-Spamd-Bar: ---- X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:36236, ipnet:199.48.128.0/22, country:US] On Wed, Jan 03, 2024 at 07:13:35PM +0000, Jamie Landeg-Jones wrote: > https://cgit.freebsd.org/ports/ > > The latest update to "main" is : > > author Yuri Victorovich 2023-01-03 14:49:38 +0000 > committer Yuri Victorovich 2023-01-03 14:49:38 +0000 > > I.e. A year old. Reading the commit message, it does appear to be a wrong > clock, rather than an old message, but whilst the author date is local to > the author, I thought the commit date was centralised. > > If nothing else, this does seem to bugger up "commits since " > within git itself. Nothing about dates is centralized in git, but some server side checks could be implemented on CommitDate. IMO we should require that CommitDate be >= the previous one and less than "now". -- Brooks From nobody Wed Jan 3 22:52:04 2024 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4T54jS3lyhz56slb for ; Wed, 3 Jan 2024 22:52:12 +0000 (UTC) (envelope-from jamie@catflap.org) Received: from donotpassgo.dyslexicfish.net (donotpassgo.dyslexicfish.net [IPv6:2001:19f0:7400:8808:123::1]) by mx1.freebsd.org (Postfix) with ESMTP id 4T54jS1G4tz4gd2; Wed, 3 Jan 2024 22:52:11 +0000 (UTC) (envelope-from jamie@catflap.org) Authentication-Results: mx1.freebsd.org; none X-Catflap-Envelope-From: Received: from donotpassgo.dyslexicfish.net (donotpassgo.dyslexicfish.net [209.250.224.51]) by donotpassgo.dyslexicfish.net (8.14.5/8.14.5) with ESMTP id 403Mq4pa034511; Wed, 3 Jan 2024 22:52:04 GMT (envelope-from jamie@donotpassgo.dyslexicfish.net) Received: (from jamie@localhost) by donotpassgo.dyslexicfish.net (8.14.5/8.14.5/Submit) id 403Mq4qV034510; Wed, 3 Jan 2024 22:52:04 GMT (envelope-from jamie) From: Jamie Landeg-Jones Message-Id: <202401032252.403Mq4qV034510@donotpassgo.dyslexicfish.net> Date: Wed, 03 Jan 2024 22:52:04 +0000 Organization: Dyslexic Fish To: jamie@catflap.org, brooks@freebsd.org Cc: dvl@freebsd.org, yuri@freebsd.org, freebsd-current@freebsd.org Subject: Re: git repo port issues? References: <202401031913.403JDZBt028036@donotpassgo.dyslexicfish.net> In-Reply-To: User-Agent: Heirloom mailx 12.4 7/29/08 List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Greylist: Sender passed SPF test, not delayed by milter-greylist-4.2.7 (donotpassgo.dyslexicfish.net [209.250.224.51]); Wed, 03 Jan 2024 22:52:04 +0000 (GMT) X-Rspamd-Queue-Id: 4T54jS1G4tz4gd2 X-Spamd-Bar: ---- X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:20473, ipnet:2001:19f0:7400::/38, country:US] Brooks Davis wrote: > Nothing about dates is centralized in git, but some server side checks > could be implemented on CommitDate. IMO we should require that > CommitDate be >= the previous one and less than "now". Ah, I realised Linux doesn't like centralised dates, because of the decentralisation of git, but I thought that as we grabbed from a master repo, those commit dates would be in sync. Anyway, I think some sanity checking would be good. If nothing else, this sort of thing breaks "git log": # git log --since=2023-02-02 --format="%cd %s %cn - %cd" Wed Jan 3 17:08:58 2024 -0500 editors/cudatext: Update to 1.206.5 Jose Alonso Cardenas Marquez - Wed Jan 3 17:08:58 2024 -0500 Thu Jan 4 06:59:31 2024 +0900 net/qrcp: update to 0.11.1 Hiroki Tagato - Thu Jan 4 06:59:31 2024 +0900 Wed Jan 3 16:54:47 2024 -0500 lang/fpc-devel: Update to 3.3.1.20240103 Jose Alonso Cardenas Marquez - Wed Jan 3 16:54:47 2024 -0500 Wed Jan 3 16:54:46 2024 -0500 lang/fpc: fix stage-qa fails Jose Alonso Cardenas Marquez - Wed Jan 3 16:54:46 2024 -0500 Wed Jan 3 16:53:33 2024 -0500 sysutils/acpi_call: Check for errors from copyout() Mark Johnston - Wed Jan 3 16:53:33 2024 -0500 Wed Jan 3 15:37:13 2024 -0600 math/octave-forge-statistics-resampling: Update to 5.5.3. Stephen Montgomery-Smith - Wed Jan 3 15:37:13 2024 -0600 Wed Jan 3 23:00:58 2024 +0300 math/z3: Unbreak on i386 Gleb Popov - Wed Jan 3 23:00:58 2024 +0300 Wed Jan 3 20:52:14 2024 +0100 devel/mongo-c-driver: Use USE_GITHUB helper and always use (lib)utf8proc from ports Daniel Engberg - Wed Jan 3 20:52:14 2024 +0100 Wed Jan 3 22:26:11 2024 +0300 lang/ghc: Unbreak GHC 9.2 on AArch64, refresh bootstraps. Gleb Popov - Wed Jan 3 22:26:11 2024 +0300 Note how I specified February 2023, yet the output stops as soon as it reaches the recent entry with the rogue date. That makes the results corrupt, which may affect other things along the line. I notice the front page of Freshports doesn't even show the offending entries in the list of recent commits, for example, whilst the individual port pages shows the commits in the "wrong" order (i.e. the commits are displayed in the perceived chronalogical order) https://www.freshports.org/misc/py-laspy https://www.freshports.org/graphics/filament From nobody Wed Jan 3 23:09:15 2024 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4T555P55gXz56vrL for ; Wed, 3 Jan 2024 23:09:29 +0000 (UTC) (envelope-from bakul@iitbombay.org) Received: from mail-oi1-x234.google.com (mail-oi1-x234.google.com [IPv6:2607:f8b0:4864:20::234]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1D4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4T555P1ncRz4jY7 for ; Wed, 3 Jan 2024 23:09:28 +0000 (UTC) (envelope-from bakul@iitbombay.org) Authentication-Results: mx1.freebsd.org; none Received: by mail-oi1-x234.google.com with SMTP id 5614622812f47-3bbebe6191bso3595765b6e.3 for ; Wed, 03 Jan 2024 15:09:28 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=iitbombay-org.20230601.gappssmtp.com; s=20230601; t=1704323368; x=1704928168; darn=freebsd.org; h=to:references:message-id:content-transfer-encoding:cc:date :in-reply-to:from:subject:mime-version:from:to:cc:subject:date :message-id:reply-to; bh=mwYzG2A5+P9N7vnapNzPndu46Rzxv2sq/v89unpoaHo=; b=20DWT/f3SN2weaBl7WVTtWhJ5wPuttbJoicSp/ZHi82z4rIxjiB2PJycKfcXR32YWc z+/fpmy8ZL+A36vFgZjcG4XfXzRMSNf607IjNS8ucC3iE3L/tRCIMJGkv8930VCw+/3L uMEu8ZZhoMRN17inWRFeXcZ+3CK47CPhhcbdsixq8JKJ5S4dVfiQuM+4WGMJYwZb1Gqn erLR29qH0XRiAHrWtTqwN0okzDOl8PE70f4U15AwOd7W9UyNE3+CAMjPtDVxfn/hwgIr mx5uBcfVJU0AWCNrNsdI3yk6rUen3PYs/PwK5R+pygrdS6RqyZYULDYINig6681JMhFD XhSg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1704323368; x=1704928168; h=to:references:message-id:content-transfer-encoding:cc:date :in-reply-to:from:subject:mime-version:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=mwYzG2A5+P9N7vnapNzPndu46Rzxv2sq/v89unpoaHo=; b=pEMCZ832NuGlXRNsfic3y2CRjneQQ1a+vWGH0MR5vH6O/Q1w8DdscGRHjARMYhgFC5 LaGJ/fPOxEWF+M2H1effmZ0pFQUiw/E873DUZOv4q7MPP7ZkzRnJu6zZvovS8vcKQ31a Z1NMQzMeLKLkF/oYyRDNRZxfnUeujb8Z7sAPpv3WJ/ddrWLx9CgW1yQrJ0EvkGG4UR+m AdlKYN3vdTmJajARhAFwQ9E22GtxzNFG/QA04/ae4bVCZsDFmy7uE3WYvyb1Qc0h+BXq R+ZKsnYYvb5AKsqP28VL1tmm1xVsSu+m0LwecU+R5md5k0Wyt5logEJeObLfeGdb/gfT bOmg== X-Gm-Message-State: AOJu0YzLwRb2rNwPLC4c/hHFVrGcsJMKX/hKgTnQjuwKhek69qo4pmq/ KaVJMVm2vwxdXvvRPu0Bnkz7it021hgCsCrqevDOjGUfyw== X-Google-Smtp-Source: AGHT+IHmhs1ckaD7Ls/ffT3WiRyxInJWU/sT9bfpyTCl9C7DOPpFMgOjLg2nMJiaoqJkOTrrdb6g6g== X-Received: by 2002:a05:6808:318b:b0:3bb:d386:af61 with SMTP id cd11-20020a056808318b00b003bbd386af61mr13786495oib.107.1704323367805; Wed, 03 Jan 2024 15:09:27 -0800 (PST) Received: from smtpclient.apple (107-215-223-229.lightspeed.sntcca.sbcglobal.net. [107.215.223.229]) by smtp.gmail.com with ESMTPSA id s103-20020a25aa70000000b00dbd0d4cca6bsm11203113ybi.58.2024.01.03.15.09.26 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Wed, 03 Jan 2024 15:09:27 -0800 (PST) Content-Type: text/plain; charset=utf-8 List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3774.300.61.1.2\)) Subject: Re: git repo port issues? From: Bakul Shah In-Reply-To: Date: Wed, 3 Jan 2024 15:09:15 -0800 Cc: Jamie Landeg-Jones , FreeBSD Current , yuri@freebsd.org Content-Transfer-Encoding: quoted-printable Message-Id: <46C8698A-A004-4B5F-9107-6D9FD3685074@iitbombay.org> References: <202401031913.403JDZBt028036@donotpassgo.dyslexicfish.net> To: Brooks Davis X-Mailer: Apple Mail (2.3774.300.61.1.2) X-Rspamd-Queue-Id: 4T555P1ncRz4jY7 X-Spamd-Bar: ---- X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US] On Jan 3, 2024, at 11:22=E2=80=AFAM, Brooks Davis = wrote: >=20 > Nothing about dates is centralized in git, but some server side checks > could be implemented on CommitDate. IMO we should require that > CommitDate be >=3D the previous one and less than "now". Given that git commit objects form a DAG, I don't see how you can impose linearity.= From nobody Wed Jan 3 23:26:01 2024 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4T55SW1dTwz56xPv for ; Wed, 3 Jan 2024 23:26:03 +0000 (UTC) (envelope-from brooks@spindle.one-eyed-alien.net) Received: from spindle.one-eyed-alien.net (spindle.one-eyed-alien.net [199.48.129.229]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4T55SV6bNlz4m52; Wed, 3 Jan 2024 23:26:02 +0000 (UTC) (envelope-from brooks@spindle.one-eyed-alien.net) Authentication-Results: mx1.freebsd.org; none Received: by spindle.one-eyed-alien.net (Postfix, from userid 3001) id 862D03C019B; Wed, 3 Jan 2024 23:26:01 +0000 (UTC) Date: Wed, 3 Jan 2024 23:26:01 +0000 From: Brooks Davis To: Jamie Landeg-Jones Cc: brooks@freebsd.org, dvl@freebsd.org, yuri@freebsd.org, freebsd-current@freebsd.org Subject: Re: git repo port issues? Message-ID: References: <202401031913.403JDZBt028036@donotpassgo.dyslexicfish.net> <202401032252.403Mq4qV034510@donotpassgo.dyslexicfish.net> List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <202401032252.403Mq4qV034510@donotpassgo.dyslexicfish.net> X-Rspamd-Queue-Id: 4T55SV6bNlz4m52 X-Spamd-Bar: ---- X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:36236, ipnet:199.48.128.0/22, country:US] On Wed, Jan 03, 2024 at 10:52:04PM +0000, Jamie Landeg-Jones wrote: > Brooks Davis wrote: > > > Nothing about dates is centralized in git, but some server side checks > > could be implemented on CommitDate. IMO we should require that > > CommitDate be >= the previous one and less than "now". > > Ah, I realised Linux doesn't like centralised dates, because of the > decentralisation of git, but I thought that as we grabbed from a > master repo, those commit dates would be in sync. The dates are just strings in the commits. There's no central commit queue to rewrite the commits with new dates. The project could someday implment such a thing, but we deemed anything like that out of scope for the first phase of the migration. I do fine it quite annoying that the project has not implemented a check to monotonize CommitDate. Once upon a time clock drift between commit hosts might have been a concern, but hosts that can't stay in sync have no business committing directly. (I'd even be in favor of requiring the same for Date, effectively requiring rebase --ignore-date before each push, but there's much less concensus for that.) > Anyway, I think some sanity checking would be good. If nothing else, this > sort of thing breaks "git log": > > # git log --since=2023-02-02 --format="%cd %s %cn - %cd" > Wed Jan 3 17:08:58 2024 -0500 editors/cudatext: Update to 1.206.5 Jose Alonso Cardenas Marquez - Wed Jan 3 17:08:58 2024 -0500 > Thu Jan 4 06:59:31 2024 +0900 net/qrcp: update to 0.11.1 Hiroki Tagato - Thu Jan 4 06:59:31 2024 +0900 > Wed Jan 3 16:54:47 2024 -0500 lang/fpc-devel: Update to 3.3.1.20240103 Jose Alonso Cardenas Marquez - Wed Jan 3 16:54:47 2024 -0500 > Wed Jan 3 16:54:46 2024 -0500 lang/fpc: fix stage-qa fails Jose Alonso Cardenas Marquez - Wed Jan 3 16:54:46 2024 -0500 > Wed Jan 3 16:53:33 2024 -0500 sysutils/acpi_call: Check for errors from copyout() Mark Johnston - Wed Jan 3 16:53:33 2024 -0500 > Wed Jan 3 15:37:13 2024 -0600 math/octave-forge-statistics-resampling: Update to 5.5.3. Stephen Montgomery-Smith - Wed Jan 3 15:37:13 2024 -0600 > Wed Jan 3 23:00:58 2024 +0300 math/z3: Unbreak on i386 Gleb Popov - Wed Jan 3 23:00:58 2024 +0300 > Wed Jan 3 20:52:14 2024 +0100 devel/mongo-c-driver: Use USE_GITHUB helper and always use (lib)utf8proc from ports Daniel Engberg - Wed Jan 3 20:52:14 2024 +0100 > Wed Jan 3 22:26:11 2024 +0300 lang/ghc: Unbreak GHC 9.2 on AArch64, refresh bootstraps. Gleb Popov - Wed Jan 3 22:26:11 2024 +0300 > > Note how I specified February 2023, yet the output stops as soon as it > reaches the recent entry with the rogue date. > > That makes the results corrupt, which may affect other things along the line. > > I notice the front page of Freshports doesn't even show the offending entries > in the list of recent commits, for example, whilst the individual port pages > shows the commits in the "wrong" order (i.e. the commits are displayed in > the perceived chronalogical order) Any general git tool or workflow that depends on dates being ordered can not work completely reliably. git log has the --since-as-filter to try to work around this, but even that is questionable since the dates are just a polite fiction without some sort of server-side enforcement. It's more stable and reliable to do something commit based like git log ..HEAD -- Brooks From nobody Wed Jan 3 23:27:17 2024 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4T55V66VRJz56xBL for ; Wed, 3 Jan 2024 23:27:26 +0000 (UTC) (envelope-from steffen@sdaoden.eu) Received: from sdaoden.eu (sdaoden.eu [217.144.132.164]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4T55V64GMfz4mnF; Wed, 3 Jan 2024 23:27:26 +0000 (UTC) (envelope-from steffen@sdaoden.eu) Authentication-Results: mx1.freebsd.org; none Date: Thu, 04 Jan 2024 00:27:17 +0100 Author: Steffen Nurpmeso From: Steffen Nurpmeso To: Bakul Shah Cc: Brooks Davis , Jamie Landeg-Jones , FreeBSD Current , yuri@freebsd.org Subject: Re: git repo port issues? Message-ID: <20240103232717.CAc7Sxai@steffen%sdaoden.eu> In-Reply-To: <46C8698A-A004-4B5F-9107-6D9FD3685074@iitbombay.org> References: <202401031913.403JDZBt028036@donotpassgo.dyslexicfish.net> <46C8698A-A004-4B5F-9107-6D9FD3685074@iitbombay.org> Mail-Followup-To: Bakul Shah , Brooks Davis , Jamie Landeg-Jones , FreeBSD Current , yuri@freebsd.org User-Agent: s-nail v14.9.24-585-g9999e323b6 OpenPGP: id=EE19E1C1F2F7054F8D3954D8308964B51883A0DD; url=https://ftp.sdaoden.eu/steffen.asc; preference=signencrypt BlahBlahBlah: Any stupid boy can crush a beetle. But all the professors in the world can make no bugs. List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable X-Rspamd-Queue-Id: 4T55V64GMfz4mnF X-Spamd-Bar: ---- X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:15987, ipnet:217.144.128.0/20, country:DE] Bakul Shah wrote in <46C8698A-A004-4B5F-9107-6D9FD3685074@iitbombay.org>: |On Jan 3, 2024, at 11:22=E2=80=AFAM, Brooks Davis wr= ote: |>=20 |> Nothing about dates is centralized in git, but some server side checks |> could be implemented on CommitDate. IMO we should require that |> CommitDate be >=3D the previous one and less than "now". | |Given that git commit objects form a DAG, I don't see how you can |impose linearity. On the other hand, if a project agrees, and for example locks the main branch, any merging or plain committing to it can enforce commit-amending including date-updates etc, as well as expanding $CVS and @# SCCS format strings (i think by then this discussion came up in the past, and Warner Losh rejected such a thing, if i recall correctly ... but may not). --End of <46C8698A-A004-4B5F-9107-6D9FD3685074@iitbombay.org> --steffen | |Der Kragenbaer, The moon bear, |der holt sich munter he cheerfully and one by one |einen nach dem anderen runter wa.ks himself off |(By Robert Gernhardt) From nobody Wed Jan 3 23:32:27 2024 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4T55bv5zVzz56xyQ for ; Wed, 3 Jan 2024 23:32:27 +0000 (UTC) (envelope-from brooks@spindle.one-eyed-alien.net) Received: from spindle.one-eyed-alien.net (spindle.one-eyed-alien.net [199.48.129.229]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4T55bv5Xc5z4p4S; Wed, 3 Jan 2024 23:32:27 +0000 (UTC) (envelope-from brooks@spindle.one-eyed-alien.net) Authentication-Results: mx1.freebsd.org; none Received: by spindle.one-eyed-alien.net (Postfix, from userid 3001) id 4BBC73C019A; Wed, 3 Jan 2024 23:32:27 +0000 (UTC) Date: Wed, 3 Jan 2024 23:32:27 +0000 From: Brooks Davis To: Bakul Shah Cc: Jamie Landeg-Jones , FreeBSD Current , yuri@freebsd.org Subject: Re: git repo port issues? Message-ID: References: <202401031913.403JDZBt028036@donotpassgo.dyslexicfish.net> <46C8698A-A004-4B5F-9107-6D9FD3685074@iitbombay.org> List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <46C8698A-A004-4B5F-9107-6D9FD3685074@iitbombay.org> X-Rspamd-Queue-Id: 4T55bv5Xc5z4p4S X-Spamd-Bar: ---- X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:36236, ipnet:199.48.128.0/22, country:US] On Wed, Jan 03, 2024 at 03:09:15PM -0800, Bakul Shah wrote: > On Jan 3, 2024, at 11:22???AM, Brooks Davis wrote: > > > > Nothing about dates is centralized in git, but some server side checks > > could be implemented on CommitDate. IMO we should require that > > CommitDate be >= the previous one and less than "now". > > Given that git commit objects form a DAG, I don't see how you can > impose linearity. Check each commit in a push to ensure that its CommitDate is newer than its first parent's CommitDate (you could check them all, but as a project we're mostly linear). Seems like a pretty trivial property to enforce. -- Brooks From nobody Thu Jan 4 09:35:39 2024 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4T5M0H6wwXz56BqX for ; Thu, 4 Jan 2024 09:35:59 +0000 (UTC) (envelope-from junchoon@dec.sakura.ne.jp) Received: from www121.sakura.ne.jp (www121.sakura.ne.jp [153.125.133.21]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4T5M0H1WQbz4pG5; Thu, 4 Jan 2024 09:35:58 +0000 (UTC) (envelope-from junchoon@dec.sakura.ne.jp) Authentication-Results: mx1.freebsd.org; none Received: from kalamity.joker.local (123-1-22-158.area1b.commufa.jp [123.1.22.158]) (authenticated bits=0) by www121.sakura.ne.jp (8.17.1/8.17.1/[SAKURA-WEB]/20201212) with ESMTPA id 4049ZdVe087169; Thu, 4 Jan 2024 18:35:40 +0900 (JST) (envelope-from junchoon@dec.sakura.ne.jp) Date: Thu, 4 Jan 2024 18:35:39 +0900 From: Tomoaki AOKI To: Brooks Davis Cc: Bakul Shah , Jamie Landeg-Jones , FreeBSD Current , yuri@freebsd.org Subject: Re: git repo port issues? Message-Id: <20240104183539.cef54811b98fe53c5841edca@dec.sakura.ne.jp> In-Reply-To: References: <202401031913.403JDZBt028036@donotpassgo.dyslexicfish.net> <46C8698A-A004-4B5F-9107-6D9FD3685074@iitbombay.org> Organization: Junchoon corps X-Mailer: Sylpheed 3.7.0 (GTK+ 2.24.33; amd64-portbld-freebsd14.0) List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 4T5M0H1WQbz4pG5 X-Spamd-Bar: ---- X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:7684, ipnet:153.125.128.0/18, country:JP] On Wed, 3 Jan 2024 23:32:27 +0000 Brooks Davis wrote: > On Wed, Jan 03, 2024 at 03:09:15PM -0800, Bakul Shah wrote: > > On Jan 3, 2024, at 11:22???AM, Brooks Davis wrote: > > > > > > Nothing about dates is centralized in git, but some server side checks > > > could be implemented on CommitDate. IMO we should require that > > > CommitDate be >= the previous one and less than "now". > > > > Given that git commit objects form a DAG, I don't see how you can > > impose linearity. > > Check each commit in a push to ensure that its CommitDate is newer than > its first parent's CommitDate (you could check them all, but as a > project we're mostly linear). Seems like a pretty trivial property to > enforce. > > -- Brooks Or create database (key-value store would be sufficient) storing commit order (like r* of svn) and commit hash. I'm still not certain whether commit order or commit hash should be the "key". Possibly store hash as the key fisrt and store assigned MONOTONIC order as value, then, add the just-stored order as key and hash as value in another database would be neeed. If the database can contain 2 value for 1 key, it would be suitable for you to store the assigned time in UTC as "when it is committed to FreeBSD master repo". Just a thought. Regards. -- Tomoaki AOKI From nobody Thu Jan 4 10:40:35 2024 X-Original-To: current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4T5NRk0lDyz56K7D; Thu, 4 Jan 2024 10:41:22 +0000 (UTC) (envelope-from herbert@gojira.at) Received: from mail.bsd4all.net (mail.bsd4all.net [IPv6:2a01:4f8:13b:240c::25]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature ECDSA (P-384) client-digest SHA384) (Client CN "mail.bsd4all.net", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4T5NRh4Rzqz4wv6; Thu, 4 Jan 2024 10:41:20 +0000 (UTC) (envelope-from herbert@gojira.at) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gojira.at header.s=mail202005 header.b="Ei/qlu8/"; dmarc=none; spf=pass (mx1.freebsd.org: domain of herbert@gojira.at designates 2a01:4f8:13b:240c::25 as permitted sender) smtp.mailfrom=herbert@gojira.at Date: Thu, 04 Jan 2024 11:40:35 +0100 DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=gojira.at; s=mail202005; t=1704364871; bh=nQsBZc/f7Gu0/E8gALJixhISGbpOJC9Ka/mR6X4Hzjw=; h=Date:Message-ID:From:To:Subject:MIME-Version:Content-Type; b=Ei/qlu8/IPuOLFdjTziWhNtNRUJ0Zkm3z/WlpUzwf1pyzwyinVg1LjoYX7+eaI1Ij fHPffkAkN6Iw229DOttU+JNaZGF+i9sWlkz66k+pdmcHDrKBMjPHYaZgIHnPDSS6bM 4YGYDFNK4JwZlhwVn0cfdhkqZ6BezJWm574C1AwrsrrTgX10njIygRZSnSFx9HhAso CCW98XJyj44ZbXMb586ZCtyZ5I0uAyGUVLCtPFp76JREYxjXan3fwZJjpVVj1LerBE Aq4/+Cbk7PA93NkW1Qo7gCvj4JQWdlGxMeFy+2h2qxZu5Yl6bUdtFTR+rA6Ty3K3sl DGuRFsXu/4Rrg== Message-ID: <87o7e1s7oc.wl-herbert@gojira.at> From: "Herbert J. Skuhra" To: current@freebsd.org, net@freebsd.org Subject: Re: Request for Testing: TCP RACK In-Reply-To: <87edgo33s9.wl-herbert@gojira.at> References: <42C327BD-6CE4-43AA-A1AE-3BEC08D623DB@freebsd.org> <87pm09ykb8.wl-herbert@gojira.at> <87o7ftyhkp.wl-herbert@gojira.at> <87msvdy0v4.wl-herbert@gojira.at> <867DC224-F0B1-4C9C-8EB7-C9F7BE1C029A@freebsd.org> <87edgo33s9.wl-herbert@gojira.at> User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/29.1 Mule/6.0 List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue") Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Spamd-Bar: -- X-Spamd-Result: default: False [-2.49 / 15.00]; MID_CONTAINS_FROM(1.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_SHORT(-0.99)[-0.991]; R_DKIM_ALLOW(-0.20)[gojira.at:s=mail202005]; R_SPF_ALLOW(-0.20)[+ip6:2a01:4f8:13b:240c::25]; MIME_GOOD(-0.10)[text/plain]; FROM_HAS_DN(0.00)[]; ARC_NA(0.00)[]; ASN(0.00)[asn:24940, ipnet:2a01:4f8::/32, country:DE]; RCVD_COUNT_ZERO(0.00)[0]; RCPT_COUNT_TWO(0.00)[2]; MIME_TRACE(0.00)[0:+]; FROM_EQ_ENVFROM(0.00)[]; DMARC_NA(0.00)[gojira.at]; TO_DN_NONE(0.00)[]; MLMMJ_DEST(0.00)[current@freebsd.org,net@freebsd.org]; TO_MATCH_ENVRCPT_ALL(0.00)[]; DKIM_TRACE(0.00)[gojira.at:+] X-Rspamd-Queue-Id: 4T5NRh4Rzqz4wv6 On Fri, 17 Nov 2023 14:31:02 +0100, "Herbert J. Skuhra" wrote: >=20 > Hi, >=20 > On Fri, 17 Nov 2023 00:15:13 +0100, tuexen@freebsd.org wrote: > >=20 > > > On Nov 16, 2023, at 20:06, Herbert J. Skuhra wrot= e: > > >=20 > > > On Thu, 16 Nov 2023 19:07:29 +0100, Olivier Cochard-Labb=C3=A9 wrote: > > >>=20 > > >> On Thu, Nov 16, 2023 at 5:10=E2=80=AFPM Herbert J. Skuhra wrote: > > >>=20 > > >>>=20 > > >>> OK, I am now running GENERIC-NODEBUG + "options TCPHPTS". > > >>>=20 > > >>> After setting "sysctl net.inet.tcp.functions_default=3Drack" git no > > >>> longer works: > > >>>=20 > > >>>=20 > > >> Are you using a fresh 15 head or a specific network setup ? > > >>=20 > > >> Because I'm not able to reproduce your problem on my system: > > >>=20 > > >> $ uname -a > > >> FreeBSD bigone 15.0-CURRENT FreeBSD 15.0-CURRENT #0 > > >> main-n266452-070d9e3540e6: Thu Nov 16 17:53:15 CET 2023 > > >> root@bigone:/usr/obj/usr/src/amd64.amd64/sys/TCPHPTS > > >> amd64 > > >> $ cat /usr/src/sys/amd64/conf/TCPHPTS > > >> include GENERIC-NODEBUG > > >> ident TCPHPTS > > >> options TCPHPTS > > >> $ sysctl net.inet.tcp.functions_default > > >> net.inet.tcp.functions_default: rack > > >> $ git clone -q git@github.com:freebsd/freebsd-src.git && echo working > > >> working > > >> $ > > >=20 > > > OK, (g)it works if I disable pf. Do you use pf? > > Can you share your pf config such that I can reproduce the problem loca= lly? >=20 > 1. It even fails with a simple pf.conf: > pass in all > pass out all >=20 > 2. Fetching port distfiles also failed. >=20 > 3. If I disable rxcsum on the ethernet adapter (igb0) it works. Disabling lro also resolves the issue. Not OK: igb0: flags=3D1008843 metr= ic 0 mtu 1500 options=3D4e527bb OK: igb0: flags=3D1008843 metr= ic 0 mtu 1500 options=3D4e523bb -- Herbert From nobody Thu Jan 4 14:22:03 2024 X-Original-To: current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4T5TLp0vtkz56VN4; Thu, 4 Jan 2024 14:22:26 +0000 (UTC) (envelope-from herbert@gojira.at) Received: from mail.bsd4all.net (mail.bsd4all.net [94.130.200.20]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature ECDSA (P-384) client-digest SHA384) (Client CN "mail.bsd4all.net", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4T5TLm4tbxz4Dp9; Thu, 4 Jan 2024 14:22:24 +0000 (UTC) (envelope-from herbert@gojira.at) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gojira.at header.s=mail202005 header.b=LLScMogI; dmarc=none; spf=pass (mx1.freebsd.org: domain of herbert@gojira.at designates 94.130.200.20 as permitted sender) smtp.mailfrom=herbert@gojira.at Date: Thu, 04 Jan 2024 15:22:03 +0100 DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=gojira.at; s=mail202005; t=1704378136; bh=s22LBXQciBYHac0Wd0G56XRXa1aUi3rtEqv8zOgcAA0=; h=Date:Message-ID:From:To:Cc:Subject:MIME-Version:Content-Type; b=LLScMogIsdyLGt37kjDSwiWjLvsXFH7oVVd2Byz8sINiUjhFUd0lmLM6XT2nDvxdJ aPTZE0f9B/bXCgQgJQlTk7/y4WpawiPO+8qSCrJWae/y2XKhffOkYA4jLZoKBbvy0w GWLLYDe6TccgLluPgbN323cKULzpO7q0EhsNZOEHpQFn+FrvKUlphBb74//Q5ZBZ6E 7534QAb6DtpHxObcFWr5pVNZibl3BXtAahDXi7dU+jByH9wngG5bTTGOxuZ5awLbiv lrJjcrRGUeK5ZHNL68wBEP0alkTc4O03PAPhckBNALDnUuGhh2HxgPGETRG5LzJKNU 7hVyU7SNGUB5g== Message-ID: <87mstlrxf8.wl-herbert@gojira.at> From: "Herbert J. Skuhra" To: tuexen@fh-muenster.de Cc: current@freebsd.org, net@freebsd.org Subject: Re: Request for Testing: TCP RACK In-Reply-To: References: <42C327BD-6CE4-43AA-A1AE-3BEC08D623DB@freebsd.org> <87pm09ykb8.wl-herbert@gojira.at> <87o7ftyhkp.wl-herbert@gojira.at> <87msvdy0v4.wl-herbert@gojira.at> <867DC224-F0B1-4C9C-8EB7-C9F7BE1C029A@freebsd.org> <87edgo33s9.wl-herbert@gojira.at> <87o7e1s7oc.wl-herbert@gojira.at> User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/29.1 Mule/6.0 List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue") Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Spamd-Bar: -- X-Spamd-Result: default: False [-2.50 / 15.00]; MID_CONTAINS_FROM(1.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_SHORT(-1.00)[-0.998]; R_DKIM_ALLOW(-0.20)[gojira.at:s=mail202005]; R_SPF_ALLOW(-0.20)[+ip4:94.130.200.20]; MIME_GOOD(-0.10)[text/plain]; ARC_NA(0.00)[]; ASN(0.00)[asn:24940, ipnet:94.130.0.0/16, country:DE]; MIME_TRACE(0.00)[0:+]; FROM_HAS_DN(0.00)[]; DMARC_NA(0.00)[gojira.at]; RCPT_COUNT_THREE(0.00)[3]; FROM_EQ_ENVFROM(0.00)[]; RCVD_COUNT_ZERO(0.00)[0]; TO_DN_NONE(0.00)[]; MLMMJ_DEST(0.00)[current@freebsd.org,net@freebsd.org]; TO_MATCH_ENVRCPT_SOME(0.00)[]; DKIM_TRACE(0.00)[gojira.at:+] X-Rspamd-Queue-Id: 4T5TLm4tbxz4Dp9 On Thu, 04 Jan 2024 14:57:59 +0100, tuexen@fh-muenster.de wrote: >=20 > > On Jan 4, 2024, at 11:40, Herbert J. Skuhra wrote: > >=20 > > On Fri, 17 Nov 2023 14:31:02 +0100, "Herbert J. Skuhra" wrote: > >>=20 > >> Hi, > >>=20 > >> On Fri, 17 Nov 2023 00:15:13 +0100, tuexen@freebsd.org wrote: > >>>=20 > >>>> On Nov 16, 2023, at 20:06, Herbert J. Skuhra wro= te: > >>>>=20 > >>>> On Thu, 16 Nov 2023 19:07:29 +0100, Olivier Cochard-Labb=C3=A9 wrote: > >>>>>=20 > >>>>> On Thu, Nov 16, 2023 at 5:10=E2=80=AFPM Herbert J. Skuhra wrote: > >>>>>=20 > >>>>>>=20 > >>>>>> OK, I am now running GENERIC-NODEBUG + "options TCPHPTS". > >>>>>>=20 > >>>>>> After setting "sysctl net.inet.tcp.functions_default=3Drack" git no > >>>>>> longer works: > >>>>>>=20 > >>>>>>=20 > >>>>> Are you using a fresh 15 head or a specific network setup ? > >>>>>=20 > >>>>> Because I'm not able to reproduce your problem on my system: > >>>>>=20 > >>>>> $ uname -a > >>>>> FreeBSD bigone 15.0-CURRENT FreeBSD 15.0-CURRENT #0 > >>>>> main-n266452-070d9e3540e6: Thu Nov 16 17:53:15 CET 2023 > >>>>> root@bigone:/usr/obj/usr/src/amd64.amd64/sys/TCPHPTS > >>>>> amd64 > >>>>> $ cat /usr/src/sys/amd64/conf/TCPHPTS > >>>>> include GENERIC-NODEBUG > >>>>> ident TCPHPTS > >>>>> options TCPHPTS > >>>>> $ sysctl net.inet.tcp.functions_default > >>>>> net.inet.tcp.functions_default: rack > >>>>> $ git clone -q git@github.com:freebsd/freebsd-src.git && echo worki= ng > >>>>> working > >>>>> $ > >>>>=20 > >>>> OK, (g)it works if I disable pf. Do you use pf? > >>> Can you share your pf config such that I can reproduce the problem lo= cally? > >>=20 > >> 1. It even fails with a simple pf.conf: > >> pass in all > >> pass out all > >>=20 > >> 2. Fetching port distfiles also failed. > >>=20 > >> 3. If I disable rxcsum on the ethernet adapter (igb0) it works. > >=20 > > Disabling lro also resolves the issue. > >=20 > > Not OK: > >=20 > > igb0: flags=3D1008843 = metric 0 mtu 1500 > > options=3D4e527bb > >=20 > > OK: > >=20 > > igb0: flags=3D1008843 = metric 0 mtu 1500 > > options=3D4e523bb > What kind of NIC do you have? Can you post the output of > dmesg | grep igb0 igb0: port 0xf000-0xf01f mem 0xfc200000-0xfc27ffff= ,0xfc280000-0xfc283fff irq 28 at device 0.0 on pci3 igb0: EEPROM V3.16-0 eTrack 0x800004d6 igb0: Using 1024 TX descriptors and 1024 RX descriptors igb0: Using 4 RX queues 4 TX queues igb0: Using MSI-X interrupts with 5 vectors igb0: Ethernet address: aa:bb:cc:dd:ee:ff igb0: netmap queues/slots: TX 4/1024, RX 4/1024 igb0: link state changed to UP igb0: link state changed to DOWN igb0: link state changed to UP -- Herbert From nobody Thu Jan 4 14:20:26 2024 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4T5TM16RYFz56V4V for ; Thu, 4 Jan 2024 14:22:37 +0000 (UTC) (envelope-from warlock@phouka1.phouka.net) Received: from phouka1.phouka.net (phouka1.phouka.net [107.170.196.116]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "phouka.net", Issuer "Go Daddy Secure Certificate Authority - G2" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 4T5TM06268z4FRm; Thu, 4 Jan 2024 14:22:36 +0000 (UTC) (envelope-from warlock@phouka1.phouka.net) Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=none (mx1.freebsd.org: domain of warlock@phouka1.phouka.net has no SPF policy when checking 107.170.196.116) smtp.mailfrom=warlock@phouka1.phouka.net Received: from phouka1.phouka.net (localhost [127.0.0.1]) by phouka1.phouka.net (8.17.1/8.17.1) with ESMTPS id 404EKQPV065048 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO); Thu, 4 Jan 2024 06:20:27 -0800 (PST) (envelope-from warlock@phouka1.phouka.net) Received: (from warlock@localhost) by phouka1.phouka.net (8.17.1/8.17.1/Submit) id 404EKQ56065047; Thu, 4 Jan 2024 06:20:26 -0800 (PST) (envelope-from warlock) Date: Thu, 4 Jan 2024 06:20:26 -0800 From: John Kennedy To: Alexander Motin Cc: Kurt Jaeger , freebsd-current@freebsd.org, Alexander Leidinger Subject: Re: ZFS problems since recently ? Message-ID: References: List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Spamd-Bar: / X-Spamd-Result: default: False [-0.70 / 15.00]; AUTH_NA(1.00)[]; SUBJECT_ENDS_QUESTION(1.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-1.00)[-0.999]; NEURAL_HAM_SHORT(-0.90)[-0.897]; FORGED_SENDER(0.30)[warlock@phouka.net,warlock@phouka1.phouka.net]; MIME_GOOD(-0.10)[text/plain]; ASN(0.00)[asn:14061, ipnet:107.170.192.0/18, country:US]; MISSING_XM_UA(0.00)[]; TO_DN_SOME(0.00)[]; MIME_TRACE(0.00)[0:+]; ARC_NA(0.00)[]; R_SPF_NA(0.00)[no SPF record]; R_DKIM_NA(0.00)[]; MLMMJ_DEST(0.00)[freebsd-current@freebsd.org]; FROM_NEQ_ENVFROM(0.00)[warlock@phouka.net,warlock@phouka1.phouka.net]; FROM_HAS_DN(0.00)[]; MID_RHS_MATCH_FROMTLD(0.00)[]; RCVD_COUNT_TWO(0.00)[2]; RCVD_TLS_LAST(0.00)[]; TO_MATCH_ENVRCPT_SOME(0.00)[]; DMARC_NA(0.00)[phouka.net]; RCPT_COUNT_THREE(0.00)[4] X-Rspamd-Queue-Id: 4T5TM06268z4FRm On Tue, Jan 02, 2024 at 08:02:04PM -0800, John Kennedy wrote: > On Tue, Jan 02, 2024 at 05:51:32PM -0500, Alexander Motin wrote: > > On 01.01.2024 08:59, John Kennedy wrote: > > > ... > > > My poudriere build did eventually fail as well: > > > ... > > > [05:40:24] [01] [00:17:20] Finished devel/gdb@py39 | gdb-13.2_1: Success > > > [05:40:24] Stopping 2 builders > > > panic: VERIFY(BP_GET_DEDUP(bp)) failed > > > > Please see/test: https://github.com/openzfs/zfs/pull/15732 . > > It came back today at the end of my poudriere build. Your patch has fixed > it, so far at least. At the risk of conflating this with other ZFS issues, I beat on the VM a lot more last night without triggering any panics. My usual busy-workload is a total kernel+world rebuild (with whatever pending patches might be out), then a poudriere run (~230 or so packages). It's weird that the first (much bigger) run worked but later ones didn't (where maybe I had one port that failed to build), triggering the panic. Seemed repeatable, but don't have a feel for the exact trigger like the sysctl issue. From nobody Thu Jan 4 14:55:40 2024 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4T5V5D56GMz56Xw4 for ; Thu, 4 Jan 2024 14:55:44 +0000 (UTC) (envelope-from mavbsd@gmail.com) Received: from mail-oa1-x2d.google.com (mail-oa1-x2d.google.com [IPv6:2001:4860:4864:20::2d]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1D4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4T5V5D3R8Rz4MJY; Thu, 4 Jan 2024 14:55:44 +0000 (UTC) (envelope-from mavbsd@gmail.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-oa1-x2d.google.com with SMTP id 586e51a60fabf-204fdd685fdso395220fac.2; Thu, 04 Jan 2024 06:55:44 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1704380142; x=1704984942; darn=freebsd.org; h=content-transfer-encoding:in-reply-to:from:references:cc:to :content-language:subject:user-agent:mime-version:date:message-id :sender:from:to:cc:subject:date:message-id:reply-to; bh=8DMVkFa5SdnNG5JG1jEyKFPQM+ti4nMuuhZzHFro694=; b=P9SQM2EYAMexzFKfUq4Xh5UK6zZnU1bnthKuNqXCCOMOlQRntUBrQIMIG3uWfD6L9F RFhYf2TvrLEwIKxtDMJQhT6M1akJWuIOk0DNZJlCb+Jo1OgQ8dsVU6GALiswkhIv9yDK KDYXgKmkN6GvMlwum1J64tUX5lLnFBYGNZNvEihVv9Y8UahT40U0uo4iiC/mZ/x4U5fS UGsqNY0k2hjsoMmeATENrK7L2nNN+TarYZju0pYfqThsyUgR3r7vyfVwXPgaoVEy7zIs NX5UNaZ1quB74vINy1AKe/tBdPmFk2ZAL0UvXpUyemDYcLpVQjahYG2f3juViHO7C8PR rQRQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1704380142; x=1704984942; h=content-transfer-encoding:in-reply-to:from:references:cc:to :content-language:subject:user-agent:mime-version:date:message-id :sender:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=8DMVkFa5SdnNG5JG1jEyKFPQM+ti4nMuuhZzHFro694=; b=p55zPy2PWinMAZDUee+9W49zYw+Gyv6wkL8Ga9rdMFspAjtP/JTe5t8wUTIKISspiX FAecHvzbU1EGEv92UOBkOJb3yD+9I648RVEVLFiQ3IuF6kWAsKLS16UbdP4Zjt5r2olL JulNuDUiQ4MVPmhTKnrBYJF5dr0FAL+W2uJwzoFif9aIvn/g1847QlOtJ5tNf0lfYoFF ygeMHdhbSUPslbfaU/YsU5csPFdF1fT6CZ7vVH+MTfjmN3ysFlMOpd42aDG70UaEPzX7 KQUxf85GHhlXBTqSHatD07YUHyCfLXJ8qFMm8FtlJiIag5STElz1ljpBGgpgMBcxFa2q BFAA== X-Gm-Message-State: AOJu0YylIyR/LL1w8RR9e9PEtHMGh99dlPG6CwgvrLgYJEewtNnGFARO Dm+A08j1FpHhnZxxFyR9UCw= X-Google-Smtp-Source: AGHT+IGA1q0HKoB67AOYUT9iVzqIf2FY8JDBMR0MFfgPSSLuv17RkEzxsqSNlxm78N2zTXojuy9vbA== X-Received: by 2002:a05:6870:ff8f:b0:1fb:75c:400a with SMTP id qp15-20020a056870ff8f00b001fb075c400amr701720oab.106.1704380142387; Thu, 04 Jan 2024 06:55:42 -0800 (PST) Received: from [10.230.45.5] ([38.32.73.2]) by smtp.gmail.com with ESMTPSA id c18-20020a056830315200b006dbd51a58b8sm3817703ots.37.2024.01.04.06.55.41 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Thu, 04 Jan 2024 06:55:41 -0800 (PST) Message-ID: <67aa4991-cbcb-23f5-5234-47285861dece@FreeBSD.org> Date: Thu, 4 Jan 2024 09:55:40 -0500 List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:102.0) Gecko/20100101 Thunderbird/102.11.0 Subject: Re: ZFS problems since recently ? Content-Language: en-US To: John Kennedy Cc: Kurt Jaeger , freebsd-current@freebsd.org, Alexander Leidinger References: From: Alexander Motin In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 4T5V5D3R8Rz4MJY X-Spamd-Bar: ---- X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:15169, ipnet:2001:4860:4864::/48, country:US] John, On 04.01.2024 09:20, John Kennedy wrote: > On Tue, Jan 02, 2024 at 08:02:04PM -0800, John Kennedy wrote: >> On Tue, Jan 02, 2024 at 05:51:32PM -0500, Alexander Motin wrote: >>> On 01.01.2024 08:59, John Kennedy wrote: >>>> ... >>>> My poudriere build did eventually fail as well: >>>> ... >>>> [05:40:24] [01] [00:17:20] Finished devel/gdb@py39 | gdb-13.2_1: Success >>>> [05:40:24] Stopping 2 builders >>>> panic: VERIFY(BP_GET_DEDUP(bp)) failed >>> >>> Please see/test: https://github.com/openzfs/zfs/pull/15732 . >> >> It came back today at the end of my poudriere build. Your patch has fixed >> it, so far at least. > > At the risk of conflating this with other ZFS issues, I beat on the VM a lot > more last night without triggering any panics. My usual busy-workload is a > total kernel+world rebuild (with whatever pending patches might be out), then > a poudriere run (~230 or so packages). It's weird that the first (much bigger) > run worked but later ones didn't (where maybe I had one port that failed to > build), triggering the panic. Seemed repeatable, but don't have a feel for > the exact trigger like the sysctl issue. What is the panic you see now? It can not be the same, since the dedup assertion is no longer there. -- Alexander Motin From nobody Thu Jan 4 15:20:54 2024 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4T5Vhf6fhBz56bx6 for ; Thu, 4 Jan 2024 15:22:58 +0000 (UTC) (envelope-from warlock@phouka1.phouka.net) Received: from phouka1.phouka.net (phouka1.phouka.net [107.170.196.116]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "phouka.net", Issuer "Go Daddy Secure Certificate Authority - G2" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 4T5Vhf49lbz4QBX; Thu, 4 Jan 2024 15:22:58 +0000 (UTC) (envelope-from warlock@phouka1.phouka.net) Authentication-Results: mx1.freebsd.org; none Received: from phouka1.phouka.net (localhost [127.0.0.1]) by phouka1.phouka.net (8.17.1/8.17.1) with ESMTPS id 404FKsHM065160 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO); Thu, 4 Jan 2024 07:20:55 -0800 (PST) (envelope-from warlock@phouka1.phouka.net) Received: (from warlock@localhost) by phouka1.phouka.net (8.17.1/8.17.1/Submit) id 404FKsGb065159; Thu, 4 Jan 2024 07:20:54 -0800 (PST) (envelope-from warlock) Date: Thu, 4 Jan 2024 07:20:54 -0800 From: John Kennedy To: Alexander Motin Cc: Kurt Jaeger , freebsd-current@freebsd.org, Alexander Leidinger Subject: Re: ZFS problems since recently ? Message-ID: References: <67aa4991-cbcb-23f5-5234-47285861dece@FreeBSD.org> List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <67aa4991-cbcb-23f5-5234-47285861dece@FreeBSD.org> X-Rspamd-Queue-Id: 4T5Vhf49lbz4QBX X-Spamd-Bar: ---- X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:14061, ipnet:107.170.192.0/18, country:US] On Thu, Jan 04, 2024 at 09:55:40AM -0500, Alexander Motin wrote: > What is the panic you see now? It can not be the same, since the dedup > assertion is no longer there. Ah, not as clear as I could have been. No panics at all. I just don't how reliable my ability to CAUSE panics is. From nobody Thu Jan 4 15:25:52 2024 X-Original-To: current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4T5Vm72Dl9z56c11; Thu, 4 Jan 2024 15:25:59 +0000 (UTC) (envelope-from tuexen@freebsd.org) Received: from drew.franken.de (mail-n.franken.de [193.175.24.27]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "*.franken.de", Issuer "Sectigo RSA Domain Validation Secure Server CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4T5Vm664wNz4R2p; Thu, 4 Jan 2024 15:25:58 +0000 (UTC) (envelope-from tuexen@freebsd.org) Authentication-Results: mx1.freebsd.org; none Received: from smtpclient.apple (unknown [IPv6:2003:a:e03:d412:51e6:78d2:ac7:700a]) (Authenticated sender: micmac) by drew.franken.de (Postfix) with ESMTPSA id BCE57721E280D; Thu, 4 Jan 2024 16:25:53 +0100 (CET) Content-Type: text/plain; charset=utf-8 List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3774.300.61.1.2\)) Subject: Re: Request for Testing: TCP RACK From: tuexen@freebsd.org In-Reply-To: <87o7e1s7oc.wl-herbert@gojira.at> Date: Thu, 4 Jan 2024 16:25:52 +0100 Cc: current@freebsd.org, net@freebsd.org Content-Transfer-Encoding: quoted-printable Message-Id: <17811EF4-C0DC-4778-B5DB-0EA3FA1C171C@freebsd.org> References: <42C327BD-6CE4-43AA-A1AE-3BEC08D623DB@freebsd.org> <87pm09ykb8.wl-herbert@gojira.at> <87o7ftyhkp.wl-herbert@gojira.at> <87msvdy0v4.wl-herbert@gojira.at> <867DC224-F0B1-4C9C-8EB7-C9F7BE1C029A@freebsd.org> <87edgo33s9.wl-herbert@gojira.at> <87o7e1s7oc.wl-herbert@gojira.at> To: "Herbert J. Skuhra" X-Mailer: Apple Mail (2.3774.300.61.1.2) X-Spam-Status: No, score=-2.9 required=5.0 tests=ALL_TRUSTED,BAYES_00, T_SCC_BODY_TEXT_LINE autolearn=disabled version=3.4.1 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on mail-n.franken.de X-Rspamd-Queue-Id: 4T5Vm664wNz4R2p X-Spamd-Bar: ---- X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:680, ipnet:193.174.0.0/15, country:DE] > On Jan 4, 2024, at 11:40, Herbert J. Skuhra wrote: >=20 > On Fri, 17 Nov 2023 14:31:02 +0100, "Herbert J. Skuhra" wrote: >>=20 >> Hi, >>=20 >> On Fri, 17 Nov 2023 00:15:13 +0100, tuexen@freebsd.org wrote: >>>=20 >>>> On Nov 16, 2023, at 20:06, Herbert J. Skuhra = wrote: >>>>=20 >>>> On Thu, 16 Nov 2023 19:07:29 +0100, Olivier Cochard-Labb=C3=A9 = wrote: >>>>>=20 >>>>> On Thu, Nov 16, 2023 at 5:10=E2=80=AFPM Herbert J. Skuhra = wrote: >>>>>=20 >>>>>>=20 >>>>>> OK, I am now running GENERIC-NODEBUG + "options TCPHPTS". >>>>>>=20 >>>>>> After setting "sysctl net.inet.tcp.functions_default=3Drack" git = no >>>>>> longer works: >>>>>>=20 >>>>>>=20 >>>>> Are you using a fresh 15 head or a specific network setup ? >>>>>=20 >>>>> Because I'm not able to reproduce your problem on my system: >>>>>=20 >>>>> $ uname -a >>>>> FreeBSD bigone 15.0-CURRENT FreeBSD 15.0-CURRENT #0 >>>>> main-n266452-070d9e3540e6: Thu Nov 16 17:53:15 CET 2023 >>>>> root@bigone:/usr/obj/usr/src/amd64.amd64/sys/TCPHPTS >>>>> amd64 >>>>> $ cat /usr/src/sys/amd64/conf/TCPHPTS >>>>> include GENERIC-NODEBUG >>>>> ident TCPHPTS >>>>> options TCPHPTS >>>>> $ sysctl net.inet.tcp.functions_default >>>>> net.inet.tcp.functions_default: rack >>>>> $ git clone -q git@github.com:freebsd/freebsd-src.git && echo = working >>>>> working >>>>> $ >>>>=20 >>>> OK, (g)it works if I disable pf. Do you use pf? >>> Can you share your pf config such that I can reproduce the problem = locally? >>=20 >> 1. It even fails with a simple pf.conf: >> pass in all >> pass out all >>=20 >> 2. Fetching port distfiles also failed. >>=20 >> 3. If I disable rxcsum on the ethernet adapter (igb0) it works. >=20 > Disabling lro also resolves the issue. >=20 > Not OK: >=20 > igb0: flags=3D1008843 = metric 0 mtu 1500 > = options=3D4e527bb >=20 > OK: >=20 > igb0: flags=3D1008843 = metric 0 mtu 1500 > = options=3D4e523bb What kind of NIC do you have? Can you post the output of dmesg | grep igb0 Best regards Michael >=20 > -- > Herbert >=20 From nobody Thu Jan 4 15:28:07 2024 X-Original-To: current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4T5Vpg06rFz56cTQ; Thu, 4 Jan 2024 15:28:11 +0000 (UTC) (envelope-from tuexen@freebsd.org) Received: from drew.franken.de (mail-n.franken.de [193.175.24.27]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "*.franken.de", Issuer "Sectigo RSA Domain Validation Secure Server CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4T5Vpf5PHvz4Shb; Thu, 4 Jan 2024 15:28:10 +0000 (UTC) (envelope-from tuexen@freebsd.org) Authentication-Results: mx1.freebsd.org; none Received: from smtpclient.apple (unknown [IPv6:2003:a:e03:d412:51e6:78d2:ac7:700a]) (Authenticated sender: micmac) by drew.franken.de (Postfix) with ESMTPSA id 3747F721E280D; Thu, 4 Jan 2024 16:28:08 +0100 (CET) Content-Type: text/plain; charset=utf-8 List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3774.300.61.1.2\)) Subject: Re: Request for Testing: TCP RACK From: tuexen@freebsd.org In-Reply-To: <87mstlrxf8.wl-herbert@gojira.at> Date: Thu, 4 Jan 2024 16:28:07 +0100 Cc: current@freebsd.org, net@freebsd.org Content-Transfer-Encoding: quoted-printable Message-Id: References: <42C327BD-6CE4-43AA-A1AE-3BEC08D623DB@freebsd.org> <87pm09ykb8.wl-herbert@gojira.at> <87o7ftyhkp.wl-herbert@gojira.at> <87msvdy0v4.wl-herbert@gojira.at> <867DC224-F0B1-4C9C-8EB7-C9F7BE1C029A@freebsd.org> <87edgo33s9.wl-herbert@gojira.at> <87o7e1s7oc.wl-herbert@gojira.at> <87mstlrxf8.wl-herbert@gojira.at> To: "Herbert J. Skuhra" X-Mailer: Apple Mail (2.3774.300.61.1.2) X-Spam-Status: No, score=-2.9 required=5.0 tests=ALL_TRUSTED,BAYES_00, T_SCC_BODY_TEXT_LINE autolearn=disabled version=3.4.1 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on mail-n.franken.de X-Rspamd-Queue-Id: 4T5Vpf5PHvz4Shb X-Spamd-Bar: ---- X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:680, ipnet:193.174.0.0/15, country:DE] > On Jan 4, 2024, at 15:22, Herbert J. Skuhra wrote: >=20 > On Thu, 04 Jan 2024 14:57:59 +0100, tuexen@fh-muenster.de wrote: >>=20 >>> On Jan 4, 2024, at 11:40, Herbert J. Skuhra = wrote: >>>=20 >>> On Fri, 17 Nov 2023 14:31:02 +0100, "Herbert J. Skuhra" wrote: >>>>=20 >>>> Hi, >>>>=20 >>>> On Fri, 17 Nov 2023 00:15:13 +0100, tuexen@freebsd.org wrote: >>>>>=20 >>>>>> On Nov 16, 2023, at 20:06, Herbert J. Skuhra = wrote: >>>>>>=20 >>>>>> On Thu, 16 Nov 2023 19:07:29 +0100, Olivier Cochard-Labb=C3=A9 = wrote: >>>>>>>=20 >>>>>>> On Thu, Nov 16, 2023 at 5:10=E2=80=AFPM Herbert J. Skuhra = wrote: >>>>>>>=20 >>>>>>>>=20 >>>>>>>> OK, I am now running GENERIC-NODEBUG + "options TCPHPTS". >>>>>>>>=20 >>>>>>>> After setting "sysctl net.inet.tcp.functions_default=3Drack" = git no >>>>>>>> longer works: >>>>>>>>=20 >>>>>>>>=20 >>>>>>> Are you using a fresh 15 head or a specific network setup ? >>>>>>>=20 >>>>>>> Because I'm not able to reproduce your problem on my system: >>>>>>>=20 >>>>>>> $ uname -a >>>>>>> FreeBSD bigone 15.0-CURRENT FreeBSD 15.0-CURRENT #0 >>>>>>> main-n266452-070d9e3540e6: Thu Nov 16 17:53:15 CET 2023 >>>>>>> root@bigone:/usr/obj/usr/src/amd64.amd64/sys/TCPHPTS >>>>>>> amd64 >>>>>>> $ cat /usr/src/sys/amd64/conf/TCPHPTS >>>>>>> include GENERIC-NODEBUG >>>>>>> ident TCPHPTS >>>>>>> options TCPHPTS >>>>>>> $ sysctl net.inet.tcp.functions_default >>>>>>> net.inet.tcp.functions_default: rack >>>>>>> $ git clone -q git@github.com:freebsd/freebsd-src.git && echo = working >>>>>>> working >>>>>>> $ >>>>>>=20 >>>>>> OK, (g)it works if I disable pf. Do you use pf? >>>>> Can you share your pf config such that I can reproduce the problem = locally? >>>>=20 >>>> 1. It even fails with a simple pf.conf: >>>> pass in all >>>> pass out all >>>>=20 >>>> 2. Fetching port distfiles also failed. >>>>=20 >>>> 3. If I disable rxcsum on the ethernet adapter (igb0) it works. >>>=20 >>> Disabling lro also resolves the issue. >>>=20 >>> Not OK: >>>=20 >>> igb0: flags=3D1008843= metric 0 mtu 1500 >>> = options=3D4e527bb >>>=20 >>> OK: >>>=20 >>> igb0: flags=3D1008843= metric 0 mtu 1500 >>> = options=3D4e523bb >> What kind of NIC do you have? Can you post the output of >> dmesg | grep igb0 >=20 > igb0: port 0xf000-0xf01f mem = 0xfc200000-0xfc27ffff,0xfc280000-0xfc283fff irq 28 at device 0.0 on pci3 > igb0: EEPROM V3.16-0 eTrack 0x800004d6 > igb0: Using 1024 TX descriptors and 1024 RX descriptors > igb0: Using 4 RX queues 4 TX queues > igb0: Using MSI-X interrupts with 5 vectors > igb0: Ethernet address: aa:bb:cc:dd:ee:ff > igb0: netmap queues/slots: TX 4/1024, RX 4/1024 > igb0: link state changed to UP > igb0: link state changed to DOWN > igb0: link state changed to UP Hi Herbert, thank you very much. I'll see if I have such a NIC in one of my test = systems and will report back. Best regards Michael >=20 > -- > Herbert >=20 From nobody Thu Jan 4 17:52:03 2024 X-Original-To: current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4T5Z0v5d4Wz56s40; Thu, 4 Jan 2024 17:52:15 +0000 (UTC) (envelope-from herbert@gojira.at) Received: from mail.bsd4all.net (mail.bsd4all.net [IPv6:2a01:4f8:13b:240c::25]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature ECDSA (P-384) client-digest SHA384) (Client CN "mail.bsd4all.net", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4T5Z0s67QSz4kQ7; Thu, 4 Jan 2024 17:52:13 +0000 (UTC) (envelope-from herbert@gojira.at) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gojira.at header.s=mail202005 header.b="DdvFDiT/"; dmarc=none; spf=pass (mx1.freebsd.org: domain of herbert@gojira.at designates 2a01:4f8:13b:240c::25 as permitted sender) smtp.mailfrom=herbert@gojira.at Date: Thu, 04 Jan 2024 18:52:03 +0100 DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=gojira.at; s=mail202005; t=1704390730; bh=/nhJTs/y1ONKMMcRbpsmTQHv3IXYQqBF0w2NsdFB+ss=; h=Date:Message-ID:From:To:Subject:MIME-Version:Content-Type; b=DdvFDiT/rPD4YDiFgt2v+qh3GOg4sDpMwDRGNQt5UPl0vPuz2AJHwAfFY6yplcEK2 9km77gj8JzY2BEgQ0A20H7lNeECxJJkHROotzKuJ4RPQClvK8cZIdk7FX72kGT+sdS de49s9y+aDLo7hsmGYXdGBZbDTR8XwOYcq1OvZxNmeOsrOGVqBt1Fq4tcWVLWAd5aw 9+NZ4sjHMad5u+wxq5DeAw75htpUaaLOS6nJ5t0ljmx1/y0q80OoE1kUQ3T4RkN3x0 I0/64uRfInK14qIrxjlzDDXJKdYlDscTV8Xkj3n5QYhH7FMT2nBPo+uCn0R32Q5qhw 3+9IAAnZ2GXyw== Message-ID: <87le95rnp8.wl-herbert@gojira.at> From: "Herbert J. Skuhra" To: current@freebsd.org, net@freebsd.org Subject: Re: Request for Testing: TCP RACK In-Reply-To: <87o7e1s7oc.wl-herbert@gojira.at> References: <42C327BD-6CE4-43AA-A1AE-3BEC08D623DB@freebsd.org> <87pm09ykb8.wl-herbert@gojira.at> <87o7ftyhkp.wl-herbert@gojira.at> <87msvdy0v4.wl-herbert@gojira.at> <867DC224-F0B1-4C9C-8EB7-C9F7BE1C029A@freebsd.org> <87edgo33s9.wl-herbert@gojira.at> <87o7e1s7oc.wl-herbert@gojira.at> User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/29.1 Mule/6.0 List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue") Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Spamd-Bar: -- X-Spamd-Result: default: False [-2.50 / 15.00]; MID_CONTAINS_FROM(1.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_SHORT(-1.00)[-0.998]; R_DKIM_ALLOW(-0.20)[gojira.at:s=mail202005]; R_SPF_ALLOW(-0.20)[+ip6:2a01:4f8:13b:240c::25]; MIME_GOOD(-0.10)[text/plain]; FROM_HAS_DN(0.00)[]; ARC_NA(0.00)[]; ASN(0.00)[asn:24940, ipnet:2a01:4f8::/32, country:DE]; RCVD_COUNT_ZERO(0.00)[0]; RCPT_COUNT_TWO(0.00)[2]; MIME_TRACE(0.00)[0:+]; FROM_EQ_ENVFROM(0.00)[]; DMARC_NA(0.00)[gojira.at]; TO_DN_NONE(0.00)[]; MLMMJ_DEST(0.00)[current@freebsd.org,net@freebsd.org]; TO_MATCH_ENVRCPT_ALL(0.00)[]; DKIM_TRACE(0.00)[gojira.at:+] X-Rspamd-Queue-Id: 4T5Z0s67QSz4kQ7 On Thu, 04 Jan 2024 11:40:35 +0100, "Herbert J. Skuhra" wrote: >=20 > On Fri, 17 Nov 2023 14:31:02 +0100, "Herbert J. Skuhra" wrote: > >=20 > > Hi, > >=20 > > On Fri, 17 Nov 2023 00:15:13 +0100, tuexen@freebsd.org wrote: > > >=20 > > > > On Nov 16, 2023, at 20:06, Herbert J. Skuhra wr= ote: > > > >=20 > > > > On Thu, 16 Nov 2023 19:07:29 +0100, Olivier Cochard-Labb=C3=A9 wrot= e: > > > >>=20 > > > >> On Thu, Nov 16, 2023 at 5:10=E2=80=AFPM Herbert J. Skuhra wrote: > > > >>=20 > > > >>>=20 > > > >>> OK, I am now running GENERIC-NODEBUG + "options TCPHPTS". > > > >>>=20 > > > >>> After setting "sysctl net.inet.tcp.functions_default=3Drack" git = no > > > >>> longer works: > > > >>>=20 > > > >>>=20 > > > >> Are you using a fresh 15 head or a specific network setup ? > > > >>=20 > > > >> Because I'm not able to reproduce your problem on my system: > > > >>=20 > > > >> $ uname -a > > > >> FreeBSD bigone 15.0-CURRENT FreeBSD 15.0-CURRENT #0 > > > >> main-n266452-070d9e3540e6: Thu Nov 16 17:53:15 CET 2023 > > > >> root@bigone:/usr/obj/usr/src/amd64.amd64/sys/TCPHPTS > > > >> amd64 > > > >> $ cat /usr/src/sys/amd64/conf/TCPHPTS > > > >> include GENERIC-NODEBUG > > > >> ident TCPHPTS > > > >> options TCPHPTS > > > >> $ sysctl net.inet.tcp.functions_default > > > >> net.inet.tcp.functions_default: rack > > > >> $ git clone -q git@github.com:freebsd/freebsd-src.git && echo work= ing > > > >> working > > > >> $ > > > >=20 > > > > OK, (g)it works if I disable pf. Do you use pf? > > > Can you share your pf config such that I can reproduce the problem lo= cally? > >=20 > > 1. It even fails with a simple pf.conf: > > pass in all > > pass out all > >=20 > > 2. Fetching port distfiles also failed. > >=20 > > 3. If I disable rxcsum on the ethernet adapter (igb0) it works. >=20 > Disabling lro also resolves the issue. If I run "sysctl net.inet.tcp.rack.features.cmpack=3D0" I don't have to disable rxcsum/tcxsum or lro on igb0.=20 -- Herbert From nobody Thu Jan 4 19:10:22 2024 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4T5bl53xcsz571QJ for ; Thu, 4 Jan 2024 19:10:25 +0000 (UTC) (envelope-from jamie@catflap.org) Received: from donotpassgo.dyslexicfish.net (donotpassgo.dyslexicfish.net [IPv6:2001:19f0:7400:8808:123::1]) by mx1.freebsd.org (Postfix) with ESMTP id 4T5bl40lbBz4tyx; Thu, 4 Jan 2024 19:10:23 +0000 (UTC) (envelope-from jamie@catflap.org) Authentication-Results: mx1.freebsd.org; none X-Catflap-Envelope-From: Received: from donotpassgo.dyslexicfish.net (donotpassgo.dyslexicfish.net [209.250.224.51]) by donotpassgo.dyslexicfish.net (8.14.5/8.14.5) with ESMTP id 404JAMN9083613; Thu, 4 Jan 2024 19:10:22 GMT (envelope-from jamie@donotpassgo.dyslexicfish.net) Received: (from jamie@localhost) by donotpassgo.dyslexicfish.net (8.14.5/8.14.5/Submit) id 404JAMVE083612; Thu, 4 Jan 2024 19:10:22 GMT (envelope-from jamie) From: Jamie Landeg-Jones Message-Id: <202401041910.404JAMVE083612@donotpassgo.dyslexicfish.net> Date: Thu, 04 Jan 2024 19:10:22 +0000 Organization: Dyslexic Fish To: jamie@catflap.org, brooks@FreeBSD.org Cc: yuri@FreeBSD.org, freebsd-current@FreeBSD.org, dvl@FreeBSD.org, brooks@FreeBSD.org Subject: Re: git repo port issues? References: <202401031913.403JDZBt028036@donotpassgo.dyslexicfish.net> <202401032252.403Mq4qV034510@donotpassgo.dyslexicfish.net> In-Reply-To: User-Agent: Heirloom mailx 12.4 7/29/08 List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Greylist: Sender passed SPF test, not delayed by milter-greylist-4.2.7 (donotpassgo.dyslexicfish.net [209.250.224.51]); Thu, 04 Jan 2024 19:10:22 +0000 (GMT) X-Rspamd-Queue-Id: 4T5bl40lbBz4tyx X-Spamd-Bar: ---- X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:20473, ipnet:2001:19f0:7400::/38, country:US] Brooks Davis wrote: > The dates are just strings in the commits. There's no central commit > queue to rewrite the commits with new dates. The project could someday > implment such a thing, but we deemed anything like that out of scope for > the first phase of the migration. > > I do fine it quite annoying that the project has not implemented a check > to monotonize CommitDate. Once upon a time clock drift between commit > hosts might have been a concern, but hosts that can't stay in sync have > no business committing directly. (I'd even be in favor of requiring the same > for Date, effectively requiring rebase --ignore-date before each push, > but there's much less concensus for that.) > > > Anyway, I think some sanity checking would be good. If nothing else, this > > sort of thing breaks "git log": > > > > # git log --since=2023-02-02 --format="%cd %s %cn - %cd" > > Wed Jan 3 17:08:58 2024 -0500 editors/cudatext: Update to 1.206.5 Jose Alonso Cardenas Marquez - Wed Jan 3 17:08:58 2024 -0500 > > Thu Jan 4 06:59:31 2024 +0900 net/qrcp: update to 0.11.1 Hiroki Tagato - Thu Jan 4 06:59:31 2024 +0900 > > Wed Jan 3 16:54:47 2024 -0500 lang/fpc-devel: Update to 3.3.1.20240103 Jose Alonso Cardenas Marquez - Wed Jan 3 16:54:47 2024 -0500 > > Wed Jan 3 16:54:46 2024 -0500 lang/fpc: fix stage-qa fails Jose Alonso Cardenas Marquez - Wed Jan 3 16:54:46 2024 -0500 > > Wed Jan 3 16:53:33 2024 -0500 sysutils/acpi_call: Check for errors from copyout() Mark Johnston - Wed Jan 3 16:53:33 2024 -0500 > > Wed Jan 3 15:37:13 2024 -0600 math/octave-forge-statistics-resampling: Update to 5.5.3. Stephen Montgomery-Smith - Wed Jan 3 15:37:13 2024 -0600 > > Wed Jan 3 23:00:58 2024 +0300 math/z3: Unbreak on i386 Gleb Popov - Wed Jan 3 23:00:58 2024 +0300 > > Wed Jan 3 20:52:14 2024 +0100 devel/mongo-c-driver: Use USE_GITHUB helper and always use (lib)utf8proc from ports Daniel Engberg - Wed Jan 3 20:52:14 2024 +0100 > > Wed Jan 3 22:26:11 2024 +0300 lang/ghc: Unbreak GHC 9.2 on AArch64, refresh bootstraps. Gleb Popov - Wed Jan 3 22:26:11 2024 +0300 > > > > Note how I specified February 2023, yet the output stops as soon as it > > reaches the recent entry with the rogue date. > > > > That makes the results corrupt, which may affect other things along the line. > > > > I notice the front page of Freshports doesn't even show the offending entries > > in the list of recent commits, for example, whilst the individual port pages > > shows the commits in the "wrong" order (i.e. the commits are displayed in > > the perceived chronalogical order) > > Any general git tool or workflow that depends on dates being ordered > can not work completely reliably. git log has the --since-as-filter to > try to work around this, but even that is questionable since the dates > are just a polite fiction without some sort of server-side enforcement. > > It's more stable and reliable to do something commit based like > > git log ..HEAD > > -- Brooks > > From freebsd-current+bounces-5248-freebsd-lists=dyslexicfish.net@FreeBSD.org Wed Jan 3 23:26:23 2024 > Date: Wed, 3 Jan 2024 23:26:01 +0000 > From: Brooks Davis > To: Jamie Landeg-Jones > Cc: brooks@FreeBSD.org, dvl@FreeBSD.org, yuri@FreeBSD.org, > freebsd-current@FreeBSD.org > Subject: Re: git repo port issues? > X-Greylist: Sender passed SPF test, not delayed by milter-greylist-4.2.7 (donotpassgo.dyslexicfish.net [209.250.224.51]); Wed, 03 Jan 2024 23:26:23 +0000 (GMT) > > On Wed, Jan 03, 2024 at 10:52:04PM +0000, Jamie Landeg-Jones wrote: > > Brooks Davis wrote: > The dates are just strings in the commits. There's no central commit > queue to rewrite the commits with new dates. The project could someday > implment such a thing, but we deemed anything like that out of scope for > the first phase of the migration. Ok, thanks for the clarification. > I do fine it quite annoying that the project has not implemented a check > to monotonize CommitDate. Once upon a time clock drift between commit > hosts might have been a concern, but hosts that can't stay in sync have > no business committing directly. (I'd even be in favor of requiring the same > for Date, effectively requiring rebase --ignore-date before each push, > but there's much less concensus for that.) [ ... ] > Any general git tool or workflow that depends on dates being ordered > can not work completely reliably. git log has the --since-as-filter to > try to work around this, but even that is questionable since the dates > are just a polite fiction without some sort of server-side enforcement. I had a look at the documentation on since-as-filter - thanks, I understand the issue now. Yeah, that option isn't suitable for large repos, as the whole commit history has to be scanned, and as you say the actual values are potentially meaningless. A shame, I find update dates incredibly useful - far more than meaningless commit hashes! Anyway, seeing as the FreeBSD.org repo is the "main" repo in the FreeBSD use case, if it was me, I'd patch it to ignore the user sent commit-date, and use the local system date in its place, but obviously I don't know the use cases and requirements like you guys do. Still, I'm working on my campaign to get (at least) cgit date-aware for files :-) - https://cgit.dyslexicfish.net/ports/latest/tree/ - https://cgit.dyslexicfish.net/src/current/tree/ > git log ..HEAD Thanks for the info. It's helped me a lot in my understanding of things. Cheers, Jamie From nobody Thu Jan 4 19:14:19 2024 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4T5bqh2jlTz571Qt for ; Thu, 4 Jan 2024 19:14:24 +0000 (UTC) (envelope-from jamie@catflap.org) Received: from donotpassgo.dyslexicfish.net (donotpassgo.dyslexicfish.net [IPv6:2001:19f0:7400:8808:123::1]) by mx1.freebsd.org (Postfix) with ESMTP id 4T5bqh1YMHz3x0n; Thu, 4 Jan 2024 19:14:24 +0000 (UTC) (envelope-from jamie@catflap.org) Authentication-Results: mx1.freebsd.org; none X-Catflap-Envelope-From: Received: from donotpassgo.dyslexicfish.net (donotpassgo.dyslexicfish.net [209.250.224.51]) by donotpassgo.dyslexicfish.net (8.14.5/8.14.5) with ESMTP id 404JELll083649; Thu, 4 Jan 2024 19:14:21 GMT (envelope-from jamie@donotpassgo.dyslexicfish.net) Received: (from jamie@localhost) by donotpassgo.dyslexicfish.net (8.14.5/8.14.5/Submit) id 404JEJCm083648; Thu, 4 Jan 2024 19:14:19 GMT (envelope-from jamie) From: Jamie Landeg-Jones Message-Id: <202401041914.404JEJCm083648@donotpassgo.dyslexicfish.net> Date: Thu, 04 Jan 2024 19:14:19 +0000 Organization: Dyslexic Fish To: junchoon@dec.sakura.ne.jp, brooks@FreeBSD.org Cc: yuri@FreeBSD.org, jamie@catflap.org, freebsd-current@FreeBSD.org, bakul@iitbombay.org Subject: Re: git repo port issues? References: <202401031913.403JDZBt028036@donotpassgo.dyslexicfish.net> <46C8698A-A004-4B5F-9107-6D9FD3685074@iitbombay.org> <20240104183539.cef54811b98fe53c5841edca@dec.sakura.ne.jp> In-Reply-To: <20240104183539.cef54811b98fe53c5841edca@dec.sakura.ne.jp> User-Agent: Heirloom mailx 12.4 7/29/08 List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Greylist: Sender passed SPF test, not delayed by milter-greylist-4.2.7 (donotpassgo.dyslexicfish.net [209.250.224.51]); Thu, 04 Jan 2024 19:14:21 +0000 (GMT) X-Rspamd-Queue-Id: 4T5bqh1YMHz3x0n X-Spamd-Bar: ---- X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:20473, ipnet:2001:19f0:7400::/38, country:US] Tomoaki AOKI wrote: > > Or create database (key-value store would be sufficient) storing commit > order (like r* of svn) and commit hash. > I'm still not certain whether commit order or commit hash should be the > "key". Possibly store hash as the key fisrt and store assigned MONOTONIC > order as value, then, add the just-stored order as key and hash as > value in another database would be neeed. If the database can contain 2 > value for 1 key, it would be suitable for you to store the assigned > time in UTC as "when it is committed to FreeBSD master repo". I do miss the incrementing "r" value - it's a nice immediate way to tell which update is more recent. Actually, to me, that is more important than the date - I've attempted to base my changes on the date due to the absense of such a useful field. Actually, I think I may implement such a thing on my local cgit repo. https://cgit.dyslexicfish.net/ports/latest/tree/ https://cgit.dyslexicfish.net/src/current/tree/ Cheers, Jamie From nobody Thu Jan 4 19:49:03 2024 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4T5cby3ys4z555yf for ; Thu, 4 Jan 2024 19:49:18 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-ed1-x531.google.com (mail-ed1-x531.google.com [IPv6:2a00:1450:4864:20::531]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1D4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4T5cby26HLz42wC for ; Thu, 4 Jan 2024 19:49:18 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-ed1-x531.google.com with SMTP id 4fb4d7f45d1cf-5542a7f1f3cso1112009a12.2 for ; Thu, 04 Jan 2024 11:49:18 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20230601.gappssmtp.com; s=20230601; t=1704397755; x=1705002555; darn=freebsd.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=8PtUCy3lct6+AYYI8o+TTLrFaDQOmEu+2v6Cu7si/R4=; b=ZXLXfSNgddqGZ2YlN08qZ5Fp7w/+2zhk8iMURB+RBxlwbOK9xlSRczcl8y0ZmlXPX8 0fwgT0NIx1UhbU2MubVvmvAWa7trGxNd4VBdfkD5cF4mx5dIs+zlSjzP3zvDhAwqs2fO oeCPnE2hkP+8OnTS4OAl7s4EeO1PQ30Ox6s8xT5ChngfnJ0yxov96n5J9y3FWZE8p94z DPgBjrf6b0TXuLoIqHHyIli4S2ZFBebdY0sgMlgtOcEp94oRzy19GezpAUyvIugeSycd NthtykTN/xZfJCHAuRLEDwQVMJSN22RTbfYYGuVX+TleuMhwMoov5RE/WQypOVgpSE8h yR3A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1704397755; x=1705002555; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=8PtUCy3lct6+AYYI8o+TTLrFaDQOmEu+2v6Cu7si/R4=; b=NfOkRQ34B2wGGIwwCzihFX0AgM6EOPRG2ZTYU3Vo/QZoA6x7fXgks76FxSLqTF1M77 xCkEfnVH3NJKecd80t57Uzzd7lC22+WQVChZjiqDrRgVf01T+i4GW91uqcYsJQVEOu1d oSejpzk8U05B4AFvhl7g4hFdAe5WNnRqeI4tPXMhfkjNJRfMYGp5OdU3ioqK+6ryFvcM 3v+821u5OZ7ldhMbNUtzTz9FNg2S1f6qTW1pyWK2yaqPKGQ6nF9WBdCAdoBAguwpiO2U 8VmQsDFPO0y4gpVlR5LjM5ktnkPYPzDRuwDtJ6gdrDcZs3sALA24ehCaDMh6p+5mCBHU JjqA== X-Gm-Message-State: AOJu0Yz93UHBzG7Y6Eotjxz/KIEzlFzqHWHiuD3IWpt9IwEV/9YgaTKX RXuVUGRajRwjNFuVBM47kG/QrDeRDlD2JPX2CZUGP6oZTJGbsQ== X-Google-Smtp-Source: AGHT+IEcenbv/Q7mhjK05wtwUAoWzw+RyphZ+8eNLACWXbKg0Ac2SxCY7CeBb8vkp4qZPH2cK4pSiw5v6EGNFTR+Bng= X-Received: by 2002:a17:907:7625:b0:a28:a9a7:7b67 with SMTP id jy5-20020a170907762500b00a28a9a77b67mr435141ejc.53.1704397755266; Thu, 04 Jan 2024 11:49:15 -0800 (PST) List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 References: <202401031913.403JDZBt028036@donotpassgo.dyslexicfish.net> <46C8698A-A004-4B5F-9107-6D9FD3685074@iitbombay.org> <20240104183539.cef54811b98fe53c5841edca@dec.sakura.ne.jp> <202401041914.404JEJCm083648@donotpassgo.dyslexicfish.net> In-Reply-To: <202401041914.404JEJCm083648@donotpassgo.dyslexicfish.net> From: Warner Losh Date: Thu, 4 Jan 2024 12:49:03 -0700 Message-ID: Subject: Re: git repo port issues? To: Jamie Landeg-Jones Cc: Tomoaki AOKI , Brooks Davis , Yuri , FreeBSD Current , Bakul Shah Content-Type: multipart/alternative; boundary="000000000000c2494a060e24065b" X-Rspamd-Queue-Id: 4T5cby26HLz42wC X-Spamd-Bar: ---- X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:15169, ipnet:2a00:1450::/32, country:US] --000000000000c2494a060e24065b Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Thu, Jan 4, 2024, 12:14=E2=80=AFPM Jamie Landeg-Jones wrote: > Tomoaki AOKI wrote: > > > > > Or create database (key-value store would be sufficient) storing commit > > order (like r* of svn) and commit hash. > > I'm still not certain whether commit order or commit hash should be the > > "key". Possibly store hash as the key fisrt and store assigned MONOTONI= C > > order as value, then, add the just-stored order as key and hash as > > value in another database would be neeed. If the database can contain 2 > > value for 1 key, it would be suitable for you to store the assigned > > time in UTC as "when it is committed to FreeBSD master repo". > > I do miss the incrementing "r" value - it's a nice immediate way to > tell which update is more recent. Actually, to me, that is more important > than the date - I've attempted to base my changes on the date due to the > absense of such a useful field. > See sys/conf/newvers.sh for the 'n' value we use in uname strings. It's a linear count of commits on the first-parent branch back to the start of the repo. Also, the dates usualy are first order correct and i use them for the stats i run. Though I've also just dropped tags on the first commit of each year too... Also be advised that the pre FreeBSD 8 or so tree still has some surprising artifacts in it. Warner Actually, I think I may implement such a thing on my local cgit repo. > > https://cgit.dyslexicfish.net/ports/latest/tree/ > https://cgit.dyslexicfish.net/src/current/tree/ > > Cheers, Jamie > > --000000000000c2494a060e24065b Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable


On Thu, Jan 4, 2024, 12:14=E2=80=AFPM Jamie Landeg-Jon= es <jamie@catflap.org> wrote= :
Tomoaki AOKI <junchoon@= dec.sakura.ne.jp> wrote:

>
> Or create database (key-value store would be sufficient) storing commi= t
> order (like r* of svn) and commit hash.
> I'm still not certain whether commit order or commit hash should b= e the
> "key". Possibly store hash as the key fisrt and store assign= ed MONOTONIC
> order as value, then, add the just-stored order as key and hash as
> value in another database would be neeed. If the database can contain = 2
> value for 1 key, it would be suitable for you to store the assigned > time in UTC as "when it is committed to FreeBSD master repo"= .

I do miss the incrementing "r" value - it's a nice immediate = way to
tell which update is more recent. Actually, to me, that is more important than the date - I've attempted to base my changes on the date due to th= e
absense of such a useful field.

See sys/conf/newvers.sh for the 'n' = value we use in uname strings.=C2=A0 It's a linear count of commits on = the first-parent branch back to the start of the repo.

Also, the dates usualy are first order corre= ct and i use them for the stats i run. Though I've also just dropped ta= gs on the first commit of each year too...

Also be advised that the pre FreeBSD 8 or so tree still = has some surprising artifacts in it.

Warner

Actually, I think I may implement such a thing on my local cgit repo.

https://cgit.dyslexicfish.net/ports/lates= t/tree/
https://cgit.dyslexicfish.net/src/current/= tree/

Cheers, Jamie

--000000000000c2494a060e24065b-- From nobody Thu Jan 4 20:22:22 2024 X-Original-To: current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4T5dLB6fxgz559lj; Thu, 4 Jan 2024 20:22:26 +0000 (UTC) (envelope-from tuexen@freebsd.org) Received: from drew.franken.de (mail-n.franken.de [193.175.24.27]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "*.franken.de", Issuer "Sectigo RSA Domain Validation Secure Server CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4T5dLB4YjGz46FS; Thu, 4 Jan 2024 20:22:26 +0000 (UTC) (envelope-from tuexen@freebsd.org) Authentication-Results: mx1.freebsd.org; none Received: from smtpclient.apple (unknown [IPv6:2a02:8109:1140:c3d:b11b:2fe9:ba6c:517c]) (Authenticated sender: micmac) by drew.franken.de (Postfix) with ESMTPSA id ACF4A721E280D; Thu, 4 Jan 2024 21:22:23 +0100 (CET) Content-Type: text/plain; charset=utf-8 List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3774.300.61.1.2\)) Subject: Re: Request for Testing: TCP RACK From: tuexen@freebsd.org In-Reply-To: <87le95rnp8.wl-herbert@gojira.at> Date: Thu, 4 Jan 2024 21:22:22 +0100 Cc: current@freebsd.org, net@freebsd.org Content-Transfer-Encoding: quoted-printable Message-Id: <99432C3E-6AD0-4B1B-9E50-C455D397861B@freebsd.org> References: <42C327BD-6CE4-43AA-A1AE-3BEC08D623DB@freebsd.org> <87pm09ykb8.wl-herbert@gojira.at> <87o7ftyhkp.wl-herbert@gojira.at> <87msvdy0v4.wl-herbert@gojira.at> <867DC224-F0B1-4C9C-8EB7-C9F7BE1C029A@freebsd.org> <87edgo33s9.wl-herbert@gojira.at> <87o7e1s7oc.wl-herbert@gojira.at> <87le95rnp8.wl-herbert@gojira.at> To: "Herbert J. Skuhra" X-Mailer: Apple Mail (2.3774.300.61.1.2) X-Spam-Status: No, score=-2.9 required=5.0 tests=ALL_TRUSTED,BAYES_00, T_SCC_BODY_TEXT_LINE autolearn=disabled version=3.4.1 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on mail-n.franken.de X-Rspamd-Queue-Id: 4T5dLB4YjGz46FS X-Spamd-Bar: ---- X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:680, ipnet:193.174.0.0/15, country:DE] > On Jan 4, 2024, at 18:52, Herbert J. Skuhra wrote: >=20 > On Thu, 04 Jan 2024 11:40:35 +0100, "Herbert J. Skuhra" wrote: >>=20 >> On Fri, 17 Nov 2023 14:31:02 +0100, "Herbert J. Skuhra" wrote: >>>=20 >>> Hi, >>>=20 >>> On Fri, 17 Nov 2023 00:15:13 +0100, tuexen@freebsd.org wrote: >>>>=20 >>>>> On Nov 16, 2023, at 20:06, Herbert J. Skuhra = wrote: >>>>>=20 >>>>> On Thu, 16 Nov 2023 19:07:29 +0100, Olivier Cochard-Labb=C3=A9 = wrote: >>>>>>=20 >>>>>> On Thu, Nov 16, 2023 at 5:10=E2=80=AFPM Herbert J. Skuhra = wrote: >>>>>>=20 >>>>>>>=20 >>>>>>> OK, I am now running GENERIC-NODEBUG + "options TCPHPTS". >>>>>>>=20 >>>>>>> After setting "sysctl net.inet.tcp.functions_default=3Drack" git = no >>>>>>> longer works: >>>>>>>=20 >>>>>>>=20 >>>>>> Are you using a fresh 15 head or a specific network setup ? >>>>>>=20 >>>>>> Because I'm not able to reproduce your problem on my system: >>>>>>=20 >>>>>> $ uname -a >>>>>> FreeBSD bigone 15.0-CURRENT FreeBSD 15.0-CURRENT #0 >>>>>> main-n266452-070d9e3540e6: Thu Nov 16 17:53:15 CET 2023 >>>>>> root@bigone:/usr/obj/usr/src/amd64.amd64/sys/TCPHPTS >>>>>> amd64 >>>>>> $ cat /usr/src/sys/amd64/conf/TCPHPTS >>>>>> include GENERIC-NODEBUG >>>>>> ident TCPHPTS >>>>>> options TCPHPTS >>>>>> $ sysctl net.inet.tcp.functions_default >>>>>> net.inet.tcp.functions_default: rack >>>>>> $ git clone -q git@github.com:freebsd/freebsd-src.git && echo = working >>>>>> working >>>>>> $ >>>>>=20 >>>>> OK, (g)it works if I disable pf. Do you use pf? >>>> Can you share your pf config such that I can reproduce the problem = locally? >>>=20 >>> 1. It even fails with a simple pf.conf: >>> pass in all >>> pass out all >>>=20 >>> 2. Fetching port distfiles also failed. >>>=20 >>> 3. If I disable rxcsum on the ethernet adapter (igb0) it works. >>=20 >> Disabling lro also resolves the issue. >=20 > If I run "sysctl net.inet.tcp.rack.features.cmpack=3D0" I don't have = to > disable rxcsum/tcxsum or lro on igb0. Does the problem also goes away if you disable pf completely, but keep compressed acks enabled? Best regards Michael >=20 > -- > Herbert >=20 From nobody Thu Jan 4 20:39:37 2024 X-Original-To: current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4T5dk76hNjz55CR3; Thu, 4 Jan 2024 20:39:43 +0000 (UTC) (envelope-from herbert@gojira.at) Received: from mail.bsd4all.net (mail.bsd4all.net [94.130.200.20]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature ECDSA (P-384) client-digest SHA384) (Client CN "mail.bsd4all.net", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4T5dk71vYpz4BYg; Thu, 4 Jan 2024 20:39:43 +0000 (UTC) (envelope-from herbert@gojira.at) Authentication-Results: mx1.freebsd.org; none Date: Thu, 04 Jan 2024 21:39:37 +0100 DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=gojira.at; s=mail202005; t=1704400781; bh=07BxbbvCV4kH8HnBuc2tIKt2cWMbfCzU0s7qd0wioHI=; h=Date:Message-ID:From:To:Cc:Subject:MIME-Version:Content-Type; b=LhPmQqlQ5zS25Hl13cufbqRJm6sQA9KoO/T1o0Gm5bpjhBnI8DJ6izglbl+lEEGgW sVWBZmQUS0cYdO99OToF4bvCYxLRaxGQaEuJUxABEAbBSedOn9NSLDGmoGykDpp87k ogJVuzNC8h5MwrdHN5vB9djfnj3XH7vxrgDTvn1Az1IRNMmLYNKU4Qr8UT9dEP9rTR 6Szwfazd7VQ5mpYEYULl/U/OdG/X8ArjHyVUO86XOc6rER2LMVsNN/FpKvQAV57p1w wPMqO8NPkJ9c4pyERqS2JrCbapAJUviCHHqgzSfiUN8o6a0ha1RbwUM1Y505FeaFrn KtYhMlulBg/Og== Message-ID: <87jzoosuie.wl-herbert@gojira.at> From: "Herbert J. Skuhra" To: tuexen@freebsd.org Cc: current@freebsd.org, net@freebsd.org Subject: Re: Request for Testing: TCP RACK In-Reply-To: <99432C3E-6AD0-4B1B-9E50-C455D397861B@freebsd.org> References: <42C327BD-6CE4-43AA-A1AE-3BEC08D623DB@freebsd.org> <87pm09ykb8.wl-herbert@gojira.at> <87o7ftyhkp.wl-herbert@gojira.at> <87msvdy0v4.wl-herbert@gojira.at> <867DC224-F0B1-4C9C-8EB7-C9F7BE1C029A@freebsd.org> <87edgo33s9.wl-herbert@gojira.at> <87o7e1s7oc.wl-herbert@gojira.at> <87le95rnp8.wl-herbert@gojira.at> <99432C3E-6AD0-4B1B-9E50-C455D397861B@freebsd.org> User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/29.1 Mule/6.0 List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue") Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Rspamd-Queue-Id: 4T5dk71vYpz4BYg X-Spamd-Bar: ---- X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:24940, ipnet:94.130.0.0/16, country:DE] On Thu, 04 Jan 2024 21:22:22 +0100, tuexen@freebsd.org wrote: >=20 > > On Jan 4, 2024, at 18:52, Herbert J. Skuhra wrote: > >=20 > > On Thu, 04 Jan 2024 11:40:35 +0100, "Herbert J. Skuhra" wrote: > >>=20 > >> On Fri, 17 Nov 2023 14:31:02 +0100, "Herbert J. Skuhra" wrote: > >>>=20 > >>> Hi, > >>>=20 > >>> On Fri, 17 Nov 2023 00:15:13 +0100, tuexen@freebsd.org wrote: > >>>>=20 > >>>>> On Nov 16, 2023, at 20:06, Herbert J. Skuhra wr= ote: > >>>>>=20 > >>>>> On Thu, 16 Nov 2023 19:07:29 +0100, Olivier Cochard-Labb=C3=A9 wrot= e: > >>>>>>=20 > >>>>>> On Thu, Nov 16, 2023 at 5:10=E2=80=AFPM Herbert J. Skuhra wrote: > >>>>>>=20 > >>>>>>>=20 > >>>>>>> OK, I am now running GENERIC-NODEBUG + "options TCPHPTS". > >>>>>>>=20 > >>>>>>> After setting "sysctl net.inet.tcp.functions_default=3Drack" git = no > >>>>>>> longer works: > >>>>>>>=20 > >>>>>>>=20 > >>>>>> Are you using a fresh 15 head or a specific network setup ? > >>>>>>=20 > >>>>>> Because I'm not able to reproduce your problem on my system: > >>>>>>=20 > >>>>>> $ uname -a > >>>>>> FreeBSD bigone 15.0-CURRENT FreeBSD 15.0-CURRENT #0 > >>>>>> main-n266452-070d9e3540e6: Thu Nov 16 17:53:15 CET 2023 > >>>>>> root@bigone:/usr/obj/usr/src/amd64.amd64/sys/TCPHPTS > >>>>>> amd64 > >>>>>> $ cat /usr/src/sys/amd64/conf/TCPHPTS > >>>>>> include GENERIC-NODEBUG > >>>>>> ident TCPHPTS > >>>>>> options TCPHPTS > >>>>>> $ sysctl net.inet.tcp.functions_default > >>>>>> net.inet.tcp.functions_default: rack > >>>>>> $ git clone -q git@github.com:freebsd/freebsd-src.git && echo work= ing > >>>>>> working > >>>>>> $ > >>>>>=20 > >>>>> OK, (g)it works if I disable pf. Do you use pf? > >>>> Can you share your pf config such that I can reproduce the problem l= ocally? > >>>=20 > >>> 1. It even fails with a simple pf.conf: > >>> pass in all > >>> pass out all > >>>=20 > >>> 2. Fetching port distfiles also failed. > >>>=20 > >>> 3. If I disable rxcsum on the ethernet adapter (igb0) it works. > >>=20 > >> Disabling lro also resolves the issue. > >=20 > > If I run "sysctl net.inet.tcp.rack.features.cmpack=3D0" I don't have to > > disable rxcsum/tcxsum or lro on igb0. > Does the problem also goes away if you disable pf completely, but keep > compressed acks enabled? Yes, it works with pf disabled and compressed acks enabled. -- Herbert From nobody Fri Jan 5 06:26:17 2024 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4T5tlF55Sfz56FVP for ; Fri, 5 Jan 2024 06:26:33 +0000 (UTC) (envelope-from junchoon@dec.sakura.ne.jp) Received: from www121.sakura.ne.jp (www121.sakura.ne.jp [153.125.133.21]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4T5tlF0tchz4mkf; Fri, 5 Jan 2024 06:26:32 +0000 (UTC) (envelope-from junchoon@dec.sakura.ne.jp) Authentication-Results: mx1.freebsd.org; none Received: from kalamity.joker.local (123-1-22-158.area1b.commufa.jp [123.1.22.158]) (authenticated bits=0) by www121.sakura.ne.jp (8.17.1/8.17.1/[SAKURA-WEB]/20201212) with ESMTPA id 4056QITV049734; Fri, 5 Jan 2024 15:26:18 +0900 (JST) (envelope-from junchoon@dec.sakura.ne.jp) Date: Fri, 5 Jan 2024 15:26:17 +0900 From: Tomoaki AOKI To: Warner Losh Cc: Jamie Landeg-Jones , Brooks Davis , Yuri , FreeBSD Current , Bakul Shah Subject: Re: git repo port issues? Message-Id: <20240105152617.688ee28bfd7c1cfc383f74e3@dec.sakura.ne.jp> In-Reply-To: References: <202401031913.403JDZBt028036@donotpassgo.dyslexicfish.net> <46C8698A-A004-4B5F-9107-6D9FD3685074@iitbombay.org> <20240104183539.cef54811b98fe53c5841edca@dec.sakura.ne.jp> <202401041914.404JEJCm083648@donotpassgo.dyslexicfish.net> Organization: Junchoon corps X-Mailer: Sylpheed 3.7.0 (GTK+ 2.24.33; amd64-portbld-freebsd14.0) List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-Rspamd-Queue-Id: 4T5tlF0tchz4mkf X-Spamd-Bar: ---- X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:7684, ipnet:153.125.128.0/18, country:JP] On Thu, 4 Jan 2024 12:49:03 -0700 Warner Losh wrote: > On Thu, Jan 4, 2024, 12:14 PM Jamie Landeg-Jones wrote: > > > Tomoaki AOKI wrote: > > > > > > > > Or create database (key-value store would be sufficient) storing commit > > > order (like r* of svn) and commit hash. > > > I'm still not certain whether commit order or commit hash should be the > > > "key". Possibly store hash as the key fisrt and store assigned MONOTONIC > > > order as value, then, add the just-stored order as key and hash as > > > value in another database would be neeed. If the database can contain 2 > > > value for 1 key, it would be suitable for you to store the assigned > > > time in UTC as "when it is committed to FreeBSD master repo". > > > > I do miss the incrementing "r" value - it's a nice immediate way to > > tell which update is more recent. Actually, to me, that is more important > > than the date - I've attempted to base my changes on the date due to the > > absense of such a useful field. > > > > See sys/conf/newvers.sh for the 'n' value we use in uname strings. It's a > linear count of commits on the first-parent branch back to the start of the > repo. > > Also, the dates usualy are first order correct and i use them for the stats > i run. Though I've also just dropped tags on the first commit of each year > too... > > Also be advised that the pre FreeBSD 8 or so tree still has some surprising > artifacts in it. > > Warner What I suspect/fear is that current n* numbers are assured to same value for the same officially existing branch or not. What I want is such an assured number (order). What happenes if something lile below happened? *Accidentally commit something into local repo racking, for example, stable/14 instead of local (personal) developement branch. *Noticed before next `git pull` and revert it and commit it to correct local branch. *Pull upstream (official) updates. This case, checked-out tree would be match upstream (if no other changes are not yet done). If n* number is kept the same as upstream with situations like above, it could be VERY helpful if n* is exposed in mails automatically sent to dev-commits-* ML and somehow in cgit repo (like r* numbers for old, svn era commits). If not, what I've described in my previous post would be helpful if used for auto-post to ML and (hopefully) cgit, IMHO. Regards. > > Actually, I think I may implement such a thing on my local cgit repo. > > > > https://cgit.dyslexicfish.net/ports/latest/tree/ > > https://cgit.dyslexicfish.net/src/current/tree/ > > > > Cheers, Jamie -- Tomoaki AOKI From nobody Fri Jan 5 07:48:04 2024 X-Original-To: current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4T5wYX0DQwz56Qcl; Fri, 5 Jan 2024 07:48:16 +0000 (UTC) (envelope-from tuexen@freebsd.org) Received: from drew.franken.de (drew.ipv6.franken.de [IPv6:2001:638:a02:a001:20e:cff:fe4a:feaa]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "*.franken.de", Issuer "Sectigo RSA Domain Validation Secure Server CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4T5wYW4lB6z419Z; Fri, 5 Jan 2024 07:48:15 +0000 (UTC) (envelope-from tuexen@freebsd.org) Authentication-Results: mx1.freebsd.org; none Received: from smtpclient.apple (unknown [IPv6:2a02:8109:1140:c3d:b11b:2fe9:ba6c:517c]) (Authenticated sender: micmac) by drew.franken.de (Postfix) with ESMTPSA id 265E4721E2821; Fri, 5 Jan 2024 08:48:05 +0100 (CET) Content-Type: text/plain; charset=utf-8 List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3774.300.61.1.2\)) Subject: Re: Request for Testing: TCP RACK From: tuexen@freebsd.org In-Reply-To: <87jzoosuie.wl-herbert@gojira.at> Date: Fri, 5 Jan 2024 08:48:04 +0100 Cc: current@freebsd.org, net@freebsd.org Content-Transfer-Encoding: quoted-printable Message-Id: References: <42C327BD-6CE4-43AA-A1AE-3BEC08D623DB@freebsd.org> <87pm09ykb8.wl-herbert@gojira.at> <87o7ftyhkp.wl-herbert@gojira.at> <87msvdy0v4.wl-herbert@gojira.at> <867DC224-F0B1-4C9C-8EB7-C9F7BE1C029A@freebsd.org> <87edgo33s9.wl-herbert@gojira.at> <87o7e1s7oc.wl-herbert@gojira.at> <87le95rnp8.wl-herbert@gojira.at> <99432C3E-6AD0-4B1B-9E50-C455D397861B@freebsd.org> <87jzoosuie.wl-herbert@gojira.at> To: "Herbert J. Skuhra" X-Mailer: Apple Mail (2.3774.300.61.1.2) X-Spam-Status: No, score=-2.9 required=5.0 tests=ALL_TRUSTED,BAYES_00, T_SCC_BODY_TEXT_LINE autolearn=disabled version=3.4.1 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on mail-n.franken.de X-Rspamd-Queue-Id: 4T5wYW4lB6z419Z X-Spamd-Bar: ---- X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:680, ipnet:2001:638::/32, country:DE] > On Jan 4, 2024, at 21:39, Herbert J. Skuhra wrote: >=20 > On Thu, 04 Jan 2024 21:22:22 +0100, tuexen@freebsd.org wrote: >>=20 >>> On Jan 4, 2024, at 18:52, Herbert J. Skuhra = wrote: >>>=20 >>> On Thu, 04 Jan 2024 11:40:35 +0100, "Herbert J. Skuhra" wrote: >>>>=20 >>>> On Fri, 17 Nov 2023 14:31:02 +0100, "Herbert J. Skuhra" wrote: >>>>>=20 >>>>> Hi, >>>>>=20 >>>>> On Fri, 17 Nov 2023 00:15:13 +0100, tuexen@freebsd.org wrote: >>>>>>=20 >>>>>>> On Nov 16, 2023, at 20:06, Herbert J. Skuhra = wrote: >>>>>>>=20 >>>>>>> On Thu, 16 Nov 2023 19:07:29 +0100, Olivier Cochard-Labb=C3=A9 = wrote: >>>>>>>>=20 >>>>>>>> On Thu, Nov 16, 2023 at 5:10=E2=80=AFPM Herbert J. Skuhra = wrote: >>>>>>>>=20 >>>>>>>>>=20 >>>>>>>>> OK, I am now running GENERIC-NODEBUG + "options TCPHPTS". >>>>>>>>>=20 >>>>>>>>> After setting "sysctl net.inet.tcp.functions_default=3Drack" = git no >>>>>>>>> longer works: >>>>>>>>>=20 >>>>>>>>>=20 >>>>>>>> Are you using a fresh 15 head or a specific network setup ? >>>>>>>>=20 >>>>>>>> Because I'm not able to reproduce your problem on my system: >>>>>>>>=20 >>>>>>>> $ uname -a >>>>>>>> FreeBSD bigone 15.0-CURRENT FreeBSD 15.0-CURRENT #0 >>>>>>>> main-n266452-070d9e3540e6: Thu Nov 16 17:53:15 CET 2023 >>>>>>>> root@bigone:/usr/obj/usr/src/amd64.amd64/sys/TCPHPTS >>>>>>>> amd64 >>>>>>>> $ cat /usr/src/sys/amd64/conf/TCPHPTS >>>>>>>> include GENERIC-NODEBUG >>>>>>>> ident TCPHPTS >>>>>>>> options TCPHPTS >>>>>>>> $ sysctl net.inet.tcp.functions_default >>>>>>>> net.inet.tcp.functions_default: rack >>>>>>>> $ git clone -q git@github.com:freebsd/freebsd-src.git && echo = working >>>>>>>> working >>>>>>>> $ >>>>>>>=20 >>>>>>> OK, (g)it works if I disable pf. Do you use pf? >>>>>> Can you share your pf config such that I can reproduce the = problem locally? >>>>>=20 >>>>> 1. It even fails with a simple pf.conf: >>>>> pass in all >>>>> pass out all >>>>>=20 >>>>> 2. Fetching port distfiles also failed. >>>>>=20 >>>>> 3. If I disable rxcsum on the ethernet adapter (igb0) it works. >>>>=20 >>>> Disabling lro also resolves the issue. >>>=20 >>> If I run "sysctl net.inet.tcp.rack.features.cmpack=3D0" I don't have = to >>> disable rxcsum/tcxsum or lro on igb0. >> Does the problem also goes away if you disable pf completely, but = keep >> compressed acks enabled? >=20 > Yes, it works with pf disabled and compressed acks enabled. Thanks for the information! Best regards Michael >=20 > -- > Herbert From nobody Fri Jan 5 22:43:58 2024 X-Original-To: current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4T6JR23VS8z56F4M for ; Fri, 5 Jan 2024 22:43:58 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4T6JR229pRz4WV1 for ; Fri, 5 Jan 2024 22:43:58 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1704494638; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=Ul+lFzKlBfa7p0Lqnjw3/z6GcAgIwMXGSq+JwUAW2/g=; b=yKu/b5Hq6LTDg5e3wecs/zC2BiCfQSYN/9dmWVX/4iIBIbvZVn2cIbGzj7NAfziXJEkVEw z/miAbkJhL76eiUhGdAXfXEJRRfc3t0z87PvEzARYnQfyBXhI7l3sCtOHBcmAm+ccXujwV PqBmuQJ1LUQtAERcCKle/uhV5RJSVM8wxIntm+j1XNAxTnO8wPmw29OvSnMvGdd6Bjxxty oIIZxkPU3wni0FWHF9vTVaR2cWEInGVwJpESyhFHVS91jkUV5HuyXqaDgUjx6ul6wM7Tdb 80n6ZQRsGrcvZk44he21HQefMVx7yl4zy6JKuc8+Pm6C9tSgyN0LGChWhF15vw== ARC-Authentication-Results: i=1; mx1.freebsd.org; none ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1704494638; a=rsa-sha256; cv=none; b=r7vf+qsBKKwO1uaDrWB02Ie/aTdBYiURYvNVs42qK5oH0e9VeRuwBlToE8p+BtVV9zF3jC pS5lIXRIY23i0sCHv3YW8SbBXATfrj5aP2XLpd6SKrTCqHGzCi5ktQG/3gtpaCmvgQ4lCl wlWZn9m1LldwZCUzrkzu7Dq60B3TKQyGdqPftOrWWZkl5i6ZJOUjzE+AB5WvZVye2uwCNS rAhSqzr161VtXXbdtLNlYsbHg4F+7bwGUexg11ZsNpOtLx2SCPT6CXPZp9Hm7yQ183DSj6 yerykKTH1Hvh9ivYWcp2cHHMDbTAyv2OKo78F+FrZidbNqGpBE+KLpanwTntQA== Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2610:1c1:1:606c::50:1d]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id 4T6JR21DnQzGnx for ; Fri, 5 Jan 2024 22:43:58 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.5]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id 405Mhw6T063286 for ; Fri, 5 Jan 2024 22:43:58 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id 405MhwFS063285 for current@FreeBSD.org; Fri, 5 Jan 2024 22:43:58 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: current@FreeBSD.org Subject: [Bug 197921] scheduler: Allow non-migratable threads to bind to their current CPU Date: Fri, 05 Jan 2024 22:43:58 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: CURRENT X-Bugzilla-Keywords: needs-patch, needs-qa X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: linimon@FreeBSD.org X-Bugzilla-Status: Open X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: bugs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: flagtypes.name Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D197921 Mark Linimon changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|mfc-stable12?, | |mfc-stable11? | --- Comment #2 from Mark Linimon --- ^Triage: remove OBE flags. --=20 You are receiving this mail because: You are on the CC list for the bug.= From nobody Sat Jan 6 22:31:53 2024 X-Original-To: current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4T6w6r03RKz55g6Z for ; Sat, 6 Jan 2024 22:32:04 +0000 (UTC) (envelope-from phk@critter.freebsd.dk) Received: from phk.freebsd.dk (phk.freebsd.dk [130.225.244.222]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4T6w6q0zTsz4LRF for ; Sat, 6 Jan 2024 22:32:02 +0000 (UTC) (envelope-from phk@critter.freebsd.dk) Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=pass (mx1.freebsd.org: domain of phk@critter.freebsd.dk designates 130.225.244.222 as permitted sender) smtp.mailfrom=phk@critter.freebsd.dk Received: from critter.freebsd.dk (unknown [192.168.55.3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by phk.freebsd.dk (Postfix) with ESMTPS id 0BD3F89284 for ; Sat, 6 Jan 2024 22:31:54 +0000 (UTC) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.17.1/8.16.1) with ESMTPS id 406MVrv9002355 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO) for ; Sat, 6 Jan 2024 22:31:53 GMT (envelope-from phk@critter.freebsd.dk) Received: (from phk@localhost) by critter.freebsd.dk (8.17.1/8.16.1/Submit) id 406MVrxT002354; Sat, 6 Jan 2024 22:31:53 GMT (envelope-from phk) Message-Id: <202401062231.406MVrxT002354@critter.freebsd.dk> To: current@freebsd.org Subject: e179d973 insta-panics in nl_send_one() From: Poul-Henning Kamp List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <2352.1704580313.1@critter.freebsd.dk> Date: Sat, 06 Jan 2024 22:31:53 +0000 X-Spamd-Bar: -- X-Spamd-Result: default: False [-3.00 / 15.00]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_SHORT(-1.00)[-1.000]; FORGED_SENDER(0.30)[phk@phk.freebsd.dk,phk@critter.freebsd.dk]; R_SPF_ALLOW(-0.20)[+mx]; MIME_GOOD(-0.10)[text/plain]; MID_RHS_MATCH_FROMTLD(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; FREEFALL_USER(0.00)[phk]; ASN(0.00)[asn:1835, ipnet:130.225.0.0/16, country:EU]; MISSING_XM_UA(0.00)[]; MIME_TRACE(0.00)[0:+]; R_DKIM_NA(0.00)[]; MLMMJ_DEST(0.00)[current@freebsd.org]; DMARC_NA(0.00)[freebsd.dk]; FROM_NEQ_ENVFROM(0.00)[phk@phk.freebsd.dk,phk@critter.freebsd.dk]; FROM_HAS_DN(0.00)[]; RCVD_COUNT_THREE(0.00)[3]; TO_DN_NONE(0.00)[]; PREVIOUSLY_DELIVERED(0.00)[current@freebsd.org]; TO_MATCH_ENVRCPT_ALL(0.00)[]; RCVD_TLS_LAST(0.00)[]; ARC_NA(0.00)[] X-Rspamd-Queue-Id: 4T6w6q0zTsz4LRF With fresh current: commit e179d9739b1438ae9acb958f80a983eff7e3dce9 Author: Michael Tuexen Date: Sat Jan 6 21:31:46 2024 +0100 tcpsso: support TIME_WAIT state I get an insta-panic as soon as any network interface comes up: --- trap 0xc, rip = 0xffff...f80d97b78, rsp = 0x... nl_send_one() at nl_send_one+0x18/frame 0xf.... nl_send_group() at nl_send_group+0x1bc/frame 0xf... _nlmsg_flush() at _nlmsg_flush+0x37/frame 0xf... rtnl_handle_ifevent() + 0xa1 if_attach_internal + 0x3df I have a picture of the full panic if desired... -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. From nobody Sat Jan 6 22:34:19 2024 X-Original-To: current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4T6w9T3Gshz55gnL for ; Sat, 6 Jan 2024 22:34:21 +0000 (UTC) (envelope-from phk@critter.freebsd.dk) Received: from phk.freebsd.dk (phk.freebsd.dk [130.225.244.222]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4T6w9S5scdz4MZ9 for ; Sat, 6 Jan 2024 22:34:20 +0000 (UTC) (envelope-from phk@critter.freebsd.dk) Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=pass (mx1.freebsd.org: domain of phk@critter.freebsd.dk designates 130.225.244.222 as permitted sender) smtp.mailfrom=phk@critter.freebsd.dk Received: from critter.freebsd.dk (unknown [192.168.55.3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by phk.freebsd.dk (Postfix) with ESMTPS id 722CF89284 for ; Sat, 6 Jan 2024 22:34:19 +0000 (UTC) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.17.1/8.16.1) with ESMTPS id 406MYJnb004160 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO) for ; Sat, 6 Jan 2024 22:34:19 GMT (envelope-from phk@critter.freebsd.dk) Received: (from phk@localhost) by critter.freebsd.dk (8.17.1/8.16.1/Submit) id 406MYJ6E004159; Sat, 6 Jan 2024 22:34:19 GMT (envelope-from phk) Message-Id: <202401062234.406MYJ6E004159@critter.freebsd.dk> cc: current@freebsd.org Subject: Re: e179d973 insta-panics in nl_send_one() In-reply-to: <202401062231.406MVrxT002354@critter.freebsd.dk> From: "Poul-Henning Kamp" References: <202401062231.406MVrxT002354@critter.freebsd.dk> List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <4157.1704580459.1@critter.freebsd.dk> Date: Sat, 06 Jan 2024 22:34:19 +0000 X-Spamd-Bar: / X-Spamd-Result: default: False [-1.00 / 15.00]; MISSING_TO(2.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_SHORT(-1.00)[-1.000]; FORGED_SENDER(0.30)[phk@phk.freebsd.dk,phk@critter.freebsd.dk]; R_SPF_ALLOW(-0.20)[+mx:c]; MIME_GOOD(-0.10)[text/plain]; ARC_NA(0.00)[]; FREEFALL_USER(0.00)[phk]; ASN(0.00)[asn:1835, ipnet:130.225.0.0/16, country:EU]; MISSING_XM_UA(0.00)[]; MIME_TRACE(0.00)[0:+]; MID_RHS_MATCH_FROMTLD(0.00)[]; MLMMJ_DEST(0.00)[current@freebsd.org]; RCVD_COUNT_THREE(0.00)[3]; TO_DN_NONE(0.00)[]; FROM_NEQ_ENVFROM(0.00)[phk@phk.freebsd.dk,phk@critter.freebsd.dk]; FROM_HAS_DN(0.00)[]; R_DKIM_NA(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; RCVD_TLS_LAST(0.00)[]; PREVIOUSLY_DELIVERED(0.00)[current@freebsd.org]; DMARC_NA(0.00)[freebsd.dk]; RCPT_COUNT_ONE(0.00)[1] X-Rspamd-Queue-Id: 4T6w9S5scdz4MZ9 Addendum: I have only installed the new kernel, userland is still from dec18. (Even if that is the cause, we should not panic on bad syscall args.) Poul-Henning Kamp writes: > With fresh current: > > commit e179d9739b1438ae9acb958f80a983eff7e3dce9 > Author: Michael Tuexen > Date: Sat Jan 6 21:31:46 2024 +0100 > > tcpsso: support TIME_WAIT state > > I get an insta-panic as soon as any network interface comes up: > > --- trap 0xc, rip = 0xffff...f80d97b78, rsp = 0x... > nl_send_one() at nl_send_one+0x18/frame 0xf.... > nl_send_group() at nl_send_group+0x1bc/frame 0xf... > _nlmsg_flush() at _nlmsg_flush+0x37/frame 0xf... > rtnl_handle_ifevent() + 0xa1 > if_attach_internal + 0x3df > > I have a picture of the full panic if desired... > > -- > Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 > phk@FreeBSD.ORG | TCP/IP since RFC 956 > FreeBSD committer | BSD since 4.3-tahoe > Never attribute to malice what can adequately be explained by incompetence. > -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. From nobody Sun Jan 7 13:26:48 2024 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4T7HzJ42hjz571Cv for ; Sun, 7 Jan 2024 13:26:52 +0000 (UTC) (envelope-from void@f-m.fm) Received: from wout1-smtp.messagingengine.com (wout1-smtp.messagingengine.com [64.147.123.24]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4T7HzJ0BNMz4bqc for ; Sun, 7 Jan 2024 13:26:52 +0000 (UTC) (envelope-from void@f-m.fm) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=f-m.fm header.s=fm2 header.b=jNLRonaJ; dkim=pass header.d=messagingengine.com header.s=fm2 header.b=bCw0SXSK; dmarc=pass (policy=none) header.from=f-m.fm; spf=pass (mx1.freebsd.org: domain of void@f-m.fm designates 64.147.123.24 as permitted sender) smtp.mailfrom=void@f-m.fm Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.west.internal (Postfix) with ESMTP id 1B8853200A47 for ; Sun, 7 Jan 2024 08:26:51 -0500 (EST) Received: from mailfrontend1 ([10.202.2.162]) by compute4.internal (MEProxy); Sun, 07 Jan 2024 08:26:51 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=f-m.fm; h=cc :content-type:content-type:date:date:from:from:in-reply-to :message-id:mime-version:reply-to:subject:subject:to:to; s=fm2; t=1704634010; x=1704720410; bh=8mlpzXLCQZ8OtNiYSBFe5zpg90eEQPtO LcuhL36R0aA=; b=jNLRonaJkBa5MwRs90HQHryt7QLEQ4j+a9skzyxYeP2TXahy quzWJVTr+OPGTroegdJQYt4iyBPzQs5sGyRWOFMoAmpAJq2VLje1WxwS+oC7TUf7 xW9Jub8nGqJQbl9Ruu6S/ROuLhE45s33K+bVmIKmouWs2uzEgfW1uvBtZQBAktyf G9uFqS/TP5OLGBuPLZWfG46YtbnDOi2YQZ1/l8ki4JYlC9MNdpV2LG/NzL1nQolf u3GZpgxOc7AW0d03FBtaqxj/1jynbFM8RqsbEvv6LaUIOLDESGrF11iCm3YmLA08 JNAr1VK/cr5OMUHfSZL0f2I/giakia/XZCSohw== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-type:content-type:date:date :feedback-id:feedback-id:from:from:in-reply-to:message-id :mime-version:reply-to:subject:subject:to:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm2; t= 1704634010; x=1704720410; bh=8mlpzXLCQZ8OtNiYSBFe5zpg90eEQPtOLcu hL36R0aA=; b=bCw0SXSKr5sRtU+wGE2unlDsWwWGxUuciL3EiHerQFSyPJqVmDH xdBRFQa5znCErks82BBbHOjw45NRU8juLIgamxlnksUk5oPYjT32XgjIPJusN3nK lbq8ce00iygrUaBtQCWUFn2BJylvEjoe54aJRDcudw12Dqp8QzZzcM97LoU2svxu 1YyLNX7mNrS1/NhTQT4GSGSUx1mQSVeD8PzhKT+j5OPGUMmA5G6CpeE5TIf7F9J7 AV5OV27sIDoxU9pa7AXG+4JSAMRryGuVOTWpgI9eTZB7CnamCtmcUsPTr1MJ1DUv kFzbwYz0le1imVS7QIKD9NycxNP9fJhwIMw== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvkedrvdehfedgheefucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucenucfjughrpeffhffvuffkgggtugesthdtredttd dtvdenucfhrhhomhepvhhoihguuceovhhoihgusehfqdhmrdhfmheqnecuggftrfgrthht vghrnhepveduffeivdfffffghfegfeejfefftdeiteehteekfefhvdefgfettdeuheegff eunecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrghilhhfrhhomhepvhho ihgusehfqdhmrdhfmh X-ME-Proxy: Feedback-ID: i2541463c:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA for ; Sun, 7 Jan 2024 08:26:50 -0500 (EST) Date: Sun, 7 Jan 2024 13:26:48 +0000 From: void To: freebsd-current@freebsd.org Subject: noatime on ufs2 Message-ID: Mail-Followup-To: freebsd-current@freebsd.org List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Disposition: inline X-Spamd-Bar: --- X-Spamd-Result: default: False [-3.93 / 15.00]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_SHORT(-0.93)[-0.928]; MID_RHS_NOT_FQDN(0.50)[]; DMARC_POLICY_ALLOW(-0.50)[f-m.fm,none]; RWL_MAILSPIKE_EXCELLENT(-0.40)[64.147.123.24:from]; R_DKIM_ALLOW(-0.20)[f-m.fm:s=fm2,messagingengine.com:s=fm2]; R_SPF_ALLOW(-0.20)[+ip4:64.147.123.24:c]; MIME_GOOD(-0.10)[text/plain]; RCVD_IN_DNSWL_LOW(-0.10)[64.147.123.24:from]; FROM_HAS_DN(0.00)[]; RCVD_COUNT_THREE(0.00)[3]; RCPT_COUNT_ONE(0.00)[1]; ARC_NA(0.00)[]; RCVD_TLS_LAST(0.00)[]; FREEMAIL_FROM(0.00)[f-m.fm]; MIME_TRACE(0.00)[0:+]; TO_MATCH_ENVRCPT_ALL(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; DKIM_TRACE(0.00)[f-m.fm:+,messagingengine.com:+]; TO_DN_NONE(0.00)[]; MLMMJ_DEST(0.00)[freebsd-current@freebsd.org]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; RCVD_VIA_SMTP_AUTH(0.00)[]; MISSING_XM_UA(0.00)[]; ASN(0.00)[asn:29838, ipnet:64.147.123.0/24, country:US]; FREEMAIL_ENVFROM(0.00)[f-m.fm]; DWL_DNSWL_NONE(0.00)[messagingengine.com:dkim] X-Rspamd-Queue-Id: 4T7HzJ0BNMz4bqc Hi, Does /var/mail still need atime? I've installed a ufs2-based -current main-n267425-aa1223ac3afc on rpi4/8BG which installs into one / . If it's mounted with noatime, will it have consequences for /var/mail ? -- From nobody Sun Jan 7 14:29:33 2024 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4T7KMl6C0xz576lT for ; Sun, 7 Jan 2024 14:29:39 +0000 (UTC) (envelope-from void@f-m.fm) Received: from wout5-smtp.messagingengine.com (wout5-smtp.messagingengine.com [64.147.123.21]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4T7KMk1CFhz4ktJ for ; Sun, 7 Jan 2024 14:29:38 +0000 (UTC) (envelope-from void@f-m.fm) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=f-m.fm header.s=fm2 header.b=xv+DjJvH; dkim=pass header.d=messagingengine.com header.s=fm2 header.b=7H6D9RzZ; dmarc=pass (policy=none) header.from=f-m.fm; spf=pass (mx1.freebsd.org: domain of void@f-m.fm designates 64.147.123.21 as permitted sender) smtp.mailfrom=void@f-m.fm Received: from compute2.internal (compute2.nyi.internal [10.202.2.46]) by mailout.west.internal (Postfix) with ESMTP id 727173200A2A for ; Sun, 7 Jan 2024 09:29:36 -0500 (EST) Received: from mailfrontend2 ([10.202.2.163]) by compute2.internal (MEProxy); Sun, 07 Jan 2024 09:29:36 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=f-m.fm; h=cc :content-type:content-type:date:date:from:from:in-reply-to :message-id:mime-version:reply-to:subject:subject:to:to; s=fm2; t=1704637775; x=1704724175; bh=jHG9LudDd+ce43IywEDi+PImfCcKMECA wj8V+cxQeH8=; b=xv+DjJvH50V1AJePYcivXt5l2CYohJWg2y3BMuBsj0/zvx8H N56UZxMWYZYbmt77daVb8XBDYWdBfzYiPCRKQrWlvJleEVQKKgGyhVPADOrREYv3 EINLlrlcHkiZHuIe7gpiEh/sI4LC93kxwIOSxlEXOa9zrzDWeQBBrBNRBNpBOH61 xuteCipGjKuT0/35y9qcfObUaOdDmRulgRDmsKfPUMxQIqASJeFSylm31L0bvUe1 GBl29M2bA+sUTQmSt80dNl8kiyMHpobMir8/8MXqPkoB2NUvXt+bNSxa/Wbw4Ch1 UfynnzLTbUURIFaCTNi0dWW0+CbHN1DZVs7Hfw== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-type:content-type:date:date :feedback-id:feedback-id:from:from:in-reply-to:message-id :mime-version:reply-to:subject:subject:to:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm2; t= 1704637775; x=1704724175; bh=jHG9LudDd+ce43IywEDi+PImfCcKMECAwj8 V+cxQeH8=; b=7H6D9RzZYyRwtHNxnw5qhh2tVSBlwjAtg63K5B9W3UQGWpmJw5r Ykw3HQfqPGUO+ZhuK48dO1a+6x+CuI5i1WiNJzDxkj+s/P41xwrynUeKM+hCbLfI 4gVJEAEWcS7oodZnGNegrbyUJSBOVOgIGxGOMszhIUDgOXQ9hE64D92Uu2CmlNGy gilInyL0sHyUPHaiAkBruMEiQ/FE/mR3HKFKRAuIgSjLEmPII7qTu8166Z8W9SHP 31PBOEiFdlBgrFQ0lfGjYbT6+EzIAcipm6E9hMb5X8s2dzm2I3jr5ieEufgxfERq HZtQMBIUZQgIDw1cCpVqXYyqbUy6qic156g== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvkedrvdehgedgtdehucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucenucfjughrpeffhffvuffkgggtugesthdtredttd dtvdenucfhrhhomhepvhhoihguuceovhhoihgusehfqdhmrdhfmheqnecuggftrfgrthht vghrnhepffelvdffvdevgefhkedvvdfhudevuddvkeethfeifeekgfejffekueeiffeite fhnecuffhomhgrihhnpehhohhmvgdrrghrphgrnecuvehluhhsthgvrhfuihiivgeptden ucfrrghrrghmpehmrghilhhfrhhomhepvhhoihgusehfqdhmrdhfmh X-ME-Proxy: Feedback-ID: i2541463c:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA for ; Sun, 7 Jan 2024 09:29:35 -0500 (EST) Date: Sun, 7 Jan 2024 14:29:33 +0000 From: void To: freebsd-current@freebsd.org Subject: route ipv6 errors on bootup in -current main-n267425-aa1223ac3afc on arm64 Message-ID: Mail-Followup-To: freebsd-current@freebsd.org List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Disposition: inline X-Spamd-Bar: --- X-Spamd-Result: default: False [-3.99 / 15.00]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_SHORT(-0.99)[-0.987]; MID_RHS_NOT_FQDN(0.50)[]; DMARC_POLICY_ALLOW(-0.50)[f-m.fm,none]; RWL_MAILSPIKE_EXCELLENT(-0.40)[64.147.123.21:from]; R_DKIM_ALLOW(-0.20)[f-m.fm:s=fm2,messagingengine.com:s=fm2]; R_SPF_ALLOW(-0.20)[+ip4:64.147.123.21]; MIME_GOOD(-0.10)[text/plain]; RCVD_IN_DNSWL_LOW(-0.10)[64.147.123.21:from]; FROM_HAS_DN(0.00)[]; RCVD_COUNT_THREE(0.00)[3]; ARC_NA(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; RCVD_TLS_LAST(0.00)[]; FREEMAIL_FROM(0.00)[f-m.fm]; MIME_TRACE(0.00)[0:+]; TO_MATCH_ENVRCPT_ALL(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; DKIM_TRACE(0.00)[f-m.fm:+,messagingengine.com:+]; TO_DN_NONE(0.00)[]; MLMMJ_DEST(0.00)[freebsd-current@freebsd.org]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; RCVD_VIA_SMTP_AUTH(0.00)[]; MISSING_XM_UA(0.00)[]; ASN(0.00)[asn:29838, ipnet:64.147.123.0/24, country:US]; FREEMAIL_ENVFROM(0.00)[f-m.fm]; DWL_DNSWL_NONE(0.00)[messagingengine.com:dkim] X-Rspamd-Queue-Id: 4T7KMk1CFhz4ktJ Hi, on a rpi4/8GB, my rc.conf looks like so. It's an ipv4-only system on a LAN not directly connected to the internet hostname="generic.home.arpa" ifconfig_genet0="inet 192.168.1.199 netmask 255.255.255.0" defaultrouter="192.168.1.1" sshd_enable="YES" sendmail_enable="NONE" sendmail_submit_enable="NO" sendmail_outbound_enable="NO" sendmail_msp_queue_enable="NO" growfs_enable="YES" # Set dumpdev to "AUTO" to enable crash dumps, "NO" to disable dumpdev="AUTO" ntpd_enable="YES" ntpdate_enable="YES" when it boots, the following appears in the serial console ### Starting devd. Autoloading module: uhid Autoloading module: usbhid Autoloading module: wmt route: message indicates error: File exists add host 127.0.0.1: gateway lo0 fib 0: route already in table add net default: gateway 192.168.1.1 route: bad keyword: inet6 route: usage: route [-j jail] [-46dnqtv] command [[modifiers] args] route: bad keyword: inet6 route: usage: route [-j jail] [-46dnqtv] command [[modifiers] args] route: bad keyword: inet6 route: usage: route [-j jail] [-46dnqtv] command [[modifiers] args] route: bad keyword: inet6 route: usage: route [-j jail] [-46dnqtv] command [[modifiers] args] route: bad keyword: inet6 route: usage: route [-j jail] [-46dnqtv] command [[modifiers] args] Updating motd:. Creating and/or trimming log files. ### Why is it erroring for ipv6 when theres no ipv6 in rc.conf? I've not tried an amd64 -current system yet. -- From nobody Sun Jan 7 17:50:30 2024 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4T7PrD71zkz55XYl for ; Sun, 7 Jan 2024 17:51:08 +0000 (UTC) (envelope-from freebsd@walstatt-de.de) Received: from smtp052.goneo.de (smtp052.goneo.de [85.220.129.60]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4T7PrC5kY4z4NBc for ; Sun, 7 Jan 2024 17:51:07 +0000 (UTC) (envelope-from freebsd@walstatt-de.de) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=walstatt-de.de header.s=DKIM001 header.b=g4KvurCt; dmarc=none; spf=none (mx1.freebsd.org: domain of freebsd@walstatt-de.de has no SPF policy when checking 85.220.129.60) smtp.mailfrom=freebsd@walstatt-de.de Received: from hub2.goneo.de (hub2.goneo.de [85.220.129.53]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits)) (No client certificate requested) by smtp5.goneo.de (Postfix) with ESMTPS id A1D7A240861 for ; Sun, 7 Jan 2024 18:50:59 +0100 (CET) Received: from hub2.goneo.de (localhost [127.0.0.1]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits)) (No client certificate requested) by hub2.goneo.de (Postfix) with ESMTPS id 1242624064C for ; Sun, 7 Jan 2024 18:50:58 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=walstatt-de.de; s=DKIM001; t=1704649858; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding; bh=Pclf/gBhhivNNlrmoftPuKPjjcKUoUZG2j53Qh/MGTI=; b=g4KvurCt9Oe3sCKyJyc7sZU4UP5q+nlWILLinpjILqY/3EwdCJ25yvn1XO1q78Lpzl8E9h 9NVUgNEV4/BRPWAP5tj30rR8uQ23O5NicDrAQDe469+CMwwr1tEAUqDTDlNqM9efAWb4SU kgAXdppbvOGlGP1fEdOBKpbFi1SzxsikePE9vZ9XAZKeIR3QVbqmqGXS/TqToX+lZu07rm zrD1fdokdR160kvoKKKvRzmZsW7N7eWu6yjyADIgpTkYP/jiNfLktAER4bABZYGL/isq5K uRiG5/51htRkFoXX3kiBmzPLiaXre21uZ+XUl5S0Ufh0Qqif3nG/xxY7x5TRbQ== Received: from thor.intern.walstatt.dynvpn.de (dynamic-077-011-063-204.77.11.pool.telefonica.de [77.11.63.204]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (prime256v1) server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by hub2.goneo.de (Postfix) with ESMTPSA id DA00A240627 for ; Sun, 7 Jan 2024 18:50:57 +0100 (CET) Date: Sun, 7 Jan 2024 18:50:30 +0100 From: FreeBSD User To: FreeBSD CURRENT Subject: IPFW/IPv6 problem with JAIL: JAIL cannot ping -6 host until host first pings jail (ipv6) Message-ID: <20240107185057.73c66433@thor.intern.walstatt.dynvpn.de> Organization: walstatt-de.de List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Rspamd-UID: e66f79 X-Rspamd-UID: f80905 X-Spamd-Bar: --- X-Spamd-Result: default: False [-3.30 / 15.00]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_SHORT(-1.00)[-1.000]; R_DKIM_ALLOW(-0.20)[walstatt-de.de:s=DKIM001]; MIME_GOOD(-0.10)[text/plain]; RCVD_TLS_ALL(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; HAS_ORG_HEADER(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:25394, ipnet:85.220.128.0/17, country:DE]; MISSING_XM_UA(0.00)[]; DMARC_NA(0.00)[walstatt-de.de]; MLMMJ_DEST(0.00)[freebsd-current@freebsd.org]; RCVD_COUNT_THREE(0.00)[3]; FROM_EQ_ENVFROM(0.00)[]; FROM_HAS_DN(0.00)[]; ARC_NA(0.00)[]; R_SPF_NA(0.00)[no SPF record]; TO_DN_ALL(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; DKIM_TRACE(0.00)[walstatt-de.de:+] X-Rspamd-Queue-Id: 4T7PrC5kY4z4NBc Hello, I've got a problem with recent CURRENT, running vnet JAILs. FreeBSD 15.0-CURRENT #28 main-n267432-e5b33e6eef7: Sun Jan 7 13:18:15 CET 2024 amd64 Main Host has IPFW configured and is open for services like OpenLDAP on UDP/TCP and ICMP (ipfw is configured via rc.conf in this case, host is listening on both protocol families IPv4 and IPv6). The host itself has openldap-server 2.6 as a service. The host's interface is igb0 with assigned ULA. JAILs (around eight jails) are sharing their vnet interfaces via a bridge with the same physical device as the host (igb0). After a while (the time elapsed is unspecific) the jail is unable to contact the host via IPv6: neither UDP, TCP nor ICMP sent from the JAIL is reaching the host. IPv4 is working like a charme! No problems there. When pinging the Jail from the main host via ping -6, the jail is responding! After the first ping -6, the jail now is able to ping -6 the main host. After a fresh reboot, the problem is not present and occurs after a while and it seems to happen first to very active jails. Kind regards, oh -- O. Hartmann