verbs: Encode the private ABI version number in verbs_register_driver
PATCH 1/1 verbs: Encode the private ABI version number in verbs_register_driver
This causes the symbol table to look like:
208: 000000000000c000 142 FUNC GLOBAL DEFAULT 13 verbs_register_driver_15@@IBVERBS_PRIVATE_15
Which encodes the expected private ABI version inside the symbol name as well as with the symbol version.
This ensures that the ABI version is checked even if the linking environment does not include symbol versions, for instance if an end user is linking a provider static library to the system dynamic libibverbs.
--- buildlib/config.h.in | 1 + libibverbs/driver.h | 11 +++++++++++ libibverbs/libibverbs.map.in | 2 +- 3 files changed, 13 insertions(+), 1 deletion(-)
Since Leon says people are using static provider libraries we should do more to make sure they work right.
buildlib/config.h.in +1 -0
@@ -25,6 +25,7 @@ #define VERBS_PROVIDER_DIR "@VERBS_PROVIDER_DIR@" #define VERBS_PROVIDER_SUFFIX "@IBVERBS_PROVIDER_SUFFIX@" +#define IBVERBS_PABI_VERSION @IBVERBS_PABI_VERSION@ // FIXME This has been supported in compilers forever, we should just fail to build on such old systems. #cmakedefine HAVE_FUNC_ATTRIBUTE_ALWAYS_INLINE 1
libibverbs/driver.h +11 -0
@@ -39,6 +39,7 @@#include <infiniband/verbs.h> #include <infiniband/kern-abi.h> #include <ccan/list.h> +#include <config.h> #ifdef __cplusplus# define BEGIN_C_DECLS extern "C" {
@@ -128,6 +129,16 @@ verbs_get_device(const struct ibv_device *dev)typedef struct verbs_device *(*verbs_driver_init_func )(const char *uverbs_sys_path,int abi_version); + +/* Wire the IBVERBS_PRIVATE version number into the verbs_register_driver +* symbol name. This guarentees we link to the correct set of symbols even if +* statically linking or using a dynmic linker with symbol versioning turned +* off. +*/ +#define ___make_verbs_register_driver (x) verbs_register_driver_ ## x +#define __make_verbs_register_driver (x) ___make_verbs_register_driver(x) +#define verbs_register_driver __make_verbs_register_driver(IBVERBS_PABI_VERSION) +void verbs_register_driver (const char *name,verbs_driver_init_func init_func); void verbs_init_cq(struct ibv_cq *cq, struct ibv_context *context, struct ibv_comp_channel *channel,
libibverbs/libibverbs.map.in +1 -1
@@ -137,6 +137,6 @@ IBVERBS_PRIVATE_@IBVERBS_PABI_VERSION@ { ibv_cmd_resize_cq; ibv_query_gid_type; ibv_register_driver; - verbs_register_driver; + verbs_register_driver_@IBVERBS_PABI_VERSION@; verbs_init_cq; };
Signature · 10 lines
2.7.4 -- Jason Gunthorpe <jgunthorpe-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org> (780)4406067x832 Chief Technology Officer, Obsidian Research Corp Edmonton, Canada -- To unsubscribe from this list: send the line "unsubscribe linux-rdma" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
A message that is not in the archive (sent off-list or not yet received): 20170824215601.GA19717-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org
Leon Romanovsky
Reviewed-byQuoted 12 lines · Jason Gunthorpe
This causes the symbol table to look like:
208: 000000000000c000 142 FUNC GLOBAL DEFAULT 13 verbs_register_driver_15@@IBVERBS_PRIVATE_15Which encodes the expected private ABI version inside the symbol name as well as with the symbol version.
This ensures that the ABI version is checked even if the linking environment does not include symbol versions, for instance if an end user is linking a provider static library to the system dynamic libibverbs.
Quoted 7 lines
--- buildlib/config.h.in | 1 + libibverbs/driver.h | 11 +++++++++++ libibverbs/libibverbs.map.in | 2 +- 3 files changed, 13 insertions(+), 1 deletion(-)
Thanks,
Quoted 13 lines · Jason Gunthorpe
This causes the symbol table to look like:
208: 000000000000c000 142 FUNC GLOBAL DEFAULT 13 verbs_register_driver_15@@IBVERBS_PRIVATE_15Which encodes the expected private ABI version inside the symbol name as well as with the symbol version.
This ensures that the ABI version is checked even if the linking environment does not include symbol versions, for instance if an end user is linking a provider static library to the system dynamic libibverbs.
Quoted 8 lines
--- buildlib/config.h.in | 1 + libibverbs/driver.h | 11 +++++++++++ libibverbs/libibverbs.map.in | 2 +- 3 files changed, 13 insertions(+), 1 deletion(-)Since Leon says people are using static provider libraries we should do more to make sure they work right.
Jason,
Can you dumb this down for me? I don't understand the provider static library part. Do you mean an application statically linking in a provider library and dynamically to libibverbs? Why would someone do this? Are there examples of this?
Thanks,
Chien
--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
A message that is not in the archive (sent off-list or not yet received): 20170901203021.GA5832-TZeIlv3TuzOfrEmaQUPKxl95YUYmaKo1UNDiOz3kqAs@public.gmane.org
Quoted 19 lines · Chien Tin Tung
Quoted 18 lines · Jason Gunthorpe
This causes the symbol table to look like:
208: 000000000000c000 142 FUNC GLOBAL DEFAULT 13 verbs_register_driver_15@@IBVERBS_PRIVATE_15Which encodes the expected private ABI version inside the symbol name as well as with the symbol version.
This ensures that the ABI version is checked even if the linking environment does not include symbol versions, for instance if an end user is linking a provider static library to the system dynamic libibverbs.
buildlib/config.h.in | 1 + libibverbs/driver.h | 11 +++++++++++ libibverbs/libibverbs.map.in | 2 +- 3 files changed, 13 insertions(+), 1 deletion(-)
Quoted 8 lines
Quoted 2 lines
Since Leon says people are using static provider libraries we should do more to make sure they work right.
Jason,
Can you dumb this down for me? I don't understand the provider static library part. Do you mean an application statically linking in a provider library and dynamically to libibverbs?
Yes.
Quoted 1 line
Why would someone do this?
Not sure. Leon said there was interest and the patch is simple.
Perhaps it makes sense when combined with libmlx5dv. Eg you could build a middleware library that embeds the 'dv' library. Maybe turn on LTO to gain some speed.
Quoted 1 line
Are there examples of this?
Compile rdma-core with -DENABLE_STATIC
Quoted 1 line
From memory, untested:
$ gcc -o foo foo.o -Wl,--whole-archive -lmlx5dv
Jason
--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html