[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CAB0TPYHMF0rMkVryEW0oshbdkjdjGhfL_Z5E-Dy0vnYK8m2KNQ@mail.gmail.com>
Date: Mon, 4 May 2020 21:32:47 +0200
From: Martijn Coenen <maco@...roid.com>
To: Jens Axboe <axboe@...nel.dk>
Cc: Christoph Hellwig <hch@....de>, Ming Lei <ming.lei@...hat.com>,
Chaitanya Kulkarni <Chaitanya.Kulkarni@....com>,
linux-block <linux-block@...r.kernel.org>,
LKML <linux-kernel@...r.kernel.org>, kernel-team@...roid.com,
Bart Van Assche <bvanassche@....org>
Subject: Re: [PATCH] loop: Call loop_config_discard() only after new config is applied.
Hi Jens,
Are you ok with this one? One of my later series depends on it, but so
far I've kept it separate because it's a bug fix.
Thanks,
Martijn
On Sat, Apr 18, 2020 at 5:46 PM Bart Van Assche <bvanassche@....org> wrote:
>
> On 2020-03-31 04:41, Martijn Coenen wrote:
> > loop_set_status() calls loop_config_discard() to configure discard for
> > the loop device; however, the discard configuration depends on whether
> > the loop device uses encryption, and when we call it the encryption
> > configuration has not been updated yet. Move the call down so we apply
> > the correct discard configuration based on the new configuration.
>
> Reviewed-by: Bart Van Assche <bvanassche@....org>
Powered by blists - more mailing lists