Received: by 2002:a05:6a10:9848:0:0:0:0 with SMTP id x8csp4047595pxf; Tue, 23 Mar 2021 00:51:21 -0700 (PDT) X-Google-Smtp-Source: ABdhPJwWfNCOxkhj2WozmZFxlSUWfl8t+Jqs2eWmKae8/Ezpti7psDRiI264UzBj2rO3um/b67KX X-Received: by 2002:a17:906:3750:: with SMTP id e16mr3659303ejc.75.1616485881147; Tue, 23 Mar 2021 00:51:21 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1616485881; cv=none; d=google.com; s=arc-20160816; b=xG+Wrd/Y5mDgEuPOkWu65eyPDCz1YuJ99Sw1+vVJT554lrYo2WPN/2c65f8Z4HBGQ5 AxcyuDLjwwf8DaCKTZoCSpCs0z8mttEfSakZZOvferOkFYKlSCj+auYueNgc9sRppOSn JOL6h1VRECYOY72nLiSp5D8XPj1ZZeW15BzwECH309sko5UGMA9sMQRDMk0yPA+soKlj hiZvUidsYZZqyrEi1960u/mLXpWqiliLZOKLfXso3Eq+81KpPa5nlrfqsDI47mp67LcZ nSRYJAwx3AzdEzxFg25etizk9pcoJJTqZWJImnAItC/n3eszc3mrgjLESRVakXflzCAy vfhQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:content-language :in-reply-to:mime-version:user-agent:date:message-id:from:references :cc:to:subject; bh=QyP/iKJauWVNA6hQrE1OZdXo44P40TuQ57NC2h6aIok=; b=bTboH+0uNvnlrlYGKfV8wm+7w47lhKQdDUjHYFouV8vTlBGOLDIH0KAUe7F8b0vVXt UcMdxWJhFIuHfSrsBFTkxpZA/MAh8fr/Eb/4blmyI5+2OhJEMFOiCReiN/XtkBRIfx7X 9yK1BVyCzD2YPmEpz06jd5pmre05WPuaFxp/vGyX4a+yFfSMIw010zaBFlhFKwOPqJ2N rM+z5VkQAHkDkPNAD12IROwcfTLuv/pJfaxe/hzDMGaKOwWqxTR8PlTRwC5v78AymI9b UBz/LBnuRk3ZHgPYZAFfYp8qM3YpHS9NxECJMrqCpBOkkgGmiOrZVR/oJQtkha4F76RW 43SA== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=huawei.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id y25si13243466eje.459.2021.03.23.00.50.58; Tue, 23 Mar 2021 00:51:21 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=huawei.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229493AbhCWHr2 (ORCPT + 99 others); Tue, 23 Mar 2021 03:47:28 -0400 Received: from szxga05-in.huawei.com ([45.249.212.191]:14011 "EHLO szxga05-in.huawei.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229658AbhCWHrO (ORCPT ); Tue, 23 Mar 2021 03:47:14 -0400 Received: from DGGEMS414-HUB.china.huawei.com (unknown [172.30.72.59]) by szxga05-in.huawei.com (SkyGuard) with ESMTP id 4F4Ngt3qSGzrWks; Tue, 23 Mar 2021 15:45:14 +0800 (CST) Received: from [10.174.178.113] (10.174.178.113) by DGGEMS414-HUB.china.huawei.com (10.3.19.214) with Microsoft SMTP Server id 14.3.498.0; Tue, 23 Mar 2021 15:47:06 +0800 Subject: Re: md/dm-mpath: check whether all pgpaths have same uuid in multipath_ctr() To: Mike Snitzer , Christoph Hellwig , Zhiqiang Liu CC: , , "jejb@linux.ibm.com" , "martin.petersen@oracle.com" , , , linfeilong , "wubo (T)" References: <20210322081155.GE1946905@infradead.org> <20210322142207.GB30698@redhat.com> From: lixiaokeng Message-ID: Date: Tue, 23 Mar 2021 15:47:06 +0800 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:68.0) Gecko/20100101 Thunderbird/68.10.0 MIME-Version: 1.0 In-Reply-To: <20210322142207.GB30698@redhat.com> Content-Type: text/plain; charset="utf-8" Content-Language: en-GB Content-Transfer-Encoding: 7bit X-Originating-IP: [10.174.178.113] X-CFilter-Loop: Reflected Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 2021/3/22 22:22, Mike Snitzer wrote: > On Mon, Mar 22 2021 at 4:11am -0400, > Christoph Hellwig wrote: > >> On Sat, Mar 20, 2021 at 03:19:23PM +0800, Zhiqiang Liu wrote: >>> From: Zhiqiang Liu >>> >>> When we make IO stress test on multipath device, there will >>> be a metadata err because of wrong path. In the test, we >>> concurrent execute 'iscsi device login|logout' and >>> 'multipath -r' command with IO stress on multipath device. >>> In some case, systemd-udevd may have not time to process >>> uevents of iscsi device logout|login, and then 'multipath -r' >>> command triggers multipathd daemon calls ioctl to load table >>> with incorrect old device info from systemd-udevd. >>> Then, one iscsi path may be incorrectly attached to another >>> multipath which has different uuid. Finally, the metadata err >>> occurs when umounting filesystem to down write metadata on >>> the iscsi device which is actually not owned by the multipath >>> device. >>> >>> So we need to check whether all pgpaths of one multipath have >>> the same uuid, if not, we should throw a error. >>> >>> Signed-off-by: Zhiqiang Liu >>> Signed-off-by: lixiaokeng >>> Signed-off-by: linfeilong >>> Signed-off-by: Wubo >>> --- >>> drivers/md/dm-mpath.c | 52 +++++++++++++++++++++++++++++++++++++++++ >>> drivers/scsi/scsi_lib.c | 1 + >>> 2 files changed, 53 insertions(+) >>> >>> diff --git a/drivers/md/dm-mpath.c b/drivers/md/dm-mpath.c >>> index bced42f082b0..f0b995784b53 100644 >>> --- a/drivers/md/dm-mpath.c >>> +++ b/drivers/md/dm-mpath.c >>> @@ -24,6 +24,7 @@ >>> #include >>> #include >>> #include >>> +#include >>> #include >>> #include >>> >>> @@ -1169,6 +1170,45 @@ static int parse_features(struct dm_arg_set *as, struct multipath *m) >>> return r; >>> } >>> >>> +#define SCSI_VPD_LUN_ID_PREFIX_LEN 4 >>> +#define MPATH_UUID_PREFIX_LEN 7 >>> +static int check_pg_uuid(struct priority_group *pg, char *md_uuid) >>> +{ >>> + char pgpath_uuid[DM_UUID_LEN] = {0}; >>> + struct request_queue *q; >>> + struct pgpath *pgpath; >>> + struct scsi_device *sdev; >>> + ssize_t count; >>> + int r = 0; >>> + >>> + list_for_each_entry(pgpath, &pg->pgpaths, list) { >>> + q = bdev_get_queue(pgpath->path.dev->bdev); >>> + sdev = scsi_device_from_queue(q); >> >> Common dm-multipath code should never poke into scsi internals. This >> is something for the device handler to check. It probably also won't >> work for all older devices. > > Definitely. > > But that aside, userspace (multipathd) _should_ be able to do extra > validation, _before_ pushing down a new table to the kernel, rather than > forcing the kernel to do it. > Martin (committer of multipath-tools) said that: "Don't get me wrong, I don't argue against tough testing. But we should be aware that there are always time intervals during which multipathd's picture of the present devices is different from what the kernel sees." It is difficult to solve this in multipathd. Regards, Lixiaokeng