Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.
On Wed, Nov 27, 2013 at 03:34:04PM +0100, Joe wrote: > Hi, > > as the OpenVZ-team seems too busy to include this patch, I wonder if I > can get an answer here as to wheather it is safe or not to compile DRBD > against recent stack-OpenVZ-kernels using the workaround mentioned here: > > http://forum.proxmox.com/threads/11915-solved-Cant-compile-DRBD-8-4-2-since-latest-PVE-2-2-update-(kernel-2-6-32-82) > > https://bugzilla.openvz.org/show_bug.cgi?id=2689 Without actually looking at the kernel source changes, I cannot reliably tell whether or not "just making it compile" is "safe". The DRBD compat definition of idr_get_next started out as literal copy of the in kernel one -- but as you can see, the in kernel stuff has changed here. What they really should do is EXPORT_SYMBOL(idr_get_next); in *their* idr.c That way, the DRBD module can just use the in-kernel implementation instead of doing its own "compat" implementation, which may or may not still sufficiently match the current in-kernel implementation. Lars -- : Lars Ellenberg : LINBIT | Your Way to High Availability : DRBD/HA support and consulting http://www.linbit.com