From: Jens Axboe <axboe@kernel.dk>
To: Kristian Klausen <kristian@klausen.dk>, linux-block@vger.kernel.org
Cc: stable@vger.kernel.org, Martijn Coenen <maco@android.com>,
open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2] loop: Fix missing discard support when using LOOP_CONFIGURE
Date: Fri, 18 Jun 2021 08:52:58 -0600 [thread overview]
Message-ID: <64494b7d-01b3-8da3-e10c-d346746758ea@kernel.dk> (raw)
In-Reply-To: <20210618115157.31452-1-kristian@klausen.dk>
On 6/18/21 5:51 AM, Kristian Klausen wrote:
> Without calling loop_config_discard() the discard flag and parameters
> aren't set/updated for the loop device and worst-case they could
> indicate discard support when it isn't the case (ex: if the
> LOOP_SET_STATUS ioctl was used with a different file prior to
> LOOP_CONFIGURE).
Applied, thanks.
--
Jens Axboe
prev parent reply other threads:[~2021-06-18 14:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-18 11:51 [PATCH v2] loop: Fix missing discard support when using LOOP_CONFIGURE Kristian Klausen
2021-06-18 14:52 ` Jens Axboe [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=64494b7d-01b3-8da3-e10c-d346746758ea@kernel.dk \
--to=axboe@kernel.dk \
--cc=kristian@klausen.dk \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maco@android.com \
--cc=stable@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox