TEEOS: Fix octal notation for O_* constants

[nathaniel-bennett]

Resolves #3532

[rustbot]

r? @tgross35

rustbot has assigned @tgross35.
They will have a look at your PR within the next two weeks and either review your PR or reassign to another reviewer.

Use r? to explicitly pick a reviewer

[tgross35]

Thanks, this looks fine to me but do you have a link to the teeos headers to check against?

[nathaniel-bennett]

teeos directly pulls in musl libc headers as its source of constants, based on what the platform support page says (https://doc.rust-lang.org/nightly/rustc/platform-support/aarch64-unknown-teeos.html) and what its builld script does (https://gitee.com/openharmony-sig/tee_tee_os_kernel/blob/master/build/build_tee.sh#L60). It uses the O_* constants from musl on the kernel side of things (https://gitee.com/openharmony-sig/tee_tee_os_kernel/blob/master/user/system-services/system-servers/fs_base/fs_wrapper_ops.c#L151). Based on the musl implementation, these indeed use the C octal variant of constant values:

/~https://github.com/bminor/musl/blob/dd1e63c3638d5f9afb857fccf6ce1415ca5f1b8b/arch/arm/bits/fcntl.h

#define O_CREAT        0100
#define O_EXCL         0200
#define O_NOCTTY       0400
#define O_TRUNC       01000
#define O_APPEND      02000
#define O_NONBLOCK    04000
#define O_DSYNC      010000
#define O_SYNC     04010000
#define O_RSYNC    04010000
#define O_DIRECTORY  040000
#define O_NOFOLLOW  0100000
#define O_CLOEXEC  02000000

[tgross35]

Thanks! Just trying to get the sources linked in all the PRs since tracing some of these APIs back can be painful.