From: Ignat Korchagin <ignat@cloudflare.com>
To: agk@redhat.com, snitzer@redhat.com, dm-devel@redhat.com,
dm-crypt@saout.de, linux-kernel@vger.kernel.org
Cc: Ignat Korchagin <ignat@cloudflare.com>,
ebiggers@kernel.org, Damien.LeMoal@wdc.com, mpatocka@redhat.com,
herbert@gondor.apana.org.au, kernel-team@cloudflare.com,
nobuto.murata@canonical.com, clm@fb.com, josef@toxicpanda.com,
dsterba@suse.com, linux-btrfs@vger.kernel.org,
mail@maciej.szmigiero.name
Subject: [PATCH v3 0/2] dm crypt: some fixes to support dm-crypt running in softirq context
Date: Mon, 4 Jan 2021 14:59:46 +0000 [thread overview]
Message-ID: <20210104145948.1857-1-ignat@cloudflare.com> (raw)
Changes from v1:
* 0001: handle memory allocation failure for GFP_ATOMIC
Changes from v2:
* reordered patches
* 0002: crypt_convert will be retried from a workqueue, when a crypto request
allocation fails with GFP_ATOMIC instead of just returning an IO error to
the user
Ignat Korchagin (2):
dm crypt: do not wait for backlogged crypto request completion in
softirq
dm crypt: use GFP_ATOMIC when allocating crypto requests from softirq
drivers/md/dm-crypt.c | 138 +++++++++++++++++++++++++++++++++++++-----
1 file changed, 123 insertions(+), 15 deletions(-)
--
2.20.1
next reply other threads:[~2021-01-04 15:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-04 14:59 Ignat Korchagin [this message]
2021-01-04 14:59 ` [PATCH v3 1/2] dm crypt: do not wait for backlogged crypto request completion in softirq Ignat Korchagin
2021-01-04 14:59 ` [PATCH v3 2/2] dm crypt: use GFP_ATOMIC when allocating crypto requests from softirq Ignat Korchagin
2021-01-04 17:04 ` [PATCH v3 0/2] dm crypt: some fixes to support dm-crypt running in softirq context Mikulas Patocka
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=20210104145948.1857-1-ignat@cloudflare.com \
--to=ignat@cloudflare.com \
--cc=Damien.LeMoal@wdc.com \
--cc=agk@redhat.com \
--cc=clm@fb.com \
--cc=dm-crypt@saout.de \
--cc=dm-devel@redhat.com \
--cc=dsterba@suse.com \
--cc=ebiggers@kernel.org \
--cc=herbert@gondor.apana.org.au \
--cc=josef@toxicpanda.com \
--cc=kernel-team@cloudflare.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mail@maciej.szmigiero.name \
--cc=mpatocka@redhat.com \
--cc=nobuto.murata@canonical.com \
--cc=snitzer@redhat.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