Re: RFC: changed error code when binding unix socket twice
From: Petr Vorel
Date: Mon Oct 29 2018 - 12:33:39 EST
> On Fri, Aug 31, 2018 at 1:17 PM Petr Vorel <pvorel@xxxxxxx> wrote:
> > > commit 0fb44559ffd6 ("af_unix: move unix_mknod() out of bindlock") moves
> > > the special file creation in unix_bind() before u->bindlock is taken in
> > > order to avoid an ABBA deadlock with do_splice(). As a side effect, it
> > > also moves the check for existence of the special file (which would
> > > result in -EADDRINUSE) before the check of u->addr (which would result
> > > in -EINVAL if socket is already bound). This means that the error
> > > returned for an attempt to bind a unix socket to the same path twice
> > > changed from -EINVAL to -EADDRINUSE with this commit.
> > > One way to restore the old error code is indicated below but before
> > > submitting it, I would like to ask if we need/want it.
> > > Pro:
> > > - in general, we do not want to change return code for given testcase
> > > - old error (-EINVAL) is consistent with AF_INET(6)
> > > Con:
> > > - both POSIX and Linux man page only list error conditions without
> > > stating which should take precedence if more of them apply so
> > > neither of them seems wrong, strictly speaking
> > I'd be for restoring the original behavior (be conservative + looks like as not intended).
> > Any comment from netdev maintainers?
> Naresh noticed that LTP now has a version check to detect linux-4.10+ and
> expect a different return code from previous versions, but the 0fb44559ffd6
> commit that changed the behavior got backported to stable linux-4.4 and 4.9,
> so now LTP complains about those:
Thanks for report.
> I don't care much which error code gets returned here, but I think we
> should either handle this consistently in all kernel versions and check for
> the one that is deemed the correct one on all versions, or change LTP
> again to accept either return code.
Do you mean to apply this patch to 3.16.y? (The only still maintained LTS branch
which miss this fix). Although the patch don't apply and it's very old branch,
it'd be easy to adjust it and it looks to me deadlock can happen there as well.
I guess we need to adjust LTP test to accept either return code as EOL longterm
branches probably will not take this patch.