From: Mike Snitzer <snitzer@kernel.org>
To: Duoming Zhou <duoming@zju.edu.cn>
Cc: linux-kernel@vger.kernel.org, agk@redhat.com,
dm-devel@redhat.com, Ignat Korchagin <ignat@cloudflare.com>
Subject: Re: dm crypt: fix sleep-in-atomic-context bug in kcryptd_crypt_tasklet
Date: Tue, 23 May 2023 13:53:23 -0400 [thread overview]
Message-ID: <ZGz9k3jnVqiO20a2@redhat.com> (raw)
In-Reply-To: <20230523075857.76520-1-duoming@zju.edu.cn>
On Tue, May 23 2023 at 3:58P -0400,
Duoming Zhou <duoming@zju.edu.cn> wrote:
> In order to improve the IO performance of the dm-crypt
> implementation, the commit 39d42fa96ba1 ("dm crypt:
> add flags to optionally bypass kcryptd workqueues")
> adds tasklet to do the crypto operations.
>
> The tasklet callback function kcryptd_crypt_tasklet()
> calls kcryptd_crypt() which is an original workqueue
> callback function that may sleep. As a result, the
> sleep-in-atomic-context bug may happen. The process
> is shown below.
>
> (atomic context)
> kcryptd_crypt_tasklet()
> kcryptd_crypt()
> kcryptd_crypt_write_convert()
> wait_for_completion() //may sleep
>
> The wait_for_completion() is a function that may sleep.
> In order to mitigate the bug, this patch changes
> wait_for_completion() to try_wait_for_completion().
>
> Fixes: 39d42fa96ba1 ("dm crypt: add flags to optionally bypass kcryptd workqueues")
> Signed-off-by: Duoming Zhou <duoming@zju.edu.cn>
> ---
> drivers/md/dm-crypt.c | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/md/dm-crypt.c b/drivers/md/dm-crypt.c
> index 8b47b913ee8..5e2b2463d87 100644
> --- a/drivers/md/dm-crypt.c
> +++ b/drivers/md/dm-crypt.c
> @@ -2085,7 +2085,8 @@ static void kcryptd_crypt_write_convert(struct dm_crypt_io *io)
> crypt_finished = atomic_dec_and_test(&ctx->cc_pending);
> if (!crypt_finished && kcryptd_crypt_write_inline(cc, ctx)) {
> /* Wait for completion signaled by kcryptd_async_done() */
> - wait_for_completion(&ctx->restart);
> + while (!try_wait_for_completion(&ctx->restart))
> + ;
> crypt_finished = 1;
> }
>
> --
> 2.17.1
>
Cc'ing Ignat for closer review.
But wasn't this already addressed with this commit?:
8abec36d1274 dm crypt: do not wait for backlogged crypto request completion in softirq
Mike
next prev parent reply other threads:[~2023-05-23 17:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-23 7:58 [PATCH] dm crypt: fix sleep-in-atomic-context bug in kcryptd_crypt_tasklet Duoming Zhou
2023-05-23 17:53 ` Mike Snitzer [this message]
2023-05-25 2:34 ` duoming
2023-05-25 6:42 ` Ignat Korchagin
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=ZGz9k3jnVqiO20a2@redhat.com \
--to=snitzer@kernel.org \
--cc=agk@redhat.com \
--cc=dm-devel@redhat.com \
--cc=duoming@zju.edu.cn \
--cc=ignat@cloudflare.com \
--cc=linux-kernel@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