From mboxrd@z Thu Jan 1 00:00:00 1970 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 64459C64ED6 for ; Wed, 1 Mar 2023 14:54:02 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229884AbjCAOyB (ORCPT ); Wed, 1 Mar 2023 09:54:01 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:49358 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229683AbjCAOyA (ORCPT ); Wed, 1 Mar 2023 09:54:00 -0500 Received: from mail-il1-x134.google.com (mail-il1-x134.google.com [IPv6:2607:f8b0:4864:20::134]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id B395F2A159 for ; Wed, 1 Mar 2023 06:53:59 -0800 (PST) Received: by mail-il1-x134.google.com with SMTP id h10so8424920ila.11 for ; Wed, 01 Mar 2023 06:53:59 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kernel-dk.20210112.gappssmtp.com; s=20210112; t=1677682439; h=content-transfer-encoding:in-reply-to:from:references:cc:to :content-language:subject:user-agent:mime-version:date:message-id :from:to:cc:subject:date:message-id:reply-to; bh=TwI8tOfzfdazowf72DLvwukg9+Hal0tmqWNmV5upb6I=; b=BEv6V4RdIovKT4Th0D3aQS7wvrYFLKYoH/ySvcerlNwAdKAyA8H7w6rxRmU96F8LUF Axg/n7BS6qEkurzOhgmzD3LfrrI9+n5ITu6aaIJv7QX/+DkBh/IkfLN8ECsd6CFQm7RX zFNrfQCmCXuvcz2JegWq8dJS3Cyorvkah3AT7Jvc2ngpwMJxGmU5zX1TOoDjihWwlioq +WPM4HJdUx08/IblJRh68r1khqaLo3+g94rUSsR7b6quIzeYISTkQqls5RWZpEd8l5oL PUxtaOVuLsNKfH16iGM82R1Ztn6+UG1RCkF7AhsGdW81+nZASG+/9fcJO4F5C3vTn10r A2Vg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; t=1677682439; h=content-transfer-encoding:in-reply-to:from:references:cc:to :content-language:subject:user-agent:mime-version:date:message-id :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=TwI8tOfzfdazowf72DLvwukg9+Hal0tmqWNmV5upb6I=; b=07dtyu6IuBR/h/4J3ivNtv0zSk3KMWuO+V7lJbMyR8ZB2LwcfLg6kZrNA0UsiN9HeB jEZYxWdfb+A618yGRaJAWPmvHnjloZ90aKNUuXvOi8wuii/DeKIk4EwqfBt9JPzqMogj NHMX57Sb405n98MfKYNO/HmPdsq4TdYmfGnesvUO27EmAgEgcvfHe9sDQiGbCpd8WMoq oi33DRMv+zX+tCP2N6eSF22EHQ27fzScnLaN6bLotpyjU8uQyz5ftcgz9G0AUF6uVGgp ruKv/YiI9wSMs/dN55o1gGBcFvWAF1zHl1UgH1E4OhWndP6aCQhBm5VYQELo5ecLmJH+ NmGA== X-Gm-Message-State: AO0yUKUjUhnlu7o100LEnhbm6lFXWW+c7BjuTF6v/jK8jinr2cdm1U2r Mvcbfih8C/kiZFPnFBahzNA8Lw== X-Google-Smtp-Source: AK7set9wUTQIAy9iDR60wz+zEI48LqNnzQUExlEWqfvjXXoFgtFvDZW52iAyrGkkt59GUz7nwuJOxQ== X-Received: by 2002:a05:6e02:1a8d:b0:317:1ca3:f518 with SMTP id k13-20020a056e021a8d00b003171ca3f518mr5691984ilv.0.1677682438994; Wed, 01 Mar 2023 06:53:58 -0800 (PST) Received: from [192.168.1.94] ([96.43.243.2]) by smtp.gmail.com with ESMTPSA id v10-20020a02cbaa000000b0039c492ae300sm3696122jap.114.2023.03.01.06.53.58 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Wed, 01 Mar 2023 06:53:58 -0800 (PST) Message-ID: <5ff2b3c0-eb96-c423-dcee-1bdf6604e9df@kernel.dk> Date: Wed, 1 Mar 2023 07:53:57 -0700 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux aarch64; rv:102.0) Gecko/20100101 Thunderbird/102.8.0 Subject: Re: INFO: task hung in io_ring_exit_work Content-Language: en-US To: Sanan Hasanov , "asml.silence@gmail.com" , "io-uring@vger.kernel.org" , "linux-kernel@vger.kernel.org" Cc: "syzkaller@googlegroups.com" , "contact@pgazz.com" References: From: Jens Axboe In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Precedence: bulk List-ID: X-Mailing-List: io-uring@vger.kernel.org On 2/26/23 11:23 PM, Sanan Hasanov wrote: > Good day, dear maintainers, > > We found a bug using a modified kernel configuration file used by syzbot. > > We enhanced the coverage of the configuration file using our tool, klocalizer. > > Kernel Branch: 6.2.0-next-20230225 > Kernel config: https://drive.google.com/file/d/1NS9N8rvftQ7BouImn2OVnC96qrNhAeuO/view?usp=share_link > C Reproducer: Unfortunately, there is no reproducer for this bug yet. Not sure what we're supposed to do with this, without a syzbot or c reproducer? You can get into this condition if you SIGSTOP the task so it can't complete its task_work, for example. But impossible to glean anything from this report. -- Jens Axboe