Bug Exists in the ES_EVENT_TYPE_AUTH_UNLINK Event of System Extensions

Question

qifengle OP

Created 2w

Replies 2

Boosts 0

Participants 2

System Version: 26.1

Device: M1 Mac Mini

Steps to Reproduce:

Create a UNIX socket file at /tmp/a.sock
Execute the command: ln /tmp/a.sock /tmp/b.sock
Execute the command: rm /tmp/b.sock

Bug Description:

At this point, a bug occurs in the ES_EVENT_TYPE_AUTH_UNLINK event of the system extension. The value returned for message->event.unlink.target->path is /tmp/a.sock, while it is expected to be /tmp/b.sock

Reproducibility: 100%

Boost

Answer 1

DTS Engineer OP

Apple

1w

At this point, a bug occurs in the ES_EVENT_TYPE_AUTH_UNLINK event of the system extension. The value returned for message->event.unlink.target->path is /tmp/a.sock, while it is expected to be /tmp/b.sock.

A few questions here:

Have you filed a bug on this and, if so, what's the bug number?
What is the final result of this operation within the system? Did we delete "/tmp/b.sock" leaving "/tmp/a.sock" unaltered? Or did the rm actually disrupt the original socket?

It's not clear to me how Unix semantics expect to handle this scenario, so I'm not sure what the correct behavior here actually is.

__
Kevin Elliott
DTS Engineer, CoreOS/Hardware

1

Answer 2

DTS Engineer OP

Apple

1w

FYI, I'd also recommend reviewing this thread and this thread for more guidance on general ES client issues.

__
Kevin Elliott
DTS Engineer, CoreOS/Hardware

0