aboutgitcodebugslistschat
path: root/test/lib
diff options
context:
space:
mode:
authorStefano Brivio <sbrivio@redhat.com>2022-10-31 10:29:58 +0100
committerStefano Brivio <sbrivio@redhat.com>2022-11-04 12:01:09 +0100
commit2d4468ebb72242a2d1d5345941df2db14584f14c (patch)
tree8fb4a6aee390de85be907656887a0be1ca68639f /test/lib
parente76e65a36e9b1367efa1137df71faeb265ba151a (diff)
downloadpasst-2d4468ebb72242a2d1d5345941df2db14584f14c.tar
passt-2d4468ebb72242a2d1d5345941df2db14584f14c.tar.gz
passt-2d4468ebb72242a2d1d5345941df2db14584f14c.tar.bz2
passt-2d4468ebb72242a2d1d5345941df2db14584f14c.tar.lz
passt-2d4468ebb72242a2d1d5345941df2db14584f14c.tar.xz
passt-2d4468ebb72242a2d1d5345941df2db14584f14c.tar.zst
passt-2d4468ebb72242a2d1d5345941df2db14584f14c.zip
tap: Support for detection of existing sockets on ramfs
On ramfs, connecting to a non-existent UNIX domain socket yields EACCESS, instead of ENOENT. This is visible if we use passt directly on rootfs (a ramfs instance) from an initramfs image. It's probably wrong for ramfs to return EACCES, but given the simplicity of the filesystem, I doubt we should try to fix it there at the possible cost of added complexity. Also, this whole beauty should go away once qrap-less usage is established, so just accept EACCES as indication that a conflicting socket does not, in fact, exist. Signed-off-by: Stefano Brivio <sbrivio@redhat.com> Reviewed-by: David Gibson <david@gibson.dropbear.id.au>
Diffstat (limited to 'test/lib')
0 files changed, 0 insertions, 0 deletions