From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <sven@whgl.uni-frankfurt.de>
Received: from mps1.wohnheimg.uni-frankfurt.de
 (mps1.wohnheimg.uni-frankfurt.de [141.2.118.239])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (No client certificate requested)
 by mail.server123.net (Postfix) with ESMTPS
 for <dm-crypt@saout.de>; Sat,  6 Feb 2016 20:17:56 +0100 (CET)
Received: from p4fe84ca4.dip0.t-ipconnect.de ([79.232.76.164]
 helo=[192.168.0.11]) (Authed sender Sven 'DarKRaveR' Eschenberg)
 by mps1.wohnheimg.uni-frankfurt.de via ESMTPSA
 (TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128) (Exim)
 (envelope-from <sven@whgl.uni-frankfurt.de>) id 1aS8Ml-0007NX-VB
 for dm-crypt@saout.de; Sat, 06 Feb 2016 20:17:56 +0100
References: <20160204092017.GA25029@yeono.kjorling.se>
 <56B37D92.2030306@whgl.uni-frankfurt.de> <20160204172311.GB20874@tansi.org>
 <n92dtd$hv9$1@ger.gmane.org> <20160205155743.GA32705@tansi.org>
 <56B5356B.3030704@whgl.uni-frankfurt.de> <20160206025854.GA5986@tansi.org>
 <56B56605.4030907@whgl.uni-frankfurt.de>
 <20160206100140.GU13740@yeono.kjorling.se>
 <56B641C2.4070400@whgl.uni-frankfurt.de>
 <20160206190916.GA20801@yeono.kjorling.se>
From: Sven Eschenberg <sven@whgl.uni-frankfurt.de>
Message-ID: <56B646EA.1050100@whgl.uni-frankfurt.de>
Date: Sat, 6 Feb 2016 20:18:02 +0100
MIME-Version: 1.0
In-Reply-To: <20160206190916.GA20801@yeono.kjorling.se>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Subject: Re: [dm-crypt] The future of disk encryption with LUKS2
List-Id: <dm-crypt.saout.de>
List-Unsubscribe: <http://www.saout.de/mailman/options/dm-crypt>,
 <mailto:dm-crypt-request@saout.de?subject=unsubscribe>
List-Archive: <http://www.saout.de/pipermail/dm-crypt/>
List-Post: <mailto:dm-crypt@saout.de>
List-Help: <mailto:dm-crypt-request@saout.de?subject=help>
List-Subscribe: <http://www.saout.de/mailman/listinfo/dm-crypt>,
 <mailto:dm-crypt-request@saout.de?subject=subscribe>
To: dm-crypt@saout.de

Okay, I see, for simple updates a counter could indeed be sufficient to 
ensure consistency by bringing the header with lower counter in sync 
with the other one.

Regards

-Sven

Am 06.02.2016 um 20:09 schrieb Michael Kjörling:
> On 6 Feb 2016 19:56 +0100, from sven@whgl.uni-frankfurt.de (Sven Eschenberg):
>> Hopefully I did not miss any step and yes, it is not THAT
>> complicated as there is no concurrency involved, but the
>> transactions for resizing need to be crafted carefully.
>
> I agree, it gets more complicated when resizing a container. I was
> considering primarily the normal use case of a container that isn't in
> the process of changing its size.
>