From nobody Tue Apr 25 01:08:18 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 4Q53lk6h8fz468Dc for ; Tue, 25 Apr 2023 01:08:18 +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 4Q53lk4K61z4JcD for ; Tue, 25 Apr 2023 01:08:18 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1682384898; 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=LETLb2IosExb588w4oQXdLBTG9T/Z3ha87rgYLcXMBE=; b=XFPH5LYVKXqyMMn7g3S6hodRQo28ADcjYGSQ0WxJ/3ePS4/JdLY5IYQUBQm2mhdllPF26R uhTL0fsx5IWo0OCb8L6/0oncB5gSkxKdAl5C+o0Hx0C7BPVCqrddrFbgpewiTXy10BPnis issKzgVQOLO5nwHrxM1Gzh3ZWLdSVp1n5NoGZ/ZrLDenkpMs9sXpPddLsjk02SGhdEp5TX szD6a9TLbv68ueTqVeWpnda0JbttA52e3N9ohsp2YHSF3xtoimD+w0/nGE4vK+ACfMe9gm z2ckMw4hBiO3DzoFNtXmDYe5wbgRii/droxQ7hRlIqKg5LFctvATY3UolX/rWA== ARC-Authentication-Results: i=1; mx1.freebsd.org; none ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1682384898; a=rsa-sha256; cv=none; b=nZwJnkTwVCeVuL2Yl73febnRrIzQApU8DMi7Nu1pi7jzTROcaEbh6JEb6uI84w0xWzW5Fe Mgn6Vyl7zvKpBaB+aTCTzJ/rRAEAkdgMir0B/wJddbrJge1hMNl0eKPVGeiSzSzKW8NAIN CAlUTT0MVNJeDwGq6Qpmkw2x4Kk3Lxr+lFAtZHCQAWaOv4BtFCrXeBkl4ZbVzc6dP35yfD I1WWLzXbdw5iWAjyz+Xx8ykbAdG4OmD0gf9XUF4koEVrVPHIlUqpbXE4WYx/9uuVeVSAMS MIDwxBV1D97hXlDDt2Lnhp7un0cRK+pYz7eP8po8lvWJVzuuVZl1tVArjLzT1Q== 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 4Q53lk3PgnznZ4 for ; Tue, 25 Apr 2023 01:08:18 +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 33P18Ivd063781 for ; Tue, 25 Apr 2023 01:08:18 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id 33P18IQr063780 for bugs@FreeBSD.org; Tue, 25 Apr 2023 01:08:18 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 270810] munmap does not always sync the underlying file Date: Tue, 25 Apr 2023 01:08:18 +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: 13.1-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Many People X-Bugzilla-Who: geoffrey@dommett.com X-Bugzilla-Status: Closed X-Bugzilla-Resolution: Works As Intended 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 X-ThisMailContainsUnwantedMimeParts: N https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D270810 --- Comment #10 from geoffrey@dommett.com --- what you describe is not what happens running nfsv3 running nfsv3 the syncer seems to do this as long as the process does not e= xit before it has finished, if it does the syncer stops, and all writes not yet synced are permanently lost you can't call fsync on a mapped file, mmap uses its own file handle. For completeness, I have verified that calling fsync on the file handle makes no difference. The writes are still lost. surely msync with the flag MS_SYNC set should perform synchronous writes as= per the man page. It seems to for local file systems and nfsv2 mounts at least. nfsv3 it does not. I know linux had issues like this about 15 years ago --=20 You are receiving this mail because: You are the assignee for the bug.=