-
Bug
-
Resolution: Fixed
-
P2
-
7, 8, 11, 14
-
- 11bpr-critical-approved
- 8bpr-critical-approved
- autoverify
- azul-interest
- dcs-hwna
- dcs-pso
- jdk11u-critical-request
- jdk11u-critical-yes
- jdk11u-fix-request
- jdk11u-fix-yes
- jdk8u-critical-request
- jdk8u-critical-yes
- macos10.15
- noreg-other
- redhat-interest
- reproducer-yes
- tck-red-11.0.5
- tck-red-13.0.1
- tck-red-7u241
- tck-red-8u231
- webbug
-
b15
-
x86
-
os_x_10.15
-
Not verified
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-8231204 | 13.0.2 | Ivan Gerasimov | P2 | Resolved | Fixed | b01 |
JDK-8231208 | 11.0.6-oracle | Ivan Gerasimov | P2 | Resolved | Fixed | b01 |
JDK-8231521 | 11.0.6 | Brian Burkhalter | P2 | Resolved | Fixed | b01 |
JDK-8231728 | 11.0.5.0.1-oracle | Ivan Gerasimov | P2 | Closed | Fixed | b01 |
JDK-8231407 | 11.0.5 | Brian Burkhalter | P2 | Resolved | Fixed | b09 |
JDK-8232546 | openjdk8u242 | Brian Burkhalter | P2 | Resolved | Fixed | team |
JDK-8231523 | openjdk8u232 | Brian Burkhalter | P2 | Resolved | Fixed | b08 |
JDK-8231212 | 8u241 | Ivan Gerasimov | P2 | Closed | Fixed | b01 |
JDK-8231696 | 8u231 | Ivan Gerasimov | P2 | Closed | Fixed | b31 |
JDK-8235057 | emb-8u241 | Ivan Gerasimov | P2 | Resolved | Fixed | team |
JDK-8231217 | 7u251 | Ivan Gerasimov | P2 | Closed | Fixed | b01 |
JDK-8240058 | openjdk7u | Brian Burkhalter | P2 | Resolved | Fixed | master |
macOS Catalina (beta), OpenJDK 11.0.4 (but most likely this will affect any Java version)
A DESCRIPTION OF THE PROBLEM :
Beginning with macOS Catalina certain parts of the file system are write-protected.
However, `Files.getFileStore(anyPath)` doesn't distinguish protected and non-protected parts and will always return the same file store, which will then be reported as read-only.
The root path of a file system no longer defines whether the file system as a whole is read-only.
STEPS TO FOLLOW TO REPRODUCE THE PROBLEM :
Run attached test program on macOS Catalina.
Optionally change the path variable to any other existing path residing in non-protected regions.
EXPECTED VERSUS ACTUAL BEHAVIOR :
EXPECTED -
Program prints "read-only: false"
ACTUAL -
Program prints "read-only: true"
---------- BEGIN SOURCE ----------
import java.io.IOException;
import java.nio.file.Files;
import java.nio.file.Path;
import java.nio.file.Paths;
public class Test {
public static void main(String[] args) throws IOException {
Path path = Paths.get("/tmp");
System.out.println("read-only: " + Files.getFileStore(path).isReadOnly());
}
}
---------- END SOURCE ----------
FREQUENCY : always
- backported by
-
JDK-8231204 (fs) FileStore::isReadOnly is always true on macOS Catalina
- Resolved
-
JDK-8231208 (fs) FileStore::isReadOnly is always true on macOS Catalina
- Resolved
-
JDK-8231407 (fs) FileStore::isReadOnly is always true on macOS Catalina
- Resolved
-
JDK-8231521 (fs) FileStore::isReadOnly is always true on macOS Catalina
- Resolved
-
JDK-8231523 (fs) FileStore::isReadOnly is always true on macOS Catalina
- Resolved
-
JDK-8232546 (fs) FileStore::isReadOnly is always true on macOS Catalina
- Resolved
-
JDK-8235057 (fs) FileStore::isReadOnly is always true on macOS Catalina
- Resolved
-
JDK-8240058 (fs) FileStore::isReadOnly is always true on macOS Catalina
- Resolved
-
JDK-8231212 (fs) FileStore::isReadOnly is always true on macOS Catalina
- Closed
-
JDK-8231217 (fs) FileStore::isReadOnly is always true on macOS Catalina
- Closed
-
JDK-8231696 (fs) FileStore::isReadOnly is always true on macOS Catalina
- Closed
-
JDK-8231728 (fs) FileStore::isReadOnly is always true on macOS Catalina
- Closed
- relates to
-
JDK-8231254 (fs) Add test for macOS Catalina changes to protect system software
- Resolved
-
JDK-8232178 MacVolumesTest failed after upgrade to MacOS Catalina
- Resolved
- links to