From nobody Wed Sep 20 15:52:26 2023 X-Original-To: bugs@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 4RrNMZ4HK7z4tqWl for ; Wed, 20 Sep 2023 15:52:26 +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 4RrNMZ1jDSz4N3N for ; Wed, 20 Sep 2023 15:52:26 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1695225146; a=rsa-sha256; cv=none; b=nlA26OL4Ic6oZsPEdTFE4KqgtjXWhO1ZrVGVvS5nBKjanD7tKxW+TFK4xbNU9x7Tg0gphz IV5rY5oltE3Pmh6GdE9VJpQwhdpgKr0XRcwLgcdHasI2LBXiLCGmBFsjxJAD4lw/M4XDFn PEMJe4n/aCdL59ZHAtiOffgay93uAYdZmhFjImrdcWwfeAZyqdHnmjiaLcGv4Z1IrKBUe3 WIpiU8EMbgfbAHCy3so41bslgaK+oZ3542aLieVZG7WXElbhNj532tS4piMjDI3iN2wMnF 8Dc8RGN5ZvsHu7DqqnMkZXtM0R3mISM6Xid1Nu3oI5FR2qcIpZOTB8NSsF+0JA== 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=1695225146; 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=3fbfKX2mXXxuEd19eLB3c95XwlcSbznaM5jmcgy5T7c=; b=eel8lYz52QMgmAkVUBaJP823W03cjJddDbqdScV3ZUR5KO70U0yUk+25onzy/uZesqMs5l g0jCtC/A6SBWRylqWS54/PL+W/gPn8WrrFlY9ePxEqTxcMxgP1bCbs5Y2kuZhknlUsMW+/ /7xdr/lPvIUJjfa/8nYXSnrNvGzNL56RIfcNNS0QZnmj4UBHD/uLJys+YAXE/ggsWfF2f2 BrkR6ko5aYeXtRKFni0DUYBaelJ67rsqgs5HARASZ0Qu8uROG0Ns+1csaPGJkt2qeokSzv 8AOnsgLX59PFgtSkf+sqTcEH8XVi6Lq2B434E3Xcro0nVXNOYxRglrWwK8xf5w== 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 4RrNMZ0pXQz121X for ; Wed, 20 Sep 2023 15:52:26 +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 38KFqQ2U022207 for ; Wed, 20 Sep 2023 15:52:26 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id 38KFqQQJ022206 for bugs@FreeBSD.org; Wed, 20 Sep 2023 15:52:26 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: bugs@FreeBSD.org Subject: [Bug 273962] copy_file_range does not work on shared memory objects Date: Wed, 20 Sep 2023 15:52:26 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: CURRENT X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: theraven@FreeBSD.org X-Bugzilla-Status: New 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: Bug reports List-Archive: https://lists.freebsd.org/archives/freebsd-bugs List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-bugs@freebsd.org MIME-Version: 1.0 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D273962 --- Comment #2 from David Chisnall --- (In reply to Rick Macklem from comment #1) > The title uses "file" which I think of as "regular file", On *NIX, everything is a file. I found it very surprising that it didn't w= ork with shared memory objects. On Linux (where this call originated), shared memory objects are files in a special memory filesystem and so the line is especially blurry. I don't believe the Linux implementation has such a limitation: it falls back to the equivalent of a read and write loop in the kernel if the fast paths are not supported). As a user, it's very surprising that a pair of file descriptors that work w= ith lseek, read, and write, do not work with `copy_file_range`. It's made wors= e by the fact that `EINVAL` covers a variety of errors and so writing fallback c= ode for when the file descriptor provided to an API does not work with this function cannot unambiguously detect that the reason for the failure was a = file descriptor for which this is not supported. --=20 You are receiving this mail because: You are the assignee for the bug.=