[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <2b466945-0ad1-43e9-5530-4bcd3d469e33@nvidia.com>
Date: Tue, 25 Apr 2023 08:13:22 +0000
From: Chaitanya Kulkarni <chaitanyak@...dia.com>
To: Li Lingfeng <lilingfeng@...weicloud.com>
CC: "linux-block@...r.kernel.org" <linux-block@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"yukuai1@...weicloud.com" <yukuai1@...weicloud.com>,
"houtao1@...wei.com" <houtao1@...wei.com>,
"yi.zhang@...wei.com" <yi.zhang@...wei.com>,
"axboe@...nel.dk" <axboe@...nel.dk>, "hch@....de" <hch@....de>
Subject: Re: [PATCH -next] block: don't allow a disk link holder to its
ancestor
Li,
On 4/25/23 00:55, Li Lingfeng wrote:
> From: Li Lingfeng <lilingfeng3@...wei.com>
>
> Previously commit 077a4033541f ("block: don't allow a disk link holder
> to itself") prevent user from reloading dm with itself. However, user
> can reload dm with its ancestor which will trigger dead loop and result
> in oom.
>
> Test procedures:
> 1) dmsetup create test --table "0 20971520 linear /dev/sdd 0"
> 2) dmsetup create test1 --table "0 20971520 linear /dev/sdd 20971520"
> 3) dmsetup suspend test
> 4) dmsetup reload test --table "0 2048 linear /dev/mapper/test1 0"
> 5) dmsetup resume test
> 6) dmsetup suspend test1
> 7) dmsetup reload test1 --table "0 2048 linear /dev/mapper/test 0"
> 8) dmsetup resume test1
>
Can you please add blktest for this one ?
-ck
Powered by blists - more mailing lists