Skip to content
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

Mix of case insensitivity/sensitivity causing problems when memstick folder ends with PSP #15236

Closed
hrydgard opened this issue Dec 15, 2021 · 5 comments
Labels
I/O Affected by I/O timing settings, or other kind of I/O issue. No Feedback / Outdated? Platform-specific (Linux/POSIX)
Milestone

Comments

@hrydgard
Copy link
Owner

Reported by mrfixit2001 on discord.

Not entirely clear what's going on but apparently when he named his memstick folder "psp" (on a Linux machine), the hack we use to strip off the PSP prefix to the path (added for Android scoped storage support) seems to activate while still not being able to access the files, which is weird.

Additionally, seems when he named it PSP instead it segfaults, while other names work.

So this is all a little confusing but should be looked into.

@hrydgard hrydgard added Platform-specific (Linux/POSIX) I/O Affected by I/O timing settings, or other kind of I/O issue. labels Dec 15, 2021
@hrydgard hrydgard added this to the v1.13.0 milestone Dec 15, 2021
@ghost
Copy link

ghost commented Dec 15, 2021

it's basically related to what I reported here in a way:
#15052
#15052 (comment)

@mrfixit2001
Copy link
Contributor

I saw other similar issues reported regarding all the saves being corrupt. Some games report missing files as corruption, which I observed on Burn Out in this case.

The technical detail behind this is that when FixPathCase calls FixFilenameCase it passes two paths, and when the mem stick directory included PSP then both paths that are passed include PSP. An example from my build:
"/rcade/share/saves/psp" and "/PSP/SAVEDATA/ULUS10025SAVE006"

This causes FixPathCase to return false, which then causes DirectoryFileHandle::Open to exit early also returning false and not properly create the files.

@hrydgard
Copy link
Owner Author

Likely fixed by #15237 ?

@unknownbrackets
Copy link
Collaborator

I don't think we've seen any further reports about this - absent of any confirmation, perhaps we should close? It ought to be fixed, and that no one has complained may be the most confirmation we'll see.

-[Unknown]

@unknownbrackets
Copy link
Collaborator

I'm going to close this - there have been no new reports of these issues since that was merged and there was a comment in Discord I believe that it fixed the initial problem.

-[Unknown]

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
I/O Affected by I/O timing settings, or other kind of I/O issue. No Feedback / Outdated? Platform-specific (Linux/POSIX)
Projects
None yet
Development

No branches or pull requests

3 participants