Pu Wang
Pu Wang
Currently, SpinalEnum does not support print in simulation, that: ``` println(${some SpinalEnum val} ``` will print it as `null`.
Advanced file operations includes setxattr, getxattr, listxattr, removexattr, getlk, setlk, flock, fallocation, readdirplus, copy_file_range, lseek, etc.
File system (FS) usually requires a journaling subsystem. The FS journaling part is not like database binlog, journaling is not required to recover data, but binlog does. The journaling design...
When using Rust async framework, the sequential style logging is no longer feasible. It might leverage [tracing framework from Tokio](https://github.com/tokio-rs/tracing) for async logging.
a sample BPF program to dump read and write buffer from kernel tracepoint. BPF might be used later for journaling.
**Is your feature request related to a problem? Please describe.** Handle `FUSE` `INTERRUPT` request, according to [`FUSE` kenerl document](https://www.kernel.org/doc/html/latest/filesystems/fuse.html#interrupting-filesystem-operations). **Describe the solution you'd like** Send a reply to the original...
There are some difference of system API's between x86_64 and ARM64, such as syscall argument type, filesystem metadata field type, etc. So it needs to setup GitHub action to run...
Rust supports several [sanitizers](https://doc.rust-lang.org/unstable-book/compiler-flags/sanitizer.html): * AddressSanitizer a fast memory error detector. * LeakSanitizer a run-time memory leak detector. * MemorySanitizer a detector of uninitialized reads. * ThreadSanitizer a fast data...