mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Mikulas Patocka <mpatocka@redhat.com>
To: Hou Tao <houtao@huaweicloud.com>
Cc: dm-devel@lists.linux.dev, linux-kernel@vger.kernel.org,
	 Alasdair Kergon <agk@redhat.com>,
	Mike Snitzer <snitzer@kernel.org>,
	 Ignat Korchagin <ignat@cloudflare.com>,
	houtao1@huawei.com
Subject: Re: [PATCH 0/6] dm-crypt: misc cleanups and fixes
Date: Tue, 21 Jan 2025 13:31:01 +0100 (CET)	[thread overview]
Message-ID: <a0c0eed2-a068-551f-9c86-2a07bd4e3eca@redhat.com> (raw)
In-Reply-To: <20250120082951.1423804-1-houtao@huaweicloud.com>



On Mon, 20 Jan 2025, Hou Tao wrote:

> From: Hou Tao <houtao1@huawei.com>
> 
> Hi,
> 
> The patchset contains misc cleanups and minor fixes for dm-crypt. These
> problem were spotted during the code inspection. The patchset have been
> tested by running fio on dm-crypt devices (both with and without
> integrity feature). Patch #6 is tested by asynchronizing the
> crypt/decrypt algorithm when using random IV.
> 
> Please see individual patches for more details. Comments are always
> welcome.
> 
> Hou Tao (6):
>   dm-crypt: set atomic as false when calling crypt_convert() in kworker
>   dm-crypt: fully initialize clone->bi_iter in crypt_alloc_buffer()
>   dm-crypt: use bi_sector in bio when initialize integrity seed
>   dm-crypt: don't update io->sector after
>     kcryptd_crypt_write_io_submit()
>   dm-crypt: don't initialize cc_sector again
>   dm-crypt: track tag_offset in convert_context
> 
>  drivers/md/dm-crypt.c | 42 ++++++++++++++++--------------------------
>  1 file changed, 16 insertions(+), 26 deletions(-)
> 
> -- 
> 2.29.2

I applied the patches. Thanks.

Mikulas


      parent reply	other threads:[~2025-01-21 12:31 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-20  8:29 Hou Tao
2025-01-20  8:29 ` [PATCH 1/6] dm-crypt: set atomic as false when calling crypt_convert() in kworker Hou Tao
2025-01-20 17:21   ` Ignat Korchagin
2025-01-20  8:29 ` [PATCH 2/6] dm-crypt: fully initialize clone->bi_iter in crypt_alloc_buffer() Hou Tao
2025-01-20  8:29 ` [PATCH 3/6] dm-crypt: use bi_sector in bio when initialize integrity seed Hou Tao
2025-01-20  8:29 ` [PATCH 4/6] dm-crypt: don't update io->sector after kcryptd_crypt_write_io_submit() Hou Tao
2025-01-20  8:29 ` [PATCH 5/6] dm-crypt: don't initialize cc_sector again Hou Tao
2025-01-20  8:29 ` [PATCH 6/6] dm-crypt: track tag_offset in convert_context Hou Tao
2025-01-21 12:31 ` Mikulas Patocka [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=a0c0eed2-a068-551f-9c86-2a07bd4e3eca@redhat.com \
    --to=mpatocka@redhat.com \
    --cc=agk@redhat.com \
    --cc=dm-devel@lists.linux.dev \
    --cc=houtao1@huawei.com \
    --cc=houtao@huaweicloud.com \
    --cc=ignat@cloudflare.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=snitzer@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

all inboxes | Powered by JetHome®