From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-11.6 required=3.0 tests=BAYES_00,DKIM_INVALID, DKIM_SIGNED,HEADER_FROM_DIFFERENT_DOMAINS,INCLUDES_PATCH,MAILING_LIST_MULTI, SPF_HELO_NONE,SPF_PASS,USER_AGENT_GIT autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 4CB06C433DB for ; Tue, 5 Jan 2021 00:58:05 +0000 (UTC) Received: from mail.server123.net (mail.server123.net [78.46.64.186]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id C38F82256F for ; Tue, 5 Jan 2021 00:58:04 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org C38F82256F Authentication-Results: mail.kernel.org; dmarc=fail (p=reject dis=none) header.from=cloudflare.com Authentication-Results: mail.kernel.org; spf=pass smtp.mailfrom=dm-crypt-bounces@saout.de X-Virus-Scanned: amavisd-new at saout.de Authentication-Results: mail.server123.net (amavisd-new); dkim=pass (1024-bit key) header.d=cloudflare.com Received-SPF: Pass (mailfrom) identity=mailfrom; client-ip=2a00:1450:4864:20::32f; helo=mail-wm1-x32f.google.com; envelope-from=ignat@cloudflare.com; receiver= Received: from mail-wm1-x32f.google.com (mail-wm1-x32f.google.com [IPv6:2a00:1450:4864:20::32f]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by mail.server123.net (Postfix) with ESMTPS for ; Mon, 4 Jan 2021 16:00:05 +0100 (CET) Received: by mail-wm1-x32f.google.com with SMTP id g185so19608625wmf.3 for ; Mon, 04 Jan 2021 07:00:05 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cloudflare.com; s=google; h=from:to:cc:subject:date:message-id:mime-version :content-transfer-encoding; bh=zX8HfL31wQZp5jl2djKi9uuAu6EFw+BifBJL8TfPFYI=; b=iZ+iMncSyLwlAaQXDZtSclG1TAiabyBIgpxpm6gwMhtwbK9uLIPw0KJkoz4mOk9f0F rHnD2/9O68rmG8J+8w2HgaVnFZ5OEFNHNYLnPI+b1SbXBAU263EFyuSKd5cB4ybDV2Tk Q2Ucnog/Ug5GYE+l8FlOnNY6Dt/g0EgWKtnjA= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:cc:subject:date:message-id:mime-version :content-transfer-encoding; bh=zX8HfL31wQZp5jl2djKi9uuAu6EFw+BifBJL8TfPFYI=; b=ARqhuLffb6lex7xlDLrpmnPkNLWjC5CjGrWGz8W5o8ARAhUtyMnxYngDcnnX77Xh6Z 91n8zJMNSVRPRSsppWWxkaamhRnKV3BVP7aCd6fSdf6psP0p8HeJGmDNnRSWyCisohMR ooaq0ILIb93v1q7MnarncA126FjIrQi1qaFVsSVj5zI+DhTM4whpFanVPm6Ws0v2oXwb 2df5LF8rMOhC1FBmT1Jc+z1KvJqbayYKcpgcYGT0THlLxxT3L/dH+SygYADoG4n9Sq3D GDbousst4PPuw9MN5iqgm+O6alftIQqrbG+qoY3ZUnp+X5kwsMx9togyxzUkBdbnqDMI G2ZQ== X-Gm-Message-State: AOAM531NmAUoVvTpOnS6jyNtTllLqy3IlPxMpsItVSlnyVuFWv9+lkrz kMk4yi5VEHZb1EC5TPcodG5QFA== X-Google-Smtp-Source: ABdhPJyZ7mnenRW8F7aJHWIfVzmZOehv2AMU4Up9FryPAzuecSePdIqVbZnPsKBWirVBfeRygVofGw== X-Received: by 2002:a1c:9949:: with SMTP id b70mr26716903wme.72.1609772404590; Mon, 04 Jan 2021 07:00:04 -0800 (PST) Received: from dev.cfops.net (165.176.200.146.dyn.plus.net. [146.200.176.165]) by smtp.gmail.com with ESMTPSA id r1sm94445954wrl.95.2021.01.04.07.00.03 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Mon, 04 Jan 2021 07:00:03 -0800 (PST) From: Ignat Korchagin To: agk@redhat.com, snitzer@redhat.com, dm-devel@redhat.com, dm-crypt@saout.de, linux-kernel@vger.kernel.org Date: Mon, 4 Jan 2021 14:59:46 +0000 Message-Id: <20210104145948.1857-1-ignat@cloudflare.com> X-Mailer: git-send-email 2.20.1 MIME-Version: 1.0 X-Mailman-Approved-At: Tue, 05 Jan 2021 01:57:24 +0100 Subject: [dm-crypt] [PATCH v3 0/2] dm crypt: some fixes to support dm-crypt running in softirq context X-BeenThere: dm-crypt@saout.de X-Mailman-Version: 2.1.29 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , 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 , dsterba@suse.com, mail@maciej.szmigiero.name, linux-btrfs@vger.kernel.org Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: dm-crypt-bounces@saout.de Sender: "dm-crypt" 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 _______________________________________________ dm-crypt mailing list dm-crypt@saout.de https://www.saout.de/mailman/listinfo/dm-crypt