Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id C2D86C433F5 for ; Thu, 9 Dec 2021 03:45:33 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S231591AbhLIDtF (ORCPT ); Wed, 8 Dec 2021 22:49:05 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:54692 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229790AbhLIDtE (ORCPT ); Wed, 8 Dec 2021 22:49:04 -0500 Received: from mail-pl1-x635.google.com (mail-pl1-x635.google.com [IPv6:2607:f8b0:4864:20::635]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 51B3AC061746 for ; Wed, 8 Dec 2021 19:45:31 -0800 (PST) Received: by mail-pl1-x635.google.com with SMTP id p18so2902043plf.13 for ; Wed, 08 Dec 2021 19:45:31 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kernel-dk.20210112.gappssmtp.com; s=20210112; h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=njhG45usifVSAm2aSkNzlUSK10yx6nuwV6S2Kl0u5U4=; b=lxly56tID1rFfrom22nKVj1Bo78mbuL35BeHfQH79mlihekrCddSi5Z+LZwr72g+Ib OGMytoPiNYXJi++qs9qW6OLDloUcsHFmByYTKXbYJfrzsRODKzaRmzb3AK/WHjfC5rSD AQaRRc49NahQhibS0vpWikeNSMn06Fr0jzyHOVdtDEIGNFxHreehIZI3xVXy7/00KG5n 3lSNN7og+b9EzdYzz4IQHlLTmENYs5GVzi5cNMUAQ7dFUOvUb8Y9Tp0RmXdohQr8PVuR oEDr1ZwpdQ5o9veyEm3JYw0v8RDYE1CSPpq4zLRTPYu5fv43o3qmzWvgpQR+D6aG6tUC 0FZg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=njhG45usifVSAm2aSkNzlUSK10yx6nuwV6S2Kl0u5U4=; b=CQHsucmurWCmwZNDRdcJlveGtWE/0S4j5h28E1VveSYZjxuK+0Jj60+Fj71Bk0frUA JdY+Edic/GhiSjqlcqaD3AIr2jjWhnP4DqlBnouo/GwX+NQ22Di6fWvRcvyrwXua1LTO ynL3ryDnlOz9PI0gJF4jbpUYBFejeptwmDXeK/x2bq4xigNea03Wt51CatJvuA8inpUg ADxiHMUQvhAN7qIo3EEiVHQxxk/n7lcvVAgfsTXL/5AkdKDjT2XPiU+r+aMVJ7yp+yw6 aKCsjCnOv+WtHQr9xWl6tMGsOCdjcrJ7oE3S54TxnPB1DmvpR67xwyR8kwmQf7++zXfV ZZTw== X-Gm-Message-State: AOAM5329OPGSvBO+KNIoA1QVMdPXoK2AeFBmz+4j6PJt/kX1ScDBUcLh nVnUJz1uwsrb6X6YDrH3S1eLCQ== X-Google-Smtp-Source: ABdhPJz7tUH9m3lXUkXs8q2IISmHauEMBN0g0gHbAw9FC3FwsSbC6W27CPuO4vqyFhv7N8g8VPJ6tw== X-Received: by 2002:a17:903:1d2:b0:142:24f1:1213 with SMTP id e18-20020a17090301d200b0014224f11213mr64832437plh.81.1639021530561; Wed, 08 Dec 2021 19:45:30 -0800 (PST) Received: from [172.20.4.26] ([66.185.175.30]) by smtp.gmail.com with ESMTPSA id i1sm3967058pgs.50.2021.12.08.19.45.28 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Wed, 08 Dec 2021 19:45:30 -0800 (PST) Subject: Re: [syzbot] INFO: task hung in io_uring_cancel_generic (2) To: Josef Bacik , syzbot Cc: asml.silence@gmail.com, clm@fb.com, dsterba@suse.com, fgheet255t@gmail.com, io-uring@vger.kernel.org, linux-btrfs@vger.kernel.org, linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com, wqu@suse.com References: <000000000000e016c205d1025f4c@google.com> <000000000000fadd4905d2a9c7e8@google.com> From: Jens Axboe Message-ID: Date: Wed, 8 Dec 2021 20:45:27 -0700 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.10.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 12/8/21 7:51 PM, Josef Bacik wrote: > On Wed, Dec 08, 2021 at 02:12:09PM -0800, syzbot wrote: >> syzbot has bisected this issue to: >> >> commit 741ec653ab58f5f263f2b6df38157997661c7a50 >> Author: Qu Wenruo >> Date: Mon Sep 27 07:22:01 2021 +0000 >> >> btrfs: subpage: make end_compressed_bio_writeback() compatible >> > > This isn't the right patch, this is x86 so sectorsize == pagesize, so this patch > didn't change anything at all. Also unless the local fs is btrfs with > compression enabled I'm not entirely sure how this would even matter, the > reproducer seems to be purely io_uring related. Thanks, Yeah, it's not btrfs, it's just one of those "bisect gone awry" cases. btrfs guys can ignore this one. -- Jens Axboe