From nobody Thu Sep 5 21:06:12 2024 X-Original-To: freebsd-hackers@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 4X0BmV6Zs8z5TxHb for ; Thu, 05 Sep 2024 21:08:42 +0000 (UTC) (envelope-from dsl@FreeBSD.org) Received: from smtp.freebsd.org (smtp.freebsd.org [96.47.72.83]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "smtp.freebsd.org", Issuer "R10" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4X0BmV65p0z4vQT; Thu, 5 Sep 2024 21:08:42 +0000 (UTC) (envelope-from dsl@FreeBSD.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1725570522; 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=r9dn/8/RGwEdVZ1rszk3TVaSZNQyHg8Hqhnulq6NhQg=; b=iIMTmkVJffFPQJ7QJEFtHzmyohyD4m4BdEg0t8u77xXg/wJa5k1cTVYdkTclG5HnivIDQ/ SDgGZmAb6Qn4T9ZGUwSrlhMA6IObRR1gj7+lBrZDMS+xuN/WIU6o92UR4mZqp2Le069vvR kP3WzQm+t+sAF+9pqZEU/rfULdOu1LCVpHsC2sOFmhYWifkDH0421JV+ejG9tqIuoYafA3 kZh10KMaypIe6b03uQEbA7yr5D5+zIKcKwcypQDXl5UquvH4YU4X7YtF3ode1rFXvL3vKY 79ZI06A9BSMHG4Yoy9k6NGUIhI218MyoXpuC/Ao++A5oYFh0IJ0tyYMrH1LJcw== ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1725570522; a=rsa-sha256; cv=none; b=Eecgky92xZVRNBq2CpAHJbV1c9cmpWh4p8sZvCib62dz06AMOYRe6fYzLbsjlMFB6MeDcf USOy2fhLS2rDVUalo74H9StdnZc2GT/qymD/8HM3et3ODy/jzQvW9TYOPnw7eOSlfr20pF ZZKqskWtIP/s5UPhcH01ZQN5ozgWg/lVYzbk21Yhiq4NXZF887/X/N7kzWBDb7pLf8JXhX yQEt0j/XkOmiqdCSVLaMd99w1O26fun66Pfki1KAgDAcGxR5A3+ULaTaoqmVL69TmkOCVZ ZngaAmuQL0ZzoEvxTxREb6bdNjQYBExyPT6upFzaMZj62FN8nJmXZUh/Cma7Fg== ARC-Authentication-Results: i=1; mx1.freebsd.org; none ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1725570522; 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=r9dn/8/RGwEdVZ1rszk3TVaSZNQyHg8Hqhnulq6NhQg=; b=jbP5eEiqS5awACK4BNW1+Vz6e7NZoaP5W93fRme8sm+PfRJgeWbe9kXYtEFvV2SavxRWL5 RznmBj/8k7RIrwKeHqErGPMoj6n5g/YlrCklP7wC4nFgdPNWTLtWDrDLVlxBZP10Msa33h BD2D3XcBoJGVaIAvvfvLoDAFMNFeRZnUDbe7DNtcQ+UlxIn+e4yVpeJuwGmO+b+12kPGSl GgaBioHcNsrc3XUk/n/rX4yT7WWr7gHhAiPWckfA2IeQ3qPnS3VavTdlJKoHhd9QJIB7hY uoAN3SDzWVHNKAtTOt/HEu+Pz4J5EOsV9ETHhj8UPo8tU6Rb6fbIVyhtehU7jQ== Received: from localhost (unknown [91.226.51.235]) (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) (Authenticated sender: dsl) by smtp.freebsd.org (Postfix) with ESMTPSA id 4X0BmV3f3nz1J5Y; Thu, 5 Sep 2024 21:08:42 +0000 (UTC) (envelope-from dsl@FreeBSD.org) References: <7d1a0ae5-b047-4b2b-894e-615af0a5093e@digitaldaemon.com> User-agent: mu4e 1.8.13; emacs 29.4 From: Dmitry Salychev To: Jan Knepper Cc: Alan Somers , freebsd-hackers@freebsd.org Subject: Re: The Case for Rust (in any system) Date: Thu, 05 Sep 2024 23:06:12 +0200 In-reply-to: <7d1a0ae5-b047-4b2b-894e-615af0a5093e@digitaldaemon.com> Message-ID: <86y1453j1k.fsf@peasant.bootbsd.com> List-Id: Technical discussions relating to FreeBSD List-Archive: https://lists.freebsd.org/archives/freebsd-hackers List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-hackers@FreeBSD.org MIME-Version: 1.0 Content-Type: text/plain Jan Knepper writes: > Is this used? > > Does anyone from the team monitor this? > > https://scan.coverity.com/projects/freebsd > I check it from time to time hoping to find anything about sys/dev/dpaa2, but no issues there reported. I wonder whether Coverity configured in a specific way not to get any code from CURRENT. > > > On 9/5/24 14:09, Alan Somers wrote: >> By now I expect that most of you have seen the long list of new >> security advisories that just came out. Strikingly, all were the >> result of memory handling errors. And none of them wouldn't have >> happened if their respective programs had been written in a >> memory-safe language. >> >> In fact, of all the C bug fixes that I've been involved with (as >> either author or reviewer) since May, about three quarters could've >> been avoided just by using a better language. >> >> The real takeaway here is that C is no longer sufficient for writing >> high quality code in the 2020s. Everyone needs to adapt their tools. >> Programmers who don't will increasingly come to resemble experimental >> archaeologists, i.e. people who learn flintknapping to "keep the >> knowledge alive". Such people are valuable, but definitely niche. I >> for one don't want my career to go in that trajectory. >> >> To summarize, here's the list of this week's security advisories, and >> also some other recent C bug fixes of my own involvement: >> >> Buffer overflow >> =============== >> https://cgit.freebsd.org/src/commit/?id=3aaaca1b51ad844ef9e9b3d945217ab3dd189bae >> CVE-2024-45288 FreeBSD-SA-24:09.libnv >> https://cgit.freebsd.org/src/commit/?id=a06fc21e770a482c8915411ebc98c870e42dd29b >> CVE-2024-41928 FreeBSD-SA-24:10.bhyve >> https://cgit.freebsd.org/src/commit/?id=af438acbfde3d25dbdc82b2b3d72380f0191e9d9 >> CVE-2024-42416 FreeBSD-SA-24:11.ctl >> https://cgit.freebsd.org/src/commit/?id=db87c98168b1605f067d283fa36a710369c3849d >> FreeBSD-SA-24:11.ctl >> https://cgit.freebsd.org/src/commit/?id=5c9308a4130858598c76f3ae6e3e3dfb41ccfe68 >> CVE-2024-32668 FreeBSD-SA-24:12.bhyve >> >> Integer overflow >> ================ >> https://cgit.freebsd.org/src/commit/?id=36fa90dbde0060aacb5677d0b113ee168e839071 >> CVE-2024-45287 FreeBSD-SA-24:09.libnv >> https://cgit.freebsd.org/src/commit/?id=c3e6dfe55c0e81d0717b0458bc95128384c3ebe8 >> FreeBSD-SA-24:14.umtx >> >> Use after free >> ============== >> https://cgit.freebsd.org/src/commit/?id=670b582db6cb827a8760df942ed8af0020a0b4d0 >> CVE-2024-45063 FreeBSD-SA-24:11.ctl >> https://cgit.freebsd.org/src/commit/?id=62f40433ab47ad4a9694a22a0313d57661502ca1 >> CVE-2024-43102 FreeBSD-SA-24:14.umtx >> >> Uninitialized memory access >> =========================== >> https://cgit.freebsd.org/src/commit/?id=ea44766b78d639d3a89afd5302ec6feffaade813 >> CVE-2024-8178 FreeBSD-SA-24:11.ctl >> https://cgit.freebsd.org/src/commit/?id=0f2b2276abc305905e7d88619a7abca26b0dd7eb >> >> Memory Leaks >> ============ >> https://cgit.freebsd.org/src/commit/?id=2909ddd17cb4d750852dc04128e584f93f8c5058 >> >> Incorrect union member access >> ============================= >> https://cgit.freebsd.org/src/commit/?id=9a5a7c90d5e5971fe2b9c9265e9279a6f173a8f3 >> CVE-2024-6119 FreeBSD-SA-24:13.openssl >> >> Concurrent unsychronized memory access >> ====================================== >> https://cgit.freebsd.org/src/commit/?id=1f5bf91a85e93afa17bc9c03fe7fade0852da046 >> >> RAII >> ==== >> https://cgit.freebsd.org/src/commit/?id=4b3141f5d5373989598f9447ab5a9f87e2d1c9fb >> >> Unchecked errors [^1] >> ====================== >> https://cgit.freebsd.org/src/commit/?id=35f4984343229545881a324a00cdbb3980d675ce >> https://cgit.freebsd.org/src/commit/?id=eced2e2f1e56b54753702da52a88fccbe73b3dcb >> https://cgit.freebsd.org/src/commit/?id=f625d038d2ae59fa1ae81b76079da464ed6db61a >> >> Not preventable by a safer programming language >> =============================================== >> https://cgit.freebsd.org/src/commit/?id=7d6932d20aedbbb220cd78e90ab4e82d1abaad31 >> https://cgit.freebsd.org/src/commit/?id=6efba04df3f8c77b9b12f1df3e5124a7249b82fc >> https://cgit.freebsd.org/src/commit/?id=4b72bab96e8978eaed30fd44f7f51e1b4918d4db >> https://cgit.freebsd.org/src/commit/?id=b64afa41d56e98b5817aaf14c7deb0fa7e2142fb >> >> [^1]: while not memory-safety bugs, Rust's lints actually make >> ignoring errors like this pretty difficult. So I consider these bugs >> to have been preventable. >> -- https://wiki.freebsd.org/DmitrySalychev