-
Notifications
You must be signed in to change notification settings - Fork 5.2k
[Bug] DFSv1 mount rw flags #9270
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
GuEe-GUI
added a commit
to GuEe-GUI/rt-thread
that referenced
this issue
Oct 30, 2024
1. Not support link. 2. Fixup the DFS open flag with readonly. Link: RT-Thread#9270 Signed-off-by: GuEe-GUI <[email protected]>
GuEe-GUI
added a commit
to GuEe-GUI/rt-thread
that referenced
this issue
Oct 30, 2024
1. Not support link. 2. Fixup the DFS open flag with readonly. Link: RT-Thread#9270 Signed-off-by: GuEe-GUI <[email protected]>
GuEe-GUI
added a commit
to GuEe-GUI/rt-thread
that referenced
this issue
Oct 30, 2024
1. Not support link. 2. Fixup the DFS open flag with readonly. Link: RT-Thread#9270 Signed-off-by: GuEe-GUI <[email protected]>
GuEe-GUI
added a commit
to GuEe-GUI/rt-thread
that referenced
this issue
Nov 8, 2024
1. Not support link. 2. Fixup the DFS open flag with readonly. Link: RT-Thread#9270 Signed-off-by: GuEe-GUI <[email protected]>
GuEe-GUI
added a commit
to GuEe-GUI/rt-thread
that referenced
this issue
Nov 20, 2024
1. Not support link. 2. Fixup the DFS open flag with readonly. Link: RT-Thread#9270 Signed-off-by: GuEe-GUI <[email protected]>
GuEe-GUI
added a commit
to GuEe-GUI/rt-thread
that referenced
this issue
Nov 20, 2024
1. Not support link. 2. Fixup the DFS open flag with readonly. Link: RT-Thread#9270 Signed-off-by: GuEe-GUI <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
RT-Thread Version
all
Hardware Type/Architectures
all
Develop Toolchain
Other
Describe the bug
此处打开设备代码需要考虑设备只读情况,驱动开发者有权利在 open 阶段拒绝访问:
rt-thread/components/dfs/dfs_v1/src/dfs_fs.c
Lines 323 to 337 in f4cb323
Other additional context
No response
The text was updated successfully, but these errors were encountered: