Re: [PATCH 1/2] btrfs-progs: Ignore path device during device scan
From: David Sterba <hidden>
Date: 2021-09-29 18:31:59
On Tue, Sep 28, 2021 at 03:37:29PM +0300, Nikolay Borisov wrote:
quoted hunk ↗ jump to hunk
Currently btrfs-progs will happily enumerate any device which has a btrfs filesystem on it. For the majority of use cases that's fine and there haven't been any problems with that. However, there was a recent report that in multipath scenario when running "btrfs fi show" after a path flap instead of the multipath device being show the path device is shown. So a multipath filesystem might look like: Label: none uuid: d3c1261f-18be-4015-9fef-6b35759dfdba Total devices 1 FS bytes used 192.00KiB devid 1 size 10.00GiB used 536.00MiB path /dev/mapper/3600140501cc1f49e5364f0093869c763 /dev/mapper/xxx can actually be backed by an arbitrary number of path, which in turn are presented to the system as ordinary scsi devices i.e /dev/sdd. If a path flaps and a user re-runs 'btrfs fi show' the output would look like: Label: none uuid: d3c1261f-18be-4015-9fef-6b35759dfdba Total devices 1 FS bytes used 192.00KiB devid 1 size 10.00GiB used 536.00MiB path /dev/sdd Turns out the output of this command is consumed by libraries and the presence of a path device rather than the actual multipath one can cause issues. Fix this by relying on the fact that path devices are tagged with the DM_MULTIPATH_DEVICE_PATH attribute by the respective udev scripts. In order to access it an optional dependency on libudev is added, if the library can't be found then device enumeration will continue working as it was before the commit. Since libudev doesn't have static library for now support for this behavior in case of static builds is going to be disabled. Fallback code for static builds will come in a future commit. Signed-off-by: Nikolay Borisov <redacted> --- Makefile | 2 +- Makefile.inc.in | 2 +- common/device-scan.c | 44 ++++++++++++++++++++++++++++++++++++++++++++ configure.ac | 9 +++++++++ 4 files changed, 55 insertions(+), 2 deletions(-)diff --git a/Makefile b/Makefile index 93fe4c2b3e08..e96f66a36b46 100644 --- a/Makefile +++ b/Makefile@@ -129,7 +129,7 @@ LIBS = $(LIBS_BASE) $(LIBS_CRYPTO) LIBBTRFS_LIBS = $(LIBS_BASE) $(LIBS_CRYPTO) # Static compilation flags -STATIC_CFLAGS = $(CFLAGS) -ffunction-sections -fdata-sections +STATIC_CFLAGS = $(CFLAGS) -ffunction-sections -fdata-sections -DSTATIC_BUILD
Could you please split the configure/makefile changes to a separate patch? For progs the patch separation rules/recommendations are less strict as for kernel but at least the build and code changes should be separate as each has a different justification. Doing libudev and -DSTATIC_BUILD is probably fine in one patch.
quoted hunk ↗ jump to hunk
STATIC_LDFLAGS = -static -Wl,--gc-sections STATIC_LIBS = $(STATIC_LIBS_BASE)diff --git a/Makefile.inc.in b/Makefile.inc.in index 9f49337147b8..c995aef97219 100644 --- a/Makefile.inc.in +++ b/Makefile.inc.in@@ -27,7 +27,7 @@ CRYPTO_CFLAGS = @GCRYPT_CFLAGS@ @SODIUM_CFLAGS@ @KCAPI_CFLAGS@ SUBST_CFLAGS = @CFLAGS@ SUBST_LDFLAGS = @LDFLAGS@ -LIBS_BASE = @UUID_LIBS@ @BLKID_LIBS@ -L. -pthread +LIBS_BASE = @UUID_LIBS@ @BLKID_LIBS@ @LIBUDEV_LIBS@ -L. -pthread LIBS_COMP = @ZLIB_LIBS@ @LZO2_LIBS@ @ZSTD_LIBS@ LIBS_PYTHON = @PYTHON_LIBS@ LIBS_CRYPTO = @GCRYPT_LIBS@ @SODIUM_LIBS@ @KCAPI_LIBS@diff --git a/common/device-scan.c b/common/device-scan.c index b5bfe844104b..2ed0e34d3664 100644 --- a/common/device-scan.c +++ b/common/device-scan.c@@ -14,6 +14,10 @@ * Boston, MA 021110-1307, USA. */ +#ifdef STATIC_BUILD +#undef HAVE_LIBUDEV +#endif + #include "kerncompat.h" #include <sys/ioctl.h> #include <stdlib.h>@@ -25,6 +29,10 @@ #include <dirent.h> #include <blkid/blkid.h> #include <uuid/uuid.h> +#ifdef HAVE_LIBUDEV +#include <sys/stat.h> +#include <libudev.h> +#endif #include "kernel-lib/overflow.h" #include "common/path-utils.h" #include "common/device-scan.h"@@ -364,6 +372,37 @@ void free_seen_fsid(struct seen_fsid *seen_fsid_hash[]) } } +#ifdef HAVE_LIBUDEV +static bool is_path_device(char *device_path)
Please rename it to is_multipath_device, we've been using 'path' for normal paths and I find using 'path' confusing in this context.
quoted hunk ↗ jump to hunk
+{ + struct udev *udev = NULL; + struct udev_device *dev = NULL; + struct stat dev_stat; + const char *val; + bool ret = false; + + if (stat(device_path, &dev_stat) < 0) + return false; + + udev = udev_new(); + if (!udev) + goto out; + + dev = udev_device_new_from_devnum(udev, 'b', dev_stat.st_rdev); + if (!dev) + goto out; + + val = udev_device_get_property_value(dev, "DM_MULTIPATH_DEVICE_PATH"); + if (val && atoi(val) > 0) + ret = true; +out: + udev_device_unref(dev); + udev_unref(udev); + + return ret; +} +#endif + int btrfs_scan_devices(int verbose) { int fd = -1;@@ -394,6 +433,11 @@ int btrfs_scan_devices(int verbose) /* if we are here its definitely a btrfs disk*/ strncpy_null(path, blkid_dev_devname(dev)); +#ifdef HAVE_LIBUDEV + if (is_path_device(path)) + continue; +#endif
I'd rather avoid inline ifdef, the cleaner way is to define 2 versions
based on the macro like
#ifdef HAVE_LIBUDEV
static bool is_path_device(char *device_path)
{
... as above
}
#else
static bool is_path_device(char *device_path)
{
return false;
}
#endif
and inside btrfs_scan_devices do
if (is_multipath_device(...))
quoted hunk ↗ jump to hunk
+ fd = open(path, O_RDONLY); if (fd < 0) { error("cannot open %s: %m", path);diff --git a/configure.ac b/configure.ac index 038c2688421c..d0ceb0d70d16 100644 --- a/configure.ac +++ b/configure.ac@@ -304,6 +304,15 @@ PKG_STATIC(UUID_LIBS_STATIC, [uuid]) PKG_CHECK_MODULES(ZLIB, [zlib]) PKG_STATIC(ZLIB_LIBS_STATIC, [zlib]) +PKG_CHECK_EXISTS([libudev], [pkg_config_libudev=yes], [pkg_config_libudev=no]) +if test "x$pkg_config_libudev" = xyes; then + PKG_CHECK_MODULES([LIBUDEV], [libudev]) + AC_DEFINE([HAVE_LIBUDEV], [1], [Define to 1 if libudev is available]) +else + AC_MSG_CHECKING([for LIBUDEV]) + AC_MSG_RESULT([no]) +fi + AC_ARG_ENABLE([zstd], AS_HELP_STRING([--disable-zstd], [build without zstd support]), [], [enable_zstd=yes]-- 2.17.1