You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Pinning a map / program currently takes an uninterpreted string as the key for the ebpf pinning table. On Linux, pinning works on paths. So applications may rely on behaviour such as:
. and .. special cases
normalizing slashes when joining paths
case sensitivity
Applications ported from Linux might therefore expect that foo/../map and foo/map or foo\map refer to the same object. They also might assume that foo/Map is distinct from foo/map.
If the goal is to expose objects via something similar to a file-system it would be great to start canonicalizing names now when the breakage potential is still low.
Proposed solution
Start interpreting pinning keys as paths, and canonicalize them according to Windows conventions.
Additional context
No response
The text was updated successfully, but these errors were encountered:
Describe the feature you'd like supported
Pinning a map / program currently takes an uninterpreted string as the key for the ebpf pinning table. On Linux, pinning works on paths. So applications may rely on behaviour such as:
.
and..
special casesApplications ported from Linux might therefore expect that
foo/../map
andfoo/map
orfoo\map
refer to the same object. They also might assume thatfoo/Map
is distinct fromfoo/map
.If the goal is to expose objects via something similar to a file-system it would be great to start canonicalizing names now when the breakage potential is still low.
Proposed solution
Start interpreting pinning keys as paths, and canonicalize them according to Windows conventions.
Additional context
No response
The text was updated successfully, but these errors were encountered: