netdev - svc: failed to register lockdv1 RPC service (errno 97).

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-Id: <200905110248.48695.elendil@planet.nl>
Date:	Mon, 11 May 2009 02:48:47 +0200
From:	Frans Pop <elendil@...net.nl>
To:	Netdev <netdev@...r.kernel.org>
Cc:	linux-kernel@...r.kernel.org, Chuck Lever <chuck.lever@...cle.com>,
	Trond Myklebust <Trond.Myklebust@...app.com>
Subject: svc: failed to register lockdv1 RPC service (errno 97).

After switching from 2.6.29.2 to 2.6.30-rc5 I get this new message during 
boot of my home server:
   svc: failed to register lockdv1 RPC service (errno 97).

This looks to be the result of the following commit:
commit 363f724cdd3d2ae554e261be995abdeb15f7bdd9
Author: Chuck Lever <chuck.lever@...cle.com>
    SUNRPC: rpcb_register() should handle errors silently
    Move error reporting for RPC registration to rpcb_register's caller.

Question is: do I really want to know this? I assume the "failure" 
happened with previous kernels too, but silently.

If I do need to know this, it would be nice if the error was more 
informative. I had to grep the kernel source to see that 97 is
-EAFNOSUPPORT and that that means "Address family not supported by 
protocol". And even with that I don't know whether it's IPv4 or IPv6 
where the failure is.

My impression is that this is a bogus message from a user's perspective 
and that it should not be displayed.

Cheers,
FJP


View attachment "config" of type "text/plain" (69248 bytes)