public inbox for linux-block@vger.kernel.org
 help / color / mirror / Atom feed
From: Linlin Zhang <linlin.zhang@oss.qualcomm.com>
To: Benjamin Marzinski <bmarzins@redhat.com>
Cc: linux-block@vger.kernel.org, ebiggers@kernel.org,
	mpatocka@redhat.com, gmazyland@gmail.com,
	linux-kernel@vger.kernel.org, adrianvovk@gmail.com,
	dm-devel@lists.linux.dev, quic_mdalam@quicinc.com,
	israelr@nvidia.com, hch@infradead.org, axboe@kernel.dk
Subject: Re: [PATCH v2 2/3] dm-inlinecrypt: add target for inline block device encryption
Date: Tue, 28 Apr 2026 17:20:07 +0800	[thread overview]
Message-ID: <6390db35-7f8e-4d00-9c1f-43d676007910@oss.qualcomm.com> (raw)
In-Reply-To: <ae_vacHQ75AgZbm_@redhat.com>



On 4/28/2026 7:21 AM, Benjamin Marzinski wrote:
> On Mon, Apr 27, 2026 at 01:23:27AM -0400, Benjamin Marzinski wrote:
>> On Fri, Apr 10, 2026 at 06:40:30AM -0700, Linlin Zhang wrote:
>>> From: Eric Biggers <ebiggers@google.com>
>>> +	/*
>>> +	 * Since we've added an encryption context to the bio and
>>> +	 * blk-crypto-fallback may be needed to process it, it's necessary to
>>> +	 * use the fallback-aware bio submission code rather than
>>> +	 * unconditionally returning DM_MAPIO_REMAPPED.
>>> +	 *
>>> +	 * To get the correct accounting for a dm target in the case where
>>> +	 * __blk_crypto_submit_bio() doesn't take ownership of the bio (returns
>>> +	 * true), call __blk_crypto_submit_bio() directly and return
>>> +	 * DM_MAPIO_REMAPPED in that case, rather than relying on
>>> +	 * blk_crypto_submit_bio() which calls submit_bio() in that case.
>>> +	 */
>>> +	if (__blk_crypto_submit_bio(bio))
>>
>> This will still double account for fallback writes (which call
>> submit_bio() on the encrypted bios, and return DM_MAPIO_SUBMITTED here). 
> 
> Just to clarify, I'm talking about the vmstats accounting. The IO
> originally gets accounted by submit_bio() when the bio is submitted to
> the dm device. For actual inline encryption and fallback reads, dm will
> submit the bio to the underlying device using submit_bio_noacct() to
> avoid double-counting the IO.
> 
> For fallback writes, __blk_crypto_submit_bio() will submit the encrypted
> bios to the underlying device with submit_bio(). This adds the IO
> sectors again, even though it's the same IO, only encrypted now.


Right, thanks for calling this out.

For fallback writes, the IO is still double-counted. Given that this only
affects IO accounting in the blk-crypto fallback write slow-path and not
correctness, I think this is an acceptable tradeoff, and we can leave a
TODO to revisit the accounting once a better solution exists.

Add the bellow to the annotate.

  /*
   * TODO: blk-crypto fallback write slow-path currently double-accounts
   * IO in vmstat, as encrypted bios are submitted via submit_bio().
   * This does not affect data correctness. Consider fixing this if
   * a cleaner accounting model for derived bios is introduced.
   */

Do you agree?

> 
> -Ben
> 
>>
>> -Ben
>>
>>> +		return DM_MAPIO_REMAPPED;
>>> +	return DM_MAPIO_SUBMITTED;
>>> +}
>>
> 


  reply	other threads:[~2026-04-28  9:20 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-10 13:40 [PATCH v2 0/3] dm-inlinecrypt: add target for inline block device encryption Linlin Zhang
2026-04-10 13:40 ` [PATCH v2 1/3] block: export blk-crypto symbols required by dm-inlinecrypt Linlin Zhang
2026-04-10 13:40 ` [PATCH v2 2/3] dm-inlinecrypt: add target for inline block device encryption Linlin Zhang
2026-04-27  1:19   ` Benjamin Marzinski
2026-04-27 12:20     ` Linlin Zhang
2026-04-28 10:43       ` Linlin Zhang
2026-04-28 16:20         ` Benjamin Marzinski
2026-04-29 12:16           ` Linlin Zhang
2026-04-27  5:23   ` Benjamin Marzinski
2026-04-27 23:21     ` Benjamin Marzinski
2026-04-28  9:20       ` Linlin Zhang [this message]
2026-04-28 16:36         ` Benjamin Marzinski
2026-04-29 12:34           ` Linlin Zhang
2026-04-29 15:25             ` Benjamin Marzinski
2026-04-29 15:58               ` Benjamin Marzinski
2026-04-30  9:21                 ` Linlin Zhang
2026-04-10 13:40 ` [PATCH v2 3/3] dm: add documentation for dm-inlinecrypt target Linlin Zhang
2026-04-10 17:07   ` Milan Broz
2026-04-24 13:53     ` Linlin Zhang

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=6390db35-7f8e-4d00-9c1f-43d676007910@oss.qualcomm.com \
    --to=linlin.zhang@oss.qualcomm.com \
    --cc=adrianvovk@gmail.com \
    --cc=axboe@kernel.dk \
    --cc=bmarzins@redhat.com \
    --cc=dm-devel@lists.linux.dev \
    --cc=ebiggers@kernel.org \
    --cc=gmazyland@gmail.com \
    --cc=hch@infradead.org \
    --cc=israelr@nvidia.com \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mpatocka@redhat.com \
    --cc=quic_mdalam@quicinc.com \
    /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