On Sun, Apr 3, 2016 at 4:42 PM, Jeffrey Walton <noloader@xxxxxxxxx> wrote: > I'm testing userspace crypto code using AF_ALG domain socket. The call > to 'socket(AF_ALG, SOCK_SEQPACKET, 0)' always fails with errno=2. The > failure has been experienced on 3.8, 4.1, 4.2 and 4.4 kernels > (provided by Debian, Fedora, Lubuntu and Ubuntu). I also experienced > it on a Gentoo kernel, but I don't recall the kernel version. I've > checked the kernel configs, and they all include > "CONFIG_CRYPTO_USER_API={y|m}". > > When similar code is called from userland using the async crypto gear, > then the call to socket usually succeeds. During async testing, I also > see a dmesg about registering a socket family 38. The dmesg is not > present during the non-async failures. > > I also checked the kernel crypto documentation at > http://www.kernel.org/doc/Documentation/crypto/ and > http://www.kernel.org/doc/htmldocs/crypto-API/User.html, but I don't > see a requirement I might be missing. I also checked a couple of slide > decks introducing the userspace crypto API, and I don't see what the > presenters are doing differently. Finally, I checked the LVN example > provided at http://lwn.net/Articles/410848/. > > If it matters, I usually disable IPv6 via a boot parameter since I > don't use it in my environments. But I'm guessing it has nothing to do > with the problem since the async gear works fine. > > What are the requirements to create/open an AF_ALG socket? > > Or maybe, what is missing so the call to socket succeeds? Cancel...My apologies... The call to bind() was failing after the socket was created. Mis-identifying socket() was due to a copy/paste of the error logic. The bind failure was due to .salg_type = "hmac" with .salg_name = "sha512". Jeff -- To unsubscribe from this list: send the line "unsubscribe linux-crypto" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html