From nobody Mon Dec 16 00:03: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 4YBKtB2ZF3z5gX7R for ; Mon, 16 Dec 2024 00:04:02 +0000 (UTC) (envelope-from marklmi@yahoo.com) Received: from sonic314-20.consmr.mail.gq1.yahoo.com (sonic314-20.consmr.mail.gq1.yahoo.com [98.137.69.83]) (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) by mx1.freebsd.org (Postfix) with ESMTPS id 4YBKt90t9Dz54mq for ; Mon, 16 Dec 2024 00:04:01 +0000 (UTC) (envelope-from marklmi@yahoo.com) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=yahoo.com header.s=s2048 header.b=Ur1Erm9w; spf=pass (mx1.freebsd.org: domain of marklmi@yahoo.com designates 98.137.69.83 as permitted sender) smtp.mailfrom=marklmi@yahoo.com; dmarc=pass (policy=reject) header.from=yahoo.com DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1734307439; bh=u3vsgOkGhpjAtOWN2CNHiEvYTDPd4wbGj/8E7Y4b6WA=; h=From:Subject:Date:To:References:From:Subject:Reply-To; b=Ur1Erm9wVon53uLYLn5owuXxiaazZD2eE4i5rImvYeu/D2Xg8bDqeiZZaXvDVo/w4fZlsB83TsSdtXhSoN6bxnJnnB4jEK+K2PeZPGcEOoq8n2xl+Nu0VUp/c87KZtNftZ+ldN68euIB9PEEBX5AYQHlLcEO0mi7KJ1P1k51o26IaY9PMzF3eM12z9rZAkfK6Qo7HO0TKNJwOesVdqIQcgnZtQY0057QssgQUkvzLh9hSv7VPBwb34DMQwaCLhJf8teJhMMl/TvhJ3qBx7nrCKGws26tOkuUOZK2W180892WMqRGQMXHyZtioyW7x3xdjzxtrf1xFOfMmcY1tOl7KQ== X-SONIC-DKIM-SIGN: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1734307439; bh=FYzGvN/UsrYZf+tv51tkYTwM9ErXatjWb1tCstHu9cU=; h=X-Sonic-MF:From:Subject:Date:To:From:Subject; b=hRCepPEHbSuDPPhwhWsq82lF0ZZFZ1imqq0iRHkvsbHPlyQzfCmZluVwgv0W4cf/knB5xJxkQ30y6yBabeepi+UiYhH+4/ZbZlV8m3NO4i4WkOypc00jAqiFTFtoVoAlcep7iiZJw/4dxtTDIQfQPZao2TLH3EEXMTRHiNZU0q8+VkGtR2izMATsrwco8iSlyaEvGdHgkqshGI8yIIIovwd2hWKZjzHIoozcfA1a629yFi/JugWZ5dUiRlfy3jqfq3W2GqAMkgJz1RplRizxDnGcCukLu7dnYHPgG3gMQlD3MkSXP7B0nfhxoEYWMRqFV9I8uNd0f+87+sdfplhTgg== X-YMail-OSG: tfPZRFAVM1kHkKW9_0TojoL5O9B31AaKIAxbtcDS6yaREpc0Kx7hC8cFQ1lLYFL LsdANrKekQiRVsWu6zX4dg3ulu.tuxvwKa1TTS4Fs9iImfS5C9b6ZqczjaeJ6i5UL3jOzjSRsCBr 6GzgGJHD07a4hQL7qcATTmgBp4gwHEezkXNTq5zBD4y7A8Tfk_.fJqqi8SxSg5PWn1hn7jDUqneD frwXvhmlko4QxsyqJcuN7omWG9KlcDcV4dIkK2P5oXKgYty25sv5jhbMZ4KhzAod85sKUlKdK4G7 3lsyUil6WdbdDgyf.Dd7DYYABNV8yiV1M_iBBx5zFdsufevVxUac7EnitTl9K9IZdePv03GmFEhO mH2V5Xj8kibBV2mX2E_sazmyr3bhLkIE8XPM.xSou2Hh9w2IHHGUA_kUx1oF1hzXvHtU9H_qYXKF 6_mc4YpyMDiqIQa1nAJuDEONPLfsawo8noZEHwSytGiAm9wZ9zSgAWrVf5ID2XaetUl7BeH8OUGg UxZ44Z5wPaV_wmaGrMMyek5cNAuzNecnZFFU_wxc1yknc5YVjJK_TME8CUYesimRuYyBSYvuOr7C x26UJ5P7.ImOVirVXuMUfVqedbFldmVbqt4LVsJyu7p76RTllqdOlXtPdFzdmppxrjDK_WuEK9r_ LEGpRm7lFVi.5Gk5qbVH9ePf3tmojihljQcse5qETd20Iqlqx98JsmSFfQ5CLM2S3RjPU4ovkRBu 2579M9pgoT7NnCf0spFgFAQNSQpF7VnJHwD0WyH.qttdQvTF1T_7mKVnCR7jHtk0hIbnr7IhsAUR t_n1s49dfCmRuuWLSIFCyKjjzjT2YGEtOGZqI6C8w6VViTU7yLCdpPhw29RMn5bnuZ3.0p9P72a_ C5Bf0Ahk5KIPoRKe.dzRIFp3Mk8yzyKd3FVgMfu3YYZvhVGRWrTyfNUDb6naEWIJOikBP7ssYWZU AIMEZVlZpGOZUXPlVV1pbOz0g0hHugNo7kU.1_p3kIRsFxh9RGK2Lvx6UrNdgpWZgIHmLOdgV8vy F.zHC_NbBd_RdFYHRt_zNWB1H5koOW83kn3oat3N9XHL8FCDfTM1y2xlJJaSrVVCRybkKV7KL.Ud 5fnwORGMmuQkdHLGOz5iKexehtT6SICkQ9NL7jkT3RA0ATD4hgqjONwg6VlK.eA2umw6oBrX_1DV QNGbn8Gt0S9Yir5d6Q9KV_vaHBWjOnXGdDAeEOaF04kq6kWpkptKLZrB18gYtYbsSGmXEGglJEv4 jxQynq.CaFFB8kJCTcCoVOOO7_Ljgsz976HeHwgYp1xIM_0Y5f_opRAm0UYu.kXG7UbmCD_8OLR_ VNpllF0z2pqRUT5Lm9V7eXkYC6LfYA63dGZwSrck5yS1ZZ2R74eGyw4QzixBNDUEA_H9V8O4B7dY 6lCurx9vtmeyhAYM18m11h.nVcnP5WF15Qje2irNZV5Z8T4kci9Fd.pGX.FyPUS5a53pRTm2GrE7 tbchXixuxT5kz7Zk4FbKZwUelBrFoHbzKAXByfkfhT0dZWYcUNUldZO29EVHrWEf0jH60PKXFt50 1p.32YLRSKtMfS4XzwAciLJWrHQDzUO9iQZxpPtG6ZPWg69wHvMZyJ3Ob6Wq73o4aWX_Ssx8m.Ps BIHn5bvcUYJuDAGlveM5tQ3dZEK_3ee8BgRRmIuhMtgh5pAoicCXO0Kthky3c1BRuEf1LU8fgdJM Rsgl_EYo2Ta1UemlgmoMEBLLousHVkW8wwiOJOHGW9_f2.GEByAJJGBWwG77u6wLWnPaz76A0_gd nYG6Jb_Xh5jt8WNTmWx0f2qWtOArWwSqn_xilKuLSjEO5t7Xzf6tX5tuZPFs6hI2G_jNttpSkARf zlLaksk9C6qd8RbH2OcgxLXmlle.jKnYHe3eScqhbfjzQUsHZHCFcAJ_RgQYE2wxjW_qZ4S6K3ot XUn1xhnfxEbIi_f9S1z.hTYfOjHb4ubsugh2wUnVeJ44rdvx15Mwdy5yNRz55ECAuKZNXd1ayuz8 4C.VCjKo0ZmRZsqH6cskt5Q.EAnJzWaAxhS9sSO3Z44Lt9mYzdBP52SiejhkmwtObziHOqyZvbrY OofIPQoj6vZXgJxgHdTJRb4D9J0LEahkp1vjaQNi.E3ikPBUh8hPn5FoAJXm1T2Q5HwH6fRw_1r. xkD4yDo2kY4IUJzUL72z50oKo4qO_xtMJxMtOUErHBMPPROM0grmYbxY7YkCEvce8rBPU3wl.8cW iM0z7xCzlrbPMzJl9sqclrpRMTRM- X-Sonic-MF: X-Sonic-ID: 355063b9-6205-4294-826e-26fe27e39f49 Received: from sonic.gate.mail.ne1.yahoo.com by sonic314.consmr.mail.gq1.yahoo.com with HTTP; Mon, 16 Dec 2024 00:03:59 +0000 Received: by hermes--production-gq1-5dd4b47f46-5qmz7 (Yahoo Inc. Hermes SMTP Server) with ESMTPA ID 2d2f7e71c4d8b929c6d109c5f62268cd; Mon, 16 Dec 2024 00:03:56 +0000 (UTC) From: Mark Millard Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@FreeBSD.org Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3826.300.87.4.3\)) Subject: What kind of code might generate amd64 addressses like 0xFFFFF80000000007 or be based on 0xFFFFF80000000000 ? Message-Id: <65B0673C-287A-47E5-A732-17CC5EEE3350@yahoo.com> Date: Sun, 15 Dec 2024 16:03:42 -0800 To: FreeBSD Current , FreeBSD-STABLE Mailing List , freebsd-hackers , freebsd-amd64@freebsd.org X-Mailer: Apple Mail (2.3826.300.87.4.3) References: <65B0673C-287A-47E5-A732-17CC5EEE3350.ref@yahoo.com> X-Spamd-Result: default: False [-2.50 / 15.00]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; SUBJECT_ENDS_QUESTION(1.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_SHORT(-1.00)[-1.000]; MV_CASE(0.50)[]; DMARC_POLICY_ALLOW(-0.50)[yahoo.com,reject]; R_DKIM_ALLOW(-0.20)[yahoo.com:s=s2048]; R_SPF_ALLOW(-0.20)[+ptr:yahoo.com]; MIME_GOOD(-0.10)[text/plain]; RCVD_TLS_LAST(0.00)[]; FROM_HAS_DN(0.00)[]; MIME_TRACE(0.00)[0:+]; TO_DN_SOME(0.00)[]; ARC_NA(0.00)[]; DWL_DNSWL_NONE(0.00)[yahoo.com:dkim]; FREEMAIL_FROM(0.00)[yahoo.com]; DKIM_TRACE(0.00)[yahoo.com:+]; RCVD_VIA_SMTP_AUTH(0.00)[]; ASN(0.00)[asn:36647, ipnet:98.137.64.0/20, country:US]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCVD_COUNT_TWO(0.00)[2]; FROM_EQ_ENVFROM(0.00)[]; RCPT_COUNT_THREE(0.00)[4]; MLMMJ_DEST(0.00)[freebsd-current@freebsd.org]; RWL_MAILSPIKE_POSSIBLE(0.00)[98.137.69.83:from]; MID_RHS_MATCH_FROM(0.00)[]; FREEMAIL_ENVFROM(0.00)[yahoo.com]; RCVD_IN_DNSWL_NONE(0.00)[98.137.69.83:from] X-Rspamd-Queue-Id: 4YBKt90t9Dz54mq X-Spamd-Bar: -- https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D267028 is for a = crash problem someone has been having over more than 2 years. There are boot time = crashes involved. It appears that 0xFFFFF80000000007 is showing up in use and stored in = data structures as a pointer value in fields/arguments that are pointers, = where such a special value would not be expected. Later defrerencing does not go = well, at least when the dererefenced data is then in-turn put to use. The small offset from 0xFFFFF80000000000 suggests to me that the special = value likely is inappropriately left around and somehow picked up and used. = 0xFFFFF80000000000 (or near it) might be odd enough to have only a few known likely possible = usages. Such notes in the bugzilla report would be good if such is the case. Thus my = question. The context has amdgpu raven support in use normally. Reportedly the = problem has never been seen with that disabled. (However, I'm not aware of = experiments with alternate card types, for example.) Where, when, and if a boot crash occurs is variable, not stable. But use = of the list found_modules->tqh_first->. . . tends to be involved. Some other modern 13.4-RELEASE related context notes ( comments #231 and #233 ): The person with the problem reports . . . I am not using a stock distribution of the kernel: diff -u sys/amd64/conf/{GENERIC,M5P} --- sys/amd64/conf/GENERIC 2024-07-03 16:23:56.252550000 -0400 +++ sys/amd64/conf/M5P 2024-07-03 16:25:05.287604000 -0400 @@ -18,12 +18,13 @@ # =20 cpu HAMMER -ident GENERIC +ident M5P =20 makeoptions DEBUG=3D-g # Build kernel with gdb(1) debug symbols makeoptions WITH_CTF=3D1 # Run ctfconvert(1) for DTrace support =20 -options SCHED_ULE # ULE scheduler +#options SCHED_ULE # ULE scheduler +options SCHED_4BSD # 4BSD scheduler options NUMA # Non-Uniform Memory Architecture support options PREEMPTION # Enable kernel thread preemption options VIMAGE # Subsystem virtualization, e.g. VNET I also noted (for modern 13.4-RELEASE times): Also: the build is based on the -p2 source code (hash 3f40d5821): # strings boot/kernel/kernel | grep "\-RELEASE" @(#)FreeBSD 13.4-RELEASE-p2 3f40d5821 M5P FreeBSD 13.4-RELEASE-p2 3f40d5821 M5P 13.4-RELEASE-p2 Because it is a rebuild, the kernel ends up with -p2 instead of the official -p1 ( from -p2 not updating boot/kernel/kernel in the official distributions ). =3D=3D=3D Mark Millard marklmi at yahoo.com From nobody Mon Dec 16 04:13:45 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 4YBRQw6KTjz5gqrt; Mon, 16 Dec 2024 04:14:16 +0000 (UTC) (envelope-from darius@dons.net.au) Received: from midget.dons.net.au (midget.dons.net.au [IPv6:2403:580d:ae98:0:225:90ff:fe47:39b4]) by mx1.freebsd.org (Postfix) with ESMTP id 4YBRQw2HDNz4DZs; Mon, 16 Dec 2024 04:14:16 +0000 (UTC) (envelope-from darius@dons.net.au) Authentication-Results: mx1.freebsd.org; none Received: from smtpclient.apple (unknown [IPv6:2001:44b8:1d2:8900:1876:809f:8906:ef38]) by midget.dons.net.au (Postfix) with ESMTPSA id 15A57756308; Mon, 16 Dec 2024 14:44:03 +1030 (ACDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=dons.net.au; s=default; t=1734322445; bh=mNVyqTmcw9SeJxg5bqR5OOr4IpOtPA32g9kQkL4xq7E=; h=Subject:From:In-Reply-To:Date:Cc:References:To; b=qf+kdrOLn9fj5YMvSR0GfCpP/ARmVg3EF1hOs7m60HWfJi7gAlB1RNAtdZzCm2cER Pp6YVYrdd6vkLveVnT86hpFQiDUQEhL9IoqlQGmu4jP0LxQzc3G0PmXrIfC5QoSjz1 bB1t7/lKvWf52y60LKt7RgEArey7jLSCOvAsCVGaQ4C86lkJ4OH+7Ss8HLVdggUchu bVorf8mwlhI8LEr+V4QtqamlrfB2+1wWy7ljgzFyb+tZYGjJmQv1A09jFTH9AAwj71 lHPbU939JW7GuviGQ5cuqe/V5NrVCPLPNsU6Hyl/+Mw72qi3EJj1AjHE5CM+4DR+1W 803T2nvrSQsdg== 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 \(3826.200.121\)) Subject: Re: What kind of code might generate amd64 addressses like 0xFFFFF80000000007 or be based on 0xFFFFF80000000000 ? From: Daniel O'Connor In-Reply-To: <65B0673C-287A-47E5-A732-17CC5EEE3350@yahoo.com> Date: Mon, 16 Dec 2024 14:43:45 +1030 Cc: FreeBSD Current , FreeBSD-STABLE Mailing List , freebsd-hackers , freebsd-amd64@freebsd.org Content-Transfer-Encoding: quoted-printable Message-Id: <8C32FA41-C0EC-4679-9E26-B7CC3C69ECE6@dons.net.au> References: <65B0673C-287A-47E5-A732-17CC5EEE3350.ref@yahoo.com> <65B0673C-287A-47E5-A732-17CC5EEE3350@yahoo.com> To: Mark Millard X-Mailer: Apple Mail (2.3826.200.121) X-Rspamd-Action: no action X-Rspamd-Server: midget.dons.net.au X-Spam-Status: No, score=-0.09 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:4764, ipnet:2403:5800::/27, country:AU] X-Rspamd-Queue-Id: 4YBRQw2HDNz4DZs X-Spamd-Bar: ---- Hi Mark, > On 16 Dec 2024, at 10:33, Mark Millard wrote: > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D267028 is for a = crash problem > someone has been having over more than 2 years. There are boot time = crashes > involved. >=20 > It appears that 0xFFFFF80000000007 is showing up in use and stored in = data > structures as a pointer value in fields/arguments that are pointers, = where such > a special value would not be expected. Later defrerencing does not go = well, at > least when the dererefenced data is then in-turn put to use. >=20 > The small offset from 0xFFFFF80000000000 suggests to me that the = special value likely > is inappropriately left around and somehow picked up and used. = 0xFFFFF80000000000 (or > near it) might be odd enough to have only a few known likely possible = usages. Such > notes in the bugzilla report would be good if such is the case. Thus = my question. That value (0xffffffff80000000) is kernbase (see sysctl = kern.base_address). However it is hard to think of why that value (or a small offset to it) = is getting put in places it shouldn't be.. -- Daniel O'Connor "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum From nobody Mon Dec 16 05:48:45 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 4YBTXL43dcz5gx31 for ; Mon, 16 Dec 2024 05:49:06 +0000 (UTC) (envelope-from marklmi@yahoo.com) Received: from sonic306-19.consmr.mail.gq1.yahoo.com (sonic306-19.consmr.mail.gq1.yahoo.com [98.137.68.82]) (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) by mx1.freebsd.org (Postfix) with ESMTPS id 4YBTXK5s4Fz4N7L for ; Mon, 16 Dec 2024 05:49:05 +0000 (UTC) (envelope-from marklmi@yahoo.com) Authentication-Results: mx1.freebsd.org; none DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1734328143; bh=i2MvppBsFKhlJqN4/mEffoGFJneWWAFY/vjCRVyL1qY=; h=Subject:From:In-Reply-To:Date:Cc:References:To:From:Subject:Reply-To; b=ZTlQblc0hsHZBjJAZa/+q7maW0tUQ/t04kiRacxAV6Zh93iiZfhKz+KO4QXOrbA2DDgp/bJds6YPX+XCrVjIbvvFBvdyx7A59ADnLE8i+4CP/+PfyscgfqSCvz8Bu9YXNoPnSZlxENugJIcupmWNOegxxhKMipxoNciloZ+4Bz8skf6I9rmatOmhgvXpne0cbpf+LRkQrwigUu+jOJAxJ0yJlHhdlkB4tIeagBPziGK7+n0ilDoCt8lki00ExHfl398kW2tEgGJgA3bRNzwag3bOl7COVQPsniLx15TGA3DqwztHRCRp/kHtAV+H5U8jFXPP5hm8wplWXav49lhNzA== X-SONIC-DKIM-SIGN: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1734328143; bh=bZ8pyFD11Ak73UctFbb+8i8rOwu7e6P82U6sl7fibCC=; h=X-Sonic-MF:Subject:From:Date:To:From:Subject; b=gy+N49PoWlaUf+QwAa+IEGQ8IFQF2zrRF2qE1Sl9uCRX+czHk5uq/WhnKX7wu9INBplHiRvOztL4Vtrfc443kWWCijeijhEXnxX5lySTGdMNx4ZKTjys176m9VrS3dQ0mjeX46SEX5xrTjnCJXeR9JqXvPwPnl6C9tkls/5S8UGJcAHUlWt+OeeYwjm6HGTI64KwhlRf0kgSCIfXn9dmG9LE4VI4QEWYZCf2rp1+EY9R814ctFk2Uo0s7TCtBEMu1qRGM7PqsKRzdFK3otdDqw+MhDw78CSaE3+LxBwt04mXy+oUBBSmD94l1t96dIKZS2mP+AleDk/tPRYBL+/sBg== X-YMail-OSG: 2D6y..0VM1nW733Laf0tH_CpE3xMPTI.f3btRqi26I4y0O1PZZhKAIEidK156Cf D0V8CvdcbHW5XjUHs2X7obC1RvtZ3s00m_IUPYbJiut1PRxgwCCBOtpkHouPukJ2wjLKJjzrEeDp RsTIxNdU4eoZR3QRQOiDXlTsU0A8yIbHBlR.Q2e8G36EHf6xtWFFFcgzeplBsfMKtzNQlCBeZBCA XuR26859.6NMzRIpqdtgsDIjxNq4fdFjClCJbhxH4sImZtp3ERdNwbO4bO3FmmZNniM2odqzYppH LGfYmrUs6D_VsLNBu3fjt7LV8A5PWIe3wx3G4q5dluHvuqgqdRL7NIv9ZiMbYfk5LQLWscuulqqr 4los7ehJergzMKI_bZQ8.kz43dj_mKztyb6zYKIswYeryZBWKbgJESkcBNTSuJB5v4cmfNsVXNV5 nERGES.c3yB1m3Wc_XQXrhTzt63j8xE2fUt3UT1xAjLOWCUcP9UOSVfOxyg23ERuPQkVzynBCPrY bZE.uCYwrjPb6ptaCeoOWL4s85YCrTPEU9btfqOXmr3H7fpsHGmNz4ZHhbjNxfeht67aqtnLDEpZ G5R9y.2IflEl0YvCgLpwZEX7gLaVDnr1rCG5yt1cQhIONf4JIS_QlJFZRWtliebWkGVKEbphbdlj doKKytEpj86ZS2wQZU8dWrzy7YLxmYxiTfk_tJyZcOVv6Vh8ohp5hp18F4cSXLKyQKr9uKJNsN9s a5f03QO4NwCMLDJXaCGulSWH5scCzRboxAjbXJtlMCIrc6WXSSkLSaEh2ATHrVwiNviRt2Pzy59A N958zkDhWbQ2t06_6NR.IKPP5HIbzoCFPtW4dfa9jrWIZGcAP6Dqrmak7mtR2y7nn9OaoqscAtOb jkRNDvim8mfrjFNgwPpXk1XnEH2iGp.2C0niW3bj11J1CDO3GxcNXjLb1tggepSfzM74Rxuv5_kQ Sq4_ElThKcwTpaErfY0l1xqA3Yjbo6p6nkFiOPr8hLmwf2jxm8mTGD2TUQJXrPhzIqB.Vf59cXHD 4TXG7uOW5SOEmI7bOTrhCAXyj7vSsc5EMKjfn5GuUJI0U61B8mvx9swL3ULQKOaKDCtXNtjBKTvj 8nDtpYLV70EICzoaAl9j.RoeOysrolpE59QqmmKMlESk8qe6b7qbHx_niEtyi75cVRg_J1y.x33R bXMKqPFcOuwrFd0JGQwn3IyrhrFyeS.0IMC3iKHxMe4qViUwpZPzH7gupnXg_w9Uwq87JWtvL1Ql AvPlT6zHUQvwRZoB20EMOujl.A5k6eNo.T5Qwismf8KJga64zYD0kTV9bRiRURAaU5VU57nGdXqN 1dfXVBpPm_HwEiuI9A7g28gi0Hgwlukd2mcHcnH4ZKJVQOwwwrgNiLnaRiMuVyeO5YeuOi.q7wMa bPSRg9qh4fRYfKlAijAE6g2P714Ealt.YEanklnm6bsdnKW_xPJyiQoauVDcegeYHj6cNo7nodqs bOd02Avyd6XUqWD81du02.a7MZhjyjh1sOL.lvu9uv6mOvmCQou8ASidnxgptkGxWWTeX3XUQC3k vq3xEDUdyMoJdZLujxpyA9UPXyFX1vjSeo62QBxHPAWwxJGvIfUVkiFEY9WYod6fEtQtPY6_787t imqurXEC_vIB0NN9gG9JMwTJqTY_6q4Un8KiddmBXuPlAcPG7nznDd6Dbqu7Di9mk0SLfPjuErfX xYOqlJ.S_s2eUBK0fnjZIcQrzx5GqcpNfLgGYqDRZ.XP0kiUy_EcaYzlXDdsN1_WV8h9szDN4GQe Kh0q_1bGQ1Y3aZB4tslKwlkjjTu3N1J76kJNDSItqqy1HKOomkx9tgLvo9lIL_FqoYs43kfQdpdF log3xPOjtoXeKEdoXKV7dsUZ6DibR991GIrNS75P7qr.njLwbrKIskEu.Yb64L95mArsoZMvZKrW sxRN76LuDJxmAd.VcjT3pFsm1YSf9Hytv.yhcpqkMn3UR.sRDrf4ifVHvARv0oJaqr6Cfbc2wuXe YhVGg2IPwoIPOWBK22b7GWx1JSqtbXcimoonZA_Dij26D0SKVjGPPM1Ydef5XPU0P6i_UrLAD3_k h04l3nSHzxCfw.demcEpOIRpG0wtqjos9sDH0aZY.EMcq2RhtSi8MbFzbh3Kz8N6SZ54rsArxhhY bzGjUJ839Gk03CN.FxmQvGebYjE_rJ9VzofpCdBKGgSdKHpsWQEHVnnuTWzqUX3ummgbzVQHhaWP Vh.LYWMi8bFStagLSKg07fyseTzwKlaH0DatUVLhMGt92jG0IsS6owC7U.agqIZB9HRMg1YaAqg- - X-Sonic-MF: X-Sonic-ID: 1a89d55d-ca63-4714-b2f4-3f351511bf74 Received: from sonic.gate.mail.ne1.yahoo.com by sonic306.consmr.mail.gq1.yahoo.com with HTTP; Mon, 16 Dec 2024 05:49:03 +0000 Received: by hermes--production-gq1-5dd4b47f46-5xsmt (Yahoo Inc. Hermes SMTP Server) with ESMTPA ID ec0cbc91b415346e55b2360efa58ebfe; Mon, 16 Dec 2024 05:48:59 +0000 (UTC) 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 \(3826.300.87.4.3\)) Subject: Re: What kind of code might generate amd64 addressses like 0xFFFFF80000000007 or be based on 0xFFFFF80000000000 ? From: Mark Millard In-Reply-To: <8C32FA41-C0EC-4679-9E26-B7CC3C69ECE6@dons.net.au> Date: Sun, 15 Dec 2024 21:48:45 -0800 Cc: FreeBSD Current , FreeBSD-STABLE Mailing List , freebsd-hackers , freebsd-amd64@freebsd.org Content-Transfer-Encoding: quoted-printable Message-Id: References: <65B0673C-287A-47E5-A732-17CC5EEE3350.ref@yahoo.com> <65B0673C-287A-47E5-A732-17CC5EEE3350@yahoo.com> <8C32FA41-C0EC-4679-9E26-B7CC3C69ECE6@dons.net.au> To: Daniel O'Connor X-Mailer: Apple Mail (2.3826.300.87.4.3) 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:36647, ipnet:98.137.64.0/20, country:US] X-Rspamd-Queue-Id: 4YBTXK5s4Fz4N7L X-Spamd-Bar: ---- On Dec 15, 2024, at 20:13, Daniel O'Connor wrote: > Hi Mark, Hello Daniel, >> On 16 Dec 2024, at 10:33, Mark Millard wrote: >> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D267028 is for a = crash problem >> someone has been having over more than 2 years. There are boot time = crashes >> involved. >>=20 >> It appears that 0xFFFFF80000000007 is showing up in use and stored in = data >> structures as a pointer value in fields/arguments that are pointers, = where such >> a special value would not be expected. Later defrerencing does not go = well, at >> least when the dererefenced data is then in-turn put to use. >>=20 >> The small offset from 0xFFFFF80000000000 suggests to me that the = special value likely >> is inappropriately left around and somehow picked up and used. = 0xFFFFF80000000000 (or >> near it) might be odd enough to have only a few known likely possible = usages. Such >> notes in the bugzilla report would be good if such is the case. Thus = my question. >=20 > That value (0xffffffff80000000) is kernbase (see sysctl = kern.base_address). On an amd64 system that I have access to: # sysctl -x kern.base_address kern.base_address: 0xffffffff80000000 But, while looking similar, it is not the same base number: 0xfffff80000000007 (copied and pasted from the kgdb session on the = vmcore.*) 0xffffffff80000000 However, kern.base_address might be something that varies from system to system in some way. The closest examples I see in sysctl -ax output, start with 0xfffff801. . ., such as shown by: kern.geom.confdot: digraph geom { z0xfffff80105633a00 [shape=3Dbox,label=3D"ZFS::VDEV\nzfs::vdev\nr#4"]; z0xfffff827c9e7dc80 [label=3D"r1w1e1"]; z0xfffff827c9e7dc80 -> z0xfffff827c9e6d800; z0xfffff80105633a00 -> z0xfffff827c9e7dc80; z0xfffff8255c020300 [shape=3Dbox,label=3D"SWAP\nswap\nr#4"]; z0xfffff80e3c0bed00 [label=3D"r1w1e0"]; z0xfffff80e3c0bed00 -> z0xfffff80105633e00; z0xfffff8255c020300 -> z0xfffff80e3c0bed00; z0xfffff8010553c300 [shape=3Dbox,label=3D"PART\nda0\nr#2"]; z0xfffff80105531700 [label=3D"r0w0e0"]; z0xfffff80105531700 -> z0xfffff80105337c00; z0xfffff8010553c300 -> z0xfffff80105531700; . . . z0xfffff80105afa080 [label=3D"r0w0e0"]; z0xfffff80105afa080 -> z0xfffff80105631000; z0xfffff827c9f56400 -> z0xfffff80105afa080; z0xfffff8013806b800 [shape=3Dbox,label=3D"DEV\nnda0\nr#2"]; z0xfffff827c992f580 [label=3D"r0w0e0"]; z0xfffff827c992f580 -> z0xfffff80105931200; z0xfffff8013806b800 -> z0xfffff827c992f580; . . . kern.geom.confxml: . . . ZFS::VDEV zfs::vdev 4 r1w1e1 SWAP swap 4 r1w1e0 . . . nda0 2 r0w0e0 So: Only seen in such kern.geom.* related sysctl -ax output. Thanks: I'd not considered looking at sysctl output. > However it is hard to think of why that value (or a small offset to = it) is getting put in places it shouldn't be.. Certainly does seem odd. =3D=3D=3D Mark Millard marklmi at yahoo.com From nobody Mon Dec 16 06:35: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 4YBVZs5VSTz5h0NW; Mon, 16 Dec 2024 06:36:21 +0000 (UTC) (envelope-from darius@dons.net.au) Received: from midget.dons.net.au (midget.dons.net.au [IPv6:2403:580d:ae98:0:225:90ff:fe47:39b4]) by mx1.freebsd.org (Postfix) with ESMTP id 4YBVZs2J3cz4TYH; Mon, 16 Dec 2024 06:36:21 +0000 (UTC) (envelope-from darius@dons.net.au) Authentication-Results: mx1.freebsd.org; none Received: from smtpclient.apple (unknown [IPv6:2001:44b8:1d2:8900:1876:809f:8906:ef38]) by midget.dons.net.au (Postfix) with ESMTPSA id 578E3738668; Mon, 16 Dec 2024 17:06:13 +1030 (ACDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=dons.net.au; s=default; t=1734330974; bh=SaTxBtUxsyP0HBLCkOEmO+jkXtZDSAXyypzjGo1X5eo=; h=Subject:From:In-Reply-To:Date:Cc:References:To; b=CfTiiUmK1b10j3PBaNqK+Ggw+l/MM5lcvFasxR7xJ1DVTx0psGAUAXzbQ3Ya/J+4P crLr2rXKfHxcHOLwmfmdlJGNevUdtJRKvkOeEGilQXbWjPowM3bOX9ECamdrBA5Zsg RVcIfu8zk5BFHcu3KOCypaL/Ybrl2qUqK5dKER+yvKHiTVAoZp0IUqh/XHkvGRX6Tp JIceJ7D+eBd50EuYql7eqOddHcamA4OsHHfn/H56nCfqOgzAz5A5PAXT6Hd89VFiWq YWbZI8mSpQGxjaIq1VGTSq7TRDMSE1eoH00Hl1IK01csibisuu49FAku4IcMEwkJyp yQofUz/t/a8PA== 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 \(3826.200.121\)) Subject: Re: What kind of code might generate amd64 addressses like 0xFFFFF80000000007 or be based on 0xFFFFF80000000000 ? From: Daniel O'Connor In-Reply-To: Date: Mon, 16 Dec 2024 17:05:55 +1030 Cc: FreeBSD Current , FreeBSD-STABLE Mailing List , freebsd-hackers , freebsd-amd64@freebsd.org Content-Transfer-Encoding: quoted-printable Message-Id: <358515C3-C6B0-46C4-BC4F-03DA80598559@dons.net.au> References: <65B0673C-287A-47E5-A732-17CC5EEE3350.ref@yahoo.com> <65B0673C-287A-47E5-A732-17CC5EEE3350@yahoo.com> <8C32FA41-C0EC-4679-9E26-B7CC3C69ECE6@dons.net.au> To: Mark Millard X-Mailer: Apple Mail (2.3826.200.121) X-Rspamd-Action: no action X-Rspamd-Server: midget.dons.net.au X-Spam-Status: No, score=-0.09 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:4764, ipnet:2403:5800::/27, country:AU] X-Rspamd-Queue-Id: 4YBVZs2J3cz4TYH X-Spamd-Bar: ---- > On 16 Dec 2024, at 16:18, Mark Millard wrote: >>> On 16 Dec 2024, at 10:33, Mark Millard wrote: >>> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D267028 is for a = crash problem >>> someone has been having over more than 2 years. There are boot time = crashes >>> involved. >>>=20 >>> It appears that 0xFFFFF80000000007 is showing up in use and stored = in data >>> structures as a pointer value in fields/arguments that are pointers, = where such >>> a special value would not be expected. Later defrerencing does not = go well, at >>> least when the dererefenced data is then in-turn put to use. >>>=20 >>> The small offset from 0xFFFFF80000000000 suggests to me that the = special value likely >>> is inappropriately left around and somehow picked up and used. = 0xFFFFF80000000000 (or >>> near it) might be odd enough to have only a few known likely = possible usages. Such >>> notes in the bugzilla report would be good if such is the case. Thus = my question. >>=20 >> That value (0xffffffff80000000) is kernbase (see sysctl = kern.base_address). >=20 > On an amd64 system that I have access to: >=20 > # sysctl -x kern.base_address > kern.base_address: 0xffffffff80000000 >=20 > But, while looking similar, it is not the same base number: >=20 > 0xfffff80000000007 (copied and pasted from the kgdb session on the = vmcore.*) > 0xffffffff80000000 Oops, my mistake! > However, kern.base_address might be something that varies from > system to system in some way. Your value is the same as mine on this amd64 system - I don't think it = varies (for a given architecture anyway) > The closest examples I see in sysctl -ax output, start with > 0xfffff801. . ., such as shown by: >=20 > kern.geom.confdot: digraph geom { > z0xfffff80105633a00 [shape=3Dbox,label=3D"ZFS::VDEV\nzfs::vdev\nr#4"]; I assume these addresses are pointers to the internal GEOM objects = (because they must be unique) - ie they are actual memory location. Hmm, perhaps 0xfffff80000000000 is where kernel RAM starts? -- Daniel O'Connor "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum From nobody Mon Dec 16 07:01:59 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 4YBW8c3jLKz5h1tL; Mon, 16 Dec 2024 07:02:08 +0000 (UTC) (envelope-from philipp.takacs@asta.kit.edu) Received: from scc-mailout-kit-02.scc.kit.edu (scc-mailout-kit-02.scc.kit.edu [IPv6:2a00:1398:9:f712::810d:e752]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4YBW8c1z9cz4YmY; Mon, 16 Dec 2024 07:02:08 +0000 (UTC) (envelope-from philipp.takacs@asta.kit.edu) Authentication-Results: mx1.freebsd.org; none Received: by scc-mailout-kit-02.scc.kit.edu with esmtps (TLS1.3:ECDHE_SECP256R1__RSA_PSS_RSAE_SHA256__AES_256_GCM:256) (envelope-from ) id 1tN57E-00383S-0V; Mon, 16 Dec 2024 08:02:04 +0100 Received: from imap-1.asta.kit.edu ([2a00:1398:5:f400::73]) by hekate.asta.kit.edu with esmtp (Exim 4.94.2) (envelope-from ) id 1tN57A-003sR9-On; Mon, 16 Dec 2024 08:02:00 +0100 Received: from localhost ([2a02:8071:7111:c540:62cb:5ce4:5722:8d85]) by imap-1.asta.kit.edu with ESMTPSA id GfhoHGjQX2eWNBQA0pLxkA (envelope-from ); Mon, 16 Dec 2024 08:02:00 +0100 Message-ID: <63a9fdaa4ac204c319a1c1e273a29c18.philipp.takacs@asta.kit.edu> From: Philipp To: Mark Millard Cc: FreeBSD Current , FreeBSD-STABLE Mailing List , freebsd-hackers , freebsd-amd64@freebsd.org Subject: Re: What kind of code might generate amd64 addressses like 0xFFFFF80000000007 or be based on 0xFFFFF80000000000 ? In-reply-to: <65B0673C-287A-47E5-A732-17CC5EEE3350@yahoo.com> References: <65B0673C-287A-47E5-A732-17CC5EEE3350.ref@yahoo.com> <65B0673C-287A-47E5-A732-17CC5EEE3350@yahoo.com> Comments: In-reply-to Mark Millard message dated "Sun, 15 Dec 2024 16:03:42 -0800." List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@FreeBSD.org MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <1212416.1734332519.1@hell> Content-Transfer-Encoding: quoted-printable Date: Mon, 16 Dec 2024 08:01:59 +0100 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)[freebsd]; ASN(0.00)[asn:34878, ipnet:2a00:1398::/32, country:DE] X-Rspamd-Queue-Id: 4YBW8c1z9cz4YmY X-Spamd-Bar: ---- Hi Mark [2024-12-15 16:03] Mark Millard > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D267028 is for a crash= problem > someone has been having over more than 2 years. There are boot time crash= es > involved. > > It appears that 0xFFFFF80000000007 is showing up in use and stored in dat= a > structures as a pointer value in fields/arguments that are pointers, wher= e such > a special value would not be expected. Later defrerencing does not go wel= l, at > least when the dererefenced data is then in-turn put to use. > > The small offset from 0xFFFFF80000000000 suggests to me that the special = value likely > is inappropriately left around and somehow picked up and used. 0xFFFFF800= 00000000 (or > near it) might be odd enough to have only a few known likely possible usa= ges. Such > notes in the bugzilla report would be good if such is the case. Thus my q= uestion. By simple grep through sys/ I found following comment in sys/amd64/include/= vmparam.h: > /* > * Virtual addresses of things. Derived from the page directory and > * page table indexes from pmap.h for precision. > [...] > * 0xfffff80000000000 - 0xfffffbffffffffff 4TB direct map The direct map is 4TB of virtuall address space mapping the physical address space 1:1 (minus the base). So I would guess this is caused by an NULL pointer converted by PHYS_TO_DMAP. Philipp > The context has amdgpu raven support in use normally. Reportedly the prob= lem has > never been seen with that disabled. (However, I'm not aware of experiment= s with > alternate card types, for example.) > > Where, when, and if a boot crash occurs is variable, not stable. But use = of the > list found_modules->tqh_first->. . . tends to be involved. > > > > Some other modern 13.4-RELEASE related context notes > ( comments #231 and #233 ): > > The person with the problem reports . . . > > I am not using a stock distribution of the kernel: > > diff -u sys/amd64/conf/{GENERIC,M5P} > --- sys/amd64/conf/GENERIC 2024-07-03 16:23:56.252550000 -0400 > +++ sys/amd64/conf/M5P 2024-07-03 16:25:05.287604000 -0400 > @@ -18,12 +18,13 @@ > # > = > cpu HAMMER > -ident GENERIC > +ident M5P > = > makeoptions DEBUG=3D-g # Build kernel with gdb(1) debug symbols > makeoptions WITH_CTF=3D1 # Run ctfconvert(1) for DTrace support > = > -options SCHED_ULE # ULE scheduler > +#options SCHED_ULE # ULE scheduler > +options SCHED_4BSD # 4BSD scheduler > options NUMA # Non-Uniform Memory Architecture support > options PREEMPTION # Enable kernel thread preemption > options VIMAGE # Subsystem virtualization, e.g. VNET > > > I also noted (for modern 13.4-RELEASE times): > > Also: the build is based on the -p2 source code (hash 3f40d5821): > > # strings boot/kernel/kernel | grep "\-RELEASE" > @(#)FreeBSD 13.4-RELEASE-p2 3f40d5821 M5P > FreeBSD 13.4-RELEASE-p2 3f40d5821 M5P > 13.4-RELEASE-p2 > > Because it is a rebuild, the kernel ends up with -p2 instead > of the official -p1 ( from -p2 not updating boot/kernel/kernel > in the official distributions ). > > > > =3D=3D=3D > Mark Millard > marklmi at yahoo.com > > From nobody Mon Dec 16 13:42:46 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 4YBh375MrQz5hRd8 for ; Mon, 16 Dec 2024 13:42:59 +0000 (UTC) (envelope-from carpeddiem@gmail.com) Received: from mail-io1-f49.google.com (mail-io1-f49.google.com [209.85.166.49]) (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 4YBh366mBtz4J9y for ; Mon, 16 Dec 2024 13:42:58 +0000 (UTC) (envelope-from carpeddiem@gmail.com) Authentication-Results: mx1.freebsd.org; dkim=none; spf=pass (mx1.freebsd.org: domain of carpeddiem@gmail.com designates 209.85.166.49 as permitted sender) smtp.mailfrom=carpeddiem@gmail.com; dmarc=fail reason="SPF not aligned (relaxed), No valid DKIM" header.from=freebsd.org (policy=none) Received: by mail-io1-f49.google.com with SMTP id ca18e2360f4ac-844dac0a8f4so309914639f.2 for ; Mon, 16 Dec 2024 05:42:58 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1734356577; x=1734961377; 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=8EXM8dg3QuKrEnQCqi+IgdPMqaGpYH45GlfNB8z9Bb8=; b=tEJHyi37o8oFqtGSeVA8/Af45MYnYFyLNn8X5V0bLmH5EjoBSzrnxlpc8SCCwhECIW xwwfTmYvZW4I8ZdZiogaf0kwr2egkZjKIGExUIj1JjZoVYJW9i1rwx37Yi1goj5pQilj NhwC4r56C/4IVc36pBbcDHtXOlZtaWoEan968gz4b3k4QOtkJYvPzz38Z6w8smDPeTv9 D19EHeGeC8YYmVBOBXnigYnm55nq+RpG+FhHpasl/hF+IPiuqyPYQtJ7qzY22q+wOuKk gFWiL2Ts2NugzPXn5PpDWBn+UnkNogPaevbccbSzm1yOKiJXZShQ+WLMFMcYCTYYjnnO LskA== X-Gm-Message-State: AOJu0YxojJYDeVXxFsXP1xqP4Z0DW9GmMqSXL9FD4qtyXjVciVhgVjEc fHIap2s7bGcE2Gd3w75HwwM70mscYFR1zIBH6lywMC0G/h4PSuWN29NPM7U7IM+n0vwfMi25VHI 4JbrgEi69BGirjwdRHVw93ChMraE= X-Gm-Gg: ASbGncvaMm9Nurf5XTkfm97YrD1a82k63XYItWyYRK8e/QJC0ZBMScVCTd0qW6kKWMS hbHyydIsy+oGLz5D73jbBPoX6fcIaBNfPUC9Yt8JoziWIjQN/iPpGuaZ9zrzkq/Wd604hmSad X-Google-Smtp-Source: AGHT+IFrTVYHwGT9e5jKF3ZQeVozvGWL8tbtm2dttavmVVG2p6bgMNfQh8FtlR6EQiySA5hy3i0lGYBZThxW3JAKUkM= X-Received: by 2002:a05:6602:1354:b0:83b:a47c:dbfd with SMTP id ca18e2360f4ac-844e881ca67mr1393988539f.6.1734356577630; Mon, 16 Dec 2024 05:42:57 -0800 (PST) List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@FreeBSD.org MIME-Version: 1.0 References: <42173.1734202821@kaos.jnpr.net> In-Reply-To: <42173.1734202821@kaos.jnpr.net> From: Ed Maste Date: Mon, 16 Dec 2024 08:42:46 -0500 Message-ID: Subject: Re: Switching release media dist sets to .tzst (tar + zstd)? To: "Simon J. Gerraty" Cc: FreeBSD Current Content-Type: text/plain; charset="UTF-8" X-Spamd-Result: default: False [-1.34 / 15.00]; SUBJECT_ENDS_QUESTION(1.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-0.996]; NEURAL_HAM_SHORT(-0.90)[-0.896]; NEURAL_HAM_LONG(-0.55)[-0.548]; FORGED_SENDER(0.30)[emaste@freebsd.org,carpeddiem@gmail.com]; R_SPF_ALLOW(-0.20)[+ip4:209.85.128.0/17:c]; DMARC_POLICY_SOFTFAIL(0.10)[freebsd.org : SPF not aligned (relaxed), No valid DKIM,none]; MIME_GOOD(-0.10)[text/plain]; FROM_HAS_DN(0.00)[]; TO_DN_ALL(0.00)[]; RCVD_TLS_LAST(0.00)[]; RCPT_COUNT_TWO(0.00)[2]; MIME_TRACE(0.00)[0:+]; ARC_NA(0.00)[]; MISSING_XM_UA(0.00)[]; ASN(0.00)[asn:15169, ipnet:209.85.128.0/17, country:US]; FREEFALL_USER(0.00)[carpeddiem]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; TO_MATCH_ENVRCPT_SOME(0.00)[]; FROM_NEQ_ENVFROM(0.00)[emaste@freebsd.org,carpeddiem@gmail.com]; RCVD_COUNT_ONE(0.00)[1]; MLMMJ_DEST(0.00)[freebsd-current@freebsd.org]; RWL_MAILSPIKE_POSSIBLE(0.00)[209.85.166.49:from]; R_DKIM_NA(0.00)[]; FREEMAIL_ENVFROM(0.00)[gmail.com]; RCVD_IN_DNSWL_NONE(0.00)[209.85.166.49:from] X-Rspamd-Queue-Id: 4YBh366mBtz4J9y X-Spamd-Bar: - On Sat, 14 Dec 2024 at 14:02, Simon J. Gerraty wrote: > > Ed Maste wrote: > > Pros of zstd: > > - Faster compression and decompression speeds. > > - Aligns with the compression method used for FreeBSD packages. > > FWIW this should also allow the sets to be mountable using tarfs? > Browse the content without having to unpack. I imagine it would, yes. From nobody Mon Dec 16 13:51: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 4YBhDk2QM3z5hSCr for ; Mon, 16 Dec 2024 13:51:18 +0000 (UTC) (envelope-from carpeddiem@gmail.com) Received: from mail-io1-f52.google.com (mail-io1-f52.google.com [209.85.166.52]) (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 4YBhDj2vL9z4Nvl for ; Mon, 16 Dec 2024 13:51:17 +0000 (UTC) (envelope-from carpeddiem@gmail.com) Authentication-Results: mx1.freebsd.org; dkim=none; spf=pass (mx1.freebsd.org: domain of carpeddiem@gmail.com designates 209.85.166.52 as permitted sender) smtp.mailfrom=carpeddiem@gmail.com; dmarc=fail reason="SPF not aligned (relaxed), No valid DKIM" header.from=freebsd.org (policy=none) Received: by mail-io1-f52.google.com with SMTP id ca18e2360f4ac-844ee166150so83361239f.2 for ; Mon, 16 Dec 2024 05:51:17 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1734357076; x=1734961876; 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=UWNF03cSXU89QxMrEQMG9aV6XZmB6gazqzsSnauqSzU=; b=ojTYezh30IZESzGU7OAN3hNxgfJh8jniN9GUpuZRkTGBqXjoL/uw21e0u9sT/5QMRu 3w6BH1qOUFuTu4KaDXVDPTKja2g5e3vCeDzY6hj2q0mGyhB/5NQ21SI5z1FlRHlUz5QN xlaKVJUaauZ5RU7h+k8gio2ECv1erxFb7toNJmtthcL83i1tCAL3I01mWdoflpi00g5j 0yzNvwiGY/ptc7UE0a+SO2mXI4ncvG25a+6Hy+h5XjgZLEm0zOS18DNAdIyRL/tGYwk6 o3zdlMDVS2pA8ElrYvwbr6wS1Yyl5CYjORdRtCV+ijRYGcGLjBVWDKPDtCm9ABQOJvF6 EBuw== X-Gm-Message-State: AOJu0Yy64SNfI8UgKaqt6UvDnO6xiNtLdqqQjCAoRdBFsy1nDz+GQfPG wUG7VByyYky4LsDAtqp4Mo+F2SXhpMN3AkS22/n3MmHX375z0kQR2ilqqM6mUWHzVS1S8bZDS4z lF7pd52mxmEEQ4eUPr7rt5ZbPuA2/kA== X-Gm-Gg: ASbGncsjcHxFDMkxyPjWd16jd043/cim6FBHInEiWzb+luDD3162tSDrcAPVMnfg2FK EVLjgXeamI/r9590c0Sc9z07YQDB28BOJzItHqGhYo9Tk5AfoFHfiLBDFOn0v3CM903NWJ+Me X-Google-Smtp-Source: AGHT+IFsLngVqhi+KTWdRJ2HYGsswE8fnKsnAeJ6688cp+dMC+ceSTknXybkrt93e4ePrenbwX8fBdJwfCY0jydeCpc= X-Received: by 2002:a05:6602:15c2:b0:843:e9c1:9317 with SMTP id ca18e2360f4ac-844e8b9c9e8mr1057818839f.14.1734357076578; Mon, 16 Dec 2024 05:51:16 -0800 (PST) List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@FreeBSD.org MIME-Version: 1.0 References: In-Reply-To: From: Ed Maste Date: Mon, 16 Dec 2024 08:51:04 -0500 Message-ID: Subject: Re: Switching release media dist sets to .tzst (tar + zstd)? To: Shawn Webb Cc: FreeBSD Current Content-Type: text/plain; charset="UTF-8" X-Spamd-Result: default: False [-1.26 / 15.00]; SUBJECT_ENDS_QUESTION(1.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-0.995]; NEURAL_HAM_SHORT(-0.89)[-0.894]; NEURAL_HAM_LONG(-0.47)[-0.470]; FORGED_SENDER(0.30)[emaste@freebsd.org,carpeddiem@gmail.com]; 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]; MIME_GOOD(-0.10)[text/plain]; FROM_HAS_DN(0.00)[]; TO_DN_ALL(0.00)[]; RCVD_TLS_LAST(0.00)[]; RCPT_COUNT_TWO(0.00)[2]; MIME_TRACE(0.00)[0:+]; ARC_NA(0.00)[]; MISSING_XM_UA(0.00)[]; ASN(0.00)[asn:15169, ipnet:209.85.128.0/17, country:US]; FREEFALL_USER(0.00)[carpeddiem]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; TO_MATCH_ENVRCPT_SOME(0.00)[]; FROM_NEQ_ENVFROM(0.00)[emaste@freebsd.org,carpeddiem@gmail.com]; RCVD_COUNT_ONE(0.00)[1]; MLMMJ_DEST(0.00)[freebsd-current@freebsd.org]; RWL_MAILSPIKE_POSSIBLE(0.00)[209.85.166.52:from]; R_DKIM_NA(0.00)[]; FREEMAIL_ENVFROM(0.00)[gmail.com]; RCVD_IN_DNSWL_NONE(0.00)[209.85.166.52:from] X-Rspamd-Queue-Id: 4YBhDj2vL9z4Nvl X-Spamd-Bar: - On Fri, 13 Dec 2024 at 16:47, Shawn Webb wrote: > > Hey Ed, > > Thanks for providing the opportunity to discuss this before landing > it. To be clear, this was just intended to explore the idea. I was looking at some release artifact build infrastructure and was curious about how extensive the changes would be. > The tool for updating HardenedBSD installs (and the tool used to build > the update artifacts) would be impacted. It wouldn't be too difficult > to update the tools (hbsd-update and hbsd-update-build). However, if > the switch zstd is not done at the same time for all supported > branches (main and stable/14), we would need to have hbsd-update > reference different archives between different branches--zstd for > main and xz for stable/14. I would prefer not to have to include > branch-specific code in a generic system updater utility. Interesting, so you're using the dist sets for updates as well? This is one good outcome of this discussion -- identifying different ways folks are using the dist sets. From nobody Mon Dec 16 22:31:22 2024 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4YBvmt6T7Dz5gcfp for ; Mon, 16 Dec 2024 22:31:26 +0000 (UTC) (envelope-from ler@FreeBSD.org) Received: from smtp.freebsd.org (smtp.freebsd.org [IPv6:2610:1c1:1:606c::24b:4]) (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 "R10" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4YBvmt5fJKz45Mb for ; Mon, 16 Dec 2024 22:31:26 +0000 (UTC) (envelope-from ler@FreeBSD.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1734388286; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type; bh=Pv9OsA/6F40eY6efvFMmTP8u0qbJ/bCDI9ogldjfLis=; b=BnJuR/o3ivVTE2yR51hN39zYh8yH+Y7E+Ehw0CeFniPGYNQwDGjDNyCSCFi/TVRkoUZmeS uh/XwEuS0pCg0gDvSa9TQE0Z9LhqccHH4Jnx3vEy8vEe7OSKeOiQ3S8JlTrk2zJiCTTt8q Jy4CmKB217GY30PoXcWvOln6kfA36C7Vyegf/l9WlufFAMPWB6Ub7hJvFoaHFHHngXX7+j 9TdM+RlqwsmwEPlm9HbJeDPMlI9UjFW5dWgeeS4SlZUf1p6BpPTikV/XBlqCDH4KLVdtJk BCKTXPKxZK/3a9p2tcczCJt1sfo4lj/AkSx19kcmMzH6kEXi06yXHq/J1R4SjQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1734388286; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: dkim-signature; bh=Pv9OsA/6F40eY6efvFMmTP8u0qbJ/bCDI9ogldjfLis=; b=rn+yNrZn1XHVm5zvsiHONQA5dCpu3G3N4huWc4DXyxBTYhI1PHKYej4gVJgF2fli7c5+6J 7Jarr2RCLCf/rhWSQGOq62d+h9Egr+7Cztjd3jVIAab1hfVbfpjEIeo7WXbXliMAuVh3K4 qmZqKSfW18NR++M/PkYqkj6AV3HFItHTM/1BJ+nTXPpR3LYb5EPVFCEyzY/czKVl0onVZJ hO0IHbHPZZNnf4hjObgmVch7rH6Q/f8r1UZdUQyN0P0Ct5CEiNQHiAVLW4uw6ceSx00w73 fm1bltCthlOfvvq8vdRn3XMc83zVdA8+FssHYFQ5g4bKiIKMd7XrK4/y4Tdxeg== ARC-Authentication-Results: i=1; thebighonker.lerctr.org; iprev=pass (thebighonker.lerctr.org) smtp.remote-ip=2607:9c00:1009::53:1; auth=pass (LOGIN) smtp.auth=ler@lerctr.org; spf=softfail smtp.mailfrom=FreeBSD.org; arc=none ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1734388286; a=rsa-sha256; cv=none; b=gTN7Qr87QJ05ptmuykAmmnqjKmkCYxExJHZZsiDt/c7EMVrROADttz5pUwLCqaDSv5up6A Qet8JzyLJnNTMgNBX5uyjmVfupLZycWHVrVDi5aZLR4KOttveqjJ+f8UEV8GBuvu7rET8x kBD1WnpVOfljNT5xNuknMo2p29thMwv1VYHabtYI4hq27OlssPCUpYAzwBQVxM4BtsogmF fPGsQQffEGOcsZGEA+z8GkN4O3XYUZl1GMzk9UvW2ZwVymTKS4viuFXD5YUvA4UIFF3ank lBRHqPt3KGTIreMCHcxUjhbqo2Mcl8JdiCifmpBz0XUUQKVGQD2HBq6IcldIaA== Received: from thebighonker.lerctr.org (unknown [IPv6:2607:9c00:1009:0:7ae3:b5ff:fe1b:23b4]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "*.lerctr.org", Issuer "R10" (verified OK)) (Authenticated sender: ler/mail) by smtp.freebsd.org (Postfix) with ESMTPSA id 4YBvmt4CFhz1Lgf for ; Mon, 16 Dec 2024 22:31:26 +0000 (UTC) (envelope-from ler@FreeBSD.org) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lerctr.org; s=ler2019; h=Content-Type:Message-ID:Subject:To:From:Date:MIME-Version:Sender :Reply-To:Cc:Content-Transfer-Encoding:Content-ID:Content-Description; bh=Pv9OsA/6F40eY6efvFMmTP8u0qbJ/bCDI9ogldjfLis=; b=HsWLRdSxVUvH1KOYWhuxFQVEO1 H51qlJApzfbKkmejz3gIghIi94p9RdTbWGFLHynJBwi7hRMtjfC6g92du4kJOqGCASTmoQOg6LCiZ h++RH6fkK4Mo3BIyR8VVkd4KJzu7zC+Yt2B3WF1cOu/RqShtM6yioV+4tuC1BzUnxuvcgCND/AcjJ 7NWfXCXDRLjfgrZUl1oSMk6WyWq6IOpO4ApPpPuQv9zjzdj9pseMwmVu691c8dM9VXornASKGZcxc YujPAHTv5YYOtbB9OnKml873o3+dTU1DCretsYDcFV7G07rM6oiYfi9jCSnKY6oe9tEZOSAMWQ9pA YrJYJfsA==; Authentication-Results: thebighonker.lerctr.org; iprev=pass (thebighonker.lerctr.org) smtp.remote-ip=2607:9c00:1009::53:1; auth=pass (LOGIN) smtp.auth=ler@lerctr.org; spf=softfail smtp.mailfrom=FreeBSD.org; arc=none Received-SPF: softfail (thebighonker.lerctr.org: transitioning domain of FreeBSD.org does not designate 2607:9c00:1009::53:1 as permitted sender) client-ip=2607:9c00:1009::53:1; envelope-from=ler@FreeBSD.org; helo=webmail.lerctr.org; Received: from thebighonker.lerctr.org ([2607:9c00:1009::53:1]:35162 helo=webmail.lerctr.org) by thebighonker.lerctr.org with esmtpsa (TLS1.3) tls TLS_AES_256_GCM_SHA384 (Exim 4.98 (FreeBSD)) (envelope-from ) id 1tNJcb-00000000G1v-0kd2 for freebsd-current@freebsd.org; Mon, 16 Dec 2024 16:31:25 -0600 Received: from syn-2603-8080-2000-bd01-acc6-0631-f924-c7f5.res6.spectrum.com (2603:8080:2000:bd01:acc6:631:f924:c7f5) by webmail.lerctr.org with HTTP (HTTP/1.1 POST); Mon, 16 Dec 2024 16:31:22 -0600 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 Date: Mon, 16 Dec 2024 16:31:22 -0600 From: Larry Rosenman To: Freebsd current Subject: Makefile.inc1: Broken .if/.else Message-ID: <9085fba431dc31198858e60225c66c36@FreeBSD.org> X-Sender: ler@FreeBSD.org Content-Type: multipart/signed; protocol="application/pgp-signature"; boundary="=_cc621c40413e8f90cdbe213ec72682a5"; micalg=pgp-sha256 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --=_cc621c40413e8f90cdbe213ec72682a5 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII; format=flowed make[1]: "/usr/src/Makefile.inc1" line 1012: if-less else in directory /usr/src make[1]: "/usr/src/Makefile.inc1" line 1014: if-less endif in directory /usr/src make[1]: Fatal errors encountered -- cannot continue make[1]: stopped making "buildworld" in /usr/src .ERROR_TARGET='' .ERROR_META_FILE='' .MAKE.LEVEL='1' MAKEFILE='' .MAKE.MODE='meta missing-filemon=yes missing-meta=yes silent=yes verbose' _ERROR_CMD='.PHONY' .CURDIR='/usr/src' .MAKE='make' .OBJDIR='/usr/obj/usr/src/amd64.amd64' .TARGETS='buildworld' CPUTYPE='' DESTDIR='' LD_LIBRARY_PATH='' MACHINE='amd64' MACHINE_ARCH='amd64' MACHINE_CPUARCH='amd64' MAKEOBJDIRPREFIX='' MAKESYSPATH='/usr/src/share/mk' MAKE_VERSION='20240711' PATH='/sbin:/bin:/usr/sbin:/usr/bin' SRCTOP='/usr/src' OBJTOP='/usr/obj/usr/src/amd64.amd64' .MAKE.MAKEFILES='/usr/src/share/mk/sys.mk /usr/src/share/mk/local.sys.env.mk /usr/src/share/mk/src.sys.env.mk /etc/src-env.conf /usr/src/share/mk/bsd.mkopt.mk /usr/src.MAKE.MAKEFILES='/usr/src/share/mk/sys.mk /usr/src/share/mk/local.sys.env.mk /usr/src/share/mk/src.sys.env.mk /etc/src-env.conf /usr/src/share/mk/bsd.mkopt.mk /usr/src.MAKE.MAKEFILES='/usr/src/share/mk/sys.mk /usr/src/share/mk/local.sys.env.mk /usr/src/share/mk/src.sys.env.mk /etc/src-env.conf /usr/src/share/mk/bsd.mkopt.mk /usr/src.MAKE.MAKEFILES='/usr/src/share/mk/sys.mk /usr/src/share/mk/local.sys.env.mk /usr/src/share/mk/src.sys.env.mk /etc/src-env.conf /usr/src/share/mk/bsd.mkopt.mk /usr/src.MAKE.MAKEFILES='/usr/src/share/mk/sys.mk /usr/src/share/mk/local.sys.env.mk /usr/src/share/mk/src.sys.env.mk /etc/src-env.conf /usr/src/share/mk/bsd.mkopt.mk /usr/src.MAKE.MAKEFILES='/usr/src/share/mk/sys.mk /usr/src/share/mk/local.sys.env.mk /usr/src/share/mk/src.sys.env.mk /etc/src-env.conf /usr/src/share/mk/bsd.mkopt.mk /usr/src.PATH='. /usr/src' make: stopped making "buildworld buildkernel" in /usr/src -- Larry Rosenman http://people.freebsd.org/~ler Phone: +1 214-642-9640 E-Mail: ler@FreeBSD.org US Mail: 13425 Ranch Road 620 N, Apt 718, Austin, TX 78717-1010 --=_cc621c40413e8f90cdbe213ec72682a5 Content-Type: application/pgp-signature; name=signature.asc Content-Disposition: attachment; filename=signature.asc; size=488 Content-Description: OpenPGP digital signature -----BEGIN PGP SIGNATURE----- iQEzBAEBCAAdFiEEHjgknedhWzvJgwVzaXyZsatIp30FAmdgqjwACgkQaXyZsatI p33eAAf/b4irePifVDFA5YyUFfbop2PCg19mnsKHnhpWk3qazLcojGR/erH4D8UN 4Id4IAII42Ed4P33ysdNu9XL2ZrRHl85hms4aavkS4SvMd+zYEBxhY8JN25TARtF G2PgxbeTqWKgO8kWMuL7u7NJpezD+1UJBuKfLrj8OGfhfTapLUxdm81OHxJm9iRQ NTk5Pwlh+T0h8coAn+XJ+uwC0AYkas2w5dzZTAnAuel3kERvFf4ywdaquWUnCv58 Z7VzTK0yToGhv++NyAm8TxCKb6+oIyg3Qmp2/U7GAPrK2h0XUho52T3V3Kj4GB1z /AP5LspUkwOwody99Rs2vZG6Z09w8w== =WMX6 -----END PGP SIGNATURE----- --=_cc621c40413e8f90cdbe213ec72682a5-- From nobody Tue Dec 17 19:19:26 2024 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4YCRTB6DTxz5hc1n for ; Tue, 17 Dec 2024 19:19:42 +0000 (UTC) (envelope-from asomers@gmail.com) Received: from mail-ed1-f54.google.com (mail-ed1-f54.google.com [209.85.208.54]) (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 4YCRT93XcMz4RTx for ; Tue, 17 Dec 2024 19:19:41 +0000 (UTC) (envelope-from asomers@gmail.com) Authentication-Results: mx1.freebsd.org; dkim=none; spf=pass (mx1.freebsd.org: domain of asomers@gmail.com designates 209.85.208.54 as permitted sender) smtp.mailfrom=asomers@gmail.com; dmarc=fail reason="SPF not aligned (relaxed), No valid DKIM" header.from=freebsd.org (policy=none) Received: by mail-ed1-f54.google.com with SMTP id 4fb4d7f45d1cf-5d27243ba8bso1120055a12.2 for ; Tue, 17 Dec 2024 11:19:41 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1734463179; x=1735067979; h=to:subject:message-id:date:from:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=9OH733AY6ZQx12b7Yfs80B25jygvB5Cm2C+B362ndwU=; b=ITH9n6wkt6/JKFoP1Xqpeo4a0VJvRQr2027GS8YKAMaLL4VeX2avwlB9pJuvX0NokZ HZAnCgikNHROjJkT26AFHp7tp+GXx+y+mLInrOI0UooI3Z81gjMwaruBvD5lT2WncvqD lc9zNhUxmkuR7RKlHm2jcKMUlUQGDmXM59T9lDmJXlFNt2LDfg6Ave9O2ok28RMAM83J SpT3EUd0ZmT2JXbhtTXyCdJ1n0rfvUlf7b/hEXB6vgxdhHW91BJ6oRPlnogBQkZeYIfR AZQX/0H5Uh6lSPO3pDQ3qpCHunDwj+g78378ZNKFFqqXCQhUoeTlaapDrwSB9OIwlgGJ c9OA== X-Gm-Message-State: AOJu0YxyWrItIc0Jc+fKd9MLZW9fhS90SVUuRTKHLCDw7pBxtN5PhYP3 qIhEjRzYzM9kzu5yLn0N2Izc+tca8r1SL8B2VW0PlkGT5U3xrSodcqtXq3YVm5xE5e3DrEhTIuJ D6/ZsRXewcs4Jg2QN7FEKO51iX/folKNp X-Gm-Gg: ASbGncuh1T2j3VfK+GuaHNdlXhA9GKLC5XM6abRYsq1Lnwd00uOF2dPgUNs1ur7ywZl Qu/mbUhyswwuVzcz9KLy02edoedEpGQ/UOvHPTA== X-Google-Smtp-Source: AGHT+IECv+mUIb/+vB8rnVVNKXo5RoQ0Ej3dnSjgHQTLB93vEIZb1Fp86qaKg/eDf0DI/R75+wWs3826YLXxLFTBNcU= X-Received: by 2002:a05:6402:5203:b0:5d0:ee52:353e with SMTP id 4fb4d7f45d1cf-5d7ee4242d0mr200184a12.29.1734463178858; Tue, 17 Dec 2024 11:19:38 -0800 (PST) List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@FreeBSD.org MIME-Version: 1.0 From: Alan Somers Date: Tue, 17 Dec 2024 12:19:26 -0700 Message-ID: Subject: Why does namei return an exclusively locked vnode when LOCKSHARED is specified? To: FreeBSD CURRENT Content-Type: text/plain; charset="UTF-8" X-Spamd-Result: default: False [0.37 / 15.00]; SUBJECT_ENDS_QUESTION(1.00)[]; NEURAL_HAM_MEDIUM(-0.60)[-0.605]; FORGED_SENDER(0.30)[asomers@freebsd.org,asomers@gmail.com]; NEURAL_HAM_SHORT(-0.21)[-0.206]; 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]; MIME_GOOD(-0.10)[text/plain]; NEURAL_SPAM_LONG(0.08)[0.080]; TO_DN_ALL(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; ARC_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; RCVD_TLS_LAST(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; FROM_HAS_DN(0.00)[]; RCVD_COUNT_ONE(0.00)[1]; FREEMAIL_ENVFROM(0.00)[gmail.com]; MLMMJ_DEST(0.00)[freebsd-current@freebsd.org]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; FROM_NEQ_ENVFROM(0.00)[asomers@freebsd.org,asomers@gmail.com]; MISSING_XM_UA(0.00)[]; R_DKIM_NA(0.00)[]; RWL_MAILSPIKE_POSSIBLE(0.00)[209.85.208.54:from]; TO_DOM_EQ_FROM_DOM(0.00)[]; FREEFALL_USER(0.00)[asomers]; ASN(0.00)[asn:15169, ipnet:209.85.128.0/17, country:US]; RCVD_IN_DNSWL_NONE(0.00)[209.85.208.54:from] X-Rspamd-Queue-Id: 4YCRT93XcMz4RTx X-Spamd-Bar: / According to namei(9), namei should return a shared lock when LOCKSHARED is specified. But in my experiments, it always seems to return an exclusive lock instead. For example: $ cd /usr/tests/sys/fs/fusefs $ sudo dtrace -i 'fbt:fusefs:fuse_vnop_getattr:entry /pid==$target/ {printf("islocked=%#x", args[0]->a_vp->v_vnlock->lk_lock); stack();}' -i 'fbt:kernel:vop_stdstat:entry /pid==$target/ {printf("islocked=%#x", args[0]->a_vp->v_vnlock->lk_lock);}' -c "./getattr --gtest_filter=Getattr.attr_cache -v" [==========] Running 1 test from 1 test suite. [----------] Global test environment set-up. [----------] 1 test from Getattr [ RUN ] Getattr.attr_cache INIT ino= 0 ACCESS ino= 1 mask=0x1 LOOKUP ino= 1 some_file.txt GETATTR ino=42 [ OK ] Getattr.attr_cache (3 ms) [----------] 1 test from Getattr (3 ms total) [----------] Global test environment tear-down [==========] 1 test from 1 test suite ran. (4 ms total) [ PASSED ] 1 test. CPU ID FUNCTION:NAME 3 19743 vop_stdstat:entry islocked=0x21 3 19743 vop_stdstat:entry islocked=0xfffff80004f16740 3 68298 fuse_vnop_getattr:entry islocked=0xfffff80004f16740 kernel`VOP_GETATTR_APV+0x90 kernel`vop_stdstat+0x147 kernel`VOP_STAT_APV+0x91 kernel`kern_statat+0x183 kernel`sys_fstatat+0x27 kernel`amd64_syscall+0x1af kernel`0xffffffff8106cd5b 3 19743 vop_stdstat:entry islocked=0xfffff80004f16740 3 68298 fuse_vnop_getattr:entry islocked=0xfffff80004f16740 kernel`VOP_GETATTR_APV+0x90 kernel`vop_stdstat+0x147 kernel`VOP_STAT_APV+0x91 kernel`kern_statat+0x183 kernel`sys_fstatat+0x27 kernel`amd64_syscall+0x1af kernel`0xffffffff8106cd5b dtrace: pid 3554 has exited >From that output, the first vop_stdstat is probably for the mountpoint, and isn't what I'm concerned about. But the second two are for a fusefs file. The LK_SHARE bit is not set, indicating an exclusive lock. That's even though the call to namei in kern_statat specifies LOCKSHARED | LOCKLEAF. What am I missing? From nobody Tue Dec 17 19:27: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 4YCRfR4hjyz5hcSg for ; Tue, 17 Dec 2024 19:27:43 +0000 (UTC) (envelope-from markjdb@gmail.com) Received: from mail-qt1-x82b.google.com (mail-qt1-x82b.google.com [IPv6:2607:f8b0:4864:20::82b]) (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 4YCRfR2Rd7z4TCr; Tue, 17 Dec 2024 19:27:43 +0000 (UTC) (envelope-from markjdb@gmail.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-qt1-x82b.google.com with SMTP id d75a77b69052e-4679eacf25cso29237881cf.3; Tue, 17 Dec 2024 11:27:43 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1734463662; x=1735068462; darn=freebsd.org; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:cc:to:from:date:sender:from:to:cc:subject:date:message-id :reply-to; bh=sikpmuVhMi5uEr9cN8LuPeQp/azzNyWCVtD5nK80410=; b=N4D96A4GQuiwokX0TLYDugb0M+vbaiht+9h/v7aO1gxbXlINHMASyeeUUssFp1NISD hE5yD4XXRGjRfh4ubfVdRWu/fuIIVPBLNvxMoNH+dPy++h0ht6odORTpzcfuzDSqQZ6b Y/3gSWawY4Gx1WGC+xvdPE44RZ2jomMmuE11+cySC1WE4YvqQFxXdMi9ePd7DYVv83I3 ajy3oO23wnHaJ2RMn2GlRzkJHC0NnCaxQ2iNIsEEf5AMsoTl3Vc0z4AHYGtE31Ywy7Z7 tVUOI55VCWE2P0k03uQIJd4MV2Ud7VzNwx4UdUgWW9D1ISHkvzvEsv7TiA1ZG3RGKF0C k8ow== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1734463662; x=1735068462; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:cc:to:from:date:sender:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=sikpmuVhMi5uEr9cN8LuPeQp/azzNyWCVtD5nK80410=; b=GBs2AnFVLRMTuh6QPrYuBYN92ZUVcjeXcIk0inuDrUz5KxmTOPMh4OiQeORal7jGn/ 46RcfOGhB4MQW5eyvIuOkaDvk7dyrz6xoMVjW49YPKBPnR/O6O+jlIgP0u/kN13DDmbb ryv0/KBsxEXKGQlV1xmtqJG6/X2oAIItKt2hnraE8WhPK+HAwvLtL4CkB75kd09LVhb2 P/l3WEqXcfRThEdASL/bht8nKDfpa0IHFTpblsJ/HMwLWezfhd1XNJgnZBiY/3yURHOP PMfb7mtGKtsUy7EEihToEqSMcNBl/XMIahcTr7Eiaz1KfinDCd+GEf7JhAyqDATLgHCP kWOQ== X-Gm-Message-State: AOJu0YwPcvthQM24jzb3B87/ZIm+YjFBiB7Vrmjq/8WdVdbNmFeL+j+y TVp95UrhGee/BmuUaYezdEMCLEWxegKKbk9hAgFgHLhUjaYleffvDwg57A== X-Gm-Gg: ASbGncvgdufrzuaBfIrCnoXkpmI1VsRqZaVL/kIRioQaEmcdaa3qep7aKK3BcB2cPK6 mjzgpeY8eojLBFhIyoyvJaqqNTgWgPaax67zxJ4i1zvT4cBjFDM0IklfZ6+Cj+LhUEiqSMQmT8i uXocBsEUb9WVWm+tia96z2U2JapsgTmVbNfswKErAjYFhHmCYlwPZYSg+1X0HPUNkchNoFRkYAq FBBU1/EmakTuVr7paOvIUj7St62o8AID62/sIeCEeCTl4/lmDAIBFAzr3xL9Ba0GYIemXM= X-Google-Smtp-Source: AGHT+IFMYWyjDjtn7FKq94qzv50ONTMQLDsCJAJ+SfEqfGdTYxYMhrsHB3NPo/FpSjWGLO5bBSGpwQ== X-Received: by 2002:ac8:5a48:0:b0:467:65d4:7e07 with SMTP id d75a77b69052e-46908ec9ab6mr247441cf.53.1734463662116; Tue, 17 Dec 2024 11:27:42 -0800 (PST) Received: from nuc (192-0-220-237.cpe.teksavvy.com. [192.0.220.237]) by smtp.gmail.com with ESMTPSA id d75a77b69052e-467b2cbb69asm42657471cf.39.2024.12.17.11.27.40 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 17 Dec 2024 11:27:41 -0800 (PST) Date: Tue, 17 Dec 2024 14:27:38 -0500 From: Mark Johnston To: Alan Somers Cc: FreeBSD CURRENT Subject: Re: Why does namei return an exclusively locked vnode when LOCKSHARED is specified? Message-ID: References: List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@FreeBSD.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US] X-Rspamd-Queue-Id: 4YCRfR2Rd7z4TCr X-Spamd-Bar: ---- On Tue, Dec 17, 2024 at 12:19:26PM -0700, Alan Somers wrote: > According to namei(9), namei should return a shared lock when > LOCKSHARED is specified. But in my experiments, it always seems to > return an exclusive lock instead. For example: > > $ cd /usr/tests/sys/fs/fusefs > $ sudo dtrace -i 'fbt:fusefs:fuse_vnop_getattr:entry /pid==$target/ > {printf("islocked=%#x", args[0]->a_vp->v_vnlock->lk_lock); stack();}' > -i 'fbt:kernel:vop_stdstat:entry /pid==$target/ > {printf("islocked=%#x", args[0]->a_vp->v_vnlock->lk_lock);}' -c > "./getattr --gtest_filter=Getattr.attr_cache -v" > [==========] Running 1 test from 1 test suite. > [----------] Global test environment set-up. > [----------] 1 test from Getattr > [ RUN ] Getattr.attr_cache > INIT ino= 0 > ACCESS ino= 1 mask=0x1 > LOOKUP ino= 1 some_file.txt > GETATTR ino=42 > [ OK ] Getattr.attr_cache (3 ms) > [----------] 1 test from Getattr (3 ms total) > > [----------] Global test environment tear-down > [==========] 1 test from 1 test suite ran. (4 ms total) > [ PASSED ] 1 test. > CPU ID FUNCTION:NAME > 3 19743 vop_stdstat:entry islocked=0x21 > 3 19743 vop_stdstat:entry islocked=0xfffff80004f16740 > 3 68298 fuse_vnop_getattr:entry islocked=0xfffff80004f16740 > kernel`VOP_GETATTR_APV+0x90 > kernel`vop_stdstat+0x147 > kernel`VOP_STAT_APV+0x91 > kernel`kern_statat+0x183 > kernel`sys_fstatat+0x27 > kernel`amd64_syscall+0x1af > kernel`0xffffffff8106cd5b > > 3 19743 vop_stdstat:entry islocked=0xfffff80004f16740 > 3 68298 fuse_vnop_getattr:entry islocked=0xfffff80004f16740 > kernel`VOP_GETATTR_APV+0x90 > kernel`vop_stdstat+0x147 > kernel`VOP_STAT_APV+0x91 > kernel`kern_statat+0x183 > kernel`sys_fstatat+0x27 > kernel`amd64_syscall+0x1af > kernel`0xffffffff8106cd5b > > dtrace: pid 3554 has exited > > From that output, the first vop_stdstat is probably for the > mountpoint, and isn't what I'm concerned about. But the second two > are for a fusefs file. The LK_SHARE bit is not set, indicating an > exclusive lock. That's even though the call to namei in kern_statat > specifies LOCKSHARED | LOCKLEAF. > > What am I missing? Having noticed the same phenomenon in p9fs and scratching my head for a while: is fusefs failing to call VN_LOCK_ASHARE() in this case? I see that it's predicated on "data->dataflags & FSESS_ASYNC_READ", but I'm not sure why - the comment seems to suggest a misunderstanding of what VN_LOCK_ASHARE() does. ... oh, also perhaps because fusefs mounts don't set MNTK_LOOKUP_SHARED? From nobody Tue Dec 17 20:02:18 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 4YCSQd388hz5hfWd for ; Tue, 17 Dec 2024 20:02:33 +0000 (UTC) (envelope-from asomers@gmail.com) Received: from mail-ed1-f52.google.com (mail-ed1-f52.google.com [209.85.208.52]) (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 4YCSQc6q08z4Xg5; Tue, 17 Dec 2024 20:02:32 +0000 (UTC) (envelope-from asomers@gmail.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-ed1-f52.google.com with SMTP id 4fb4d7f45d1cf-5d3e6f6cf69so2621425a12.1; Tue, 17 Dec 2024 12:02:32 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1734465751; x=1735070551; 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=HSvS9hikQgHwQ0/+gc+R/5zsN4hIyPWkLRkxA3QrurY=; b=PcQIL2hWG2mGdTW6/HD+aZxVXCKvIpaGHiFUs0Kf2nMAAFtca3wh/XOUT4eYRRSjVJ TLptRqvmZUOEfqQevVJ28wh2lo3/hDav8Q2Tw6mvwHomeCTYIu9uRas1Jry4QanNbQK7 v/+XeV0WSlJO5Wi0r06+jwtZxYSSlgxCLxpjqiS8kqldMAsMAz+I4e5FIGdoCxIiMO+3 8p102ACONBapGqevZEoOdyWn4qLkwmmn3HG+nLKf58+aWE3Nb8jakT67chaLOCNjSp3a 4MI6uHLMvmnEQjN0WyiQfNWm1t5nzdZpWuLijnUkM9q1ObT/jcXLaSZ6fTRE9CWiiwpX BFxA== X-Gm-Message-State: AOJu0YzcVGXxVtBm0pgkhmDfnDQJZPI4xVMCVu91PVre31ggZxNeY5t4 Yq8OGRQ0n/MyKPecFHKljzDN9uVdMwEuzkICMuGOqR4midDOfqE2Pi9MUQPQFA+pSFa4TgrKu7B 5KVmGosa2LmOGkyVlFfwKgQWLUNN2VQ== X-Gm-Gg: ASbGncuZjJ7PER5IrJgu2PakCH5yA8mrQg9m8iph3yaV0mUOL19LVbrCJKp0B7Fn/w5 igtkyn3ABe37CDKVtVt26qJOo3bL6yXk4KBvoeA== X-Google-Smtp-Source: AGHT+IF7A6nCZAp7bijcUvYUqNFdp7d22tKhyZKzxGhyXRNjvpxFB/fuTuddHeqXWc7R5p1TZqPlgv4htxJ/1o3+KCk= X-Received: by 2002:a05:6402:448a:b0:5d0:a80d:bce9 with SMTP id 4fb4d7f45d1cf-5d7ee3b62c0mr250840a12.20.1734465750636; Tue, 17 Dec 2024 12:02:30 -0800 (PST) List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@FreeBSD.org MIME-Version: 1.0 References: In-Reply-To: From: Alan Somers Date: Tue, 17 Dec 2024 13:02:18 -0700 Message-ID: Subject: Re: Why does namei return an exclusively locked vnode when LOCKSHARED is specified? To: Mark Johnston Cc: FreeBSD CURRENT Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable 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: 4YCSQc6q08z4Xg5 X-Spamd-Bar: ---- On Tue, Dec 17, 2024 at 12:27=E2=80=AFPM Mark Johnston = wrote: > > On Tue, Dec 17, 2024 at 12:19:26PM -0700, Alan Somers wrote: > > According to namei(9), namei should return a shared lock when > > LOCKSHARED is specified. But in my experiments, it always seems to > > return an exclusive lock instead. For example: > > > > $ cd /usr/tests/sys/fs/fusefs > > $ sudo dtrace -i 'fbt:fusefs:fuse_vnop_getattr:entry /pid=3D=3D$target/ > > {printf("islocked=3D%#x", args[0]->a_vp->v_vnlock->lk_lock); stack();}' > > -i 'fbt:kernel:vop_stdstat:entry /pid=3D=3D$target/ > > {printf("islocked=3D%#x", args[0]->a_vp->v_vnlock->lk_lock);}' -c > > "./getattr --gtest_filter=3DGetattr.attr_cache -v" > > [=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D] Running 1 test from 1 test suite. > > [----------] Global test environment set-up. > > [----------] 1 test from Getattr > > [ RUN ] Getattr.attr_cache > > INIT ino=3D 0 > > ACCESS ino=3D 1 mask=3D0x1 > > LOOKUP ino=3D 1 some_file.txt > > GETATTR ino=3D42 > > [ OK ] Getattr.attr_cache (3 ms) > > [----------] 1 test from Getattr (3 ms total) > > > > [----------] Global test environment tear-down > > [=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D] 1 test from 1 test suite ran. (4 ms to= tal) > > [ PASSED ] 1 test. > > CPU ID FUNCTION:NAME > > 3 19743 vop_stdstat:entry islocked=3D0x21 > > 3 19743 vop_stdstat:entry islocked=3D0xfffff80004f167= 40 > > 3 68298 fuse_vnop_getattr:entry islocked=3D0xfffff80004f167= 40 > > kernel`VOP_GETATTR_APV+0x90 > > kernel`vop_stdstat+0x147 > > kernel`VOP_STAT_APV+0x91 > > kernel`kern_statat+0x183 > > kernel`sys_fstatat+0x27 > > kernel`amd64_syscall+0x1af > > kernel`0xffffffff8106cd5b > > > > 3 19743 vop_stdstat:entry islocked=3D0xfffff80004f167= 40 > > 3 68298 fuse_vnop_getattr:entry islocked=3D0xfffff80004f167= 40 > > kernel`VOP_GETATTR_APV+0x90 > > kernel`vop_stdstat+0x147 > > kernel`VOP_STAT_APV+0x91 > > kernel`kern_statat+0x183 > > kernel`sys_fstatat+0x27 > > kernel`amd64_syscall+0x1af > > kernel`0xffffffff8106cd5b > > > > dtrace: pid 3554 has exited > > > > From that output, the first vop_stdstat is probably for the > > mountpoint, and isn't what I'm concerned about. But the second two > > are for a fusefs file. The LK_SHARE bit is not set, indicating an > > exclusive lock. That's even though the call to namei in kern_statat > > specifies LOCKSHARED | LOCKLEAF. > > > > What am I missing? > > Having noticed the same phenomenon in p9fs and scratching my head for a > while: is fusefs failing to call VN_LOCK_ASHARE() in this case? I see > that it's predicated on "data->dataflags & FSESS_ASYNC_READ", but I'm > not sure why - the comment seems to suggest a misunderstanding of what > VN_LOCK_ASHARE() does. > > ... oh, also perhaps because fusefs mounts don't set MNTK_LOOKUP_SHARED? Yes, that's it! Both of those things need to change. Now I can get on with solving my real bug. Thank you. From nobody Tue Dec 17 23:48:24 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 4YCYRH42Ckz5htYQ for ; Tue, 17 Dec 2024 23:48:27 +0000 (UTC) (envelope-from glebius@freebsd.org) Received: from smtp.freebsd.org (smtp.freebsd.org [IPv6:2610:1c1:1:606c::24b:4]) (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 "R10" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4YCYRH3Y4Gz3xKt; Tue, 17 Dec 2024 23:48:27 +0000 (UTC) (envelope-from glebius@freebsd.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1734479307; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type; bh=YG4ztVUDpeIK2zrs+rREDylQavZ38/YTUkXAearKSBw=; b=HnUsYgvrDx892bcKMDmp99vNc7cdoAhCDYB/N98K90t+S2GOM66sjCBF5zir8ibkY0qdQs n8fvTHk9IByi9Rik5gAjYqBHBcY99iX35QpRxqwG1KZqP5LI7EYsAFTKPVoCJmOM1zfxTM sdu1z34bxzXROMPtb7swe0pK8xCJZv+nxTLlB1a9Dh5nUUWzkKxbGcpaOTXt8C4XtJ/5gb 22xK/0j3kU/74/EvrzgtsnwqNJ7K6BAnZ5TM+xJojd/KndkC58mWjV87SZx6emxDdu6D2w C2hfcmArvhp3Y6zC+PWLOv1g1dIWzHoLj6uxCmvg6gHv7b/ush85iAMgdbCePw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1734479307; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type; bh=YG4ztVUDpeIK2zrs+rREDylQavZ38/YTUkXAearKSBw=; b=q5TMzdSoNrDrQVibLpi0QdoZgP7g4bBy4yPiwg+31YSsQI1d2EK8/0S4z32odR9lKkOWQW 8kJtvIUbXp1FZl2Rhlnci7rZ0QfAtsnlWm9jjdQ1mSgH5tc5Cviq0u7eU2Vxys5KdphH5I Snvuc4e8yrRKEqZELsXp+Jqvzn92VDfiFi2VyegU49sLIjWIMkQABu6PL+oX/AMAgYkn33 BX9etDgTPCmzesoH3JNM8t5Rg6sbscKl63K0Gobsp1zs+1HBkStWTdPxd3TsNGIqXZm9nq YJl++/pYvJYSu9QvH8qrMlfOHnVsU93kx/UwSEZPoMqKIsuYzlZluekMyvGPHg== ARC-Authentication-Results: i=1; mx1.freebsd.org; none ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1734479307; a=rsa-sha256; cv=none; b=pn3GkX684Sct8wvWW28OYQoGLZhjJ0YpP+HJZolO664KI6viVdhY07Bh2RotmspKYxK11c EQLBHofDtMgDiWyx8IKBFoRekpK/9lsQZVZvVimhn2cWbTh+AirxCyZCFJ1YFpG8y7kaNy KwAEwb+bj+k0r479WCUsob4zBtsHGt6huzUb+cdnFslFNcymEf9YKiTn0XvLz6Ioi5wNNn fbDxaQ3szdbKoVcE9HkbbDKhyXtCGXN4TesfFH9Aj3SOo/ax6dkVgqtPOCUUpmmkdB9HQc Bt/zy2Sgw8lsxPeBXcL4F2BfRRMPWyYeldqnmS4yJ7cRg8kgXl3qQw86G9IE0g== Received: from cell.glebi.us (glebi.us [162.251.186.162]) (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) (Authenticated sender: glebius) by smtp.freebsd.org (Postfix) with ESMTPSA id 4YCYRH0F3Pzd7J; Tue, 17 Dec 2024 23:48:26 +0000 (UTC) (envelope-from glebius@freebsd.org) Date: Tue, 17 Dec 2024 15:48:24 -0800 From: Gleb Smirnoff To: freebsd-current@freebsd.org, src-committers@freebsd.org Subject: December 2024 stabilization week CANCELED! Message-ID: List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@FreeBSD.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Hi, due to shortage of human resources and due to reservation of certain hardware for the Christmas events, we won't be able to properly A/B test the December snapshot at Netflix as we usually do. Given that testing performed by Netflix is the largest sieve to catch regressions, and we still don't have any second large party participating in the stabweek, me together with David dhw@ decided that this month the stabweek to be skipped. -- Gleb Smirnoff From nobody Wed Dec 18 06:15:40 2024 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4YCk281DrYz5gsDk for ; Wed, 18 Dec 2024 06:15:44 +0000 (UTC) (envelope-from glebius@freebsd.org) Received: from smtp.freebsd.org (smtp.freebsd.org [IPv6:2610:1c1:1:606c::24b:4]) (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 "R10" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4YCk280hyHz4XvM; Wed, 18 Dec 2024 06:15:44 +0000 (UTC) (envelope-from glebius@freebsd.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1734502544; 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=he3mvkBjYkcrMIP0Fw0ci6RJumNtyQtZxLcYLR5f16c=; b=b2yMjzgWgXhOUw3+EGNh4V9rV3D7MtFVqoSS2e5MBKPIhIf+6pU8J+EMAtR2CKqVv/vdM8 wJGOzNJzwcht3veoDTNhZ2fwfz9TG0+NRLlzY3wl4jArjeHlET/ve922P9eErnNsBg6uTU pZQwDLS5Gg3g3QPabcoGb2xMk1kaIw+fCdnIjudZKOwNJ1B/4ncwdWMjN2rWZu0e7Qo67I 8YeLLutIP7s+9uL1Qd22sXZtzAtJjL4BhNrW0BFOZ/c1GdoxQIjHfSx3r7MOp7yQF5Hjum vCV0q7Q353RGMiQ4/2pzUjnfS/VPXWNGIx3yjps32DW+5fJUaD/FDuxQWMk6xQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1734502544; 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=he3mvkBjYkcrMIP0Fw0ci6RJumNtyQtZxLcYLR5f16c=; b=QNSSrhqmTUYgLmwo0hw9n8MGNwfQwjNxq0smz7QbB4qE3GoyO53aTM4IYBkMFtHa5KCEG8 R2kG/uFaUGfGbqvKBRzfubpLNgjgiB44ggCgtwhYSdB/x5Nirk7zARabjTov8sZgjVMkId lchNsmTGrE2jIl3crvarWNvO+F9KpVgooy7Vh610ts82NB9cbzf+xHnWDcPt14d9l/9RKw 2ob0oPpPldUBuHIp1p/CQAFZ69uEIw3gnVxd6FZRBmKXmqLtQcTmBNeYWPbHJFMyizi5WY ps3s4qapkiBV9mtxJiZxXsyJn4H/a4+XJG4VWzZ/uJ1P5UtQOkN7SmYsSvM/DQ== ARC-Authentication-Results: i=1; mx1.freebsd.org; none ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1734502544; a=rsa-sha256; cv=none; b=CuZ+Pzcr/jw/yajFzm3QIRBM16ZXNluTCieTJ6q6LDljBFDCht50hne2ZRL/ptw7tIvada GGf6kzzhCwaG634uLWHsdMI6AK6b6QvQQof2Kem1/xNnXFemUFwUPjjY4pbqvFudOhAMfz RbaNm7sYU+tkBGgLjDvQneW2RvN6K5d3AbFOnnrNcSKq50TMJw49PtdzzMGsmzcqAO8VcB E5o5Y6aGv8XjslQWTvZLuN92XYFeDbJPgHw+PCCR3nOt1XHu0r1E/wo/EwbkVARNlviVXu F9bFbu0cWvxTYbna5dNcXh9N1sJw6VACbh3ZQKGM/R6A/ZgB43pU86p/L8xHjw== Received: from cell.glebi.us (glebi.us [162.251.186.162]) (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) (Authenticated sender: glebius) by smtp.freebsd.org (Postfix) with ESMTPSA id 4YCk274PbGz13S3; Wed, 18 Dec 2024 06:15:43 +0000 (UTC) (envelope-from glebius@freebsd.org) Date: Tue, 17 Dec 2024 22:15:40 -0800 From: Gleb Smirnoff To: George Neville-Neil Cc: freebsd-current@freebsd.org, src-committers@freebsd.org Subject: Re: December 2024 stabilization week CANCELED! Message-ID: References: <53FED895-91D1-46F1-8702-A82B9E046927@neville-neil.com> List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@FreeBSD.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <53FED895-91D1-46F1-8702-A82B9E046927@neville-neil.com> On Wed, Dec 18, 2024 at 08:29:46AM +0800, George Neville-Neil wrote: G> > due to shortage of human resources and due to reservation of certain hardware G> > for the Christmas events, we won't be able to properly A/B test the December G> > snapshot at Netflix as we usually do. Given that testing performed by Netflix G> > is the largest sieve to catch regressions, and we still don't have any second G> > large party participating in the stabweek, me together with David dhw@ decided G> > that this month the stabweek to be skipped. G> G> How much hardware is required for this? Could this be done with new machines either in the cluster or at Sentex (the test lab) or does this have to be done at NetFlix because that's where the systems are best set up to do this? If more hardware is needed you should talk to Ed at the Foundation and get some ordered. I don't think there is anything in the world comparable to the A/B testing that David does at Netflix. Although, the test covers only some subset of FreeBSD functionality: TCP (including advanced stacks), sendfile(2), kernel TLS and a small set of device drivers, it does that at a very large scale on production traffic. You can't repeat that at home :) But the point is not about substituting the David's test with an other test (next week or anytime). The point of the stabweeks cycle is that several parties pick the same revision and extensively test it with their own tests. I was really hoping that more large companies that use FreeBSD would join the stabweek cycle, that the FreeBSD cluster updates would also use the same revision, that more individuals will follow the stabweek. Unfortunately, little participation is observed right now. This December, if we exclude Netflix/dhw@ test from the stabweek, it would be only a handful of individuals updating their desktops, which in my opinion, isn't enough to announce a stabweek and the associated freeze. But for any future months any additional testing resources are very much appreciated. E.g., I'd be glad to see Peter's Holm stress2 running on the Sentex test lab during Monday of stabweek. If you can provide more coverage in future stabweeks - please join. -- Gleb Smirnoff From nobody Wed Dec 18 18:15:45 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 4YD21G07tkz5hgbN for ; Wed, 18 Dec 2024 18:16:02 +0000 (UTC) (envelope-from asomers@gmail.com) Received: from mail-ed1-f48.google.com (mail-ed1-f48.google.com [209.85.208.48]) (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 4YD21F0kQxz4l5t for ; Wed, 18 Dec 2024 18:16:01 +0000 (UTC) (envelope-from asomers@gmail.com) Authentication-Results: mx1.freebsd.org; dkim=none; spf=pass (mx1.freebsd.org: domain of asomers@gmail.com designates 209.85.208.48 as permitted sender) smtp.mailfrom=asomers@gmail.com; dmarc=fail reason="SPF not aligned (relaxed), No valid DKIM" header.from=freebsd.org (policy=none) Received: by mail-ed1-f48.google.com with SMTP id 4fb4d7f45d1cf-5d3e8f64d5dso12354070a12.3 for ; Wed, 18 Dec 2024 10:16:01 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1734545759; x=1735150559; h=content-transfer-encoding:cc: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=vlb8clm+GUW0C4+2M33ZNNF89F5WHms+nojnrUAe4Iw=; b=VzZbJHwCfdAXYfD2lith82vJvLSZI8Enrd7zUYHegRmwVXWZ5SI3JTdpL+C0wBMi2j 2Jt1jB3rslcLWV/ZarySj3WjMrb1AyWoGrBud6exF/nzVtgR6Wc3SZS7t5g2o9cgRJgo 0vPEDNQhkvCLEJZHoqkxWLOolQ9lorqG/zJ7z5Z2Bn06v4OjGFU0u63xpQjrQGC90jtA hjZFSsCGiZU1vo0eutBki8pMK9I2V+Y9lLZSa8Vp3iMhZ0gzjvACbHIbaNtvHV2xj9v8 EAK090IS9cx1LcQUZsi2IoCvsyD9ePygQ0dmCc68agj5mIJ4QSfgWVxlLQEkB5pFrRIA Rv+w== X-Forwarded-Encrypted: i=1; AJvYcCVFCNsvfWIpun9Bj+TNAgcWrsVBLVUAaOLvNXwsDLoyupHQMp9VIUoEDEy9HSkjG4tpgI90lSwcaOj4c+2IqGg=@freebsd.org X-Gm-Message-State: AOJu0Yxnt63PQawOtnmFe/cmB0nxi+NrOEut+nmSuyY8y0OF9MiUMvN3 C2pZyd+iyibFEb21x5h+g4mZUmleVQvTXOrjzPW755/4vBbxQKQSwXGzJVbJBuxAT4we5+hK+Ii S4eXjfW0QEiE0sX+lptel8GTMYNSNsJkH X-Gm-Gg: ASbGncuAA2TVnW6ytCqbDpstVB8KKM33E8cJa8q5ezRpu8QgQ2fCz3rbKymAmUMXLtK x/z8aEpjXuxuHWgbB1FR6l3L+iNKWlxULw/yVOg== X-Received: by 2002:a05:6402:26ca:b0:5d4:4143:c07a with SMTP id 4fb4d7f45d1cf-5d7ee3a27eemt3228143a12.1.1734545757590; Wed, 18 Dec 2024 10:15:57 -0800 (PST) List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@FreeBSD.org MIME-Version: 1.0 References: In-Reply-To: From: Alan Somers Date: Wed, 18 Dec 2024 11:15:45 -0700 Message-ID: Subject: Re: Why does namei return an exclusively locked vnode when LOCKSHARED is specified? Cc: Mark Johnston , FreeBSD CURRENT Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Spamd-Result: default: False [0.44 / 15.00]; MISSING_TO(2.00)[]; SUBJECT_ENDS_QUESTION(1.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-0.999]; NEURAL_HAM_SHORT(-0.99)[-0.995]; NEURAL_HAM_LONG(-0.66)[-0.664]; FORGED_SENDER(0.30)[asomers@freebsd.org,asomers@gmail.com]; R_SPF_ALLOW(-0.20)[+ip4:209.85.128.0/17:c]; DMARC_POLICY_SOFTFAIL(0.10)[freebsd.org : SPF not aligned (relaxed), No valid DKIM,none]; MIME_GOOD(-0.10)[text/plain]; RCVD_TLS_LAST(0.00)[]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_TWO(0.00)[2]; ARC_NA(0.00)[]; TO_DN_ALL(0.00)[]; MIME_TRACE(0.00)[0:+]; MISSING_XM_UA(0.00)[]; FREEFALL_USER(0.00)[asomers]; FREEMAIL_ENVFROM(0.00)[gmail.com]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; TO_MATCH_ENVRCPT_SOME(0.00)[]; FROM_NEQ_ENVFROM(0.00)[asomers@freebsd.org,asomers@gmail.com]; RCVD_COUNT_ONE(0.00)[1]; MLMMJ_DEST(0.00)[freebsd-current@freebsd.org]; RWL_MAILSPIKE_POSSIBLE(0.00)[209.85.208.48:from]; R_DKIM_NA(0.00)[]; ASN(0.00)[asn:15169, ipnet:209.85.128.0/17, country:US]; RCVD_IN_DNSWL_NONE(0.00)[209.85.208.48:from] X-Rspamd-Queue-Id: 4YD21F0kQxz4l5t X-Spamd-Bar: / On Tue, Dec 17, 2024 at 1:02=E2=80=AFPM Alan Somers w= rote: > > On Tue, Dec 17, 2024 at 12:27=E2=80=AFPM Mark Johnston wrote: > > > > On Tue, Dec 17, 2024 at 12:19:26PM -0700, Alan Somers wrote: > > > According to namei(9), namei should return a shared lock when > > > LOCKSHARED is specified. But in my experiments, it always seems to > > > return an exclusive lock instead. For example: > > > > > > $ cd /usr/tests/sys/fs/fusefs > > > $ sudo dtrace -i 'fbt:fusefs:fuse_vnop_getattr:entry /pid=3D=3D$targe= t/ > > > {printf("islocked=3D%#x", args[0]->a_vp->v_vnlock->lk_lock); stack();= }' > > > -i 'fbt:kernel:vop_stdstat:entry /pid=3D=3D$target/ > > > {printf("islocked=3D%#x", args[0]->a_vp->v_vnlock->lk_lock);}' -c > > > "./getattr --gtest_filter=3DGetattr.attr_cache -v" > > > [=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D] Running 1 test from 1 test suite. > > > [----------] Global test environment set-up. > > > [----------] 1 test from Getattr > > > [ RUN ] Getattr.attr_cache > > > INIT ino=3D 0 > > > ACCESS ino=3D 1 mask=3D0x1 > > > LOOKUP ino=3D 1 some_file.txt > > > GETATTR ino=3D42 > > > [ OK ] Getattr.attr_cache (3 ms) > > > [----------] 1 test from Getattr (3 ms total) > > > > > > [----------] Global test environment tear-down > > > [=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D] 1 test from 1 test suite ran. (4 ms = total) > > > [ PASSED ] 1 test. > > > CPU ID FUNCTION:NAME > > > 3 19743 vop_stdstat:entry islocked=3D0x21 > > > 3 19743 vop_stdstat:entry islocked=3D0xfffff80004f1= 6740 > > > 3 68298 fuse_vnop_getattr:entry islocked=3D0xfffff80004f1= 6740 > > > kernel`VOP_GETATTR_APV+0x90 > > > kernel`vop_stdstat+0x147 > > > kernel`VOP_STAT_APV+0x91 > > > kernel`kern_statat+0x183 > > > kernel`sys_fstatat+0x27 > > > kernel`amd64_syscall+0x1af > > > kernel`0xffffffff8106cd5b > > > > > > 3 19743 vop_stdstat:entry islocked=3D0xfffff80004f1= 6740 > > > 3 68298 fuse_vnop_getattr:entry islocked=3D0xfffff80004f1= 6740 > > > kernel`VOP_GETATTR_APV+0x90 > > > kernel`vop_stdstat+0x147 > > > kernel`VOP_STAT_APV+0x91 > > > kernel`kern_statat+0x183 > > > kernel`sys_fstatat+0x27 > > > kernel`amd64_syscall+0x1af > > > kernel`0xffffffff8106cd5b > > > > > > dtrace: pid 3554 has exited > > > > > > From that output, the first vop_stdstat is probably for the > > > mountpoint, and isn't what I'm concerned about. But the second two > > > are for a fusefs file. The LK_SHARE bit is not set, indicating an > > > exclusive lock. That's even though the call to namei in kern_statat > > > specifies LOCKSHARED | LOCKLEAF. > > > > > > What am I missing? > > > > Having noticed the same phenomenon in p9fs and scratching my head for a > > while: is fusefs failing to call VN_LOCK_ASHARE() in this case? I see > > that it's predicated on "data->dataflags & FSESS_ASYNC_READ", but I'm > > not sure why - the comment seems to suggest a misunderstanding of what > > VN_LOCK_ASHARE() does. > > > > ... oh, also perhaps because fusefs mounts don't set MNTK_LOOKUP_SHARED= ? > > Yes, that's it! Both of those things need to change. Now I can get > on with solving my real bug. Thank you. FYI: this is the bug I was working on: https://github.com/freebsd/freebsd-src/pull/1556 From nobody Thu Dec 19 16:12:46 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 4YDbDv2dtMz5hPRQ; Thu, 19 Dec 2024 16:13:03 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-lf1-f53.google.com (mail-lf1-f53.google.com [209.85.167.53]) (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 4YDbDt1FZ9z4rJr; Thu, 19 Dec 2024 16:13:02 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Authentication-Results: mx1.freebsd.org; dkim=none; spf=pass (mx1.freebsd.org: domain of adrian.chadd@gmail.com designates 209.85.167.53 as permitted sender) smtp.mailfrom=adrian.chadd@gmail.com; dmarc=fail reason="SPF not aligned (relaxed), No valid DKIM" header.from=freebsd.org (policy=none) Received: by mail-lf1-f53.google.com with SMTP id 2adb3069b0e04-5401ab97206so898282e87.3; Thu, 19 Dec 2024 08:13:02 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1734624779; x=1735229579; h=to:subject:message-id:date:from:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=5OzahfK3aM+N8chF5VuRXKDV9poWMA6ClPXebdGSZos=; b=gZ7Z2sIpV0bvly0Pweb24XQ4xacyMXL1K1cDT0YNVeqkNaK7vlG9oflNhABNUqOGuv pNW/a2WqVwcuSx/hvUgOdgOl40GtNf6aZWY6IWcI9Boi75TGYy5w5h7t/i7wWAtd7DRR buSuI4SBnWF/MEWM2BIMj31vAZ3i9oyPKjSCo2OMjH/hQb8GK6ey/SquJRbyIj9w7cHa YUsa6OW0INNixo7ETFhxrwszdHISTnRZrdwsjF54Wr4UWh9laC4qdmKuI4lR18HKnDhq zpOGF7v72yZJTWA6PWdbFYG+Bi8dfCK4Y+/Rnf2OO7J9hoA/2FZ9caW9gcNog3oN7mYt NDww== X-Forwarded-Encrypted: i=1; AJvYcCUx/2sCiYIROdZkYYiDbF/CxCwoxjo2/gSd9jEFMFJzasjRSGfDpHRmdHzQBlzfZOriVYd3YZhQMykqfBaf6hQ=@freebsd.org X-Gm-Message-State: AOJu0YxKrQkdUiD7xA9ENEk5WcwMkyqmU/wBkjXtDaHIiH8Z2ydRvTIn YW7OSBI3ZpNZy9aLbvHb7gsT/XEJPXyt5gE5bS6tbsGPh612Cwp+ZoX5Vh3h9/6XlczcihFdGzm TxsBqy1oyULLnnmNTtRQfG4DT1gjtTQ== X-Gm-Gg: ASbGncuzS9DOahSS+DeGmkf2a1glyL3j8hapKHh9xFsQCdllcwZvlNyVFjVGY/EQ2X1 zmdo0F1dLBhyc4629WE269fiWadXDmP/ygMWk2uE= X-Google-Smtp-Source: AGHT+IGW4xK4M80BhIlJG1ghjoZi6QPsPD0gMBCICEgDE1ae38IyOZgjN+fViU86mHbgmnPZ2D+cXUTfTiaTa/UVfdA= X-Received: by 2002:a05:6512:3d25:b0:542:2871:535e with SMTP id 2adb3069b0e04-542287154ebmr15884e87.55.1734624778945; Thu, 19 Dec 2024 08:12:58 -0800 (PST) List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@FreeBSD.org MIME-Version: 1.0 From: Adrian Chadd Date: Thu, 19 Dec 2024 08:12:46 -0800 Message-ID: Subject: rtwn updates, please test (especially if you're using an RTL8192CU) To: freebsd-wireless , freebsd-current Content-Type: multipart/alternative; boundary="000000000000c48e240629a1cd59" X-Spamd-Result: default: False [-1.73 / 15.00]; NEURAL_HAM_LONG(-1.00)[-0.996]; NEURAL_HAM_SHORT(-0.93)[-0.934]; FORGED_SENDER(0.30)[adrian@freebsd.org,adrianchadd@gmail.com]; R_SPF_ALLOW(-0.20)[+ip4:209.85.128.0/17]; NEURAL_SPAM_MEDIUM(0.10)[0.104]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; DMARC_POLICY_SOFTFAIL(0.10)[freebsd.org : SPF not aligned (relaxed), No valid DKIM,none]; ASN(0.00)[asn:15169, ipnet:209.85.128.0/17, country:US]; RCVD_COUNT_ONE(0.00)[1]; MISSING_XM_UA(0.00)[]; MIME_TRACE(0.00)[0:+,1:+,2:~]; FREEMAIL_ENVFROM(0.00)[gmail.com]; RWL_MAILSPIKE_POSSIBLE(0.00)[209.85.167.53:from]; RCPT_COUNT_TWO(0.00)[2]; R_DKIM_NA(0.00)[]; TAGGED_FROM(0.00)[]; FROM_NEQ_ENVFROM(0.00)[adrian@freebsd.org,adrianchadd@gmail.com]; FROM_HAS_DN(0.00)[]; RCVD_IN_DNSWL_NONE(0.00)[209.85.167.53:from]; TO_DN_ALL(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; RCVD_TLS_LAST(0.00)[]; MLMMJ_DEST(0.00)[freebsd-wireless@freebsd.org,freebsd-current@freebsd.org]; ARC_NA(0.00)[] X-Rspamd-Queue-Id: 4YDbDt1FZ9z4rJr X-Spamd-Bar: - --000000000000c48e240629a1cd59 Content-Type: text/plain; charset="UTF-8" hi! I've pushed a bunch more changes / fixes into rtwn. This includes a bunch of RTL8192CU fixes and preparation for firmware rate control support. One of the changes removes an old work-around. I've tested it locally on my 11bg and 11bgn APs in 11b, 11g and 11n modes. It seemed to behave just fine now that I've fixed other parts of the driver. But 802.11 is unpredictable at the best of times, and it's possible I haven't been in enough weird wifi environments lately! So if you're using rtwn, please do update to the latest -HEAD and try it out and report back. If you're using or have an RTL8192CU USB NIC, I would super appreciate any feedback about behavioural changes. Thanks! -adrian --000000000000c48e240629a1cd59 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
hi!

I've pushed a bunch more change= s / fixes into rtwn. This includes=C2=A0a bunch of RTL8192CU fixes and prep= aration for firmware rate control support.

One of = the changes removes an old work-around. I've tested it locally on my 11= bg and 11bgn APs in 11b, 11g and 11n modes. It seemed to behave just fine n= ow that I've fixed other parts of the driver. But 802.11 is unpredictab= le at the best of times, and it's possible I haven't been in enough= weird wifi environments lately!

So if you're = using rtwn, please do update to the latest -HEAD and try it out and report = back. If you're using or have an RTL8192CU USB NIC, I would super appre= ciate any feedback about behavioural changes.

Than= ks!



-adrian

--000000000000c48e240629a1cd59-- From nobody Fri Dec 20 00:38:27 2024 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4YDpS61h0fz5h04S for ; Fri, 20 Dec 2024 00:38:30 +0000 (UTC) (envelope-from ler@FreeBSD.org) Received: from smtp.freebsd.org (smtp.freebsd.org [IPv6:2610:1c1:1:606c::24b:4]) (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 "R10" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4YDpS619JCz4qnr for ; Fri, 20 Dec 2024 00:38:30 +0000 (UTC) (envelope-from ler@FreeBSD.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1734655110; 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=xq5OjHgf8nsk5Nvlz4uOxINnqaHmUeVzQNtWi0pmuTo=; b=MjbcdGt0+UMtdriN86F4Jz58ZxDm6zVELWRfAH7XR+1AVryB36uVlLygz2xV6jzAkQO17t w/lj8nI53zHu9CBL4HiFl7V1RdKBlcOgsQIZwLQ3c16WbSdRpW/0IY6m0bX5YJJ6FhaL3B 2JR495N0xLW87TkoeZbz8hFhAKJTmgX/Q0AidYxg3B/WABwYxVevwNrQZ5qMwZeiLoRu2l VBCqv1DV/y8eiFeJjGDY0PfiS0uDQYGUChyVVGJmJWJ1eUGv1ftNFUOZNAStSBjr7vUXDR Afj2TFovfLT8X3au/v8r5Dmuj0+8kIEYfa17nUmpszZTpOEL/wAlIrbULuwIag== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1734655110; 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:dkim-signature; bh=xq5OjHgf8nsk5Nvlz4uOxINnqaHmUeVzQNtWi0pmuTo=; b=xWOZnOYRtp87atmhLuZAOJrOuClgkCvt7BPwox1Wnm2xxRjBOLaLqXP0UCdl0HRFMF1qVZ n4pvMxuZ1zyM1A2JPDXJBKhs0uowIIGPrAKx8JARqXprTHhJX4A2ZiFuJ554/MYwzx+OGX SQ4rUWjeo++5n0rhBWCl4omxPiPL4jbTKSOvPQ1CagunOOcDQlZQjU6nQb2ZyO2pr3UoNL 51mlu3YRWN6CedjxDX+rzXv4f7qY2mmYx66ZuSuZtkmkSajP9E2+j4cn2MPwRTM+TI1iG5 s26f+yKWi2kwkzlwDLt/M+X+qSkiWE+tvnkVMUucywhtfHQB5CWpC9gOM0TXtQ== ARC-Authentication-Results: i=1; thebighonker.lerctr.org; iprev=pass (thebighonker.lerctr.org) smtp.remote-ip=2607:9c00:1009::53:1; auth=pass (LOGIN) smtp.auth=ler@lerctr.org; spf=softfail smtp.mailfrom=FreeBSD.org; arc=none ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1734655110; a=rsa-sha256; cv=none; b=Am61x++GSu7mw5xDeBE2XiPihIcHegLp49bNHpWCQY/8Gq8nE4tYRti02qqDF6SmMrSHer 53G+Q2SI+wo4xGQpyPJXKFK81OGu5p64r8RIAu4f+OvfVlfRV0tdDLRElFIDnqFZSF4DQh E3EDInr480gy7s1JlLDVCA5q1NaePIrLHlQZ4Oteb+hEqArh19XPQSRrohx+1PJKZ7rwJi RQrjtai+FfRBQ4Rk1JusU/T0MqB/XQzlKz9EMNFnQHf4qfQzSWPOEiyBi/20ulO5AJCwsn 2d27FoyK3ceO77GxLesg1EL2/ISKXfpGXnUxXU/zpQkewDNfKh7i/ilkR1kiIg== Received: from thebighonker.lerctr.org (unknown [IPv6:2607:9c00:1009:0:7ae3:b5ff:fe1b:23b4]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "*.lerctr.org", Issuer "R10" (verified OK)) (Authenticated sender: ler/mail) by smtp.freebsd.org (Postfix) with ESMTPSA id 4YDpS60db1zyjl for ; Fri, 20 Dec 2024 00:38:30 +0000 (UTC) (envelope-from ler@FreeBSD.org) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lerctr.org; s=ler2019; h=Content-Transfer-Encoding:Content-Type:Message-ID:Subject:To: From:Date:MIME-Version:Sender:Reply-To:Cc:Content-ID:Content-Description; bh=xq5OjHgf8nsk5Nvlz4uOxINnqaHmUeVzQNtWi0pmuTo=; b=qWlW3yUj0cmqr93tG5+UL9Fr66 UjK67px3JI/g0F7PHDNpT1XMeratZmd48BuyUptf7Xy9dWWG8MzzHkS2gjI7Xz0RzQ8duzRIt/3e5 Xofk/KWrEziDIYoYJDVmHYefjp52AoLjTMiNZys3LNoCQ1PanE9Vrs8rnoQYlpf2qb008+3ryUjq1 vyso2xnxhwZmRmGVT5p96rweUx2jDGruQh/yicPYMu56RoGZfnk1Y39Dw1mD1IICmq6/vYGCoZGLY wcuiqVhp7pS3PRCkR2+EFNWBC3IOiG/MFW9urXLCQrcKY5SNC+0RieRjAkz3NhlLRxs91kJB5poZB EiGi6YAw==; Authentication-Results: thebighonker.lerctr.org; iprev=pass (thebighonker.lerctr.org) smtp.remote-ip=2607:9c00:1009::53:1; auth=pass (LOGIN) smtp.auth=ler@lerctr.org; spf=softfail smtp.mailfrom=FreeBSD.org; arc=none Received-SPF: softfail (thebighonker.lerctr.org: transitioning domain of FreeBSD.org does not designate 2607:9c00:1009::53:1 as permitted sender) client-ip=2607:9c00:1009::53:1; envelope-from=ler@FreeBSD.org; helo=webmail.lerctr.org; Received: from thebighonker.lerctr.org ([2607:9c00:1009::53:1]:11819 helo=webmail.lerctr.org) by thebighonker.lerctr.org with esmtpsa (TLS1.3) tls TLS_AES_256_GCM_SHA384 (Exim 4.98 (FreeBSD)) (envelope-from ) id 1tOR2C-00000000FOR-3DRC for freebsd-current@freebsd.org; Thu, 19 Dec 2024 18:38:28 -0600 Received: from syn-2603-8080-2000-bd01-8d6d-6011-80ef-328d.res6.spectrum.com (2603:8080:2000:bd01:8d6d:6011:80ef:328d) by webmail.lerctr.org with HTTP (HTTP/1.1 POST); Thu, 19 Dec 2024 18:38:27 -0600 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 Date: Thu, 19 Dec 2024 18:38:27 -0600 From: Larry Rosenman To: Freebsd current Subject: Do we have drivers for any of these? Message-ID: <28605a698ed9ea842bc8ec6cdf0977fe@FreeBSD.org> X-Sender: ler@FreeBSD.org Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit none0@pci0:0:0:2: class=0x080600 rev=0x00 hdr=0x00 vendor=0x1022 device=0x14b6 subvendor=0x1022 subdevice=0x14b6 vendor = 'Advanced Micro Devices, Inc. [AMD]' device = 'Family 17h-19h IOMMU' class = base peripheral -- none1@pci0:0:20:0: class=0x0c0500 rev=0x71 hdr=0x00 vendor=0x1022 device=0x790b subvendor=0x1022 subdevice=0x790b vendor = 'Advanced Micro Devices, Inc. [AMD]' device = 'FCH SMBus Controller' class = serial bus -- none2@pci0:4:0:0: class=0x028000 rev=0x00 hdr=0x00 vendor=0x14c3 device=0x0616 subvendor=0x14c3 subdevice=0xc616 vendor = 'MEDIATEK Corp.' device = 'MT7922 802.11ax PCI Express Wireless Network Adapter' class = network -- none3@pci0:118:0:2: class=0x108000 rev=0x00 hdr=0x00 vendor=0x1022 device=0x1649 subvendor=0x1022 subdevice=0x1649 vendor = 'Advanced Micro Devices, Inc. [AMD]' device = 'Family 19h PSP/CCP' class = encrypt/decrypt -- none4@pci0:118:0:5: class=0x048000 rev=0x60 hdr=0x00 vendor=0x1022 device=0x15e2 subvendor=0x1022 subdevice=0x15e2 vendor = 'Advanced Micro Devices, Inc. [AMD]' device = 'ACP/ACP3X/ACP6x Audio Coprocessor' class = multimedia -- none5@pci0:119:0:5: class=0x0c0340 rev=0x00 hdr=0x00 vendor=0x1022 device=0x162e subvendor=0x1022 subdevice=0x162e vendor = 'Advanced Micro Devices, Inc. [AMD]' device = 'Rembrandt USB4/Thunderbolt NHI controller' class = serial bus -- Larry Rosenman http://people.freebsd.org/~ler Phone: +1 214-642-9640 E-Mail: ler@FreeBSD.org US Mail: 13425 Ranch Road 620 N, Apt 718, Austin, TX 78717-1010 From nobody Fri Dec 20 14:54:46 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 4YF9SN2Zr3z5Mfpm for ; Fri, 20 Dec 2024 14:55:00 +0000 (UTC) (envelope-from mohammad@thelightbird.com) Received: from mail-lj1-x22f.google.com (mail-lj1-x22f.google.com [IPv6:2a00:1450:4864:20::22f]) (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 4YF9SN04whz4nFV for ; Fri, 20 Dec 2024 14:54:59 +0000 (UTC) (envelope-from mohammad@thelightbird.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-lj1-x22f.google.com with SMTP id 38308e7fff4ca-3002c324e7eso20159031fa.3 for ; Fri, 20 Dec 2024 06:54:59 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=thelightbird-com.20230601.gappssmtp.com; s=20230601; t=1734706498; x=1735311298; 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=pMJnP9kYquFRq9GmRH0K/aKkO/ARc2uHGHtOijRhQp0=; b=fRq9EPv6emcUXa4JEGgzXoRgPQMF4esndZ0S38Cd3Ta4YA2DATCtB7tag1/8LT/7Cj /OAst0/nhJeFItXwmcXwKKtQR5GiPSwC2kls3jQJK7eddaEnmw2zELVxiQdlbXjE18IQ MFoLwPgwSRdvjpOS1aRGJUwaDDibAb5OSf6rWvnIj084VlPMejYbcRfXP35IsvaCwVkp BKiz1Z35W5UzW9ZYA5XmyytEjaO7HVF+4J5y4f3G7vTuVVv4iso0/OMyNSSzunF5t6hP jhQ2xpITfoW5TusRU9X8X0boo1qpvflOGVP6rGpHleXD475RU0AI+Y2BIFWLOEhG7065 2Cvw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1734706498; x=1735311298; 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=pMJnP9kYquFRq9GmRH0K/aKkO/ARc2uHGHtOijRhQp0=; b=WOL9G9Tfb+RNa0fgpZzr7th3hD5nJLko+GlPUjVc/JvuUW8WO1C1+3yLpLDghJYpzJ DQfoG3/xdWR0rFGvx0co4gFO3VkC47gw7J+OCzCeYYANHDIvRlf/bo4TCHD0hiRiXqMJ etf9V8Sjj0oM4k/mu4gtRa5SoywJSjr3oMXN+yMKYUbOZ0Twyi4cXDYfeJGlMXv4Fi/f F9zVQJneuHOovV0FFjNt5DiNbU9ohfSp8aMdZl9ylT/YwkiD1mdYyXq/qQkxvPhpZllj qDhJc/jW8u2fNquyXlQNwqFJ1agk5hWRagRlZYYKsJRo9HZ3YzERq2RAvm76cV0O3Ct5 CwMQ== X-Gm-Message-State: AOJu0YykMZtna99S1oIsTIq3LBNtaR7o9lRg7VvET19CPpTsCBR103sZ dZ0aXY8Vsj9lT0BZI1o3JWYe2eQg+5IAE1w3PFiWUC4IXz0FTE5xuMnA3I0ic2UZTFzkvjA4s88 iawJWB7fIBAYGoWls2mgr5LmwHd+6foVpZ+b1 X-Gm-Gg: ASbGncu4rCqN37uCuRodfTxJLZGF0ic/BJGlag28/nciBadcvQEAqM/eMzTddkEfNBf zDs3IO8aPaOLHAbLp79LKK13T9q/0xKQXVvUPI8s3tCw4YAEy9fi025tsUKHZQeOJrts= X-Google-Smtp-Source: AGHT+IGO0+fX8Z4YtEBJH71N72GD/F8tvjuJq8/bjTZTHk8DsJ0QF4RPPNrwUVI+P1mSIAG1fCmol29WTvhlXlahoYM= X-Received: by 2002:a2e:a7ca:0:b0:300:26bc:4311 with SMTP id 38308e7fff4ca-30468569292mr8157621fa.18.1734706497419; Fri, 20 Dec 2024 06:54:57 -0800 (PST) List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@FreeBSD.org MIME-Version: 1.0 References: <28605a698ed9ea842bc8ec6cdf0977fe@FreeBSD.org> In-Reply-To: <28605a698ed9ea842bc8ec6cdf0977fe@FreeBSD.org> From: Mohammad Noureldin Date: Fri, 20 Dec 2024 15:54:46 +0100 Message-ID: Subject: Re: Do we have drivers for any of these? To: Larry Rosenman Cc: Freebsd current Content-Type: multipart/alternative; boundary="000000000000919c560629b4d4de" X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:15169, ipnet:2a00:1450::/32, country:US] X-Rspamd-Queue-Id: 4YF9SN04whz4nFV X-Spamd-Bar: ---- --000000000000919c560629b4d4de Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hi Larry, On Fri, Dec 20, 2024 at 1:38=E2=80=AFAM Larry Rosenman wr= ote: > -- > none5@pci0:119:0:5: class=3D0x0c0340 rev=3D0x00 hdr=3D0x00 vendor=3D0= x1022 > device=3D0x162e subvendor=3D0x1022 subdevice=3D0x162e > vendor =3D 'Advanced Micro Devices, Inc. [AMD]' > device =3D 'Rembrandt USB4/Thunderbolt NHI controller' > class =3D serial bus > This is being worked on: - https://wiki.freebsd.org/MohammadNoureldin/FreeBSDUSB4TBT3Support I will share this on relevant mailing lists but I need to flesh out some final details and I didn't want to annoy anyone with any noise on any mailing lists before I feel details are complete and clear enough. Worth mentioning it is also a topic addressed in LDWG (Laptop and Desktop WG): - https://docs.google.com/spreadsheets/d/15btrze2sZrprSBd3Hb3YG27cZqG0AFjcvLl= cTTifpIE/edit?usp=3Dsharing - https://github.com/orgs/FreeBSDFoundation/projects/1?pane=3Dissue&itemId=3D= 90561631&issue=3DFreeBSDFoundation%7Cproj-laptop%7C40 > -- > Larry Rosenman http://people.freebsd.org/~ler > Phone: +1 214-642-9640 E-Mail: ler@FreeBSD.org > US Mail: 13425 Ranch Road 620 N, Apt 718, Austin, TX 78717-1010 > > Have a good day --=20 Thanks - Mohammad Noureldin -- "Life is like riding a bicycle. To keep your balance you must keep moving" - Albert Einstein --000000000000919c560629b4d4de Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi Larry,

On Fri, De= c 20, 2024 at 1:38=E2=80=AFAM Larry Rosenman <ler@freebsd.org> wrote:

<snip>


--
none5@pci0:119:0:5:=C2=A0 =C2=A0 =C2=A0class=3D0x0c0340 rev=3D0x00 hdr=3D0x= 00 vendor=3D0x1022
device=3D0x162e subvendor=3D0x1022 subdevice=3D0x162e
=C2=A0 =C2=A0 =C2=A0vendor=C2=A0 =C2=A0 =C2=A0=3D 'Advanced Micro Devic= es, Inc. [AMD]'
=C2=A0 =C2=A0 =C2=A0device=C2=A0 =C2=A0 =C2=A0=3D 'Rembrandt USB4/Thund= erbolt NHI controller'
=C2=A0 =C2=A0 =C2=A0class=C2=A0 =C2=A0 =C2=A0 =3D serial bus

This is being worked on:
I will share this on relevant mailing lists but I need to flesh= out some final details and I didn't want to annoy anyone with any nois= e on any mailing lists before I feel details are complete and clear enough.=

Worth mentioning it is also a topic addressed in = LDWG (Laptop and Desktop WG):
=C2=A0
=
--
Larry Rosenman=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 =C2=A0http://people.freebsd.org/~ler
Phone: +1 214-642-9640=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0E-Mail: ler@FreeBSD.org
US Mail: 13425 Ranch Road 620 N, Apt 718, Austin, TX 78717-1010


Have a good day
<= div>
--
Thanks
- Mohammad Noureldin
--
&qu= ot;Life is like riding a bicycle. To keep your balance you must keep moving= "
- Albert Einstein

--000000000000919c560629b4d4de--