crun and runc give different results when using -v .:/a/b/../c:Z

[eriksjolund]

I know it does not make sense to specify a destination path that contains /../ but this result might be interesting nonetheless.
crun 1.12 and runc 1.1.9 give different results when using -v .:/a/b/../c:Z

$ bash ~/test.bash crun
/a
/a/b
/a/c
$ bash ~/test.bash runc
/a
/a/c

The file ~/test.bash contains

#!/bin/bash

set -o nounset

runtime=$1
tmpdir=$(mktemp -d)
cd $tmpdir
podman --runtime $runtime run --rm -v .:/a/b/../c:Z docker.io/library/alpine find /a

About the system: Fedora CoreOS 40.20231209.91.0

$ rpm -q runc
runc-1.1.9-1.fc40.aarch64
$ rpm -q crun
crun-1.12-1.fc40.aarch64
$ rpm-ostree status 
State: idle
warning: Failed to query journal: couldn't find current boot in journal
Deployments:
● ostree-remote-image:fedora:docker://quay.io/fedora/fedora-coreos:rawhide
                   Digest: sha256:67a4ad873c2876ad1c190867ba91310d7c5fc26a2c0e93c17e3103c1584f2a86
                  Version: 40.20231209.91.0 (2023-12-09T14:06:31Z)