From nobody Wed Sep 20 21:24:04 2023 X-Original-To: doc@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 4RrWkD6Q3Yz4vBmC for ; Wed, 20 Sep 2023 21:24:04 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4RrWkD4sfcz4QqW for ; Wed, 20 Sep 2023 21:24:04 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1695245044; a=rsa-sha256; cv=none; b=ed/MzKXZHhFGygWiailQ4UndwoA+0m/f4CF8qn5JGdNX6vg1OxCyuLUTB3ypNjZeSmwwqE QBshY3aNRgoYgH9DdxcY/1a74CvXojvve+VBZ+Q11Y9CO2OaqTXzQw0ay+dUSTlHTLm/Za 5ve1f7bmYY2hsxe+1twCrilZfMPlHFSLmxImNmnIuyGd7wOqmmfGZ8l5D9uEfI8EDfXdR+ ymoKiZcVzdH0Kcl9kZ0NR97StD3iGW9Abtd0CBiQwOEoG5QqB/D72Ct+bRUY5C4iL8r05j mwXBHMMfdC770gENEn89xmB9GV/80bYAY2YyTKmrtAre0CKVJIk/jpFWOyAtiQ== 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=1695245044; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=ddlFdgdmWL8Bem6JmImlNd0Nlr437No1yurcDgKl+l4=; b=Nv1Idx2hwHhneYgD9GrTLnooLoh0ODtemyNrT37097SNhk1tLwidgkMjUWwMPUdeJx4PUu okiyYZNNQb2dr3XNrU+G19+/YpxkcaRwmn227OT73S/jwa/pjthm5JMx7+dZGwAd2Gypzd hm66rlLgaGGG+LmAow3kJnh8n1kmN4SKpwKqZ1Xf2bCAo2Vzxgd8nSJv0ZK8g2kbZbcyqN ORH+1az38Cdryyi/Tq315TrL/7R8YSq0fwxkwMXm5LIV3Cv/b7gQRzTgj2b6mm5LRHSAie 6tfLcM8ZEDA3iwVNX8KEJC2ULXN794zhmXCRu5p2dGXWq/MjJazXF71xzr31tQ== Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2610:1c1:1:606c::50:1d]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id 4RrWkD3yt2z1BM1 for ; Wed, 20 Sep 2023 21:24:04 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.5]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id 38KLO4hk030623 for ; Wed, 20 Sep 2023 21:24:04 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id 38KLO4n7030622 for doc@FreeBSD.org; Wed, 20 Sep 2023 21:24:04 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: doc@FreeBSD.org Subject: [Bug 273962] copy_file_range does not work on shared memory objects Date: Wed, 20 Sep 2023 21:24:04 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Documentation X-Bugzilla-Component: Manual Pages X-Bugzilla-Version: Latest X-Bugzilla-Keywords: needs-patch X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: rmacklem@FreeBSD.org X-Bugzilla-Status: Open X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: bugs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated List-Id: Documentation project List-Archive: https://lists.freebsd.org/archives/freebsd-doc List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-doc@freebsd.org MIME-Version: 1.0 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D273962 --- Comment #6 from Rick Macklem --- It looks like there would need to be a layering violation, since the code that goes in kern_copy_file_range() will need to be specific to shm_ops, since the range lock code needs to use shm_mtx. (Or a new f_op specifically for copy_file_range() would need to be added.) So, the fallback is not trivial, although it is not a lot of work. --=20 You are receiving this mail because: You are on the CC list for the bug.=