From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mail-qt1-f181.google.com (mail-qt1-f181.google.com [209.85.160.181]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 592A513B797 for ; Tue, 27 Feb 2024 15:16:43 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=209.85.160.181 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1709047004; cv=none; b=TFqtYUncn2CnTv8zOH+epK7PFHD2F08U8Qy6FkZbFEHnSB1fccb/VzW41sjRP/IZFUYJ/SU+CTGQ0hEMHC/8ga+Xzg/67NGdVG+rXdRHQCcsMGnToCyNABfasRcozdXWijfJECipbKERD/8qQskR3Irh11jHDSxBTYBYIbvFalI= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1709047004; c=relaxed/simple; bh=1TjOgn7EZpOUEEsdqxGzzOJEHrIXNZsYpIJc8flVC+Y=; h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version: Content-Type:Content-Disposition:In-Reply-To; b=BsBU/cokxt4dFcXcpErluqlIcHnTc3XS0zs/dHDDQvvJ2l7eYladVNPi6wZto1vAvn58D5Z5JY+Z/8+K0/LaWZaboCU7m+bx/mkMaFvmBRxBvZCHFD0UU6DIzYVjEiDxC71CGDav2iWDtL2SmMMTZWlhv31q5Gq7Z9pHPSC8uHE= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=fail (p=none dis=none) header.from=kernel.org; spf=pass smtp.mailfrom=redhat.com; arc=none smtp.client-ip=209.85.160.181 Authentication-Results: smtp.subspace.kernel.org; dmarc=fail (p=none dis=none) header.from=kernel.org Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=redhat.com Received: by mail-qt1-f181.google.com with SMTP id d75a77b69052e-42a4516ec46so43228481cf.0 for ; Tue, 27 Feb 2024 07:16:43 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1709047002; x=1709651802; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:cc:to:from:date:x-gm-message-state:from:to:cc:subject:date :message-id:reply-to; bh=wkw57nIPcfh6PkDenfS4Isf5pAlTCASFCEKqDWK0EfE=; b=aU78drhWyUVxieH9w1Swlnq0OVtCvoGq+K7GRXXkhOsZBK7Xu7aFnZ+QopB5PyDN8P f5HwlRD2F/JI1talv3tKr9oxzGURIlCmiZeIuxuFse1WSL0pvfaPizWbuEiySrhkde0f qbLkOAvgz5kR2JW3nydsNzX1XZ2mtnXs6il9cVcfBH9ietpem/S/kyDPailH1E/Gybyk myCUX472Wa6d5aNISgEnT5hiRVBYceU9LE9WuokWdQuOwkZDiTo3HBNENj0z1MFd7nhH 6zMSU6mJB/H9zAxP25KACVgbWccmAv4m3BPto9GQX8lam5PMFLURb/T1sRQr/8UODHVV btoQ== X-Forwarded-Encrypted: i=1; AJvYcCUlzwmTAKZHFDiiRjv92Yt8hb5Y30OPK+Xy5OAawU1n8ETFwwDGfJXHI5Tcfc5BlV1oVF4vQFHNHhpyccgKP6np0Wa1Iasp5bwtWQ== X-Gm-Message-State: AOJu0YwvPpcK9WwqxfKy7Rq1HG+J7J3Dkdv9xdDWP5w9HT6iox6yHRDO TjBcVJWe7bldO6ibqGX73JdyRZDrpGFtQmQrAK9faILIFVS5pAqB7Uie8OJlQQ== X-Google-Smtp-Source: AGHT+IF3OX3RYDmLw5Xwj18/cLQPLdUQKcDoUQ0MjVBxCwuhrwbbGKCfPKDKriEFGlBfhfC7wVJNEA== X-Received: by 2002:a05:622a:293:b0:42e:8114:9469 with SMTP id z19-20020a05622a029300b0042e81149469mr9852481qtw.10.1709047002287; Tue, 27 Feb 2024 07:16:42 -0800 (PST) Received: from localhost (pool-68-160-141-91.bstnma.fios.verizon.net. [68.160.141.91]) by smtp.gmail.com with ESMTPSA id y19-20020ac87c93000000b0042e79e54811sm3071786qtv.64.2024.02.27.07.16.41 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 27 Feb 2024 07:16:41 -0800 (PST) Date: Tue, 27 Feb 2024 10:16:39 -0500 From: Mike Snitzer To: Christoph Hellwig Cc: Jens Axboe , Mikulas Patocka , Song Liu , Yu Kuai , dm-devel@lists.linux.dev, linux-block@vger.kernel.org, linux-raid@vger.kernel.org Subject: Re: atomic queue limit updates for stackable devices Message-ID: References: <20240223161247.3998821-1-hch@lst.de> <20240227151016.GC14335@lst.de> Precedence: bulk X-Mailing-List: linux-raid@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20240227151016.GC14335@lst.de> On Tue, Feb 27 2024 at 10:10P -0500, Christoph Hellwig wrote: > On Fri, Feb 23, 2024 at 12:38:46PM -0500, Mike Snitzer wrote: > > Also, you can use the lvm2 source code's testsuite to get really solid > > DM test coverge (particularly for changes in this patchset which is > > dealing with setting limits at device creation). > > And that one runs fine, although even with Jens' tree as a baseline > it hangs in the md code when dm tries to stop it. Trying mainline > now.. That's the mainline issue a bunch of MD (and dm-raid) oriented engineers are working hard to fix, they've been discussing on linux-raid (with many iterations of proposed patches). It regressed due to 6.8 MD changes (maybe earlier). Mike