From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <SRS0=cicp=DF=vger.kernel.org=linux-block-owner@kernel.org>
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=-4.8 required=3.0 tests=BAYES_00,DKIMWL_WL_HIGH,
	DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,MAILING_LIST_MULTI,SPF_HELO_NONE,
	SPF_PASS autolearn=no 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 9C848C2D0A8
	for <linux-block@archiver.kernel.org>; Mon, 28 Sep 2020 20:59:37 +0000 (UTC)
Received: from vger.kernel.org (vger.kernel.org [23.128.96.18])
	by mail.kernel.org (Postfix) with ESMTP id 40773208D5
	for <linux-block@archiver.kernel.org>; Mon, 28 Sep 2020 20:59:37 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org;
	s=default; t=1601326777;
	bh=ec6OoHmgvoth50UzS4i3XOLm6RLc5Pxm7GGje4jPB0U=;
	h=Date:From:To:Cc:Subject:References:In-Reply-To:List-ID:From;
	b=Kxz8kNZ68DIIJULwEVEwaApG1Ul6HGwHi4Y/V604jBrhLRcHm1NzRIjs0Kw/2UL9U
	 XeCx1WmrOMrE/RchCqNUwnYdSeHsyjDcbGqsXVfh8AggoVKU/EoRu0mbIDXlQl5uFm
	 CnG2kGBvWXD5sw0fMw27HWzFlcDZJzLj71lLQ33o=
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
        id S1726668AbgI1U7g (ORCPT <rfc822;linux-block@archiver.kernel.org>);
        Mon, 28 Sep 2020 16:59:36 -0400
Received: from mail.kernel.org ([198.145.29.99]:45314 "EHLO mail.kernel.org"
        rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
        id S1726627AbgI1U7g (ORCPT <rfc822;linux-block@vger.kernel.org>);
        Mon, 28 Sep 2020 16:59:36 -0400
Received: from sol.localdomain (172-10-235-113.lightspeed.sntcca.sbcglobal.net [172.10.235.113])
        (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
        (No client certificate requested)
        by mail.kernel.org (Postfix) with ESMTPSA id DF42B2080A;
        Mon, 28 Sep 2020 20:59:35 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org;
        s=default; t=1601326776;
        bh=ec6OoHmgvoth50UzS4i3XOLm6RLc5Pxm7GGje4jPB0U=;
        h=Date:From:To:Cc:Subject:References:In-Reply-To:From;
        b=J+VdfQfMacRKngiL9dbRg51Sx3tPH8JEYO4Pf9dPr05eYVYk670xoZO7Xv8MnDkPD
         LfDgwPSL3lc5YEHvtXVPWGI2nBdsOepIHa2GmiWtHof01cupmY3XfiVMfIJLBTT9Xd
         IstUej1FacbbaPSLC++7W6Q1fdXjiEUf2b97wVpo=
Date:   Mon, 28 Sep 2020 13:59:34 -0700
From:   Eric Biggers <ebiggers@kernel.org>
To:     Jens Axboe <axboe@kernel.dk>
Cc:     linux-block@vger.kernel.org, dm-devel@redhat.com,
        Satya Tangirala <satyat@google.com>,
        Miaohe Lin <linmiaohe@huawei.com>
Subject: Re: [PATCH v2 0/3] block: fix up bio_crypt_ctx allocation
Message-ID: <20200928205934.GA1340@sol.localdomain>
References: <20200916035315.34046-1-ebiggers@kernel.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20200916035315.34046-1-ebiggers@kernel.org>
Precedence: bulk
List-ID: <linux-block.vger.kernel.org>
X-Mailing-List: linux-block@vger.kernel.org

On Tue, Sep 15, 2020 at 08:53:12PM -0700, Eric Biggers wrote:
> This series makes allocation of encryption contexts either able to fail,
> or explicitly require __GFP_DIRECT_RECLAIM (via WARN_ON_ONCE).
> 
> This applies to linux-block/for-next.
> 
> Changed since v1 (https://lkml.kernel.org/r/20200902051511.79821-1-ebiggers@kernel.org):
>     - Added patches 2 and 3.
>     - Added kerneldoc for bio_crypt_clone().
>     - Adjusted commit message.
> 
> Eric Biggers (3):
>   block: make bio_crypt_clone() able to fail
>   block: make blk_crypto_rq_bio_prep() able to fail
>   block: warn if !__GFP_DIRECT_RECLAIM in bio_crypt_set_ctx()

Jens, any interest in applying these patches for 5.10?

- Eric