From nobody Mon Jun 3 08:10: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 4Vt5yN07QCz5M4Lk; Mon, 03 Jun 2024 08:10:52 +0000 (UTC) (envelope-from salvadore@freebsd.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2610:1c1:1:6074::16:84]) (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 "freefall.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4Vt5yM5M4Rz47xb; Mon, 3 Jun 2024 08:10:51 +0000 (UTC) (envelope-from salvadore@freebsd.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1717402251; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc; bh=Zo/nxmY3NMGzs/HocIrbPCQuSo5fsPZ9J+VRhg7pgRI=; b=pRDASE4brHkNHqNW9wa/DxO/fPvhSWd2ockx15l+8e4MKlUGT+rTau1lzhsRed1O07qPaD xYRRq4MOaEakHqM6Ia8J1zF2vSLYo3n0idDRkBzsFtbL09El3AZHcKKZUbLf0cqNo6tSy3 Lq1p2cue495JaUln91LNbfRGsrDYm0yIFQ+kF0BTG4/se+O9m5U979+qahC3jc0ZmgduoL 221xXDHcx350B94/mvXgkW+yTWNtzIZsgYCw2Zcoh0hZ8sfE59Hys+eJGwI3Lu24K24/4D z0FCwOa5uwUeLnGlrG1t1gsNZSKuoC+5Cay9AMe3gextHy/JK4sZ6yn4fEdOKA== ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1717402251; a=rsa-sha256; cv=none; b=SB/CIKiKTI2SB4FgHxi8dj+pndBwqiluHzxaaXQF/fUytBth4WeUl+k25j7irpxqddjFTY C4W8QYDQ4nzHaLuBk9HsIGKpU5ZbZ5FShNntLT9cLt9cXuwnSD97uXY0s4wLYqS55OkWgv JtqR6T+pB4kyJOs3H40QbEUbGRHTayabmJQ6NIzzkxe5zQf+yZ3K+AtLBoGwB3wHko/WaM Hr9CzmBzMXsOZeZOnQlamLwfOhDcmGYb1oGt0CUNkQY7zsg+I6LoD0iszTFuTJ4Q9Vheyb 0aGveDn7oVHQ7S0QD8g7wkLldEajQl4abHydOY+Mya4XI/H6JyZzRuj/1ClaNw== ARC-Authentication-Results: i=1; mx1.freebsd.org; none ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1717402251; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc; bh=Zo/nxmY3NMGzs/HocIrbPCQuSo5fsPZ9J+VRhg7pgRI=; b=WLlwf0bh8sut2L2VkP+L2hxUGBdfSDWi0vHCLWH+jOXNhUAKG2WUh5enZkcYyNHelctwMe gSWRW31v7pTJdpmB0AQxf/zSyL541gb13LhsHd/Nv+WKOKjAlxKFv6k5c6GYo6t/wtAsph ahIV1vJNcU0fRqg41qKXK+rFNtGuQP9+aD8ohxeuS2I8h70AtV4XjyjDDTfJTbv/CsCRzW 3+vnhI8rI9docPupW6K+RmNUBhraKs4v06izEHWFxwfc9E0ddwl488Jgcr6xrDdcoyxsrM hAS+K5rEJjWk63HEZje9ccqfeKO7oTXw9/b/wGFepo6HlGxm8Py06MbU/1ty2Q== Received: by freefall.freebsd.org (Postfix, from userid 1472) id B2318CECF; Mon, 03 Jun 2024 08:10:51 +0000 (UTC) To: freebsd-status-calls@FreeBSD.org Subject: Call for 2024Q2 status reports Cc: freebsd-current@FreeBSD.org,freebsd-hackers@FreeBSD.org,devsummit@FreeBSD.org,info@bsdcan.org,soc-students@FreeBSD.org,soc-mentors@FreeBSD.org Message-Id: <20240603081051.B2318CECF@freefall.freebsd.org> Date: Mon, 03 Jun 2024 08:10:51 +0000 (UTC) From: Lorenzo Salvadore 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 Dear FreeBSD Community, The deadline for the next FreeBSD Status Report update is June, 30th 2024 for work done since the last round of quarterly reports: April 2024 - June 2024. I would like to remind you that reports are published on a quarterly basis and are usually collected during the last month of each quarter, You are also welcome to submit them even earlier if you want, and the earlier you submit them, the more time we have for reviewing. Status report submissions do not need to be very long. They may be about anything happening in the FreeBSD project and community, and they provide a great way to inform FreeBSD users and developers about work that is underway or has been completed. Report submissions are not limited to committers; anyone doing anything interesting and FreeBSD related can -- and should -- write one! The following methods are available to submit your reports: * submit a review on Phabricator and add the group "status" to the reviewers list. You should put your reports in the directory doc/website/content/en/status/report-2024-04-2024-06/ (create it if it is missing); * submit a pull request at . You should put your reports in the directory doc/website/content/en/status/report-2024-04-2024-06/ (create it if it is missing); * send an email to status-submissions@FreeBSD.org including your report. An AsciiDoc template is available at . We look forward to seeing your 2024Q2 reports! Thanks, Lorenzo Salvadore (on behalf of status@) From nobody Mon Jun 3 19: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 4VtNQW2NRdz5JqNp for ; Mon, 03 Jun 2024 19:02:43 +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 4VtNQV1xJlz4R9J for ; Mon, 3 Jun 2024 19:02:42 +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=oqoW5nwu; dmarc=none; spf=pass (mx1.freebsd.org: domain of freebsd@walstatt-de.de designates 85.220.129.60 as permitted sender) smtp.mailfrom=freebsd@walstatt-de.de Received: from hub2.goneo.de (hub2.goneo.de [IPv6:2001:1640:5::8: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 E95E2240C2A for ; Mon, 3 Jun 2024 21:02:33 +0200 (CEST) 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 3B85F240524 for ; Mon, 3 Jun 2024 21:02:32 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=walstatt-de.de; s=DKIM001; t=1717441352; 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=A+JwO+ER+MFxzPIgLRHiSYjOBAHbGHMnK+KXXB5LqdU=; b=oqoW5nwu5+LeUUh5/fxLSDND5hADFtAFAflSL1oK81iU/jOJJOSutC6VCZqap/PCVH36Nk xV/M0SueLOVqG0GQgi/AXw3yuIiwGne1ZZ5WvzrjncD2lCwASTmvel1WLbzoChI2APP0Vu 87w4vMkFd1dIN6QlFDlC9/+E/+niQssd8j/tX9sTf+NP8BNAQCsjolz1FiGPZqfoK4aNhD eFt/DC3GkJPBss7OXOft7kjFweqog+K/d+j7ubtFDWI8p75pCO5C68ObmVhxTWuY9HcLqX qx7hV5n3Jm0ClxXXXNxzKQWNp0HtZ82vCSCx4NoHaw32csLIGunloIA++SFThg== Received: from thor.intern.walstatt.dynvpn.de (dynamic-089-012-030-072.89.12.pool.telefonica.de [89.12.30.72]) (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 1101724050D for ; Mon, 3 Jun 2024 21:02:32 +0200 (CEST) Date: Mon, 3 Jun 2024 21:02:04 +0200 From: FreeBSD User To: FreeBSD CURRENT Subject: bridge: no traffic with vnet (epair) beyond bridge device Message-ID: <20240603210231.64889de0@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: 51dddf X-Rspamd-UID: 796c86 X-Spamd-Bar: --- X-Spamd-Result: default: False [-3.50 / 15.00]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_SHORT(-1.00)[-0.998]; R_DKIM_ALLOW(-0.20)[walstatt-de.de:s=DKIM001]; R_SPF_ALLOW(-0.20)[+ip4:85.220.129.0/25]; MIME_GOOD(-0.10)[text/plain]; RCPT_COUNT_ONE(0.00)[1]; RCVD_VIA_SMTP_AUTH(0.00)[]; ASN(0.00)[asn:25394, ipnet:85.220.128.0/17, country:DE]; MIME_TRACE(0.00)[0:+]; HAS_ORG_HEADER(0.00)[]; MISSING_XM_UA(0.00)[]; RCVD_TLS_ALL(0.00)[]; DMARC_NA(0.00)[walstatt-de.de]; MLMMJ_DEST(0.00)[freebsd-current@freebsd.org]; FROM_EQ_ENVFROM(0.00)[]; FROM_HAS_DN(0.00)[]; ARC_NA(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; TO_DN_ALL(0.00)[]; RCVD_COUNT_THREE(0.00)[3]; DKIM_TRACE(0.00)[walstatt-de.de:+] X-Rspamd-Queue-Id: 4VtNQV1xJlz4R9J Hello, I'm running a dual socket NUMA CURRENT host (Fujitsu RX host) running several jails. Jails are attached to a bridge device (bridge1), the physical device on that bridge is igb1 (i350 based NIC). The bridge is created via host's rc scripts, adding and/or deleting epair members of the bridge is performed by the jail.conf script. I do not know how long the setup worked, but out of the blue, last week after a longish poudriere run after updating the host to most recent CURRENT (as of today, latest update kernel and world) and performing "etcupdate" on both the host and all jails, traffic beyond the bridge is not seen on the network! All jails can communicate with each other. Traffic from the host itself is routed via igb0 to network and back via igb1 onto the bridge. I check all setups for net.link.bridge: net.link.bridge.ipfw: 0 net.link.bridge.log_mac_flap: 1 net.link.bridge.allow_llz_overlap: 0 net.link.bridge.inherit_mac: 0 net.link.bridge.log_stp: 0 net.link.bridge.pfil_local_phys: 0 net.link.bridge.pfil_member: 0 net.link.bridge.ipfw_arp: 0 net.link.bridge.pfil_bridge: 0 net.link.bridge.pfil_onlyip: 0 I did not change anything (knowingly). I also have an oldish box running single socket processor, also driven by the very same CURRENT and similar, but not identical setup. The box is running very well and the bridge is working as expected. I was wondering if something in detail has changed in the handling of jails, epair and bridges. I followed the setup "after the book", nothing suspicious. Maybe someone has a clue what might break the bridge. By the way: ifconfig bridge1 looks as always, igb1 as member and it doesn't make any difference whether I force the bridge to inherit igb1's MAC or not. We also checked for the switches whether BPDU Guard may have been triggered, but everything looks good from the outside - execept the fact the brdiged interface seems inactive (but up) from the outside ... Kind regards oh -- O. Hartmann From nobody Tue Jun 4 01:21: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 4VtXqV6wsPz5M0tB for ; Tue, 04 Jun 2024 01:21:26 +0000 (UTC) (envelope-from zlei@FreeBSD.org) Received: from smtp.freebsd.org (smtp.freebsd.org [96.47.72.83]) (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 "smtp.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4VtXqV6Tqkz4FH9; Tue, 4 Jun 2024 01:21:26 +0000 (UTC) (envelope-from zlei@FreeBSD.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1717464086; 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: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=CKGD9QNNARKr4V+NfwGtBA8WQeMBUoTsjmuEAsM0TVo=; b=bsVN9jm/SwK8oF2hvBk1DlZkQjyJT5hS222Qe0s/79rxCaVAqootXRlzRDP8UwDvOUVvld bMp215NtDzUDT/kGYd/4FuFyA8V/hcTrtJYQdqLjvB9I+IBTX28Q5KxauVVu5jjBpUjvED KXgE85ARvB95Vl14FmrZZcS7/pMsFiIvob5096vo9xrvOSTNmZxZdCe2fUGct4V1XsE0KG ohG57UU/iomiWSxDa3+8ejg0VcrmOfgn+rk/Zi4F2BGALqf78J0sYz3V73fSbkDIM/i1dE NlIv3oKwTVEsHyZHuk5Aes+Zq4yUIPsh6B1hxpLwXFV3HE6Eg8ze44vY3I+h/g== ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1717464086; a=rsa-sha256; cv=none; b=jz+ygSr77mQt5tDVqEgHV/6C7wBUN9OegHVpqcJnBAC0Ygy8RwGRuZ3O37bXd5d59lMzJa qf8eAXREkBo7UshdeGQvVjY/R9pjs45ruIQhPSJDoHdCwRUOx3Fz7rpAKsoEkXBkGAKtLm L5ar913Qko4QsdkZ4OC4fGjV5jscFvtKuaNZe5xPOisSxoupb4UK3oRBq6zjg2YMSu8Jva apsl/s7o87Xi/HT5f4M1Ps4AHU1HVxBMuov9Gy1vCroII0EwPxFvH6HkYF+itUJ+tEI1l4 TdXfILIc7aeyr9j0MFwBe+RxVbFDbhyp4dGIGuCuIdpDJIM8qRVaaXBX3dNreg== ARC-Authentication-Results: i=1; mx1.freebsd.org; none ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1717464086; 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: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=CKGD9QNNARKr4V+NfwGtBA8WQeMBUoTsjmuEAsM0TVo=; b=HgxnQz/7djA/yyEKBbdTm6UyxmPbK4Ldbph3PscOXu513RQWLEgZQIT9B3585bt1KMQUld Gs/cXDLSwpOasTxTmBglHxirJOs82hp2i7KMFZ3Ux9f+qdLgMN8GruP8t840vaP5nFUbMc 4AE5b459PpIGIc5tEP34DXIofik2r8rjkqPK+Wzab0KzsKSpaVkLvzCgLRUOhvX6OD6lzq ts9JFsKbTLDhMTH2ms2YYSkh0xAmapC9elP7mQwbZ4+ZTxAyMDIyZHHA7FmxbOXfALWncg RHee/nw1xMiFapciMBQ/LoAUvEKsWQRXtAM99Y8O7iMiKSmrZp3CMO62Wyn1Gg== Received: from smtpclient.apple (ns1.oxydns.net [45.32.91.63]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) (Authenticated sender: zlei/mail) by smtp.freebsd.org (Postfix) with ESMTPSA id 4VtXqT5lHyz19Wd; Tue, 4 Jun 2024 01:21:25 +0000 (UTC) (envelope-from zlei@FreeBSD.org) Content-Type: text/plain; charset=us-ascii 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 \(3696.120.41.1.8\)) Subject: Re: bridge: no traffic with vnet (epair) beyond bridge device From: Zhenlei Huang In-Reply-To: <20240603210231.64889de0@thor.intern.walstatt.dynvpn.de> Date: Tue, 4 Jun 2024 09:21:19 +0800 Cc: FreeBSD CURRENT Content-Transfer-Encoding: quoted-printable Message-Id: <081448E7-E158-49BA-8758-39FAC9278EFC@FreeBSD.org> References: <20240603210231.64889de0@thor.intern.walstatt.dynvpn.de> To: FreeBSD User X-Mailer: Apple Mail (2.3696.120.41.1.8) > On Jun 4, 2024, at 3:02 AM, FreeBSD User = wrote: >=20 > Hello, >=20 > I'm running a dual socket NUMA CURRENT host (Fujitsu RX host) running = several jails. Jails are > attached to a bridge device (bridge1), the physical device on that = bridge is igb1 (i350 based > NIC). The bridge is created via host's rc scripts, adding and/or = deleting epair members of the > bridge is performed by the jail.conf script. >=20 > I do not know how long the setup worked, but out of the blue, last = week after a longish > poudriere run after updating the host to most recent CURRENT (as of = today, latest update > kernel and world) and performing "etcupdate" on both the host and all = jails, traffic beyond > the bridge is not seen on the network! All jails can communicate with = each other. Traffic from > the host itself is routed via igb0 to network and back via igb1 onto = the bridge. Can you elaborate your setup of network. I'm getting confused by the = last sentence. Is it ( the network for jails ) a bridged one or routed one ? >=20 > I check all setups for net.link.bridge: >=20 > net.link.bridge.ipfw: 0 > net.link.bridge.log_mac_flap: 1 > net.link.bridge.allow_llz_overlap: 0 > net.link.bridge.inherit_mac: 0 > net.link.bridge.log_stp: 0 > net.link.bridge.pfil_local_phys: 0 > net.link.bridge.pfil_member: 0 > net.link.bridge.ipfw_arp: 0 > net.link.bridge.pfil_bridge: 0 > net.link.bridge.pfil_onlyip: 0 >=20 > I did not change anything (knowingly).=20 >=20 > I also have an oldish box running single socket processor, also driven = by the very same > CURRENT and similar, but not identical setup. The box is running very = well and the bridge is > working as expected. >=20 > I was wondering if something in detail has changed in the handling of = jails, epair and > bridges. I followed the setup "after the book", nothing suspicious. No functional changes to if_bridge / if_epair / jail since the beginning = of this year as far as I known. >=20 > Maybe someone has a clue what might break the bridge. >=20 > By the way: ifconfig bridge1 looks as always, igb1 as member and it = doesn't make any > difference whether I force the bridge to inherit igb1's MAC or not. >=20 > We also checked for the switches whether BPDU Guard may have been = triggered, but everything > looks good from the outside - execept the fact the brdiged interface = seems inactive (but up) > from the outside ... >=20 > Kind regards >=20 > oh >=20 > --=20 > O. Hartmann >=20 Best regards, Zhenlei From nobody Tue Jun 4 07:36: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 4Vtj9Y1Pgkz5MkDR for ; Tue, 04 Jun 2024 07:37:37 +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 4Vtj9X5Mxyz4tkD for ; Tue, 4 Jun 2024 07:37:36 +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=1717486651; 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=/PHWuzOShPhwS6pfMn9tKKh4MBWTNYcQTYi0f710YzI=; b=LW7sJwdof3XeuOpWHTPms0ExbHakAgcctFn2Sfi3hSvqKloaM13TnPq2oY++giJcFWB3Os vJjAHBL71ivw735m1wOYMYdHaGiL3OmZjbo69qAWxDnnhDxIkKz/NfcigsodPavd3d1W3V LB2iF/g0d949t5fQhPO3ITG6ZtD6JdWpv7CRdfkTiEyKs/S9QR3fBpaTvkzLAF1YonGtI+ TVCiQcOqXYMl7pfxjIf1T9DJ+SNiltY6iXkodjvfxzMBQ9qSPzJU3G4UJ/2N7/Z7R1eyR0 IC7TkFP/OMgGUMc0RCQKbld7qr2DypxwA0pl6aHHcgi+O0LCWtdaQObuhIKSsw== Date: Tue, 04 Jun 2024 09:36:38 +0200 From: Alexander Leidinger To: FreeBSD User Cc: FreeBSD CURRENT Subject: Re: bridge: no traffic with vnet (epair) beyond bridge device In-Reply-To: <20240603210231.64889de0@thor.intern.walstatt.dynvpn.de> References: <20240603210231.64889de0@thor.intern.walstatt.dynvpn.de> Message-ID: <2433e25ebf6eae827bcd7912bbe27fbc@Leidinger.net> Organization: No organization, this is a private message. Content-Type: multipart/signed; protocol="application/pgp-signature"; boundary="=_2fd468e28f2a3da942f7a63a9ca99663"; micalg=pgp-sha256 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:34240, ipnet:89.238.64.0/18, country:DE] X-Rspamd-Queue-Id: 4Vtj9X5Mxyz4tkD This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --=_2fd468e28f2a3da942f7a63a9ca99663 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII; format=flowed Am 2024-06-03 21:02, schrieb FreeBSD User: > Hello, > > I'm running a dual socket NUMA CURRENT host (Fujitsu RX host) running > several jails. Jails are > attached to a bridge device (bridge1), the physical device on that > bridge is igb1 (i350 based > NIC). The bridge is created via host's rc scripts, adding and/or > deleting epair members of the > bridge is performed by the jail.conf script. > > I do not know how long the setup worked, but out of the blue, last week > after a longish > poudriere run after updating the host to most recent CURRENT (as of > today, latest update > kernel and world) and performing "etcupdate" on both the host and all > jails, traffic beyond > the bridge is not seen on the network! All jails can communicate with > each other. Traffic from > the host itself is routed via igb0 to network and back via igb1 onto > the bridge. > > I check all setups for net.link.bridge: > > net.link.bridge.ipfw: 0 > net.link.bridge.log_mac_flap: 1 > net.link.bridge.allow_llz_overlap: 0 > net.link.bridge.inherit_mac: 0 > net.link.bridge.log_stp: 0 > net.link.bridge.pfil_local_phys: 0 > net.link.bridge.pfil_member: 0 > net.link.bridge.ipfw_arp: 0 > net.link.bridge.pfil_bridge: 0 > net.link.bridge.pfil_onlyip: 0 > > I did not change anything (knowingly). > > I also have an oldish box running single socket processor, also driven > by the very same > CURRENT and similar, but not identical setup. The box is running very > well and the bridge is > working as expected. > > I was wondering if something in detail has changed in the handling of > jails, epair and > bridges. I followed the setup "after the book", nothing suspicious. "after the book" = the IP of the host itself is not on igb1 but on a different interface or on the bridge? Is there a firewall active on the box itself? Which one? What does wireshark / a traffic dump at the physical interface level tell compared to a traffic dump at the switch interface? Did you replace the cable / SFP / move to a different switch port as a test? I suggest to provide the output of ifconfig -a and netstat -rn (feel free to mangle the IPs, as long as the mangling is a consistent replacement and not a cut-off). Bye, Alexander. -- http://www.Leidinger.net Alexander@Leidinger.net: PGP 0x8F31830F9F2772BF http://www.FreeBSD.org netchild@FreeBSD.org : PGP 0x8F31830F9F2772BF --=_2fd468e28f2a3da942f7a63a9ca99663 Content-Type: application/pgp-signature; name=signature.asc Content-Disposition: attachment; filename=signature.asc; size=833 Content-Description: OpenPGP digital signature -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEER9UlYXp1PSd08nWXEg2wmwP42IYFAmZexBgACgkQEg2wmwP4 2IZjpg/+Nj8i23LkQ5zgkIU0tjOqIu7/D7NXY/MlVElWHWuZYPF+lJeD3oN1Gfsx uwSfxOEmnlvDG4Wny6hWEefzfrNdmtPpfZsfeavvaJEXqw78Gu4d7u5D5ymYNi8b GRNqUcFMDwVVMq5wPOOuXQifh2f6+2eOQ/rdL5HLPtPAdGyF/dWuI/ejbW7MxBRR Ad9/tTGN4hAbQqi+HbnEaqRxjgeLeWDr0bEHvTDZWm/aH68ydTUyqztyU0l5bSZ3 nnWoPp0Lrw5NivvDufEwGySxYL1T6fPkHcehjFW7BnLoCbRWryKyPF8EmcGw+D0V bVWmS4suVf2fvPoHsMAQsZekPZuTUoUg8unkrEJgN/dZFaWp+0vjckGHkpQJC845 QYk/8Rse+/OxUTUrf/BXn0Z9Pan6qnHxEoXv/YQTQhBmVeb7FjlX4aIuUpoe2U+V Nb0qb9F5hvRepiuIevDOd8l+7Nl3d7OXNjtX2GrkE0mrJm22hnJWO+fRQuAkGPNE o4s6Bjf9LGGtGS0dSqp02hwOPh94+evVzTvVyI1Es//hkXsgsdCE9nDHkBYu54fd rtr7Nto84cetwJ8I1/QE5VjuO4rSwTPMUeWn0kd0E1W1mCG3ytCCFbF+39BU9LV6 vDYxwmYLHYpE9Gp+mdzNhRkTQRshW3eC2zUcrhln7ySwfUXkVNg= =o4+t -----END PGP SIGNATURE----- --=_2fd468e28f2a3da942f7a63a9ca99663-- From nobody Tue Jun 4 10:49:42 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 4VtnRJ34dfz5NBVh for ; Tue, 04 Jun 2024 10:49:48 +0000 (UTC) (envelope-from sm@codenetworks.net) Received: from relayout08-q01.dominioabsoluto.net (relayout08-q01.dominioabsoluto.net [217.116.26.111]) (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 4VtnRG58XFz4HdM for ; Tue, 4 Jun 2024 10:49:46 +0000 (UTC) (envelope-from sm@codenetworks.net) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=codenetworks.net header.s=domabs header.b=Hc3PawIm; dmarc=none; spf=pass (mx1.freebsd.org: domain of sm@codenetworks.net designates 217.116.26.111 as permitted sender) smtp.mailfrom=sm@codenetworks.net Received: from relayout08-redir.dominioabsoluto.net (relayout08-redir.dominioabsoluto.net [217.116.26.119]) by relayout08.dominioabsoluto.net (Postfix) with ESMTP id 4VtnRB4mnpzr560; Tue, 4 Jun 2024 12:49:42 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=codenetworks.net; s=domabs; t=1717498182; bh=srmU/wfDRCjTmTWtQ+0kWHil/si+8egFxvkN/+XZhdE=; h=Date:Subject:To:Cc:References:From:In-Reply-To:From; b=Hc3PawImDdxwxGexDZ9a1nEyz7OMxczB1ZgOZWI8mckx1SqKZOqtdzwApKJIK6gJX jNlsezuUokPzNT8/z92V0sPQfk/VtQu1hlfg6fBmGQOubchaKo8h0SOh5N06Yrwv9u Z/N5D3u/DHA/YbubwVRo8JWls/u10hImKNYJAe/U= Received: from [192.168.3.20] (unknown [188.241.98.123]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: sm.codenetworks.net) by relayout08-dsp.dominioabsoluto.net (Postfix) with ESMTPSA id 4VtnRB2lkczr56q; Tue, 4 Jun 2024 12:49:42 +0200 (CEST) Message-ID: Date: Tue, 4 Jun 2024 12:49:42 +0200 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: [Bug 269133] bnxt(4): BCM57416 - HWRM_CFA_L2_SET_RX_MASK command returned RESOURCE_ALLOC_ERROR error To: =?UTF-8?Q?Gerrit_K=C3=BChn?= Cc: freebsd-current@freebsd.org References: <944a89c4-618d-4a3e-b253-6b56df3e4f3c@codenetworks.net> <0100018fbbdb5718-3ed4929d-183a-4080-b176-b1edce263fc2-000000@email.amazonses.com> <20240528084018.24cb5b5e@arc.aei.uni-hannover.de> <51be0cbf-20ae-48ff-aa37-befbf6f05d76@codenetworks.net> <20240528111942.6a649174@arc.aei.uni-hannover.de> <137a57c8-ca86-493c-bbc0-f357f8bff5cd@codenetworks.net> <20240528113008.39964887@arc.aei.uni-hannover.de> Content-Language: en-US From: Santiago Martinez Autocrypt: addr=sm@codenetworks.net; keydata= xsDNBGGx1zYBDAC4jWCD3yN13RQY9C5bsWzwubAkl8zD/t2GOtXZs2oLzmiOVinsTP5HEqko E+BdeprhF4nrWLm/lVOttQpyNWs94U01d4BAg3gMy9MQhZ1JdkhJNYc3CiE/aYytl4ZIF9ju AfSwKr/govkPMtsvipvEBcV8vuCy3EO3c4FsMWrvYRDSI1Gr+7gjAILgzp13Xv1o03aBbL8o XWL3SJPuAchbfeyfeIgOd8LoW8qMfXctXxJb9zfzAzDpUm7ZmQS/YhJ8az5ep3nv0U8M2vza dR18cf12umt8jurdNXFz0Sgs+kmqY6/d/OZzEbTUdH3tZP+n5nVlTGspSUyz/yY39vVKMWfi K1UPAU6qhYQB0AotIMkrL740PsDIXchwrO/nE9Hv4e9c3IznQq1tl4Q7Mn4ipFGqPadveQZz 2l5KRDswqDCm6Rva/Emevynu9fFVtSbNU0LckxNhU/s+60duyG+wimfDc/jH2VmFdhvQxIBL vN1j5N1XqWlyoA189+ThijEAEQEAAc0nU2FudGlhZ28gTWFydGluZXogPHNtQGNvZGVuZXR3 b3Jrcy5uZXQ+wsEPBBMBCAA5FiEEwQCqg+937H/V6G80Fiys1CziDEkFAmGx1zcFCQWjmoAC GwMFCwkIBwIGFQgJCgsCBRYCAwEAAAoJEBYsrNQs4gxJpMUL/Rf/VMXByz+jN6hkuPfGLC1q 5zheK//aZ7ITQ9mkSajVZvU0qCRYQapEOAYe8nv95/VNoTnZb3RHTcx9dJOpDGbCR+FrldlJ eAglOvqwwwSO4vU6PpXw27iDd/Hoohy+ReVtBJwxIOZjRtAmyBBKJLjJBQiQe+xuOzSXeXfA EAM2S+bxmwa8P0l/kbGi/mXlsWDi6zsnXNs9wkq07Z1ZTAGsziQ0tn7ZBRvvxl+dehYaJ/xD 7GBstABqOm04rY4nsHmlhfQo/S92S38dM9H4EG18m1KKJDjHD5+jh/+8ULSH/aGfni6iE8kL oiU/gAS3ROuIBODkA0xVQ8XMj20A4pQDuJIutc5qWSz3M3e8hW3365djJwhrMnwvB2I9VQDp Y3HzDD2RQEPXHkMs7TywL5hxUE5sQy+5ueCJokOl++1IJDvHe3ObAd6YdlTV1my6m2w9XV7Z QEIBEpvNHZMNRxqDKB1fCfwqXgC3Q6S2f1+LycA/tG1kRLXzesyFMBLZ/87AzQRhsdc3AQwA wliyyO46nJw/z/LikDMKkKX5qyx6QiWOF73mWnKcLXfNq2ejD2GYf5cB2DGtbXcOY6AkpB8S yCwBzcfdsGOsObe14dHSZzp5RwxYuJiOmrt4pOjN1BkPmD28e2WrlaXR2ZT73GsZuTLOPHM7 eKZx6YEla1Va5/Oq1bnCXVThsz+hKDgbhArAiFJYitw+Cx31eAkxKpHo/l+fIhaxQTKQnFCI MaklCZMl2uowiFLfZXdBpDD6Zj+sTWPfHqiFh5rhnE57XjonYVhTGxJsFY+pJn7XMT2g344q G3d48grAg2YILG5TfmtVaEKAkNsyJWuLju7KdBiEzMWiSRpkhX4MJjLPUkGUqMZ/cQN/ae8m lTOy5Jd9OhY94uCuDQcIhsOraExmQcek5MlvT9y+2KDKMk/gGL52FkmdlpDlGJJkX8snYqHn 2q27prK+LlMzKlBwvhsfgQINgcqAnKpeNC3o3tQuMRS8CN9bp5/8KbZTr9FGCNqTb3eDuu0r vUP7Y6JNABEBAAHCwPwEGAEIACYWIQTBAKqD73fsf9XobzQWLKzULOIMSQUCYbHXNwUJBaOa gAIbDAAKCRAWLKzULOIMSfpqC/9edCYRJtJrW4tIa31BRp/XxZoVD8q3IFHB8MQ+OS6yOnCO qoi9a2xxuFTEsRiyzdl3/D6YIf7QKVG5izhtFH7q+cLuzusgFhWZDADMcfojmVD7Z/nDPkgy Filc1FSiJf7aCD3iV2dQtV1r8J4Aseso67ge35qcL1QGCKcPubEw3vUM+YE1lhZe2U0PeAfK zIPqYGN1nHtxh4dFmKuHJpNAGHkWCo2RNdkkYR/2qIpOyeSFrRYE2dogYUGLz0Wv2bdm3LCb XbBsFbnpeaTTZ6SNYxyzjoDyRjPtinijbaeXIekJt4lUFZnezGusxMGBSZV+5Ms47aQpzSLp fZVWlMbB2/5mJTUJhJNYAwm2wWPyVcMcuFEriqEXal/xPq5bdK25s7mfHrx4ienGySHUROpX kVxSMw0XUdlEoqpOqCuyrfYNsSUf8ck8ssLeWKpkRKy76oMN76VidVLleT404o8BRSPuuJT5 Gu7Qzc+/hiQrZnxuQ9FhKgfg2W9b7kFM7R0= In-Reply-To: <20240528113008.39964887@arc.aei.uni-hannover.de> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-PostalOut-Country: IP: 188.241.98.123 | Country: ES X-PostalOut-Information: AntiSPAM and AntiVIRUS on relayout08 X-PostalOut-MsgID: 4VtnRB2lkczr56q.AC7E1 X-PostalOut-SpamCheck: no es spam, clean X-PostalOut-From: sm@codenetworks.net X-PostalOut-Watermark: 1718102982.51312@H8EtxYey1ptCMO2tMKJwWw X-Spam-Status: No X-Spamd-Bar: --- X-Spamd-Result: default: False [-3.89 / 15.00]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_SHORT(-1.00)[-0.998]; RWL_MAILSPIKE_VERYGOOD(-0.20)[217.116.26.111:from]; RCVD_IN_DNSWL_LOW(-0.20)[217.116.26.111:from,217.116.26.119:received]; R_SPF_ALLOW(-0.20)[+ip4:217.116.26.0/24]; R_DKIM_ALLOW(-0.20)[codenetworks.net:s=domabs]; MIME_GOOD(-0.10)[text/plain]; XM_UA_NO_VERSION(0.01)[]; ASN(0.00)[asn:16371, ipnet:217.116.24.0/21, country:ES]; TO_DN_SOME(0.00)[]; MIME_TRACE(0.00)[0:+]; RCVD_VIA_SMTP_AUTH(0.00)[]; ARC_NA(0.00)[]; FROM_HAS_DN(0.00)[]; MID_RHS_MATCH_FROM(0.00)[]; RCPT_COUNT_TWO(0.00)[2]; RCVD_COUNT_TWO(0.00)[2]; FROM_EQ_ENVFROM(0.00)[]; DMARC_NA(0.00)[codenetworks.net]; TO_MATCH_ENVRCPT_SOME(0.00)[]; MLMMJ_DEST(0.00)[freebsd-current@freebsd.org]; RCVD_TLS_LAST(0.00)[]; DKIM_TRACE(0.00)[codenetworks.net:+] X-Rspamd-Queue-Id: 4VtnRG58XFz4HdM Hi everyone, just to follow up. I have found something interesting, at the moment I'm focusing on the issue related to the creation and deletion of sub-interfaces that trigger ALLOC/MASK errors and bricks the NIC ( not completely as the other port keeps working, this card has 2x10G). I have found the following: - If a port is down (let's say bnxt1) and sub-interfaces are created ( bnxt1.1100) then the port is activated (ifconfig bnxt1 up). this will trigger the issues of the filters and the card will not be able to be  "programmed" again until the next reboot (not sure if there is any way to reset it, the devctl reset did not work). echo "Creating Interfaces and brick the card" ifconfig bnxt1.1011 create up fib 10 192.168.11.43/24 ifconfig bnxt1.1001 create up fib 11 192.168.12.43/24 ifconfig bnxt1.1002 create up fib 12 192.168.13.43/24 ifconfig bnxt1.1003 create up fib 13 192.168.14.43/24 ifconfig bnxt1.1004 create up fib 14 192.168.15.43/24 ifconfig bnxt1.1005 create up fib 15 192.168.16.43/24 ifconfig bnxt1 up --- ( at this point is bricked) --- --- then destroy and shutdown bnxt1 --- - If I do the same, but just make sure that the port is "admin up" before creating and deleting the sub-interfaces, everything works like charm. No errors are seen. echo "Creating Interfaces and bricks the card" ifconfig bnxt1 up ifconfig bnxt1.1011 create up fib 10 192.168.11.43/24 ifconfig bnxt1.1001 create up fib 11 192.168.12.43/24 ifconfig bnxt1.1002 create up fib 12 192.168.13.43/24 ifconfig bnxt1.1003 create up fib 13 192.168.14.43/24 ifconfig bnxt1.1004 create up fib 14 192.168.15.43/24 ifconfig bnxt1.1005 create up fib 15 192.168.16.43/24 --- then destroy and shutdown bnxt1 --- This is tested against main from yesterday. Best regards. Santi On 5/28/24 11:30, Gerrit Kühn wrote: > Am Tue, 28 May 2024 11:25:09 +0200 > schrieb Santiago Martinez : > >> *"The latest I have is 214.0.286.18"* >> Indeed, the firmware on my box is older, I cannot upgrade it right now, >> but it is on my to-do list. > Same here, I guess (pkgver). It says > dev.bnxt.0.ver.fw_ver: 214.4.9.10/pkg 214.0.286.18 > on both systems. > > Also, I don't think I can upgrade the firmware separately, it comes with > the mainboard's bios (which is the latest available). > > > cu > Gerrit From nobody Tue Jun 4 14:16:53 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 4Vtt2V0VJtz5LVLH for ; Tue, 04 Jun 2024 14:17:06 +0000 (UTC) (envelope-from gerrit.kuehn@aei.mpg.de) Received: from umail2.aei.mpg.de (umail2.aei.mpg.de [194.94.224.8]) (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 4Vtt2S5f5cz4klr for ; Tue, 4 Jun 2024 14:17:04 +0000 (UTC) (envelope-from gerrit.kuehn@aei.mpg.de) Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=pass (mx1.freebsd.org: domain of gerrit.kuehn@aei.mpg.de designates 194.94.224.8 as permitted sender) smtp.mailfrom=gerrit.kuehn@aei.mpg.de Received: from arc.aei.uni-hannover.de (ahgate1.aei.uni-hannover.de [130.75.117.49]) by umail2.aei.mpg.de (Postfix) with ESMTPS id AD7E21BBFE2F; Tue, 4 Jun 2024 16:16:59 +0200 (CEST) Date: Tue, 4 Jun 2024 16:16:53 +0200 From: Gerrit =?UTF-8?B?S8O8aG4=?= To: Santiago Martinez Cc: freebsd-current@freebsd.org Subject: Re: [Bug 269133] bnxt(4): BCM57416 - HWRM_CFA_L2_SET_RX_MASK command returned RESOURCE_ALLOC_ERROR error Message-ID: <20240604161653.0b2e852a@arc.aei.uni-hannover.de> In-Reply-To: <20240528111942.6a649174@arc.aei.uni-hannover.de> References: <944a89c4-618d-4a3e-b253-6b56df3e4f3c@codenetworks.net> <0100018fbbdb5718-3ed4929d-183a-4080-b176-b1edce263fc2-000000@email.amazonses.com> <20240528084018.24cb5b5e@arc.aei.uni-hannover.de> <51be0cbf-20ae-48ff-aa37-befbf6f05d76@codenetworks.net> <20240528111942.6a649174@arc.aei.uni-hannover.de> Organization: MPG X-Mailer: Claws Mail 3.19.1 (GTK+ 2.24.33; amd64-portbld-freebsd13.2) 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; boundary="Sig_/4xHUv_IXvaTz=JAa.3wa.m2"; protocol="application/pkcs7-signature"; micalg=SHA384 X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.52 / 15.00]; SIGNED_SMIME(-2.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-1.00)[-0.998]; NEURAL_SPAM_SHORT(0.28)[0.282]; R_SPF_ALLOW(-0.20)[+ip4:194.94.224.8]; MIME_GOOD(-0.20)[multipart/signed,text/plain]; RWL_MAILSPIKE_VERYGOOD(-0.20)[194.94.224.8:from]; RCVD_IN_DNSWL_MED(-0.20)[194.94.224.8:from]; ASN(0.00)[asn:680, ipnet:194.94.0.0/15, country:DE]; RCVD_COUNT_ONE(0.00)[1]; MIME_TRACE(0.00)[0:+,1:+,2:~]; TO_DN_SOME(0.00)[]; ARC_NA(0.00)[]; HAS_ORG_HEADER(0.00)[]; RCVD_TLS_ALL(0.00)[]; R_DKIM_NA(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_TWO(0.00)[2]; TO_MATCH_ENVRCPT_SOME(0.00)[]; MLMMJ_DEST(0.00)[freebsd-current@freebsd.org]; DMARC_NA(0.00)[mpg.de]; HAS_ATTACHMENT(0.00)[] X-Rspamd-Queue-Id: 4Vtt2S5f5cz4klr --Sig_/4xHUv_IXvaTz=JAa.3wa.m2 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Am Tue, 28 May 2024 11:19:42 +0200 schrieb Gerrit K=C3=BChn : > > Not sure if it will break your setup, but this already happened with=20 > > 13.2 (I cant recall the exact release). =20 > I have two machines with onboard NICs (Supermicro H12SSL-CT mainboards) > running just fine. One is 13.3, the other is 14.0. I have updated one system to 14.1 now, and it still works happily (transferring lots of data in the background while typing this). So whatever causes the issues you have seen with the BCM chipset, not all of them appear to be affected. Maybe the firmware is making the difference here? cu Gerrit --Sig_/4xHUv_IXvaTz=JAa.3wa.m2 Content-Type: application/pkcs7-signature; name=smime.p7s Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename=smime.p7s MIAGCSqGSIb3DQEHAqCAMIACAQExDzANBglghkgBZQMEAgIFADCABgkqhkiG9w0B BwEAAKCCF/QwggQyMIIDGqADAgECAgEBMA0GCSqGSIb3DQEBBQUAMHsxCzAJBgNV BAYTAkdCMRswGQYDVQQIDBJHcmVhdGVyIE1hbmNoZXN0ZXIxEDAOBgNVBAcMB1Nh bGZvcmQxGjAYBgNVBAoMEUNvbW9kbyBDQSBMaW1pdGVkMSEwHwYDVQQDDBhBQUEg Q2VydGlmaWNhdGUgU2VydmljZXMwHhcNMDQwMTAxMDAwMDAwWhcNMjgxMjMxMjM1 OTU5WjB7MQswCQYDVQQGEwJHQjEbMBkGA1UECAwSR3JlYXRlciBNYW5jaGVzdGVy MRAwDgYDVQQHDAdTYWxmb3JkMRowGAYDVQQKDBFDb21vZG8gQ0EgTGltaXRlZDEh MB8GA1UEAwwYQUFBIENlcnRpZmljYXRlIFNlcnZpY2VzMIIBIjANBgkqhkiG9w0B AQEFAAOCAQ8AMIIBCgKCAQEAvkCd9G7h6naHHE1FRI6+RsiDBp3BKv4YH47kAvrz q11QihYxC5oG0MVwIs1JLVRjzLZuaEYLU+rLTCTAvHJO6vEVrvRUmhIKw3qyM2Di 2olV8yJY897cz++DhqKMlE+faPKYkEaEJ8d2v+PMNSyLXgdkZYLASLCokflhn3Yg UKiRx2a163hiA1bwihoT6jGjHqCZ/Tj29icyWG8H9Wu4+xQrr7eqzNZjX3OM2gWZ qDioyxd4NlGs6Z70eDqNzw/ZQuKYDKsvnw4B3u+fmUnxLd+sdE0bmLVHxeUp0fmQ GMdinL6DxyZ7Poolx8DdneY1aBAgnY/Y3tLDhJwNXugvyQIDAQABo4HAMIG9MB0G A1UdDgQWBBSgEQojPpbxB+zirynvgqV/0DCktDAOBgNVHQ8BAf8EBAMCAQYwDwYD VR0TAQH/BAUwAwEB/zB7BgNVHR8EdDByMDigNqA0hjJodHRwOi8vY3JsLmNvbW9k b2NhLmNvbS9BQUFDZXJ0aWZpY2F0ZVNlcnZpY2VzLmNybDA2oDSgMoYwaHR0cDov L2NybC5jb21vZG8ubmV0L0FBQUNlcnRpZmljYXRlU2VydmljZXMuY3JsMA0GCSqG SIb3DQEBBQUAA4IBAQAIVvwC8Jvo/6T61nvGRIDOT8TF9gBYzKa2vBRJaAR26Obu XewCD2DWjVAYTyZOAePmsKXuv7x0VEG//fwSuMdPWvSJYAV/YLcFSvP28cK/xLl0 hrYtfWvM0vNG3S/G4GrDwzQDLH2W3VrCDqcKmcEFi6sML/NcOs9sN1UJh95TQGxY 7/y2q2VuBPYb3DzgWhXGntnxWUgwIWUDbOzpIXPsmwOh4DetoBUYj/q6As6nLKkQ EyzU5QgmqyKXYPiQXnTUoppTvfKpaOCibsLXbLGjD56/62jnVvKu8uMrODoJgbVr hde+Le0/GreyY+L1YiyC1GoAQVDxOYOflek2lphuMIIFgTCCBGmgAwIBAgIQOXJE Ovkit1HX02wQ3TE1lTANBgkqhkiG9w0BAQwFADB7MQswCQYDVQQGEwJHQjEbMBkG A1UECAwSR3JlYXRlciBNYW5jaGVzdGVyMRAwDgYDVQQHDAdTYWxmb3JkMRowGAYD VQQKDBFDb21vZG8gQ0EgTGltaXRlZDEhMB8GA1UEAwwYQUFBIENlcnRpZmljYXRl IFNlcnZpY2VzMB4XDTE5MDMxMjAwMDAwMFoXDTI4MTIzMTIzNTk1OVowgYgxCzAJ BgNVBAYTAlVTMRMwEQYDVQQIEwpOZXcgSmVyc2V5MRQwEgYDVQQHEwtKZXJzZXkg Q2l0eTEeMBwGA1UEChMVVGhlIFVTRVJUUlVTVCBOZXR3b3JrMS4wLAYDVQQDEyVV U0VSVHJ1c3QgUlNBIENlcnRpZmljYXRpb24gQXV0aG9yaXR5MIICIjANBgkqhkiG 9w0BAQEFAAOCAg8AMIICCgKCAgEAgBJlFzYOw9sIs9CsVw127c0n00ytUINh4qog TQktZAnczomfzD2p7PbPwdzx07HWezcoEStH2jnGvDoZtF+mvX2do2NCtnbyqTsr kfjib9DsFiCQCT7i6HTJGLSR1GJk23+jBvGIGGqQIjy8/hPwhxR79uQfjtTkUcYR Z0YIUcuGFFQ/vDP+fmyc/xadGL1RjjWmp2bIcmfbIWax1Jt4A8BQOujM8Ny8nkz+ rwWWNR9XWrf/zvk9tyy29lTdyOcSOk2uTIq3XJq0tyA9yn8iNK5+O2hmAUTnAU5G U5szYPeUvlM3kHND8zLDU+/bqv50TmnHa4xgk97Exwzf4TKuzJM7UXiVZ4vuPVb+ DNBpDxsP8yUmazNt925H+nND5X4OpWaxKXwyhGNVicQNwZNUMBkTrNN9N6frXTps NVzbQdcS2qlJC9/YgIoJk2KOtWbPJYjNhLixP6Q5D9kCnusSTJV882sFqV4Wg8y4 Z+LoE53MW4LTTLPtW//e5XOsIzstAL81VXQJSdhJWBp/kjbmUZIO8yZ9HE0XvMns QybQv0FfQKlERPSZ51eHnlAfV1SoPv10Yy+xUGUJ5lhCLkMaTLTwJUdZ+gQek9Qm RkpQgbLevni3/GcV4clXhB4PY9bpYrrWX1Uu6lzGKAgEJTm4Diup8kyXHAc/DVL1 7e8vgg8CAwEAAaOB8jCB7zAfBgNVHSMEGDAWgBSgEQojPpbxB+zirynvgqV/0DCk tDAdBgNVHQ4EFgQUU3m/WqorSs9UgOHYm8Cd8rIDZsswDgYDVR0PAQH/BAQDAgGG MA8GA1UdEwEB/wQFMAMBAf8wEQYDVR0gBAowCDAGBgRVHSAAMEMGA1UdHwQ8MDow OKA2oDSGMmh0dHA6Ly9jcmwuY29tb2RvY2EuY29tL0FBQUNlcnRpZmljYXRlU2Vy dmljZXMuY3JsMDQGCCsGAQUFBwEBBCgwJjAkBggrBgEFBQcwAYYYaHR0cDovL29j c3AuY29tb2RvY2EuY29tMA0GCSqGSIb3DQEBDAUAA4IBAQAYh1HcdCE9nIrgJ7cz 0C7M7PDmy14R3iJvm3WOnnL+5Nb+qh+cli3vA0p+rvSNb3I8QzvAP+u431yqqcau 8vzY7qN7Q/aGNnwU4M309z/+3ri0ivCRlv79Q2R+/czSAaF9ffgZGclCKxO/WIu6 pKJmBHaIkU4MiRTOok3JMrO66BQavHHxW/BBC5gACiIDEOUMsfnNkjcZ7Tvx5Dq2 +UUTJnWvu6rvP3t3O9LEApE9GQDTF1w52z97GA1FzZOFli9d31kWTz9RvdVFGD/t So7oBmF0Ixa1DVBzJ0RHfxBdiSprhTEUxOipakyAvGp4z7h/jnZymQyd/teRCBah o1+VMIIG5jCCBM6gAwIBAgIQMQJw1DW+mySa+FbQ4eKFSTANBgkqhkiG9w0BAQwF ADCBiDELMAkGA1UEBhMCVVMxEzARBgNVBAgTCk5ldyBKZXJzZXkxFDASBgNVBAcT C0plcnNleSBDaXR5MR4wHAYDVQQKExVUaGUgVVNFUlRSVVNUIE5ldHdvcmsxLjAs BgNVBAMTJVVTRVJUcnVzdCBSU0EgQ2VydGlmaWNhdGlvbiBBdXRob3JpdHkwHhcN MjAwMjE4MDAwMDAwWhcNMzMwNTAxMjM1OTU5WjBGMQswCQYDVQQGEwJOTDEZMBcG A1UEChMQR0VBTlQgVmVyZW5pZ2luZzEcMBoGA1UEAxMTR0VBTlQgUGVyc29uYWwg Q0EgNDCCAiIwDQYJKoZIhvcNAQEBBQADggIPADCCAgoCggIBALNK4iJeJ1vpBFsU BDUyIBSutNIxQMbNUMAeoUTKr55KYX8tkN5imzNqLaRCypYBPP9wED2AaO6e8njk bjzJwLgPqDBkW9sG3kmi3GW6cF4Hwr5ysZqve/5EJDhV+9OhfTu/4dMnoR4Q41Hc jMk9MzLOADAQ0awBZ/29r0d49AUmIKELNeqEqmnTN6fndL7x/2K0TLToZLxqS7sy /Jvi0wEFr0CfdjcAsioh7KaD+Jizyb1aRKQzJ6Q20VEHX7UqWc1SkzTkbz6xj0S5 ydBBFQh0fNiy+qM/deVpK4HgmPSJrrpQZ+LlbHfWabmwoDPxF71QZVYiqrrAoUrG RJ+47iLBiIg8miIYS7Hd2ppvAUt24CugMXUjETjQ+oYh09fNi5n/AvoER8UBvTHL xt+blL0bvL+2z2YiUWk+2Qtn+dD+JU5Z2y71qV7+cr+4YXjvGzF5bYsi8HiwflTb 4Php3y+k1twKtchdcq2QGc0eDG6Y01nRHUiyr8/PtMAsLHEPNZ2wzsA7fb8mftHi V20ZFmYqknJ8AIOfwdTVA+E62JayOJ+sxadqcmFDorsz/mrPwGZ8+txr4xSuvVjg 0dlv0yuA+1YpBDIYNfL4bkX+IcZ1mTstL4Xw0f4N2iW3bBmnPnYmoYxMM8gflCiT gss73nBvG2f7v1PD7BDGYNO4iD4vAgMBAAGjggGLMIIBhzAfBgNVHSMEGDAWgBRT eb9aqitKz1SA4dibwJ3ysgNmyzAdBgNVHQ4EFgQUaQChxyFY+ODFGyCwCt2nUb8T 2eQwDgYDVR0PAQH/BAQDAgGGMBIGA1UdEwEB/wQIMAYBAf8CAQAwHQYDVR0lBBYw FAYIKwYBBQUHAwIGCCsGAQUFBwMEMDgGA1UdIAQxMC8wLQYEVR0gADAlMCMGCCsG AQUFBwIBFhdodHRwczovL3NlY3RpZ28uY29tL0NQUzBQBgNVHR8ESTBHMEWgQ6BB hj9odHRwOi8vY3JsLnVzZXJ0cnVzdC5jb20vVVNFUlRydXN0UlNBQ2VydGlmaWNh dGlvbkF1dGhvcml0eS5jcmwwdgYIKwYBBQUHAQEEajBoMD8GCCsGAQUFBzAChjNo dHRwOi8vY3J0LnVzZXJ0cnVzdC5jb20vVVNFUlRydXN0UlNBQWRkVHJ1c3RDQS5j cnQwJQYIKwYBBQUHMAGGGWh0dHA6Ly9vY3NwLnVzZXJ0cnVzdC5jb20wDQYJKoZI hvcNAQEMBQADggIBAAoFTnsNjx8TOQD9b+xixsPt7Req4wHMeNw/R5dddEPgQAQA YJZKz5BEv1cjGbH7nbPH3AxrxhN6OVH40p6OLIo9MXSrrfMzGs7/P+FTCjwgNxFE tLQ1KC9NboA3asJcl7mIs3l8h9iAgEH1zLUvq2s+5n++NQmbzudDsTFDMapY3kX1 TwyUCTRzmItqcbsYIyg2MeIXWfRtqPqC5R4bufmpzA5BPINLX340Sp/CNQ9QZqw3 VkfyHWwTo+vO9Gm2L6srNamJT6Lb+TeXZvl8UPL5a72O/pH0GgGHjt6z9QzPARna RKshVWviNK6ST4WmZHllu3CJg0BXqx1vWyswawgvNeWt1qxITacYe9mSWTbNR2Cf tvTUwerruDSY2jMaZPoNqbjUpuG/blYwWzzvVerBUhviAahPXJF/9V48ybWPBq6q KOEokW+s3B4ad5sY96KlovEijaIQDip1HO0SD+rLNYaiBcr9MV2aK+DfbZ8w9BaN CQyFEYwzxIKOVk3bYvzHRk5ihUDascmbk/bkiNl74c/KfuKQmJImaqWoWZR6jBcX cPV0WUIKz/nILTpFhGojZEQW77by3aezAi9jrEIUBHRG1LwzPbJc2V3SOzYyaJFQ atzuKZbN1Q9s9y/2x1QXtKwREY8jNgvx0iIfOK35gKgYJJcyDql4XfuEc2nVMIIH SzCCBTOgAwIBAgIRAMCEqCZW/bEp9AgcdlGEWuEwDQYJKoZIhvcNAQEMBQAwRjEL MAkGA1UEBhMCTkwxGTAXBgNVBAoTEEdFQU5UIFZlcmVuaWdpbmcxHDAaBgNVBAMT E0dFQU5UIFBlcnNvbmFsIENBIDQwHhcNMjMwODE1MDAwMDAwWhcNMjYwODE0MjM1 OTU5WjCB0zEOMAwGA1UEERMFODA1MzkxRzBFBgNVBAoMPk1heC1QbGFuY2stR2Vz ZWxsc2NoYWZ0IHp1ciBGw7ZyZGVydW5nIGRlciBXaXNzZW5zY2hhZnRlbiBlLlYu MRswGQYDVQQJDBJIb2ZnYXJ0ZW5zdHJhw59lIDgxDzANBgNVBAgTBkJheWVybjEL MAkGA1UEBhMCREUxFTATBgNVBAMTDEdlcnJpdCBLdWVobjEmMCQGCSqGSIb3DQEJ ARYXZ2Vycml0Lmt1ZWhuQGFlaS5tcGcuZGUwggIiMA0GCSqGSIb3DQEBAQUAA4IC DwAwggIKAoICAQCg7n7fRC0hIeomyBYF0RZ0L/jKjURwqPL3vBN+HvDxzp+Wcn0a Voeia3LPeXvf18d7BeIQ2SVFXWnWzVpVKzv7VUg4OD424GmcQrFXkChSvOc/rLaA FmNIaKWgYwUOAqmDh3t9JzQTVj6FrAeJwzXmnv42msNUfnhA2dRllOCmilLUqm/5 nOgrImuiA3R1S0CcljAmEr5PnUmKJaanbaq74Jb54gf622cRyWwylMJijMGboDYw uaGynrLgfo+rWbXc2TASO6pjSQDKAAfXO/NzLgp+BmneN1II9alVUAJRUpFDkgx9 peM+qUJryLtO+veOKElsOe2S4qvk0PaE/MVAcIJiThdY7qde8Q9FyOJsDN5kiX4g fsKmtF7EdB71Uc8N78L62r7/7Y5WL8gRxXCN8BsmLXSiCylvtIYsbJMDhK6C+37w 9Cg1A8AWeksg1TmCcvolEJy3+bfPx7NlmEfRdkdzuVb1KxfB0z4SbhSwOAR1WYVg mEAQuj1l9k7suUtdUY4ZeMnRLVPtmQh+bxcJPaRllpHSTYbYVQlSNXkP0al2/J8d jJHhulOsCX8oYfyQ9a33jHsKUf632Lpg8446ym19UrNPh9pntXRXVhhkw+/tPE8G BxH81BCvvSUhVu0Nckx8zOWiI1+6Z5t71udnXOEv9lJFvqDlY71lkiu+jQIDAQAB o4IBpDCCAaAwHwYDVR0jBBgwFoAUaQChxyFY+ODFGyCwCt2nUb8T2eQwHQYDVR0O BBYEFOsacOXMtCWA1hWcY7A/tb8e/tTSMA4GA1UdDwEB/wQEAwIFoDAMBgNVHRMB Af8EAjAAMB0GA1UdJQQWMBQGCCsGAQUFBwMEBggrBgEFBQcDAjA/BgNVHSAEODA2 MDQGCysGAQQBsjEBAgJPMCUwIwYIKwYBBQUHAgEWF2h0dHBzOi8vc2VjdGlnby5j b20vQ1BTMEIGA1UdHwQ7MDkwN6A1oDOGMWh0dHA6Ly9HRUFOVC5jcmwuc2VjdGln by5jb20vR0VBTlRQZXJzb25hbENBNC5jcmwweAYIKwYBBQUHAQEEbDBqMD0GCCsG AQUFBzAChjFodHRwOi8vR0VBTlQuY3J0LnNlY3RpZ28uY29tL0dFQU5UUGVyc29u YWxDQTQuY3J0MCkGCCsGAQUFBzABhh1odHRwOi8vR0VBTlQub2NzcC5zZWN0aWdv LmNvbTAiBgNVHREEGzAZgRdnZXJyaXQua3VlaG5AYWVpLm1wZy5kZTANBgkqhkiG 9w0BAQwFAAOCAgEAbUB7zWvNZ98vh3u7hzpnbA1K4U9bga1YkpVbOgv7/UY5RiZP Rk06O18f5TnRSWiiF3XImBG1uVjbcwVKIemliCQRQzVVt2JXOJVT1EafDDe9DK5o QaXGHY7NAT1lPLEwtgv8hxBBvthMaMa6lpibT/IUi83jHPZUgsGajCgPXd05Bh/L jCzWDOmHuwFdjRAMQs1VsPYx+OVcRvS1jmw0bT6o5/nruRwF5brxUK39Mftj3sIN b+UvVkXdAGw5iQWFwllGpwBgo3iESa1R72qkBMWph8D6Jbg795WBgjMULCPTiZkq eOif9sW1/37AoutSh7VMh7WMrEW9QURVWYR1hYjS0/TMo8aXfPOLtLYoSg/R6i+j eXqREsJQxMAl0e/JJej1TAFCsWg0r6Dg4mYq636plAr6pu7pJATNVPT0HrsBMYWu PV2WRH8Obs+n1xe4ftGxE4yDWiL56lnp6tnfVR8qinEqpGBfj7BAwEcO/Na9b+oK tDEmWHzupKkdmoOWktURY+Q/5RVWoiozNujYljc9iaK3agqBbJ5ZzRyrCKOPLnw4 9b8koO03WkXPqlm59nxAOdJE6ZQ2aQ8ev6ji+UlGnlIvgk70MsRukY2shpAiowb6 bKjKyK3QGNnT4zmL6ixSRmnYhC95U923Yf+hy+6jqS1Ec6kgpREYG53Qv5IxggM5 MIIDNQIBATBbMEYxCzAJBgNVBAYTAk5MMRkwFwYDVQQKExBHRUFOVCBWZXJlbmln aW5nMRwwGgYDVQQDExNHRUFOVCBQZXJzb25hbCBDQSA0AhEAwISoJlb9sSn0CBx2 UYRa4TANBglghkgBZQMEAgIFAKCBsDAYBgkqhkiG9w0BCQMxCwYJKoZIhvcNAQcB MBwGCSqGSIb3DQEJBTEPFw0yNDA2MDQxNDE2NTNaMDUGCSqGSIb3DQEJDzEoMCYw CwYJYIZIAWUDBAEqMAsGCWCGSAFlAwQBAjAKBggqhkiG9w0DBzA/BgkqhkiG9w0B CQQxMgQwSbYXbQc4n44NPs/lojKxKl8fEyVx24MPhjXwIU3qQ4zPSsp8lPMWGmsS a+Pacd5wMA0GCSqGSIb3DQEBAQUABIICAA4b7R/oqIE5JeFUkgLb2xtKVEzfXvQE X4JNpat+Y7u6vg/H1ZvnGZ8+qpKO8Z3UdiemLkHeDajTXUCCb7/Zv+aXj9zkj/vw a/3IlD2tGacAPK54WXb7l49epi8XjGZF82dGL/g27OV2PtNV6fkNAs+PyfV1uUxV IHo7r6dUNRMYvahhPV4eZA6rkKTfB3ZP3Cj+uYyTwxt0g2r2cQTcYsqkp9CfvLk5 P9M3kHLciTncphX/bPiNaD1AJdksjkwTsZxZLguF1fQVUjdduFlZZ6GdsB25OD9+ vpS7psTwPZT70EAM0YYCYKg7xL5Z6mhuc3m9fAtKJ5MV4EnPbVmpLWW720xGqN+I LHtzrK8soIT1ZM8S89Mn8qo2lcjnWRj6kV/Vq4D040HdxbPoNip49mrHXXmVGBx/ 9V6tXqehSOA1MZ5uixZGIxLFmkUlBTe4iEmd49KPVXiiaLiLIdZDF6YoCT9IiSPs FEeguBsJNE6WBnUCpseeu5ci1bW395jVVivgdobmtR/2l9gxlO8RB+wAUJNXpNEs KdVqQR0j5M0sC4Y1lzlZbbSMLyHlQbrWL7Si0B7GkwedMgGCxu3QZnW1+jqCHCol xVHUI1UEFVA9MYrnz+Wmy18kLHcN8ms/tsBHvEQemCSLdqayf+t2EAzJ7jr6IhDN S5sBqXao8hK2AAAAAAAA --Sig_/4xHUv_IXvaTz=JAa.3wa.m2-- From nobody Tue Jun 4 15:06:12 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 4Vtv7S29VSz5Lcrf for ; Tue, 04 Jun 2024 15:06:28 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-pg1-x529.google.com (mail-pg1-x529.google.com [IPv6:2607:f8b0:4864:20::529]) (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 "WR4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4Vtv7S04pyz4ttW for ; Tue, 4 Jun 2024 15:06:28 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-pg1-x529.google.com with SMTP id 41be03b00d2f7-6cb6b9ada16so2017314a12.0 for ; Tue, 04 Jun 2024 08:06:27 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20230601.gappssmtp.com; s=20230601; t=1717513586; x=1718118386; 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=8vcc24aZV8AkFGw/4he2sQGQHvRzQnLWc7/+zm8uwtA=; b=lpff28zD2UM7XMd9NlDQ1B0J9f89lmrju8LSxkj52ECiiMKaDrj175KzfZK6lYvE1L NlUEqQFXBVwaKxwpYrN/81KwYqYDmvNGKeCPhx8b5sPYrv1ys9cbNhNHXf+8dxMDecNp EoCMkfBqaF5gA9SsvjZwhy1zEpgHJIimq+gXAbXG4bBjQDJcNF3QcEoLkKUbWAhLI1Ek ArjKqdwbF8OPjVUqDqJTE6D1QFwpOv32wSC4jxqx6pa8JGwPVaTsZTVUSDAMr1LikPGt ADngPtlOlV3MSVSuEeRnIpbDOP4GsnZiTfd4hT6Xf4kyWpmOvQhu7cx9Zre6/rKMpvjy smQg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1717513586; x=1718118386; 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=8vcc24aZV8AkFGw/4he2sQGQHvRzQnLWc7/+zm8uwtA=; b=wLVPPUjIUOtC8U7KAEI315gkuUTjOBujA96bCzrhZsmD07brlXcAPD/hYXau59E3bK H7Fh3UG5KIDqDz6SUOwmaXiTakVcFZw8Tj1hjRGG0eM2vUindqsrUofBEXhs8Zgxoh65 wkzpFArjcTueEbP09TWt2ULmJWYU9kr3k2aQWI5FVsQ+99Uc/RgMRF2HbQJsisxe/bAp X/C4VrvIjp3GtXBHSnIY6cBuCrDrOhd4+QW9jhfH1K5cCYT6DaopEbljZsoJODEYMp9n 0sJqmamYQhm/bEbUqhPIAU+5gQ33MchOulFnSfiOXoiEt09XwMZKzrQsjpEeOhWd0yD6 oqVQ== X-Forwarded-Encrypted: i=1; AJvYcCVsQjh/GFpFacNvkLxb0yx4m7HOJ5uA0QUNqqNRHt5nQIALVw+grDk5tx/VT0GXQMfhJ1O+/JcB4JfDvts7UlVk98kZwukaueXCRXc= X-Gm-Message-State: AOJu0YzSxWuz4yRwu4u3IG8arW7Hmy5E8V2Egoo1E4QhwS5XgCtkbCHB tQ/98gAbxzmOqUA/Pt+XV5chPxyRLGlYL/nvJVRAq39a98z7bpYQVffBeaGUURhXiFzAmmLHUJf rJG6y3FIpxOUh2Lt3qOyE3YOLCB9wp8YAzCgxVOEmRPZRzIatCzs= X-Google-Smtp-Source: AGHT+IHIaEApwlAhD78bNIfaSzLITuh6KwMKcmUXyGVVuEwkZO79CjCAdd01HRQhNhhhuQIiZ7vNlTr5ykTtS/qAK5Y= X-Received: by 2002:a17:90b:370b:b0:2bd:eb21:a72d with SMTP id 98e67ed59e1d1-2c1dc58f8b2mr12680516a91.23.1717513586133; Tue, 04 Jun 2024 08:06:26 -0700 (PDT) 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: <944a89c4-618d-4a3e-b253-6b56df3e4f3c@codenetworks.net> <0100018fbbdb5718-3ed4929d-183a-4080-b176-b1edce263fc2-000000@email.amazonses.com> <20240528084018.24cb5b5e@arc.aei.uni-hannover.de> <51be0cbf-20ae-48ff-aa37-befbf6f05d76@codenetworks.net> <20240528111942.6a649174@arc.aei.uni-hannover.de> <20240604161653.0b2e852a@arc.aei.uni-hannover.de> In-Reply-To: <20240604161653.0b2e852a@arc.aei.uni-hannover.de> From: Warner Losh Date: Tue, 4 Jun 2024 09:06:12 -0600 Message-ID: Subject: Re: [Bug 269133] bnxt(4): BCM57416 - HWRM_CFA_L2_SET_RX_MASK command returned RESOURCE_ALLOC_ERROR error To: =?UTF-8?B?R2Vycml0IEvDvGhu?= Cc: Santiago Martinez , freebsd-current@freebsd.org Content-Type: multipart/alternative; boundary="00000000000032e8cd061a11cb44" 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] X-Rspamd-Queue-Id: 4Vtv7S04pyz4ttW --00000000000032e8cd061a11cb44 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Tue, Jun 4, 2024 at 8:17=E2=80=AFAM Gerrit K=C3=BChn wrote: > Am Tue, 28 May 2024 11:19:42 +0200 > schrieb Gerrit K=C3=BChn : > > > > Not sure if it will break your setup, but this already happened with > > > 13.2 (I cant recall the exact release). > > > I have two machines with onboard NICs (Supermicro H12SSL-CT mainboards) > > running just fine. One is 13.3, the other is 14.0. > > I have updated one system to 14.1 now, and it still works happily > (transferring lots of data in the background while typing this). So > whatever causes the issues you have seen with the BCM chipset, not all of > them appear to be affected. Maybe the firmware is making the difference > here? > I merged the next version of the driver from Broadcom to stable/14, but not 14.1 (it was too late by the time I got around to this). If there's still issues, maybe try stable/14? Warner > cu > Gerrit > --00000000000032e8cd061a11cb44 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable


=
On Tue, Jun 4, 2024 at 8:17=E2=80=AFA= M Gerrit K=C3=BChn <gerrit.ku= ehn@aei.mpg.de> wrote:
Am Tue, 28 May 2024 11:19:42 +0200
schrieb Gerrit K=C3=BChn <gerrit.kuehn@aei.mpg.de>:

> > Not sure if it will break your setup, but this already happened w= ith
> > 13.2 (I cant recall the exact release).=C2=A0

> I have two machines with onboard NICs (Supermicro H12SSL-CT mainboards= )
> running just fine. One is 13.3, the other is 14.0.

I have updated one system to 14.1 now, and it still works happily
(transferring lots of data in the background while typing this). So
whatever causes the issues you have seen with the BCM chipset, not all of them appear to be affected. Maybe the firmware is making the difference
here?

I merged the next version of the = driver from Broadcom to stable/14, but not 14.1 (it
was too late = by the time I got around to this). If there's still issues, maybe try s= table/14?

Warner
=C2=A0
cu
=C2=A0 Gerrit
--00000000000032e8cd061a11cb44-- From nobody Tue Jun 4 15:37:55 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 4VtvrX63sjz5Ly9n for ; Tue, 04 Jun 2024 15:38:36 +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 4VtvrW6brFz427B for ; Tue, 4 Jun 2024 15:38:35 +0000 (UTC) (envelope-from freebsd@walstatt-de.de) Authentication-Results: mx1.freebsd.org; none Received: from hub2.goneo.de (hub2.goneo.de [IPv6:2001:1640:5::8: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 D3B15240C54; Tue, 4 Jun 2024 17:38:33 +0200 (CEST) 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 38B4924055C; Tue, 4 Jun 2024 17:38:32 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=walstatt-de.de; s=DKIM001; t=1717515512; 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=HxgOJfg3OB7JLIVTn4pP8ES1c833IgC0vYUsvkG6qzA=; b=RqmOEaSEG4lWkjKXSOBTJNErbC+9iMBhKDknL+qnnbQlAQ+To8mdNmpYkpCOnzaKVV9/ds lCv5Av3ycbGwhdkeYMU2OBPt6C5wV3cyXRuu9Ut2wDCY4JsTtZMFvaJPZVJ7mlvmdfG/ip 6usrNFgpuiBeB82ataSPogkfMl/ahgA0V9eVtH/PD6KhxWrouq7GlpwPfVReuHlaF8aGFE 0zfBL0I1sOnfbj4u3+MEuhDtijp7los0gX74qJiNQyQ5jRMtm0Pzlf+Qa9Pz7RWFh0O7J9 FOvXaZlpaqMEtmZ4k6cDjM4iMFhSTFGwTT4eeoWCE+EwhEoS3NA849KvxgjHWQ== Received: from thor.intern.walstatt.dynvpn.de (dynamic-078-055-093-184.78.55.pool.telefonica.de [78.55.93.184]) (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 F0FF92404CD; Tue, 4 Jun 2024 17:38:31 +0200 (CEST) Date: Tue, 4 Jun 2024 17:37:55 +0200 From: FreeBSD User To: Alexander Leidinger Cc: FreeBSD CURRENT Subject: Re: bridge: no traffic with vnet (epair) beyond bridge device Message-ID: <20240604173822.4c61c1b9@thor.intern.walstatt.dynvpn.de> In-Reply-To: <2433e25ebf6eae827bcd7912bbe27fbc@Leidinger.net> References: <20240603210231.64889de0@thor.intern.walstatt.dynvpn.de> <2433e25ebf6eae827bcd7912bbe27fbc@Leidinger.net> 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: multipart/signed; boundary="Sig_/VE/tBw9YatRgLz1elRFZIZB"; protocol="application/pgp-signature"; micalg=pgp-sha512 X-Rspamd-UID: 5ce1de X-Rspamd-UID: 68d83e 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:25394, ipnet:85.220.128.0/17, country:DE] X-Rspamd-Queue-Id: 4VtvrW6brFz427B --Sig_/VE/tBw9YatRgLz1elRFZIZB Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable Am Tue, 04 Jun 2024 09:36:38 +0200 Alexander Leidinger schrieb: > Am 2024-06-03 21:02, schrieb FreeBSD User: > > Hello, > >=20 > > I'm running a dual socket NUMA CURRENT host (Fujitsu RX host) running=20 > > several jails. Jails are > > attached to a bridge device (bridge1), the physical device on that=20 > > bridge is igb1 (i350 based > > NIC). The bridge is created via host's rc scripts, adding and/or=20 > > deleting epair members of the > > bridge is performed by the jail.conf script. > >=20 > > I do not know how long the setup worked, but out of the blue, last week= =20 > > after a longish > > poudriere run after updating the host to most recent CURRENT (as of=20 > > today, latest update > > kernel and world) and performing "etcupdate" on both the host and all=20 > > jails, traffic beyond > > the bridge is not seen on the network! All jails can communicate with=20 > > each other. Traffic from > > the host itself is routed via igb0 to network and back via igb1 onto=20 > > the bridge. > >=20 > > I check all setups for net.link.bridge: > >=20 > > net.link.bridge.ipfw: 0 > > net.link.bridge.log_mac_flap: 1 > > net.link.bridge.allow_llz_overlap: 0 > > net.link.bridge.inherit_mac: 0 > > net.link.bridge.log_stp: 0 > > net.link.bridge.pfil_local_phys: 0 > > net.link.bridge.pfil_member: 0 > > net.link.bridge.ipfw_arp: 0 > > net.link.bridge.pfil_bridge: 0 > > net.link.bridge.pfil_onlyip: 0 > >=20 > > I did not change anything (knowingly). > >=20 > > I also have an oldish box running single socket processor, also driven= =20 > > by the very same > > CURRENT and similar, but not identical setup. The box is running very=20 > > well and the bridge is > > working as expected. > >=20 > > I was wondering if something in detail has changed in the handling of=20 > > jails, epair and > > bridges. I followed the setup "after the book", nothing suspicious. =20 >=20 > "after the book" =3D the IP of the host itself is not on igb1 but on a=20 > different interface or on the bridge? >=20 > Is there a firewall active on the box itself? Which one? >=20 > What does wireshark / a traffic dump at the physical interface level=20 > tell compared to a traffic dump at the switch interface? Did you replace= =20 > the cable / SFP / move to a different switch port as a test? >=20 > I suggest to provide the output of ifconfig -a and netstat -rn (feel=20 > free to mangle the IPs, as long as the mangling is a consistent=20 > replacement and not a cut-off). >=20 > Bye, > Alexander. >=20 Hello Alexander and everybody brave enough reading my post. Somehow I managed it to let=20 "ifconfig_igb1=3D"up" disappear - I guess by accident when sneaking through the rc.conf file. igb1 is the physical device connecting to the network. The bridge is layer = 2 only, no IP, only the vnet-portions pointing towards the jail do have IPv6 and IPv4. The brid= ge has around 20 members, the last entry is igb1 - I never checked whether it is up ... Sorry! Kind regards, oh --=20 O. Hartmann --Sig_/VE/tBw9YatRgLz1elRFZIZB Content-Type: application/pgp-signature Content-Description: OpenPGP digital signature -----BEGIN PGP SIGNATURE----- iHUEARYKAB0WIQRQheDybVktG5eW/1Kxzvs8OqokrwUCZl807gAKCRCxzvs8Oqok r35SAQCBNJiUsss+3BvOWQVuOsh+QubxwWM3bYKs31WaSUWavAEA1I2EBw55S1J4 K8ThmAx1zZXHp6Dz8W4RA6KTcKD1Dwo= =fuxM -----END PGP SIGNATURE----- --Sig_/VE/tBw9YatRgLz1elRFZIZB-- From nobody Tue Jun 4 16:29:41 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 4VtwzX0hs5z5M5jh for ; Tue, 04 Jun 2024 16:29:44 +0000 (UTC) (envelope-from jhb@FreeBSD.org) Received: from smtp.freebsd.org (smtp.freebsd.org [96.47.72.83]) (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 "smtp.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4VtwzW71CMz47q1; Tue, 4 Jun 2024 16:29:43 +0000 (UTC) (envelope-from jhb@FreeBSD.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1717518584; 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: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=JBIVnJ6nb6vRjwjhEGQNMQGgCDcGXXslBJnHPRDlJzY=; b=t9v9UVDWyGti+lQebCc+Ff6R4lPcq+aY0lcWnDTE/Om8EfjdxrKkBmNim9NbgTxUMHDmE2 v2wpRfnhzVCI6uac6N1reRGvUlQnZ/G0VfiTttEgM4UqqauYsVeyGRlTOFLiR395T8czuA z7uqMLYRrKqHsriX6atKe0dWd1bQDCEZMB+wpVaIg3BlUgYccW4XHe0LGXfYgsUy5R2AoD OsMFRhCKZyj3K9CeClLbd401m2d1h5v1ez5DUMbwgFG+/kD0292/YO62dz1tHqxVhEmb7n 5J8iVxBZvhefb0n8ryTa8Esq7DRUXDuuCaoBZJLxPpQPDbH9t8Ag6N1u9y1L0w== ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1717518584; a=rsa-sha256; cv=none; b=FAgQ80j2TsyPFYWhWCLGLSmRPEAn8Bt9IVwREauNPYJQQnIxTwZyPes4pBs4lYTBSnj9gK 8JyFSdJDKPKST3uCDkvwOLp6XxOFheveZeSX6j9w/lKWceSYxKUbJNNvjK1TbkI7cheC95 WuzHfJZt6Q8Ulz8WfY4/5EQmYXeN3zT0xURTCyI26/C2Nsu74bD/pckwu681e5qO0hDnFg 2mjsuzy32CfDRRXIVAgk78BrSAHXcuVqLu8VUUJUjRVVrpjKdZnSVHF3nkmIxd6ODjv0Lv se3qCieYq1R7jrhh3N96NhGQTZal0y9t7IsE/towEC9IuEcqDV0KhYifoPq5HQ== ARC-Authentication-Results: i=1; mx1.freebsd.org; none ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1717518584; 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: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=JBIVnJ6nb6vRjwjhEGQNMQGgCDcGXXslBJnHPRDlJzY=; b=xcbpUOBGpfhcJ8IKOZJRMIsytEFOfffSZAsnixf49SXYm0C3mN2t7s8V0m0/Kn72CNaUsA Aqdrc1IO+SPeodm6o96ZEhHOHBRNJBUwgPgpG1jxX3kqy4vE+3qMA30IbNfvIN4ZqlmTH4 zME3SUL3x/NnM21k47PrBEj8AlcVH7eEkiEon5XaQ/gL82fQh8tWIbTmdtFCaQ51ApLLI4 wdYLiW80UGKKboRsoj4vLJ3iwpo+8NNP6NIxU/jzwpOpLt75K9Mlkp1geD04KH/PuoUx4A W2vIicEOFYXMelmUQZzW0GuOVy1LEK+GoBKFWA+KUcgB9x2TyC8qtFpO5ZT7hg== Received: from [IPV6:2601:644:937f:4c50:e0fb:ab3b:bf07:f04] (unknown [IPv6:2601:644:937f:4c50:e0fb:ab3b:bf07:f04]) (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 did not present a certificate) (Authenticated sender: jhb) by smtp.freebsd.org (Postfix) with ESMTPSA id 4VtwzW3LVgzFny; Tue, 4 Jun 2024 16:29:43 +0000 (UTC) (envelope-from jhb@FreeBSD.org) Message-ID: Date: Tue, 4 Jun 2024 09:29:41 -0700 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: gcc behavior of init priority of .ctors and .dtors section Content-Language: en-US To: Lorenzo Salvadore , Konstantin Belousov Cc: Zhenlei Huang , FreeBSD Current References: <3ECF8C28-D2D9-4212-B025-3EC64E46BADC@FreeBSD.org> From: John Baldwin In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit On 5/16/24 4:05 PM, Lorenzo Salvadore wrote: > On Thursday, May 16th, 2024 at 20:26, Konstantin Belousov wrote: >>> gcc13 from ports >>> `# gcc ctors.c && ./a.out init 1 init 2 init 5 init 4 init 3 main fini 3 fini 4 fini 5 fini 2 fini 1` >>> >>> The above order is not expected. I think clang's one is correct. >>> >>> Further hacking with readelf shows that clang produces the right order of >>> section .rela.ctors but gcc does not. >>> >>> ``` >>> # clang -fno-use-init-array -c ctors.c && readelf -r ctors.o | grep 'Relocation section with addend (.rela.ctors)' -A5 > clang.txt >>> # gcc -c ctors.c && readelf -r ctors.o | grep 'Relocation section with addend (.rela.ctors)' -A5 > gcc.txt >>> # diff clang.txt gcc.txt >>> 3,5c3,5 >>> < 000000000000 000800000001 R_X86_64_64 0000000000000060 init_65535_2 + 0 >>> < 000000000008 000700000001 R_X86_64_64 0000000000000040 init + 0 >>> < 000000000010 000600000001 R_X86_64_64 0000000000000020 init_65535 + 0 >>> --- >>> >>>> 000000000000 000600000001 R_X86_64_64 0000000000000011 init_65535 + 0 >>>> 000000000008 000700000001 R_X86_64_64 0000000000000022 init + 0 >>>> 000000000010 000800000001 R_X86_64_64 0000000000000033 init_65535_2 + 0 >>>> ``` >>> >>> The above show clearly gcc produces the wrong order of section `.rela.ctors`. >>> >>> Is that expected behavior ? >>> >>> I have not tried Linux version of gcc. >> >> Note that init array vs. init function behavior is encoded by a note added >> by crt1.o. I suspect that the problem is that gcc port is built without >> --enable-initfini-array configure option. > > Indeed, support for .init_array and .fini_array has been added to the GCC ports > but is present in the *-devel ports only for now. I will > soon proceed to enable it for the GCC standard ports too. lang/gcc14 is soon > to be added to the ports tree and will have it since the beginning. > > If this is indeed the issue, switching to a -devel GCC port should fix it. FWIW, the devel/freebsd-gcc* ports have passed this flag to GCC's configure for a long time (since we made the switch in clang). -- John Baldwin From nobody Tue Jun 4 21:52:25 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 4Vv47y6Ld6z5Mgsy for ; Tue, 04 Jun 2024 21:52:30 +0000 (UTC) (envelope-from freebsd.jhixson@gmail.com) Received: from mail-pg1-f172.google.com (mail-pg1-f172.google.com [209.85.215.172]) (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 "WR4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4Vv47y0gQnz3xh8; Tue, 4 Jun 2024 21:52:30 +0000 (UTC) (envelope-from freebsd.jhixson@gmail.com) Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=fail reason="SPF not aligned (relaxed), No valid DKIM" header.from=freebsd.org (policy=none); spf=pass (mx1.freebsd.org: domain of freebsd.jhixson@gmail.com designates 209.85.215.172 as permitted sender) smtp.mailfrom=freebsd.jhixson@gmail.com Received: by mail-pg1-f172.google.com with SMTP id 41be03b00d2f7-6c9e8c0a15bso2295069a12.3; Tue, 04 Jun 2024 14:52:30 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1717537948; x=1718142748; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:cc:to:from:date:x-gm-message-state:from:to:cc:subject:date :message-id:reply-to; bh=xsH4yIlBPqFoybs89vdwvHzvzEr3S958lfrQ82Hz9X0=; b=TbqAmUS48L45FXl3LfQNDLUcORk9XC93LDdkHJ62+A8FDHGF7AUUb6bWhpuhAPlZKW dG7zC8TOX36jqc8dU4cppOrTAu4bIOff+Syj7Q8EKns64Mbvjzrnd9g+U4pcC2pR7kwJ OwT+wVdM51qXjBIw3EVOCu+nVEhIPa1mcw+OV5KedvoplQeNA22ORMnteCxgrPJr52UR BtgiOWlKtupMKfwatGne1Nq+1M+YasbBhN7ImajrejqtEMwENKOrqzMxM64PHw/3L9WD XfnpLmoEKRj2iip9a8aqYCDUvgCK8jkhJGZqsF7pIr6bxE/LyC6OraBgDu90YlPY5FcH bWRw== X-Forwarded-Encrypted: i=1; AJvYcCVq9diK/vu/ssWAJdmNuTzQgm49vVzyimTgF8BJxhs43hYhfOfs1IkBdGFSuCt2PEZPPe7SLZDELDXYNR3wPl5s1YMx21Syd4HBNPp4PE3PNqB6h7bsDBp6nTdGPdOKnhrN X-Gm-Message-State: AOJu0YxyagKwSjyi/0d/2F7zLYIO/vF3NyAH/NBwj6v0Uw2zzordkr1/ Ta5XtfOo0Qgw/pH4NXJl87NZLjSFiRY6Dv1aJd2wzyGjdXKErNdI X-Google-Smtp-Source: AGHT+IEIU+SXs0llr3PDdidAc9gq0sLxfnePIWoXDuXihDHVbvQoS7KsyQGkgbn8suW8G4znTnpfIA== X-Received: by 2002:a05:6a21:1f05:b0:1b2:a94d:4ec7 with SMTP id adf61e73a8af0-1b2b7155266mr905960637.60.1717537947495; Tue, 04 Jun 2024 14:52:27 -0700 (PDT) Received: from FreeBSD.org ([2001:470:801d:1::31]) by smtp.gmail.com with ESMTPSA id d2e1a72fcca58-7024548aed7sm7415727b3a.148.2024.06.04.14.52.26 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 04 Jun 2024 14:52:27 -0700 (PDT) Date: Tue, 4 Jun 2024 14:52:25 -0700 From: John Hixson To: Miroslav Lachman <000.fbsd@quip.cz> Cc: Rick Macklem , David Chisnall , "freebsd-current@freebsd.org" Subject: Re: Deprecating smbfs(5) and removing it before FreeBSD 14 Message-ID: <4ea542mqtue7ety23gpgxborpl4brx3fewhgy5p23ozivjzeay@dyk4oxvgs7c5> References: <489849ca-a404-fb54-81d1-d62ea18c5832@FreeBSD.org> <254a0b5e-72d9-f93e-0c49-82b50a35db41@quip.cz> <3bbacbac-9238-f29d-653c-86d13085afe0@quip.cz> 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-sha512; protocol="application/pgp-signature"; boundary="yuy36hhzwjkj4ibk" Content-Disposition: inline In-Reply-To: <3bbacbac-9238-f29d-653c-86d13085afe0@quip.cz> X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.07 / 15.00]; SIGNED_PGP(-2.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-0.98)[-0.979]; NEURAL_HAM_SHORT(-0.59)[-0.588]; MID_RHS_NOT_FQDN(0.50)[]; FORGED_SENDER(0.30)[jhixson@freebsd.org,freebsdjhixson@gmail.com]; MIME_GOOD(-0.20)[multipart/signed,text/plain]; R_SPF_ALLOW(-0.20)[+ip4:209.85.128.0/17]; DMARC_POLICY_SOFTFAIL(0.10)[freebsd.org : SPF not aligned (relaxed), No valid DKIM,none]; RCVD_TLS_LAST(0.00)[]; TAGGED_FROM(0.00)[]; FROM_HAS_DN(0.00)[]; TO_DN_EQ_ADDR_SOME(0.00)[]; ARC_NA(0.00)[]; TO_DN_SOME(0.00)[]; MIME_TRACE(0.00)[0:+,1:+,2:~]; RCPT_COUNT_THREE(0.00)[4]; ASN(0.00)[asn:15169, ipnet:209.85.128.0/17, country:US]; FREEMAIL_ENVFROM(0.00)[gmail.com]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCVD_COUNT_TWO(0.00)[2]; FROM_NEQ_ENVFROM(0.00)[jhixson@freebsd.org,freebsdjhixson@gmail.com]; MISSING_XM_UA(0.00)[]; MLMMJ_DEST(0.00)[freebsd-current@freebsd.org]; RWL_MAILSPIKE_POSSIBLE(0.00)[209.85.215.172:from]; R_DKIM_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; RCVD_IN_DNSWL_NONE(0.00)[209.85.215.172:from] X-Rspamd-Queue-Id: 4Vv47y0gQnz3xh8 --yuy36hhzwjkj4ibk Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Jun 27, 2022 at 03:27:54PM +0200, Miroslav Lachman wrote: > On 16/06/2022 15:56, Rick Macklem wrote: > > Miroslav Lachman <000.fbsd@quip.cz> wrote: > > > On 24/01/2022 16:13, Rick Macklem wrote: > > >=20 > > [...] > > >=20 > > > > So, I think Mark and Yuri are correct and looking at up to date > > > > Illumos sources is the next step. > > > > (As I mentioned, porting the Apple sources is beyond what I am > > > > willing to attempt.) > > > >=20 > > > > rick > > >=20 > > > Hello Rick, > > > I would like to ask you I there is some progress with porting newer > > > SMBFS / CIFS version to FreeBSD? Did you find Illumos sources as a > > > possibility where to start porting? > > Yes. I have the stuff off Illumos-gate, which I think is pretty up-to-d= ate > > and I agree that it should be easier than the Apple stuff to port into > > FreeBSD. I don't think it is "straightforward" as someone involved > > with Illumos said, due to the big differences in VFS/locking, but... > >=20 > > Having said the above, I have not done much yet. I've been cleaning up > > NFS stuff, although I am nearly done with that now. > > I do plan on starting to work on it soon, but have no idea if/when I > > will have something that might be useful for others. >=20 > I'm glad to hear that. >=20 > > > We have more and more problems with current state of mount_smbfs. I > > > would be really glad if "somebody" can do the heroic work of > > > implementing SMBv2 in FreeBSD. > > > Maybe it's time to start some fundraising for sponsoring this work? > > Well, funding isn't an issue for me (I'm just a retired guy who does th= is > > stuff as a hobby). However, if there is someone else who is capable of > > doing it if they are funded, I have no problem with that. > > I could either help them, or simply stick with working on NFS and leave > > SMBv23 to them. > >=20 > > Sorry, but I cannot report real progress on this as yet, rick >=20 > No need to sorry. I really appreciate your endless work on NFS and that y= ou > still have kind of interest to try porting SMBv2/3. > Unfortunately I don't know anybody else trying to do this tremendous work. >=20 I am working on a from scratch implementation of smbfs. I do not have any kind of time estimate since it is in my spare time. I chose this route after spending considerable time looking at Apple and Solaris implementations and wanting something without all of the legacy 1.0 crap. I do have a very minimal working FUSE version at this point, but there is much to do, and even more to abide by the various specifications. I just thought I'd share in case anyone is interested. - John --yuy36hhzwjkj4ibk Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQKTBAABCgB9FiEEJaAswQZQMflCdCA6RqljBb/iPUAFAmZfjJJfFIAAAAAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDI1 QTAyQ0MxMDY1MDMxRjk0Mjc0MjAzQTQ2QTk2MzA1QkZFMjNENDAACgkQRqljBb/i PUCHWw//daWymfX0sBCNL23MNMoJOXvoA3PnpCXJ5NFrNVQ/S5dl92BbM321Uk3W e7wFOe9eHsFhLvNM8ZFANyo9yOjX3uHdSLGbHiYAkzKIVJ9JxNQw1V4BOzgofdtf hnxSj9TF3Y9kOIUCZeWZ5amg6SD8pJQQ3fM3Y2jXh81v9RSoFLeA9VgYX7e/jctk E9kujvM7O2o4ai2yVhLuB1E5t3ujULpWG+hdrzgfKpF8PYubjRGew/v7Z4qRIwEb 4jLPFXQmv74aOI8t4G6svM0UO3R/Vlr2nz3PpIXBrgSQer7fJNbiiJdbjPomY9HB iWigG2GoJaxN2sD4X2bYcYWT9+/JJofMX1WI2kQqceJ358h+J5sV4TUixA3ytrKW AnOfiW/yJbF+G1VYE6xT5XoeFVB/9GepJZFvlt6K2HpoCKl1Xg3wlc7T13bC218o Eu+im+DEYhxU5MXrHJ50ZFr6itRVK/nQmR+/JuDZRdxEPxihUPGheO0wN+7IB9lH qTYWq0mVcsURy1ui20ImAuUwy2lgmlmAmoJ/R/I/FQrMKgTAvjEGrQLElxzfWetJ hc9AufXNOEz5rY5xf5jZwelj87CUhfY4emUlB7Wtltsa4JuhnxL4DqPdKILogIZw RRl1NyquFYd5/kOjzwCoVLGBYQZQ7teo8HqIbEGpMIMPHxI+4eI= =9qBf -----END PGP SIGNATURE----- --yuy36hhzwjkj4ibk-- From nobody Tue Jun 4 23:01:37 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 4Vv5gx2Sqqz5Ms6f for ; Tue, 04 Jun 2024 23:01:49 +0000 (UTC) (envelope-from SRS0=GIxD=NG=quip.cz=000.fbsd@elsa.codelab.cz) Received: from elsa.codelab.cz (elsa.codelab.cz [94.124.105.4]) (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 4Vv5gx0Gbxz47B6; Tue, 4 Jun 2024 23:01:48 +0000 (UTC) (envelope-from SRS0=GIxD=NG=quip.cz=000.fbsd@elsa.codelab.cz) Authentication-Results: mx1.freebsd.org; none Received: from elsa.codelab.cz (localhost [127.0.0.1]) by elsa.codelab.cz (Postfix) with ESMTP id 27A31D789E; Wed, 5 Jun 2024 01:01:40 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=quip.cz; s=private; t=1717542100; bh=oyp79VyrLrw1Z1nkLlqEeaG2Xz+uV5b42jmC2vvNHUI=; h=Date:Subject:To:Cc:References:From:In-Reply-To; b=GI5DiSJCH6fDJD5oXn0syZWHxx4cDDsGxmw44zQ61QHUj13oabtPi68knPahF+qi9 CAlPN5op9fUaG+rcjuzX9Csss0mMuIZhEtX2oFhohRSJdPLku0rSodnTndvgSR3Dqo scINlDWf3cMTHw5HfUhAbKwjeoYLXyPlXXnWjbYA= Received: from [192.168.145.49] (ip-89-177-27-225.bb.vodafone.cz [89.177.27.225]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by elsa.codelab.cz (Postfix) with ESMTPSA id 51E92D789B; Wed, 5 Jun 2024 01:01:38 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=quip.cz; s=private; t=1717542098; bh=oyp79VyrLrw1Z1nkLlqEeaG2Xz+uV5b42jmC2vvNHUI=; h=Date:Subject:To:Cc:References:From:In-Reply-To; b=Ql35mQIyi2Jc+juFXGmaGXkGOqU8Fzyzau+lqNAPiXGNBQ9Z+VW4fSDSp34RJ3SXe qvIxwgT7XTkwvP9Mnf2rWGKcoVBRgaJFOm+Xp/ll4mTUG495y4g8oWHhaMjDvsx+oG 9btushPKpyJxh+ECJvlLPZ0HwfO93s2JlkChZ/WE= Message-ID: Date: Wed, 5 Jun 2024 01:01:37 +0200 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: Deprecating smbfs(5) and removing it before FreeBSD 14 To: John Hixson Cc: Rick Macklem , "freebsd-current@freebsd.org" References: <489849ca-a404-fb54-81d1-d62ea18c5832@FreeBSD.org> <254a0b5e-72d9-f93e-0c49-82b50a35db41@quip.cz> <3bbacbac-9238-f29d-653c-86d13085afe0@quip.cz> <4ea542mqtue7ety23gpgxborpl4brx3fewhgy5p23ozivjzeay@dyk4oxvgs7c5> Content-Language: cs-Cestina From: Miroslav Lachman <000.fbsd@quip.cz> In-Reply-To: <4ea542mqtue7ety23gpgxborpl4brx3fewhgy5p23ozivjzeay@dyk4oxvgs7c5> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit 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:42000, ipnet:94.124.104.0/21, country:CZ] X-Rspamd-Queue-Id: 4Vv5gx0Gbxz47B6 On 04/06/2024 23:52, John Hixson wrote: > On Mon, Jun 27, 2022 at 03:27:54PM +0200, Miroslav Lachman wrote: >> On 16/06/2022 15:56, Rick Macklem wrote: >>> Miroslav Lachman <000.fbsd@quip.cz> wrote: >>>> On 24/01/2022 16:13, Rick Macklem wrote: >>>> >>> [...] >>>> >>>>> So, I think Mark and Yuri are correct and looking at up to date >>>>> Illumos sources is the next step. >>>>> (As I mentioned, porting the Apple sources is beyond what I am >>>>> willing to attempt.) >>>>> >>>>> rick >>>> >>>> Hello Rick, >>>> I would like to ask you I there is some progress with porting newer >>>> SMBFS / CIFS version to FreeBSD? Did you find Illumos sources as a >>>> possibility where to start porting? >>> Yes. I have the stuff off Illumos-gate, which I think is pretty up-to-date >>> and I agree that it should be easier than the Apple stuff to port into >>> FreeBSD. I don't think it is "straightforward" as someone involved >>> with Illumos said, due to the big differences in VFS/locking, but... >>> >>> Having said the above, I have not done much yet. I've been cleaning up >>> NFS stuff, although I am nearly done with that now. >>> I do plan on starting to work on it soon, but have no idea if/when I >>> will have something that might be useful for others. >> >> I'm glad to hear that. >> >>>> We have more and more problems with current state of mount_smbfs. I >>>> would be really glad if "somebody" can do the heroic work of >>>> implementing SMBv2 in FreeBSD. >>>> Maybe it's time to start some fundraising for sponsoring this work? >>> Well, funding isn't an issue for me (I'm just a retired guy who does this >>> stuff as a hobby). However, if there is someone else who is capable of >>> doing it if they are funded, I have no problem with that. >>> I could either help them, or simply stick with working on NFS and leave >>> SMBv23 to them. >>> >>> Sorry, but I cannot report real progress on this as yet, rick >> >> No need to sorry. I really appreciate your endless work on NFS and that you >> still have kind of interest to try porting SMBv2/3. >> Unfortunately I don't know anybody else trying to do this tremendous work. >> > > I am working on a from scratch implementation of smbfs. I do not have > any kind of time estimate since it is in my spare time. I chose this > route after spending considerable time looking at Apple and Solaris > implementations and wanting something without all of the legacy 1.0 > crap. I do have a very minimal working FUSE version at this point, but > there is much to do, and even more to abide by the various > specifications. > > I just thought I'd share in case anyone is interested. Thank you for the message. I'm glad someone has the courage to take the plunge. Smbfs is still very important to me. In a heterogeneous environment it is still the most common way to share data between systems. Are you planning the final version as a kernel module, or will the final version be via FUSE? I have had bad experiences with FUSE in the past with stability and performance. Best regards Miroslav Lachman From nobody Tue Jun 4 23:05:02 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 4Vv5lk5wK2z5MsrT for ; Tue, 04 Jun 2024 23:05:06 +0000 (UTC) (envelope-from freebsd.jhixson@gmail.com) Received: from mail-pf1-f179.google.com (mail-pf1-f179.google.com [209.85.210.179]) (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 "WR4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4Vv5lk3mZcz49m1 for ; Tue, 4 Jun 2024 23:05:06 +0000 (UTC) (envelope-from freebsd.jhixson@gmail.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-pf1-f179.google.com with SMTP id d2e1a72fcca58-701b0b0be38so5425984b3a.0 for ; Tue, 04 Jun 2024 16:05:06 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1717542305; x=1718147105; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:cc:to:from:date:x-gm-message-state:from:to:cc:subject:date :message-id:reply-to; bh=cfjYpsc7W5UQSVXzAKRMAjuEQlt0nsVsH5d5ylizXIE=; b=FqT9P5nkB0xAmvtJQaPHp+ICK7tUYqeAi/l+uz8WIo3jXEpEuuDKAyX651IaAg6+xQ ck2rZGhJCK4RLduc8PJ+pqEcoUKaxGs01oCBtufvDzQnibzIknwlwynUpUJQUKBwg45R QdWymgZZRXrUq+20ZBab/S/CYeBtYgUQETSKMRZXTPyPYDFOXQyNJRanCHBE9EtF9XQ+ ImQu0CS9dkQwluoqqJvqenKvIIa+AdpVgYZ5lj6kdJznVdIyGU4Tn/vxHFI/7xPqHGE7 Dq8FdXKkml1iG+oSqtScboUXqfaky97rnLHAPzBKbgGNrbeEC+IJSRhff5hYcEWjtPT2 LP2g== X-Forwarded-Encrypted: i=1; AJvYcCXbLyMaQYaANI2I2RikiV5aVTQmCp47i5Aq++JqgTBD7isKL6y+iD8e08X5hwrWT2SCPB4/IWSyj+H3PRTlUUNoJT+u+86GacAa7h8= X-Gm-Message-State: AOJu0Ywj65B/YP4M17SjYr+l8hh2nNmWl9C3i8nWF5gpJ82Uz7eW2hYZ X0d+6iPR7e7XROJVphRLkjIQ6m4L5ptf5wHr2C6pnyaL/pXQm6i8aQ3hXQ== X-Google-Smtp-Source: AGHT+IHk6REuAhMCunAqYe6ByAIYAy1qKg/ZCPAJzlPsWh7SkWSDD36phHBrNN+f3NmUv2tBvR3x9Q== X-Received: by 2002:a05:6a00:2e9b:b0:6ea:bf1c:9dfd with SMTP id d2e1a72fcca58-703e5a13297mr1073931b3a.27.1717542304850; Tue, 04 Jun 2024 16:05:04 -0700 (PDT) Received: from FreeBSD.org ([2001:470:801d:1::31]) by smtp.gmail.com with ESMTPSA id 41be03b00d2f7-6c355cd88aesm7536590a12.50.2024.06.04.16.05.03 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 04 Jun 2024 16:05:04 -0700 (PDT) Date: Tue, 4 Jun 2024 16:05:02 -0700 From: John Hixson To: Miroslav Lachman <000.fbsd@quip.cz> Cc: Rick Macklem , "freebsd-current@freebsd.org" Subject: Re: Deprecating smbfs(5) and removing it before FreeBSD 14 Message-ID: References: <489849ca-a404-fb54-81d1-d62ea18c5832@FreeBSD.org> <254a0b5e-72d9-f93e-0c49-82b50a35db41@quip.cz> <3bbacbac-9238-f29d-653c-86d13085afe0@quip.cz> <4ea542mqtue7ety23gpgxborpl4brx3fewhgy5p23ozivjzeay@dyk4oxvgs7c5> 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-sha512; protocol="application/pgp-signature"; boundary="xapqojuleodrrnc6" Content-Disposition: inline In-Reply-To: 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)[]; TAGGED_FROM(0.00)[]; ASN(0.00)[asn:15169, ipnet:209.85.128.0/17, country:US] X-Rspamd-Queue-Id: 4Vv5lk3mZcz49m1 --xapqojuleodrrnc6 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable >=20 > Thank you for the message. I'm glad someone has the courage to take the > plunge. Smbfs is still very important to me. In a heterogeneous environme= nt > it is still the most common way to share data between systems. > Are you planning the final version as a kernel module, or will the final > version be via FUSE? I have had bad experiences with FUSE in the past with > stability and performance. The final version will be a kernel module. It will also be BSD licensed. I am not an expert at the VFS layer so I want to get the stack ironed out in FUSE before moving it into kernel space. - John --xapqojuleodrrnc6 Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQKTBAABCgB9FiEEJaAswQZQMflCdCA6RqljBb/iPUAFAmZfnZhfFIAAAAAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDI1 QTAyQ0MxMDY1MDMxRjk0Mjc0MjAzQTQ2QTk2MzA1QkZFMjNENDAACgkQRqljBb/i PUBo+BAAxLbvgpPeMlgUPAAgjd3THqWD8arXA6Vfqyda6NSNbD2LLn6/fS/K5nic 96KnP8R3xzi+q8t3ldlPzIKcxAP0kOefLgjs3zTfcxKb9vV3H3tmAJC1y74A1OFJ HFlpZQyfqy4Sd8GwUl8c6sLNT6cjQfmK7FU0A4pYjUvkLihbCK8nvxWS+850Xnkc v0Lrx19R9yhimmH43d0JZ+CSSr17TGJY6TAejAtQMMEeG/iD5zPx9myBcJ88qB96 wMwU9fnwSAZ5zq0kTrEst8kRHV4zWBQQ+gGREx+1NWLtmqhTAWsIAfgvBzasZSxp WOg4OcdfoTAfcnWd8zB+LBh2u8daUvvtkunUF1jf9kLYRl7X40QXJ3yi2gcGCND/ FY0wBRah38iMN/AsZVEdbrHYBbSrH5++gIyR351dqI1dX1i5wXI5fBmK0nXQ7cNq zl0IMhd1SZvj8rlx3/jpU2JerRiUGnFBr8Qo7Bni2t+RbNgbyhkL7OR8aIO1X48B h71UF8rOc0xRtJF3zR3KxdMh0FzD3ebWB6RnmjYTWzXU8BXBlMA+rTl5EfY7W8mk Y8Qj65vX1jv0NIknOYWy+kdNnkOLo6eI+eiHm18rfqhDmjYJNIigCGOxYKST8n6Y Scc7bR60A9YsX+WTcoO+SwbNcGJUnUDq5Cc9IegzI8GYz07DfPE= =2Msf -----END PGP SIGNATURE----- --xapqojuleodrrnc6-- From nobody Wed Jun 5 00:17:57 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 4Vv7N44DwVz5N3Hd for ; Wed, 05 Jun 2024 00:18:12 +0000 (UTC) (envelope-from asomers@gmail.com) Received: from mail-vs1-f44.google.com (mail-vs1-f44.google.com [209.85.217.44]) (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 "WR4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4Vv7N42HfJz4Mdg; Wed, 5 Jun 2024 00:18:12 +0000 (UTC) (envelope-from asomers@gmail.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-vs1-f44.google.com with SMTP id ada2fe7eead31-48baea0acfdso1512622137.0; Tue, 04 Jun 2024 17:18:12 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1717546690; x=1718151490; h=content-transfer-encoding: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=wW3K0gF/0LTVKer4Rs6x14x5IQc3VIU5I61g31pnNh4=; b=a1SLHaADxb5lya5JUHYj/fRU0wEWeDXmbhGa3O48R2rRhoH+b3bC1kw75m+cJoqunP 3s8MuBe3SrOvICK2HAFjGxHojAfML0SBMn04lIqG8ecD3g0EJCWEpWAAyXOuBVuNkzTE FkuIrMG8VBzymNnSEDgur42eU27TgQ0ZdDEhnX7EjSCdDMMHuQ0MxR01BQxzNoWelMDa GTvUraMtyYoaizGJ5K7pAXOL9dlwmlGVRXL1W7yGe7UbV8Wsqa3LJh7uoCTC0oat1znI 2MGGRJikwPOBm0CyiNT0lAy+hzS46TrDpAKlT+5aUzRbZQiqtpZrhphnhBio3QtTXF3M CxYw== X-Forwarded-Encrypted: i=1; AJvYcCUArvk/+QnVc7ejMQQ1jmxQ2yBSKfERJIyqkjF5bVieh+FXxPed7DwQozVW5j30v1CVX1PzrEAc9Y/9XXZl0Ag51BBOzXPt+xDfDRaOZBmeJs4O6RqaVjszuVf19G3T1T3G X-Gm-Message-State: AOJu0Yx3VHjMm7y+g1UOEOyFkV/ZyvenZjCsJnPo2eIQOC/U4DTG8L9V +VzaQG3YDQxsG1PYPLyZbu4ahTVoeRak+TjNGP194Rw/bYoBV7NOMHdt7fYTIBFQO10akmqgDYH TyLd7ChhjrHAOM6OghjX4tZGe2iLylQ== X-Google-Smtp-Source: AGHT+IEPOXUhcE0/626BErYPDuN70/JGOquq53tRQHZ7BReUBU8f3Rx7hwcF14ZMwokps0a1YcY3xIdqHFL8ccr6aQY= X-Received: by 2002:a05:6102:216d:b0:48b:ab02:32ef with SMTP id ada2fe7eead31-48c04a60267mr1239974137.33.1717546690040; Tue, 04 Jun 2024 17:18:10 -0700 (PDT) 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: <489849ca-a404-fb54-81d1-d62ea18c5832@FreeBSD.org> <254a0b5e-72d9-f93e-0c49-82b50a35db41@quip.cz> <3bbacbac-9238-f29d-653c-86d13085afe0@quip.cz> <4ea542mqtue7ety23gpgxborpl4brx3fewhgy5p23ozivjzeay@dyk4oxvgs7c5> In-Reply-To: <4ea542mqtue7ety23gpgxborpl4brx3fewhgy5p23ozivjzeay@dyk4oxvgs7c5> From: Alan Somers Date: Tue, 4 Jun 2024 18:17:57 -0600 Message-ID: Subject: Re: Deprecating smbfs(5) and removing it before FreeBSD 14 To: John Hixson Cc: Miroslav Lachman <000.fbsd@quip.cz>, Rick Macklem , David Chisnall , "freebsd-current@freebsd.org" Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable 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:209.85.128.0/17, country:US] X-Rspamd-Queue-Id: 4Vv7N42HfJz4Mdg On Tue, Jun 4, 2024 at 3:52=E2=80=AFPM John Hixson wr= ote: > > On Mon, Jun 27, 2022 at 03:27:54PM +0200, Miroslav Lachman wrote: > > On 16/06/2022 15:56, Rick Macklem wrote: > > > Miroslav Lachman <000.fbsd@quip.cz> wrote: > > > > On 24/01/2022 16:13, Rick Macklem wrote: > > > > > > > [...] > > > > > > > > > So, I think Mark and Yuri are correct and looking at up to date > > > > > Illumos sources is the next step. > > > > > (As I mentioned, porting the Apple sources is beyond what I am > > > > > willing to attempt.) > > > > > > > > > > rick > > > > > > > > Hello Rick, > > > > I would like to ask you I there is some progress with porting newer > > > > SMBFS / CIFS version to FreeBSD? Did you find Illumos sources as a > > > > possibility where to start porting? > > > Yes. I have the stuff off Illumos-gate, which I think is pretty up-to= -date > > > and I agree that it should be easier than the Apple stuff to port int= o > > > FreeBSD. I don't think it is "straightforward" as someone involved > > > with Illumos said, due to the big differences in VFS/locking, but... > > > > > > Having said the above, I have not done much yet. I've been cleaning u= p > > > NFS stuff, although I am nearly done with that now. > > > I do plan on starting to work on it soon, but have no idea if/when I > > > will have something that might be useful for others. > > > > I'm glad to hear that. > > > > > > We have more and more problems with current state of mount_smbfs. I > > > > would be really glad if "somebody" can do the heroic work of > > > > implementing SMBv2 in FreeBSD. > > > > Maybe it's time to start some fundraising for sponsoring this work? > > > Well, funding isn't an issue for me (I'm just a retired guy who does = this > > > stuff as a hobby). However, if there is someone else who is capable o= f > > > doing it if they are funded, I have no problem with that. > > > I could either help them, or simply stick with working on NFS and lea= ve > > > SMBv23 to them. > > > > > > Sorry, but I cannot report real progress on this as yet, rick > > > > No need to sorry. I really appreciate your endless work on NFS and that= you > > still have kind of interest to try porting SMBv2/3. > > Unfortunately I don't know anybody else trying to do this tremendous wo= rk. > > > > I am working on a from scratch implementation of smbfs. I do not have > any kind of time estimate since it is in my spare time. I chose this > route after spending considerable time looking at Apple and Solaris > implementations and wanting something without all of the legacy 1.0 > crap. I do have a very minimal working FUSE version at this point, but > there is much to do, and even more to abide by the various > specifications. > > I just thought I'd share in case anyone is interested. > > - John I am indeed interested. smbfs is an important feature to have. Let me know if you need help with the fuse parts. -Alan From nobody Wed Jun 5 00:24: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 4Vv7Wh5Jdzz5N4LH for ; Wed, 05 Jun 2024 00:24:48 +0000 (UTC) (envelope-from rick.macklem@gmail.com) Received: from mail-pg1-x52d.google.com (mail-pg1-x52d.google.com [IPv6:2607:f8b0:4864:20::52d]) (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 "WR4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4Vv7Wh1Mt0z4Pb6; Wed, 5 Jun 2024 00:24:48 +0000 (UTC) (envelope-from rick.macklem@gmail.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-pg1-x52d.google.com with SMTP id 41be03b00d2f7-656d8b346d2so4432762a12.2; Tue, 04 Jun 2024 17:24:48 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1717547086; x=1718151886; darn=freebsd.org; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:from:to:cc:subject:date :message-id:reply-to; bh=R3yIZt7vMJGpOX/X8lVrbfZtbPMr95g0CciFsfCojgQ=; b=DRUAYEk4HMKiR/cm+p8UIq7rY+4gREiZtwoDvHhVm5ifwplfqMBby/jucuhCwyxbHT VUNsT8v5mCFWu1IBPhSOonb5p42L2NVLlsJ3I7TbF5k7kTNjcwZfLatEU33Uthc2Kt8v VgI+TW+yiSZCfk7aR/p3ASDf1vy++IvXH0umb8sf0WheCk2EIuRAWdwmg7awZLevM8xR bBx3wEwbwFROC45uhhloowGgWl71Kne5XalXo3jksxLPgOQuUy1saMgIOLTVZzYODC65 Btb3NKL/ABAlniqFp0p3Fi6jnsptse78K0vvaYY1Ta8GEdF7ces6iJw0khzOfJu7o7ry M7OQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1717547086; x=1718151886; h=content-transfer-encoding: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=R3yIZt7vMJGpOX/X8lVrbfZtbPMr95g0CciFsfCojgQ=; b=FZfWylrV/B1TYS2h+e7hQh+IPKcbDTxz9ErE6OOKTf9AQp0zv5RLtIXKcJ5k9GAab8 qjsXGW7po5qX1PuQQ1KM/1lQKcK9WEfGqTKwXK3BOhAdW5yazTibTrgc7i3k9he7BGmS m15v1jNwE/aWGIft0vSbqZHBVZI2o5zCYepmv6O+RwCSZ2KMl3XiQQRHkH0V+ejUzHm7 eb1PyNq0X8Qqe6aT+H1DYD9GNIfxP072JrkU0k6jDG+PmZyE752hzqu1WDtndhvCMlEp dsy5eJ6bLf9BVTHFmEcAL2gV8xXtl5hgVXV4TeiF9D1mSS+TDfA+3UQzXnXGYUEVMo8P a2oA== X-Forwarded-Encrypted: i=1; AJvYcCVWGTvkyQQCFLGLluh2ipHVSDqNKRI9xt3RXqcDoXrKlg+2LsQ1koPP8+9IqtUk8eQ5Xi8Nbq1mt3TWD1M7/BbK3KcvmfF28WDfkLLmnC+cuwl5vL+/H6IkpEBX7Z/0u3Ml X-Gm-Message-State: AOJu0YwjNw7PTxhwfHQYli2C4tnb48PHRQArBr304hYsYovzBtEATJO/ gPbI6W/OTOEhRNVAwP6OSefj//RsbiACOfnvWwQ48eM8dkAIu7SfiCjOsok3kHuX4wOcMCywIIq QMyCy4OxiG8kbfGTuLZXCi5XDhQ3u X-Google-Smtp-Source: AGHT+IH4d3HkPYooJV2fGQ8TyUJhtuKcWbn/aKyf1ELlwC+R0QCSscjYVPYW2slO1vKMMNHVhMl2K2Uh4fM2yEaJBpc= X-Received: by 2002:a17:90a:8b88:b0:2bf:b2b0:c49a with SMTP id 98e67ed59e1d1-2c27db1f872mr1083693a91.25.1717547085963; Tue, 04 Jun 2024 17:24:45 -0700 (PDT) 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: <489849ca-a404-fb54-81d1-d62ea18c5832@FreeBSD.org> <254a0b5e-72d9-f93e-0c49-82b50a35db41@quip.cz> <3bbacbac-9238-f29d-653c-86d13085afe0@quip.cz> <4ea542mqtue7ety23gpgxborpl4brx3fewhgy5p23ozivjzeay@dyk4oxvgs7c5> In-Reply-To: From: Rick Macklem Date: Tue, 4 Jun 2024 17:24:35 -0700 Message-ID: Subject: Re: Deprecating smbfs(5) and removing it before FreeBSD 14 To: Alan Somers Cc: John Hixson , Miroslav Lachman <000.fbsd@quip.cz>, Rick Macklem , David Chisnall , "freebsd-current@freebsd.org" Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable 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)[]; TAGGED_FROM(0.00)[]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US] X-Rspamd-Queue-Id: 4Vv7Wh1Mt0z4Pb6 On Tue, Jun 4, 2024 at 5:18=E2=80=AFPM Alan Somers wr= ote: > > CAUTION: This email originated from outside of the University of Guelph. = Do not click links or open attachments unless you recognize the sender and = know the content is safe. If in doubt, forward suspicious emails to IThelp@= uoguelph.ca. > > > On Tue, Jun 4, 2024 at 3:52=E2=80=AFPM John Hixson = wrote: > > > > On Mon, Jun 27, 2022 at 03:27:54PM +0200, Miroslav Lachman wrote: > > > On 16/06/2022 15:56, Rick Macklem wrote: > > > > Miroslav Lachman <000.fbsd@quip.cz> wrote: > > > > > On 24/01/2022 16:13, Rick Macklem wrote: > > > > > > > > > [...] > > > > > > > > > > > So, I think Mark and Yuri are correct and looking at up to date > > > > > > Illumos sources is the next step. > > > > > > (As I mentioned, porting the Apple sources is beyond what I am > > > > > > willing to attempt.) > > > > > > > > > > > > rick > > > > > > > > > > Hello Rick, > > > > > I would like to ask you I there is some progress with porting new= er > > > > > SMBFS / CIFS version to FreeBSD? Did you find Illumos sources as = a > > > > > possibility where to start porting? > > > > Yes. I have the stuff off Illumos-gate, which I think is pretty up-= to-date > > > > and I agree that it should be easier than the Apple stuff to port i= nto > > > > FreeBSD. I don't think it is "straightforward" as someone involved > > > > with Illumos said, due to the big differences in VFS/locking, but..= . > > > > > > > > Having said the above, I have not done much yet. I've been cleaning= up > > > > NFS stuff, although I am nearly done with that now. > > > > I do plan on starting to work on it soon, but have no idea if/when = I > > > > will have something that might be useful for others. > > > > > > I'm glad to hear that. > > > > > > > > We have more and more problems with current state of mount_smbfs.= I > > > > > would be really glad if "somebody" can do the heroic work of > > > > > implementing SMBv2 in FreeBSD. > > > > > Maybe it's time to start some fundraising for sponsoring this wor= k? > > > > Well, funding isn't an issue for me (I'm just a retired guy who doe= s this > > > > stuff as a hobby). However, if there is someone else who is capable= of > > > > doing it if they are funded, I have no problem with that. > > > > I could either help them, or simply stick with working on NFS and l= eave > > > > SMBv23 to them. > > > > > > > > Sorry, but I cannot report real progress on this as yet, rick > > > > > > No need to sorry. I really appreciate your endless work on NFS and th= at you > > > still have kind of interest to try porting SMBv2/3. > > > Unfortunately I don't know anybody else trying to do this tremendous = work. > > > > > > > I am working on a from scratch implementation of smbfs. I do not have > > any kind of time estimate since it is in my spare time. I chose this > > route after spending considerable time looking at Apple and Solaris > > implementations and wanting something without all of the legacy 1.0 > > crap. I do have a very minimal working FUSE version at this point, but > > there is much to do, and even more to abide by the various > > specifications. > > > > I just thought I'd share in case anyone is interested. Best of luck with it. I never got far into porting the Illumos code. rick > > > > - John > > I am indeed interested. smbfs is an important feature to have. Let > me know if you need help with the fuse parts. > -Alan From nobody Wed Jun 5 08:06:16 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 4VvKmF0BWTz5MK8Q for ; Wed, 05 Jun 2024 08:06:21 +0000 (UTC) (envelope-from SRS0=RKoA=NH=quip.cz=000.fbsd@elsa.codelab.cz) Received: from elsa.codelab.cz (elsa.codelab.cz [94.124.105.4]) (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 4VvKmD57pLz49jF; Wed, 5 Jun 2024 08:06:20 +0000 (UTC) (envelope-from SRS0=RKoA=NH=quip.cz=000.fbsd@elsa.codelab.cz) Authentication-Results: mx1.freebsd.org; none Received: from elsa.codelab.cz (localhost [127.0.0.1]) by elsa.codelab.cz (Postfix) with ESMTP id A5158D789B; Wed, 5 Jun 2024 10:06:17 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=quip.cz; s=private; t=1717574777; bh=0AoyQHUrlqgxeii5VTVBi8LsEvFUTnXOo3px7wRNVN0=; h=Date:Subject:To:Cc:References:From:In-Reply-To; b=LI+Gjp+UigGyw2hqt6b+GsJU23Bleh9UHjGEnV0tqDC0CLf2scXV8GFTTQZt0r8YK Vh9W/NfDDq0moUR/S8A+7jjgcTfCmzjJ0dMkzZNhR/SNES4a6+765lscb6F9F4XTg6 Q+fy1GgnzOkKSr8Iix+XwP1qVZkaGHhbc1bQKewI= Received: from [192.168.145.49] (ip-89-177-27-225.bb.vodafone.cz [89.177.27.225]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by elsa.codelab.cz (Postfix) with ESMTPSA id 8C4C1D788A; Wed, 5 Jun 2024 10:06:16 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=quip.cz; s=private; t=1717574776; bh=0AoyQHUrlqgxeii5VTVBi8LsEvFUTnXOo3px7wRNVN0=; h=Date:Subject:To:Cc:References:From:In-Reply-To; b=4bo47NCavj4DMy2pbmiC07rzG3xVY0qWWqKJWAewjGK/gqdOIz4I5bfLxSJl1+SUY +QJIAB68pvrSffq8r2g1BS2UTV+RvXZEHqaGxXD17t0i6zi2ly6wDn2G+nobRXpPRS TXeBBF/8YtSlIw/JddutM0R/gEjDoGRHdxBQkL0c= Message-ID: Date: Wed, 5 Jun 2024 10:06:16 +0200 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: Deprecating smbfs(5) and removing it before FreeBSD 14 To: John Hixson Cc: Rick Macklem , "freebsd-current@freebsd.org" References: <489849ca-a404-fb54-81d1-d62ea18c5832@FreeBSD.org> <254a0b5e-72d9-f93e-0c49-82b50a35db41@quip.cz> <3bbacbac-9238-f29d-653c-86d13085afe0@quip.cz> <4ea542mqtue7ety23gpgxborpl4brx3fewhgy5p23ozivjzeay@dyk4oxvgs7c5> Content-Language: cs-Cestina From: Miroslav Lachman <000.fbsd@quip.cz> In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit 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:42000, ipnet:94.124.104.0/21, country:CZ] X-Rspamd-Queue-Id: 4VvKmD57pLz49jF On 05/06/2024 01:05, John Hixson wrote: >> >> Thank you for the message. I'm glad someone has the courage to take the >> plunge. Smbfs is still very important to me. In a heterogeneous environment >> it is still the most common way to share data between systems. >> Are you planning the final version as a kernel module, or will the final >> version be via FUSE? I have had bad experiences with FUSE in the past with >> stability and performance. > > The final version will be a kernel module. It will also be BSD > licensed. I am not an expert at the VFS layer so I want to get the stack > ironed out in FUSE before moving it into kernel space. This is really good news. I can't help with the code, but once you get something I can test, let me know. I'd be happy to help with testing. Best regards Miroslav Lachman From nobody Wed Jun 5 08:35:17 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 4VvLPl3kB7z5MNkT for ; Wed, 05 Jun 2024 08:35:23 +0000 (UTC) (envelope-from yuri@aetern.org) Received: from fout5-smtp.messagingengine.com (fout5-smtp.messagingengine.com [103.168.172.148]) (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 4VvLPk5wzHz4Hl4 for ; Wed, 5 Jun 2024 08:35:22 +0000 (UTC) (envelope-from yuri@aetern.org) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=aetern.org header.s=fm1 header.b=jWRBtxbZ; dkim=pass header.d=messagingengine.com header.s=fm1 header.b=Tw9xh3yo; dmarc=pass (policy=none) header.from=aetern.org; spf=pass (mx1.freebsd.org: domain of yuri@aetern.org designates 103.168.172.148 as permitted sender) smtp.mailfrom=yuri@aetern.org Received: from compute2.internal (compute2.nyi.internal [10.202.2.46]) by mailfout.nyi.internal (Postfix) with ESMTP id 18C451380182 for ; Wed, 5 Jun 2024 04:35:22 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute2.internal (MEProxy); Wed, 05 Jun 2024 04:35:22 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=aetern.org; h=cc :content-transfer-encoding:content-type:content-type:date:date :from:from:in-reply-to:message-id:mime-version:reply-to:subject :subject:to:to; s=fm1; t=1717576522; x=1717662922; bh=vmsIRZojgu xChGVC3NbQ9pzzRAE7i3mLKKIWjxE1TfM=; b=jWRBtxbZM/0noFww5v6h5fqPom TMVbqg7k72asmO2ayFEu3c06ICuZHs7WQBH/q2HEE+g9JRWH7SLgMslsIoWoqUnP njoKreBsmVwQFyZG25OjYZenOPOK3ufkyDOd1oja1bcOIel/mnG0z0bQMTRrWjH0 lD6/KOYW6UbfvOgwTU1RrTQ9fgMSRaU7U0RXPKEd/ApnD1vN4APjZEzFW0B/+/nn ekrhnee4C2pudhBidHdv9qTIOK8YRdlrKd6eXjt/aFpEA9xqL3a0Da4+c2ClSdF+ Mzr9Jnj8Z9BKCFzofPRnHpA60gyMmMy/NLFSx1Hk0eNRwtHEUB0oJZ/HxD0g== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding: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= fm1; t=1717576522; x=1717662922; bh=vmsIRZojguxChGVC3NbQ9pzzRAE7 i3mLKKIWjxE1TfM=; b=Tw9xh3yoL4V6gnnenpV8EECjxe1z7Nny4IY/b1PZwVII LsobINFTYn4kwhcL9Ozi1NeBo0kuJAtrF7VAoGbiprpE5Lgo4nvJMUU0iRzx9y1t ch1ohUIK+6+tA3LmGmwgeDMlM5ZFRw55NLpgSzNqYy7TJrq1LfqVTpMgPSD0AtDO 3UvBgnktc3OLAzjZEiK5gHrFJHOH+IOaZqaaFegNNrVRNRaDYmvYZsKAcPQ50CO+ ZSTF6Xs53ST7dOy5bjvcz1xdfooSLB2/frRTzbfw9xBkowrKgyshipd11ue7ZkuW xMsaMGnoG6dBuYZ4u2r2rkScJmQheEZ4+oHES+7y0Q== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvledrvdeliedgtdeiucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucenucfjughrpefkffggfgfvhffutgfgsehtjeertd dtvdejnecuhfhrohhmpegjuhhrihcurfgrnhhkohhvuceohihurhhisegrvghtvghrnhdr ohhrgheqnecuggftrfgrthhtvghrnhepvedvheduueffvdfgvdetleelveeugeevuedvvd evgfefkedvveehuddutdeugfdvnecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghm pehmrghilhhfrhhomhephihurhhisegrvghtvghrnhdrohhrgh X-ME-Proxy: Feedback-ID: i0d79475b:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA for ; Wed, 5 Jun 2024 04:35:20 -0400 (EDT) Message-ID: <5cdddd23-90c1-4f6b-8af1-80f7621ac00c@aetern.org> Date: Wed, 5 Jun 2024 15:35:17 +0700 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 Content-Language: en-US To: current@freebsd.org From: Yuri Pankov Subject: 41dfea24eec panics during ata attach on ESXi VM Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Spamd-Bar: / X-Rspamd-Pre-Result: action=no action; module=multimap; Matched map: local_wl_from X-Spamd-Result: default: False [-0.99 / 15.00]; DMARC_POLICY_ALLOW(-0.50)[aetern.org,none]; R_SPF_ALLOW(-0.20)[+ip4:103.168.172.128/27:c]; R_DKIM_ALLOW(-0.20)[aetern.org:s=fm1,messagingengine.com:s=fm1]; RCVD_IN_DNSWL_LOW(-0.10)[103.168.172.148:from]; XM_UA_NO_VERSION(0.01)[]; ASN(0.00)[asn:209242, ipnet:103.168.172.0/24, country:US]; FREEFALL_USER(0.00)[yuri]; ARC_NA(0.00)[]; local_wl_from(0.00)[yuri@aetern.org]; MLMMJ_DEST(0.00)[current@freebsd.org]; DWL_DNSWL_NONE(0.00)[messagingengine.com:dkim]; PREVIOUSLY_DELIVERED(0.00)[current@freebsd.org]; DKIM_TRACE(0.00)[aetern.org:+,messagingengine.com:+] X-Rspamd-Queue-Id: 4VvLPk5wzHz4Hl4 After updating to 41dfea24eec (GENERIC-NODEBUG), ESXi VM started to panic while attaching atapci children. I was unable to grab original boot panic data ("keyboard" dead), but was able to boot with hint.ata.0.disabled=1, hint.ata.1.disabled=1, and `devctl enable ata0` reproduced the issue: ata0: at channel 0 on atapci0 Fatal trap 12: page fault while in kernel mode cpuid = 11; apic id = 11 fault virtual address = 0x54 fault code = supervisor read data, page not present instruction pointer = 0x20:0xffffffff80821bb2 stack pointer = 0x28:0xfffffe019330d720 frame pointer = 0x28:0xfffffe019330d750 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, long 1, def32 0, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = 99030 (devctl) rdi: fffff80002039900 rsi: fffff80002039900 rdx: fffff800beb9c180 rcx: fffff80001f1a000 r8: fffff80002027d20 r9: fffffe0035d28900 rax: 0000000000000000 rbx: fffff80002039900 rbp: fffffe019330d750 r10: fffff80030b86000 r11: fffffe019330da4c r12: 0000000000000001 r13: 0000000000000000 r14: fffff80002038400 r15: fffff800beb9c180 trap number = 12 panic: page fault cpuid = 11 time = 1717575820 KDB: stack backtrace: db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame 0xfffffe019330d410 vpanic() at vpanic+0x13f/frame 0xfffffe019330d540 panic() at panic+0x43/frame 0xfffffe019330d5a0 trap_fatal() at trap_fatal+0x40b/frame 0xfffffe019330d600 trap_pfault() at trap_pfault+0x46/frame 0xfffffe019330d650 calltrap() at calltrap+0x8/frame 0xfffffe019330d650 --- trap 0xc, rip = 0xffffffff80821bb2, rsp = 0xfffffe019330d720, rbp = 0xfffffe019330d750 --- pci_activate_resource() at pci_activate_resource+0x22/frame 0xfffffe019330d750 bus_generic_rman_alloc_resource() at bus_generic_rman_alloc_resource+0xee/frame 0xfffffe019330d790 nexus_alloc_resource() at nexus_alloc_resource+0x99/frame 0xfffffe019330d7f0 acpi_alloc_resource() at acpi_alloc_resource+0x84/frame 0xfffffe019330d8b0 acpi_pcib_acpi_alloc_resource() at acpi_pcib_acpi_alloc_resource+0x9d/frame 0xfffffe019330d920 ata_pci_alloc_resource() at ata_pci_alloc_resource+0x2bd/frame 0xfffffe019330d9a0 bus_alloc_resource() at bus_alloc_resource+0x98/frame 0xfffffe019330da00 ata_attach() at ata_attach+0x322/frame 0xfffffe019330dad0 device_attach() at device_attach+0x3ac/frame 0xfffffe019330db20 devctl2_ioctl() at devctl2_ioctl+0x56e/frame 0xfffffe019330dbf0 devfs_ioctl() at devfs_ioctl+0xcb/frame 0xfffffe019330dc40 vn_ioctl() at vn_ioctl+0xce/frame 0xfffffe019330dcb0 devfs_ioctl_f() at devfs_ioctl_f+0x1e/frame 0xfffffe019330dcd0 kern_ioctl() at kern_ioctl+0x255/frame 0xfffffe019330dd40 sys_ioctl() at sys_ioctl+0xff/frame 0xfffffe019330de00 amd64_syscall() at amd64_syscall+0x115/frame 0xfffffe019330df30 fast_syscall_common() at fast_syscall_common+0xf8/frame 0xfffffe019330df30 --- syscall (54, FreeBSD ELF64, ioctl), rip = 0x2d04d93b28fa, rsp = 0x2d04d84df398, rbp = 0x2d04d84df450 --- Uptime: 2m6s Dumping 1562 out of 32725 MB:..2%..11%..21%..31%..41%..51%..61%..71%..81%..91% From nobody Wed Jun 5 08:48:23 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 4VvLjK3wNvz5MBQZ for ; Wed, 05 Jun 2024 08:48:53 +0000 (UTC) (envelope-from 6yearold@gmail.com) Received: from mail-vk1-f179.google.com (mail-vk1-f179.google.com [209.85.221.179]) (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 "WR4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4VvLjK2CLLz4Ksn; Wed, 5 Jun 2024 08:48:53 +0000 (UTC) (envelope-from 6yearold@gmail.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-vk1-f179.google.com with SMTP id 71dfb90a1353d-4eb12b7702cso1226282e0c.3; Wed, 05 Jun 2024 01:48:53 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1717577332; x=1718182132; h=content-transfer-encoding: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=2bR4ptFOr+Gh5xzl1hTy4hl9Ag5ZPCa9vzUU8SCBMls=; b=DbQ/eloDga4uWAs7/vnIMHRMqxyc6Z4DHw+hP1K1Hlt7+sirdBKjsbfpEVdGz+ENeg NpzI2dleMeoMBW9cj15dmser7CUQGqcqVCNE+EJcBwsNmy/u7QenJ/xLxnHIfCBoXqJL LgZ23ecPI9nN40g0zEPjW+FWFspSgjhIcI42rob+Ha8V//SrGFPs7cVHQyS8lDM23P38 RjvkrvcwmvUitnrXv1fkGsUz//BFdL9mf97ViGYUCIGrZ9e1fZ0ODOmkp/QME9rsutRr IjQMH4zUNjTFz8/1OsMEAX/Yb46DgSKNp7Oo7dbt2FbeCDVJeECk1hrP/X0+4Gy7Mg5w O8ZA== X-Forwarded-Encrypted: i=1; AJvYcCWWqbI3j0h9751Q3bJSiuvo55yyKhWPjWKpOY6OpTs2Otq3vui9iNEAgJYInp9BAARhgMpIND7S8cmar7wmbndN3FoNuTdGeijij9rUpHEKY8LZlxYE/8KHIxHTooli3uSu X-Gm-Message-State: AOJu0YzVB8anBlKnNC/GfeTrIzl+gfhVAqVk4Ak2Z8LqMXC6+BNnHyT6 MuvQiWVCxOjlRSM3M9DSGO/1q2wFEuNOGw43QT791vR4wDY9MLvmtAQ5Ro7vdU0= X-Google-Smtp-Source: AGHT+IFde0rv8NziP7wgJ+xrqVwkZMn9BWcAY2W/yUSHcJa1PMrBmmFGBmOiMpkG9h/byijG5/hytA== X-Received: by 2002:a67:fd90:0:b0:48b:a757:ff7 with SMTP id ada2fe7eead31-48c04a67c43mr1964435137.29.1717577331914; Wed, 05 Jun 2024 01:48:51 -0700 (PDT) Received: from mail-vk1-f174.google.com (mail-vk1-f174.google.com. [209.85.221.174]) by smtp.gmail.com with ESMTPSA id ada2fe7eead31-48bd15e9a04sm1674715137.5.2024.06.05.01.48.51 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Wed, 05 Jun 2024 01:48:51 -0700 (PDT) Received: by mail-vk1-f174.google.com with SMTP id 71dfb90a1353d-4eb007a9f6fso1915267e0c.2; Wed, 05 Jun 2024 01:48:51 -0700 (PDT) X-Forwarded-Encrypted: i=1; AJvYcCVhcafPp4DLYetO0DNmOzxT9hw6h3sxRxKtijSMmGgKMHHI36E7obQLb9tAIWCWKZWzbZZ+/IZep2OAO+cSgFhXvba9Xm6TzpFxP90PD2q6/DoPH89x3GmTYl36bmBZzKD6 X-Received: by 2002:ac5:c971:0:b0:4d3:3846:73bb with SMTP id 71dfb90a1353d-4eb3a4191fcmr2210466e0c.7.1717577331466; Wed, 05 Jun 2024 01:48:51 -0700 (PDT) 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: <489849ca-a404-fb54-81d1-d62ea18c5832@FreeBSD.org> <254a0b5e-72d9-f93e-0c49-82b50a35db41@quip.cz> <3bbacbac-9238-f29d-653c-86d13085afe0@quip.cz> <4ea542mqtue7ety23gpgxborpl4brx3fewhgy5p23ozivjzeay@dyk4oxvgs7c5> In-Reply-To: <4ea542mqtue7ety23gpgxborpl4brx3fewhgy5p23ozivjzeay@dyk4oxvgs7c5> From: Gleb Popov Date: Wed, 5 Jun 2024 11:48:23 +0300 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: Deprecating smbfs(5) and removing it before FreeBSD 14 To: John Hixson Cc: Miroslav Lachman <000.fbsd@quip.cz>, Rick Macklem , David Chisnall , "freebsd-current@freebsd.org" Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable 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:209.85.128.0/17, country:US] X-Rspamd-Queue-Id: 4VvLjK2CLLz4Ksn On Wed, Jun 5, 2024 at 12:52=E2=80=AFAM John Hixson w= rote: > > I am working on a from scratch implementation of smbfs. I do not have > any kind of time estimate since it is in my spare time. I chose this > route after spending considerable time looking at Apple and Solaris > implementations and wanting something without all of the legacy 1.0 > crap. I do have a very minimal working FUSE version at this point, but > there is much to do, and even more to abide by the various > specifications. > > I just thought I'd share in case anyone is interested. > > - John Thanks for sharing. We're building a FreeBSD based product and SMB2/3 support is very important to us. Maybe we can combine our efforts on this matter? I also contacted the FreeBSD Enterprise Working Group about this. The Greg's reply was > The verbal offer to donate an up to date fork of this still stands, but t= he timing remains unclear. I continue asking. It is still unclear to me if the code is already written by some party and now the negotiation is going on about licensing it as BSD. From nobody Wed Jun 5 20:48:41 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 4Vvfgv18GYz5M9mj for ; Wed, 05 Jun 2024 20:48:43 +0000 (UTC) (envelope-from jhb@FreeBSD.org) Received: from smtp.freebsd.org (smtp.freebsd.org [96.47.72.83]) (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 "smtp.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4Vvfgv0RQWz4qsG; Wed, 5 Jun 2024 20:48:43 +0000 (UTC) (envelope-from jhb@FreeBSD.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1717620523; 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=uojEVWvfsFpod8opRh+NVgUikJjBj8yEJPchMRMO5Mw=; b=X5uqQbgf1zeetRingIjFOc/eJa+mKzX3AysoFbS2rui7PIhzHuXCmpY/Nz4HcHsbwPTgLl 3LQsbr9d6upFdW4yUjyS3Ec2w6V2l/WAC+43Xyz6Y8NETTRw8yLenRzlaOJprojnlXEx2S eNfm6J5LQKKUuSi9THDqoq14wv8rM9ae2u6bEu3jrjIeWPi6WjleKOXExvQ/DPMR5+J2xf /TSJr2Q7EKWFcwIPDrdei2r1iwKMmHKiWZ0rc7fHm8UxN07XQe/oazMxZbtyWYmd9weFe9 HU0N8XIte/u1yrZj6RfC9oBdFgOPs17Js93sM7danZkjj15oFT4EMVL/ibPHig== ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1717620523; a=rsa-sha256; cv=none; b=rVibePvlewAfH2Z3X1GptRWUj1bjzvY/2tpRAHLs60c4XO46/pbrvcOO76Os7De+NWzKG1 1uQEmPBGh+Bg1rQ1AIClzZitr0tb6xd/pH957ZtXzqWwGH4+1PUKnbOTWBqlQTUqCm4Ihb MCu7FQqHW8tXV1Jdp3fBLNKBv32LiduOhypdW+dWwDma2panHa5yQDTT2Xq1Gk/XxXJ7DE 0/gF2ufq1OKI1rIuf4IcDatm+KKhZja3CGPpreP6QA2LWmbXXzSMlsKxI3J/qXlVSanc/9 YmWCZPfx5AM0VDLzf2yr6osQnvigxzdEBEW6CLwv2TFs+xqTV2K0st9XZbHtNA== ARC-Authentication-Results: i=1; mx1.freebsd.org; none ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1717620523; 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=uojEVWvfsFpod8opRh+NVgUikJjBj8yEJPchMRMO5Mw=; b=ZaeS3mFZsemQVBmWvJ73hMaU8uKCBm8avwSTyRbQCk3Y3d1I6Ig9OGuVdwFQd9MsmHxRSM NkXD4Iirv+nLlgmXlfgJgCsixehBWjCc2zYpUiOqPvtIFiAPKOifmv91jdxT4nRI3fOBle itNNKNt0P8cSah4BV7ALipXXZUqve9DYhx3DMZeAzjDkEGP+JYObk4+PaOurzTwMKBNUJj 830i8LizsT95BjYDOLjuYLPeaemcdWUriUaFGGCPjDCCzGxMKWyjOaAhZf9NCgGywfeEkJ b+8SJC7hqEX7PIdHcM9cP7BZMXALFAjxaNIB9qp+mXaxlOV3chWmSZtng078cQ== Received: from [IPV6:2601:644:937f:4c50:e0fb:ab3b:bf07:f04] (unknown [IPv6:2601:644:937f:4c50:e0fb:ab3b:bf07:f04]) (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 did not present a certificate) (Authenticated sender: jhb) by smtp.freebsd.org (Postfix) with ESMTPSA id 4Vvfgt5DBsz14ky; Wed, 5 Jun 2024 20:48:42 +0000 (UTC) (envelope-from jhb@FreeBSD.org) Message-ID: Date: Wed, 5 Jun 2024 13:48:41 -0700 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: 41dfea24eec panics during ata attach on ESXi VM Content-Language: en-US To: Yuri Pankov , current@freebsd.org References: <5cdddd23-90c1-4f6b-8af1-80f7621ac00c@aetern.org> From: John Baldwin In-Reply-To: <5cdddd23-90c1-4f6b-8af1-80f7621ac00c@aetern.org> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit On 6/5/24 4:35 AM, Yuri Pankov wrote: > After updating to 41dfea24eec (GENERIC-NODEBUG), ESXi VM started to > panic while attaching atapci children. I was unable to grab original > boot panic data ("keyboard" dead), but was able to boot with > hint.ata.0.disabled=1, hint.ata.1.disabled=1, and `devctl enable ata0` > reproduced the issue: > > ata0: at channel 0 on atapci0 This should be fixed now by commit 56b822a17cde5940909633c50623d463191a7852. Sorry for the breakage. -- John Baldwin From nobody Sat Jun 8 22:14:56 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 4VxXSK09Gpz5NL4p for ; Sat, 08 Jun 2024 22:15:13 +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 4VxXSG48YHz3wsv; Sat, 8 Jun 2024 22:15:10 +0000 (UTC) (envelope-from junchoon@dec.sakura.ne.jp) Authentication-Results: mx1.freebsd.org; dkim=fail ("headers rsa verify failed") header.d=dec.sakura.ne.jp header.s=s2405 header.b=VaHf8WG6; dmarc=pass (policy=none) header.from=dec.sakura.ne.jp; spf=pass (mx1.freebsd.org: domain of junchoon@dec.sakura.ne.jp designates 153.125.133.21 as permitted sender) smtp.mailfrom=junchoon@dec.sakura.ne.jp Received: from kalamity.joker.local (123-1-21-232.area1b.commufa.jp [123.1.21.232]) (authenticated bits=0) by www121.sakura.ne.jp (8.17.1/8.17.1/[SAKURA-WEB]/20201212) with ESMTPA id 458MEuGE009533; Sun, 9 Jun 2024 07:14:56 +0900 (JST) (envelope-from junchoon@dec.sakura.ne.jp) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=dec.sakura.ne.jp; s=s2405; t=1717884899; bh=x4N+GsLX4hEcjv6SYV5gph4AVHWOPBpTSBMkmd//sMo=; h=Date:From:To:Cc:Subject:In-Reply-To:References; b=VaHf8WG6qevmYvvqwwtI8tPPv48ke9+qgb2eBOwLOC5uIV9zZxKH40k6Fxl0pDW6R hkYDk8uImGYm+5jfrkdDbN50Hl6wVt9wI1CJYIMmH+fnt4/e2BR5scwFvqZkZZ7Ajy /dCAw9PC24kNf5Iems9I0oYSmkBR/f+nKeMPbE6o= Date: Sun, 9 Jun 2024 07:14:56 +0900 From: Tomoaki AOKI To: John Hixson Cc: Miroslav Lachman <000.fbsd@quip.cz>, Rick Macklem , David Chisnall , "freebsd-current@freebsd.org" Subject: Re: Deprecating smbfs(5) and removing it before FreeBSD 14 Message-Id: <20240609071456.bcced576c22276ea6baccaa3@dec.sakura.ne.jp> In-Reply-To: <4ea542mqtue7ety23gpgxborpl4brx3fewhgy5p23ozivjzeay@dyk4oxvgs7c5> References: <489849ca-a404-fb54-81d1-d62ea18c5832@FreeBSD.org> <254a0b5e-72d9-f93e-0c49-82b50a35db41@quip.cz> <3bbacbac-9238-f29d-653c-86d13085afe0@quip.cz> <4ea542mqtue7ety23gpgxborpl4brx3fewhgy5p23ozivjzeay@dyk4oxvgs7c5> 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-Spamd-Bar: -- X-Spamd-Result: default: False [-2.20 / 15.00]; NEURAL_HAM_MEDIUM(-0.99)[-0.994]; NEURAL_HAM_LONG(-0.82)[-0.821]; DMARC_POLICY_ALLOW_WITH_FAILURES(-0.50)[]; MV_CASE(0.50)[]; R_SPF_ALLOW(-0.20)[+ip4:153.125.133.16/28]; NEURAL_HAM_SHORT(-0.18)[-0.183]; MIME_GOOD(-0.10)[text/plain]; ONCE_RECEIVED(0.10)[]; R_DKIM_REJECT(0.00)[dec.sakura.ne.jp:s=s2405]; DMARC_POLICY_ALLOW(0.00)[dec.sakura.ne.jp,none]; RCVD_TLS_LAST(0.00)[]; FROM_HAS_DN(0.00)[]; HAS_ORG_HEADER(0.00)[]; TO_DN_EQ_ADDR_SOME(0.00)[]; TO_DN_SOME(0.00)[]; MIME_TRACE(0.00)[0:+]; DKIM_TRACE(0.00)[dec.sakura.ne.jp:-]; ASN(0.00)[asn:7684, ipnet:153.125.128.0/18, country:JP]; ARC_NA(0.00)[]; TO_MATCH_ENVRCPT_SOME(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; RCVD_COUNT_ONE(0.00)[1]; MLMMJ_DEST(0.00)[freebsd-current@freebsd.org]; RCVD_VIA_SMTP_AUTH(0.00)[]; MID_RHS_MATCH_FROM(0.00)[]; RCPT_COUNT_FIVE(0.00)[5] X-Rspamd-Queue-Id: 4VxXSG48YHz3wsv On Tue, 4 Jun 2024 14:52:25 -0700 John Hixson wrote: > On Mon, Jun 27, 2022 at 03:27:54PM +0200, Miroslav Lachman wrote: > > On 16/06/2022 15:56, Rick Macklem wrote: > > > Miroslav Lachman <000.fbsd@quip.cz> wrote: > > > > On 24/01/2022 16:13, Rick Macklem wrote: > > > > > > > [...] > > > > > > > > > So, I think Mark and Yuri are correct and looking at up to date > > > > > Illumos sources is the next step. > > > > > (As I mentioned, porting the Apple sources is beyond what I am > > > > > willing to attempt.) > > > > > > > > > > rick > > > > > > > > Hello Rick, > > > > I would like to ask you I there is some progress with porting newer > > > > SMBFS / CIFS version to FreeBSD? Did you find Illumos sources as a > > > > possibility where to start porting? > > > Yes. I have the stuff off Illumos-gate, which I think is pretty up-to-date > > > and I agree that it should be easier than the Apple stuff to port into > > > FreeBSD. I don't think it is "straightforward" as someone involved > > > with Illumos said, due to the big differences in VFS/locking, but... > > > > > > Having said the above, I have not done much yet. I've been cleaning up > > > NFS stuff, although I am nearly done with that now. > > > I do plan on starting to work on it soon, but have no idea if/when I > > > will have something that might be useful for others. > > > > I'm glad to hear that. > > > > > > We have more and more problems with current state of mount_smbfs. I > > > > would be really glad if "somebody" can do the heroic work of > > > > implementing SMBv2 in FreeBSD. > > > > Maybe it's time to start some fundraising for sponsoring this work? > > > Well, funding isn't an issue for me (I'm just a retired guy who does this > > > stuff as a hobby). However, if there is someone else who is capable of > > > doing it if they are funded, I have no problem with that. > > > I could either help them, or simply stick with working on NFS and leave > > > SMBv23 to them. > > > > > > Sorry, but I cannot report real progress on this as yet, rick > > > > No need to sorry. I really appreciate your endless work on NFS and that you > > still have kind of interest to try porting SMBv2/3. > > Unfortunately I don't know anybody else trying to do this tremendous work. > > > > I am working on a from scratch implementation of smbfs. I do not have > any kind of time estimate since it is in my spare time. I chose this > route after spending considerable time looking at Apple and Solaris > implementations and wanting something without all of the legacy 1.0 > crap. I do have a very minimal working FUSE version at this point, but > there is much to do, and even more to abide by the various > specifications. > > I just thought I'd share in case anyone is interested. > > - John Hi! Thanks for popping in. As others already commented, this is a long awaited feature. As I've already raised a white flag to port darwin implementation, maybe I cannot help on coding, but I'd be happy to test once something to test is available. # I tried years ago with a bit of hope that the darwin code could be almost # a drop-in replacement, but it was clearly beyond me. Too many macros to # look for actual codes to see what for, functions etc which were incompatible # with FreeBSD SMB1 implementation. -- Tomoaki AOKI