Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
IronPort-SDR: r9Gf9U+v/3iUk4xpvjY0ElK4lxi7tdE7u4P1nMvX45upnx+Y+Zj6rF17BwspPCol1AHcXUXUbe
 76McgaTNa7zBb+Wxd6pvx9fIzIqW7WHfpDcUg+k99Ub/uUtN29tOIgwLeBCXZRWhL1jDivh5+n
 SdXo1chZq499KwACQ0cNMVUHzChEYJWjXnzvyAeEMG21pjIfUSPLeZHxXZuRP4xmxCZLd4mNIP
 zBOZwVvHwsoMZGUbI4S75Wq2d61iZYZjILcP4WSz6s0/G7oNf+dy4R8p70oz6ZTGGeIVBQ20F3
 6P8=
From:   Chaitanya Kulkarni <Chaitanya.Kulkarni@wdc.com>
To:     Christoph Hellwig <hch@lst.de>
CC:     Jens Axboe <axboe@kernel.dk>, David Anderson <dvander@google.com>,
        Alistair Delva <adelva@google.com>,
        Todd Kjos <tkjos@google.com>,
        Amit Pundir <amit.pundir@linaro.org>,
        YongQin Liu <yongqin.liu@linaro.org>,
        lkml <linux-kernel@vger.kernel.org>,
        "linux-block@vger.kernel.org" <linux-block@vger.kernel.org>
Subject: Re: [REGRESSION] "split bio_kmalloc from bio_alloc_bioset" causing
 crash shortly after bootup
Thread-Topic: [REGRESSION] "split bio_kmalloc from bio_alloc_bioset" causing
 crash shortly after bootup
Thread-Index: AQHXCZD3vAo2wh9jek+o1gtQqbdo1w==
Date:   Tue, 23 Feb 2021 07:37:52 +0000
Message-ID: <BYAPR04MB496574519941459FE83C437D86809@BYAPR04MB4965.namprd04.prod.outlook.com>
References: <CALAqxLUWjr2oR=5XxyGQ2HcC-TLARvboHRHHaAOUFq6_TsKXyw@mail.gmail.com>
 <BYAPR04MB4965F0B60169371A25CD423E86809@BYAPR04MB4965.namprd04.prod.outlook.com>
 <20210223071040.GB16980@lst.de>
Accept-Language: en-US
Content-Language: en-US
wdcipoutbound: EOP-TRUE
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: 879f6857-0daa-4135-e4ac-08d8d7cded5a
X-MS-Exchange-CrossTenant-originalarrivaltime: 23 Feb 2021 07:37:52.1990
 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: b61c8803-16f3-4c35-9b17-6f65f441df86
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: pNOtSCT/WVrmAfr3CnBaTyfc5ajkFXeW0sD4kPpAkAV4AL+/CAWb41lyT4qF90RElhjQj/drVIkkSUmF0/zzYB0CANQgjUrepeJ4cE0aAOg=
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BY5PR04MB6280
Precedence: bulk
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

On 2/22/21 23:10, Christoph Hellwig wrote:=0A=
> On Tue, Feb 23, 2021 at 03:51:23AM +0000, Chaitanya Kulkarni wrote:=0A=
>> Looking at the other call sites do we need something like following ?=0A=
>> Since __blk_queue_bounce() passes the NULL for the passthru case as a=0A=
>> bio_set value ?=0A=
> Well, that is a somewhat odd calling convention.  What about the patch be=
low=0A=
> instead?  That being we really need to kill this bouncing code off..=0A=
I assume you are sending this patch, let me know otherwise.=0A=
If you do please add, looks good.=0A=
=0A=
Reviewed-by: Chaitanya Kulkarni <chaitanya.kulkarni@wdc.com>=0A=
=0A=