Received: by 2002:a05:6358:9144:b0:117:f937:c515 with SMTP id r4csp1020192rwr; Wed, 3 May 2023 09:09:49 -0700 (PDT) X-Google-Smtp-Source: ACHHUZ6O288aYeZabt653KorMjYCG9egvkQBjG4FcDSNVVqjjFEL9RdrsibrTyCs9MVCqHJQ2ajd X-Received: by 2002:a17:902:c94d:b0:1a4:f4e6:b68 with SMTP id i13-20020a170902c94d00b001a4f4e60b68mr8259480pla.3.1683130189220; Wed, 03 May 2023 09:09:49 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1683130189; cv=none; d=google.com; s=arc-20160816; b=Ry4ZS9Dc5bItE3bJGW3QwaWr71LhFLvMA3nzi2YmAwSLeAv7bPwPp12qgpt/NkPB3e f7P6pvchMbOZqxPTt4Qxp2ZkaQtoxDZqQjPusIM1mjDMpcQV37HwEPoZjuMShox6xf2R pyCq1zit9ySezlU+3e4Hos2WqSOTF5D8wbFIv1GVUOTpqW07ZR+kVb5U9sAmobmd+/AE 6XWujF8RtboAWeNXi79Fnd+TNPPsfvqOFnVSAO77m10GC537uf8rF1uUiO7g278N1Xoh sc945VwXNZUD2BSNJbtqL6cRX9yqx+QS7HwJcsbrvZCaf15rerCC9O87c485FL/wv+DS 8ZvA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:user-agent:in-reply-to:content-disposition :mime-version:references:message-id:subject:cc:to:from:date; bh=fNgUxorvLTFSGaJeJdT1fHOlk0jYw5FRYlzD4L4LsBI=; b=Rm2DLqt2UgBhPV6zq78DlwMUrCRlDq4CZbhcT0lnxk4xcA2cMXLWxlOAlqnEjmuSaT xwVuv67N46E+ua95aEUaw40TGFkd7tAKJc+AWQCZZKD2G4scZwW09pRsmSzifrTxFPrN B+PJcbYCRI8zAv7/TIJCDrVvo/gQ45BAxh4Fs1PnIjN8bBuPkLmqEp46RdH416os370p cFLJYfw8yqwd2opd1zzFT/Pn/wPkDVArZLRuAruYkCcIyPRJIyRHXDqO6QYv6ZFliHFG 3rX3N1yOqThUdccw2NDf7Rw1rfzWOPJDiwTQqhhNo5hp6qtiEND2REBbWZUU/pTO77Zb Bc9Q== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id q10-20020a170902a3ca00b001a92e587f72si27975718plb.413.2023.05.03.09.09.33; Wed, 03 May 2023 09:09:49 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S230299AbjECP5v (ORCPT + 99 others); Wed, 3 May 2023 11:57:51 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:40256 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S230064AbjECP5t (ORCPT ); Wed, 3 May 2023 11:57:49 -0400 Received: from verein.lst.de (verein.lst.de [213.95.11.211]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 9D3BF4EEB; Wed, 3 May 2023 08:57:48 -0700 (PDT) Received: by verein.lst.de (Postfix, from userid 2407) id 44F2368AA6; Wed, 3 May 2023 17:57:45 +0200 (CEST) Date: Wed, 3 May 2023 17:57:45 +0200 From: "hch@lst.de" To: Jinyoung CHOI Cc: "axboe@kernel.dk" , "hch@lst.de" , "martin.petersen@oracle.com" , "linux-block@vger.kernel.org" , "linux-kernel@vger.kernel.org" Subject: Re: [PATCH 05/15] block: fix not to apply bip information in blk_rq_bio_prep() Message-ID: <20230503155745.GD31700@lst.de> References: <20230503094912epcms2p4bef206eab1c41a92eba2583a69c74323@epcms2p4> <20230503101048epcms2p61d61df1431955d9517c9939999ee3478@epcms2p6> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20230503101048epcms2p61d61df1431955d9517c9939999ee3478@epcms2p6> User-Agent: Mutt/1.5.17 (2007-11-01) X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,SPF_HELO_NONE, SPF_NONE,T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, May 03, 2023 at 07:10:48PM +0900, Jinyoung CHOI wrote: > When a request is initialized through the bio, bio's integrity > information is not reflected in the request. Uuh. This looks like a pretty grave bug unless I'm missing something. Can you: - submit this as a fix for 6.3 and -stable? - maybe find what broke this and add a fixes tag?