[PATCH v8 0/9] coredump: add coredump socket

[Christian Brauner]

> The path lookups work very differently between COREDUMP_SOCK and
> COREDUMP_FILE - they are interpreted relative to different namespaces,
> and they run with different privileges, and they do different format
> string interpretation. I think trying to determine dynamically whether
> the path refers to a socket or to a nonexistent location at which we
> should create a file (or a preexisting file we should clobber) would
> not be practical, partly for these reasons.

Agreed.

> 
> Also, fundamentally, if we have the choice between letting userspace
> be explicit about what it wants, or trying to guess userspace's intent
> from the kernel, I think we should always go for being explicit.

Agreed.

> 
> meaning in this context, like '>'; but I don't think we should be
> changing the overall approach because of this.

Agreed.