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: Damien.LeMoal@wdc.com, herbert@gondor.apana.org.au,
kernel-team@cloudflare.com, nobuto.murata@canonical.com,
josef@toxicpanda.com, ebiggers@kernel.org, clm@fb.com,
mpatocka@redhat.com, Ignat Korchagin <ignat@cloudflare.com>,
dsterba@suse.com, mail@maciej.szmigiero.name,
linux-btrfs@vger.kernel.org
Subject: [dm-crypt] [PATCH v2 0/2] dm crypt: some fixes to support dm-crypt running in softirq context
Date: Wed, 30 Dec 2020 21:45:18 +0000 [thread overview]
Message-ID: <20201230214520.154793-1-ignat@cloudflare.com> (raw)
Changes from v1:
0001: Handle memory allocation failure for GFP_ATOMIC
Ignat Korchagin (2):
dm crypt: use GFP_ATOMIC when allocating crypto requests from softirq
dm crypt: do not wait for backlogged crypto request completion in
softirq
drivers/md/dm-crypt.c | 135 +++++++++++++++++++++++++++++++++++++-----
1 file changed, 120 insertions(+), 15 deletions(-)
--
2.20.1
_______________________________________________
dm-crypt mailing list
dm-crypt@saout.de
https://www.saout.de/mailman/listinfo/dm-crypt
next reply other threads:[~2020-12-31 16:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-30 21:45 Ignat Korchagin [this message]
2020-12-30 21:45 ` [dm-crypt] [PATCH v2 1/2] dm crypt: use GFP_ATOMIC when allocating crypto requests from softirq Ignat Korchagin
2021-01-01 10:00 ` Mikulas Patocka
2021-01-01 10:26 ` Ignat Korchagin
2020-12-30 21:45 ` [dm-crypt] [PATCH v2 2/2] dm crypt: do not wait for backlogged crypto request completion in softirq 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=20201230214520.154793-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;
as well as URLs for NNTP newsgroup(s).