From: mwilck@suse.com Subject: [PATCH 46/54] libmultipath: path_discover(): always set DI_BLACKLIST Date: Thu, 9 Jul 2020 12:36:15 +0200 Message-ID: <20200709103623.8302-5-mwilck@suse.com> References: <20200709103623.8302-1-mwilck@suse.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <20200709103623.8302-1-mwilck@suse.com> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: dm-devel-bounces@redhat.com Errors-To: dm-devel-bounces@redhat.com To: Christophe Varoqui , Benjamin Marzinski Cc: dm-devel@redhat.com, Martin Wilck List-Id: dm-devel.ids From: Martin Wilck Since 65e1845 ("multipath: call store_pathinfo with DI_BLACKLIST"), we use DI_BLACKLIST for new paths. There's no reason why we shouldn't do the same with paths which are (unexpectedly) already in pathvec. As argued for 65e1845, this might save some unnecessary work for paths which are blacklisted anyway. Signed-off-by: Martin Wilck --- libmultipath/discovery.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/libmultipath/discovery.c b/libmultipath/discovery.c index 5f4ebf0..caabfef 100644 --- a/libmultipath/discovery.c +++ b/libmultipath/discovery.c @@ -137,7 +137,7 @@ path_discover (vector pathvec, struct config * conf, udevice, flag | DI_BLACKLIST, NULL); else - return pathinfo(pp, conf, flag); + return pathinfo(pp, conf, flag | DI_BLACKLIST); } static void cleanup_udev_enumerate_ptr(void *arg) -- 2.26.2