Received: by 2002:a05:6358:11c7:b0:104:8066:f915 with SMTP id i7csp3556145rwl; Sun, 9 Apr 2023 19:09:29 -0700 (PDT) X-Google-Smtp-Source: AKy350aQ36W2TU+Vw7Jrw0EZUOktebUgNNgKLBYzpvK8nKMTGMEojsRpHENUsMw6Rj73SlUe1s9R X-Received: by 2002:aa7:8f2a:0:b0:625:dcc1:620b with SMTP id y10-20020aa78f2a000000b00625dcc1620bmr9495527pfr.34.1681092569339; Sun, 09 Apr 2023 19:09:29 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1681092569; cv=none; d=google.com; s=arc-20160816; b=lGXd+xSdmsssENpyWmNrRrMaVbsLrdymc0vD6y7ZKVO88fHO50YmpVjxcqr7L2QVkg Vc7Xcr1eauTKSux/9KEeRP5/+S+4wZPY0t7D82dqT9kv9lOY8lhjNMMGju7NRho39Bf0 pvThb8GinfGl5NwEbB3Vx3LSv2CpqD0CTjrteDtDh6R7F3yJN7q/0exjNXbnOavrsf8y +P6hk1IFCzkqqdZOBeLHtnUbzG5PEGrIeJlW3rYykIdzyo5ZoyozonIo/BNI8t6PMYqA euZORCU2H+vdjpsbvdHGh8bf2mtdcPZybkgsEr+PJF2jSlYpPHFRLLo4ETBa71CXnvAS /6dw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:in-reply-to :mime-version:user-agent:date:message-id:from:references:cc:to :subject; bh=PtRqDW628TULpHNC+I4yTPoFmnc475kr/Drd4UnDtqU=; b=ESlY26AY9wnLeSFw602sJbFX+2DKjycZVmTbX20H4cixuYTFBUCnukXAQsI49BJjuM qknyfbW/tsYknpO/5hvgfmmp/rrO7Nd+XLh3pFMpGisISYqvFaEluWeS+dUaAgBE0fTU uDsYLO7RHQ+3olDn+j0BnzJaLO/uNs/nXZVW+o0Xc+zUmCiDnrAQgqN1pKdoKHRM7SjE hV8taUpjRspIeBuBZUKk8W4PCpmyM2JV2PUys4cb17JgRYzSmbsMgu86lXNgGvpPfDOu q5WkXrnsopK+qEUZ4lSK9bbdvIi5DT8Dvg+dJJW7APdpJvaKYiezD+vSHcc8zwX8sjj1 HiyQ== 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 i1-20020a625401000000b0062b9c3cc611si9585205pfb.329.2023.04.09.19.09.14; Sun, 09 Apr 2023 19:09:29 -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 S229475AbjDJB57 (ORCPT + 99 others); Sun, 9 Apr 2023 21:57:59 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:54440 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229455AbjDJB56 (ORCPT ); Sun, 9 Apr 2023 21:57:58 -0400 Received: from dggsgout11.his.huawei.com (dggsgout11.his.huawei.com [45.249.212.51]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id CE5C9358D; Sun, 9 Apr 2023 18:57:52 -0700 (PDT) Received: from mail02.huawei.com (unknown [172.30.67.169]) by dggsgout11.his.huawei.com (SkyGuard) with ESMTP id 4PvsYm20NLz4f4Nt5; Mon, 10 Apr 2023 09:57:48 +0800 (CST) Received: from [10.174.176.73] (unknown [10.174.176.73]) by APP3 (Coremail) with SMTP id _Ch0CgDHcyEbbTNkJq3_GQ--.14009S3; Mon, 10 Apr 2023 09:57:49 +0800 (CST) Subject: Re: [PATCH v2 0/3] blk-cgroup: some cleanup To: Bart Van Assche , Chengming Zhou , axboe@kernel.dk, tj@kernel.org Cc: paolo.valente@linaro.org, josef@toxicpanda.com, linux-block@vger.kernel.org, cgroups@vger.kernel.org, linux-kernel@vger.kernel.org, "yukuai (C)" References: <20230406145050.49914-1-zhouchengming@bytedance.com> From: Yu Kuai Message-ID: Date: Mon, 10 Apr 2023 09:57:47 +0800 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.8.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit X-CM-TRANSID: _Ch0CgDHcyEbbTNkJq3_GQ--.14009S3 X-Coremail-Antispam: 1UD129KBjvJXoW7Aw4fCr4xAr1kXw43AF1DJrb_yoW8ur4rpa 15KFZxCr48Gryqqa1rZanrWF18Ga9IkasrAr93Kr43Zas8uw48JF1kJF9FvryUGFWkZFyx WFyDGFZ5XF4jq37anT9S1TB71UUUUUUqnTZGkaVYY2UrUUUUjbIjqfuFe4nvWSU5nxnvy2 9KBjDU0xBIdaVrnRJUUUv2b4IE77IF4wAFF20E14v26r4j6ryUM7CY07I20VC2zVCF04k2 6cxKx2IYs7xG6rWj6s0DM7CIcVAFz4kK6r1j6r18M28lY4IEw2IIxxk0rwA2F7IY1VAKz4 vEj48ve4kI8wA2z4x0Y4vE2Ix0cI8IcVAFwI0_tr0E3s1l84ACjcxK6xIIjxv20xvEc7Cj xVAFwI0_Gr1j6F4UJwA2z4x0Y4vEx4A2jsIE14v26rxl6s0DM28EF7xvwVC2z280aVCY1x 0267AKxVW0oVCq3wAS0I0E0xvYzxvE52x082IY62kv0487Mc02F40EFcxC0VAKzVAqx4xG 6I80ewAv7VC0I7IYx2IY67AKxVWUJVWUGwAv7VC2z280aVAFwI0_Jr0_Gr1lOx8S6xCaFV Cjc4AY6r1j6r4UM4x0Y48IcVAKI48JM4IIrI8v6xkF7I0E8cxan2IY04v7Mxk0xIA0c2IE e2xFo4CEbIxvr21l42xK82IYc2Ij64vIr41l4I8I3I0E4IkC6x0Yz7v_Jr0_Gr1lx2IqxV Aqx4xG67AKxVWUJVWUGwC20s026x8GjcxK67AKxVWUGVWUWwC2zVAF1VAY17CE14v26r1q 6r43MIIYrxkI7VAKI48JMIIF0xvE2Ix0cI8IcVAFwI0_Jr0_JF4lIxAIcVC0I7IYx2IY6x kF7I0E14v26r1j6r4UMIIF0xvE42xK8VAvwI8IcIk0rVWrZr1j6s0DMIIF0xvEx4A2jsIE 14v26r1j6r4UMIIF0xvEx4A2jsIEc7CjxVAFwI0_Jr0_GrUvcSsGvfC2KfnxnUUI43ZEXa 7IU1zuWJUUUUU== X-CM-SenderInfo: 51xn3trlr6x35dzhxuhorxvhhfrp/ X-CFilter-Loop: Reflected X-Spam-Status: No, score=-2.9 required=5.0 tests=NICE_REPLY_A,SPF_HELO_NONE, SPF_NONE autolearn=unavailable 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 Hi, Bart 在 2023/04/08 2:41, Bart Van Assche 写道: > On 4/6/23 07:50, Chengming Zhou wrote: >> These are some cleanup patches of blk-cgroup. Thanks for review. > > With these patches applied, my kernel test VM crashes during boot. The > following crash disappears if I revert these patches: > > BUG: KASAN: null-ptr-deref in bio_associate_blkg_from_css+0x83/0x240 > Read of size 8 at addr 0000000000000518 by task blkid/5885 > Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS > 1.16.0-debian-1.16.0-5 04/01/2014 > Call Trace: >  dump_stack_lvl+0x4a/0x80 >  print_report+0x21e/0x260 >  kasan_report+0xc2/0xf0 >  __asan_load8+0x69/0x90 >  bio_associate_blkg_from_css+0x83/0x240 >  bfq_bio_bfqg+0xce/0x120 [bfq] >  bfq_bic_update_cgroup+0x2f/0x3c0 [bfq] >  bfq_init_rq+0x1e8/0xb10 [bfq] >  bfq_insert_request.isra.0+0xa3/0x420 [bfq] >  bfq_insert_requests+0xca/0xf0 [bfq] >  blk_mq_dispatch_rq_list+0x4c0/0xb00 I found this call trace quite weird, I can't figure out how bfq_insert_requests can be called from blk_mq_dispatch_rq_list, can you show the add2line result? Thanks, Kuai >  __blk_mq_sched_dispatch_requests+0x15e/0x200 >  blk_mq_sched_dispatch_requests+0x8b/0xc0 >  __blk_mq_run_hw_queue+0x3ff/0x500 >  __blk_mq_delay_run_hw_queue+0x23a/0x300 >  blk_mq_run_hw_queue+0x14e/0x350 >  blk_mq_sched_insert_request+0x181/0x1f0 >  blk_execute_rq+0xf4/0x300 >  scsi_execute_cmd+0x23e/0x350 >  sr_do_ioctl+0x173/0x3d0 [sr_mod] >  sr_packet+0x60/0x90 [sr_mod] >  cdrom_get_track_info.constprop.0+0x125/0x170 [cdrom] >  cdrom_get_last_written+0x1d4/0x2d0 [cdrom] >  mmc_ioctl_cdrom_last_written+0x85/0x120 [cdrom] >  mmc_ioctl+0x10b/0x1d0 [cdrom] >  cdrom_ioctl+0xa66/0x1270 [cdrom] >  sr_block_ioctl+0xee/0x130 [sr_mod] >  blkdev_ioctl+0x1bb/0x3f0 >  __x64_sys_ioctl+0xc7/0xe0 >  do_syscall_64+0x34/0x80 >  entry_SYSCALL_64_after_hwframe+0x46/0xb0 > > Bart. > > . >