From 1465273b86408ee154d7ef77e77085bee078ed1a Mon Sep 17 00:00:00 2001 From: sunrisepeak Date: Mon, 21 Sep 2026 11:57:59 +0800 Subject: [PATCH] 0.19.1: openkal-windows 0.10.1 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit 0.10.1 makes a file opened for writing describable. `kal_fs_file_info` answers through NtQueryInformationFile(FileBasicInformation), which requires FILE_READ_ATTRIBUTES, and `FILE_GENERIC_WRITE` does not carry it — so a write-only handle held every right except the one needed to ask it about itself. That reaches this package directly: `do_fstat` calls `okm_fs_file_info` and maps its error, so `fstat` on a descriptor the caller opened a line earlier returned EACCES on Windows. libarchive performs exactly that pair when opening an archive for output, and a consumer's Windows test suite was red on it. Measured on three real-Windows conformance jobs in openkal-windows: with the fix the query answers 0, without it 6. --- mcpp.toml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/mcpp.toml b/mcpp.toml index cf28078..0b9ea61 100644 --- a/mcpp.toml +++ b/mcpp.toml @@ -1,7 +1,7 @@ [package] namespace = "mcpplibs" name = "openkal-musl" -version = "0.19.0" +version = "0.19.1" description = "musl 1.2.5 redirected onto openkal: one C library, ported once, above every implementation of the specification rather than above one kernel." license = "Apache-2.0" @@ -207,7 +207,7 @@ openkal-opensbi = { version = "0.8.0", features = ["standalone"] } defines = ["OKM_HAS_FS=0", "OKM_HAS_PROCESS=0", "OKM_HAS_TASK=0"] [target.'cfg(windows)'.dependencies] -openkal-windows = { version = "0.10.0", features = ["standalone"] } +openkal-windows = { version = "0.10.1", features = ["standalone"] } # The feature macros musl's own build establishes. #