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 kanga.kvack.org (kanga.kvack.org [205.233.56.17]) by smtp.lore.kernel.org (Postfix) with ESMTP id 7E837C61DA4 for ; Thu, 2 Feb 2023 14:01:54 +0000 (UTC) Received: by kanga.kvack.org (Postfix) id CB5E46B0072; Thu, 2 Feb 2023 09:01:53 -0500 (EST) Received: by kanga.kvack.org (Postfix, from userid 40) id C655D6B0073; Thu, 2 Feb 2023 09:01:53 -0500 (EST) X-Delivered-To: int-list-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix, from userid 63042) id B54A46B0074; Thu, 2 Feb 2023 09:01:53 -0500 (EST) X-Delivered-To: linux-mm@kvack.org Received: from relay.hostedemail.com (smtprelay0010.hostedemail.com [216.40.44.10]) by kanga.kvack.org (Postfix) with ESMTP id A77296B0072 for ; Thu, 2 Feb 2023 09:01:53 -0500 (EST) Received: from smtpin10.hostedemail.com (a10.router.float.18 [10.200.18.1]) by unirelay02.hostedemail.com (Postfix) with ESMTP id 6898E120F04 for ; Thu, 2 Feb 2023 14:01:53 +0000 (UTC) X-FDA: 80422515306.10.41DBB59 Received: from r3-11.sinamail.sina.com.cn (r3-11.sinamail.sina.com.cn [202.108.3.11]) by imf19.hostedemail.com (Postfix) with ESMTP id E3E411A0005 for ; Thu, 2 Feb 2023 14:01:48 +0000 (UTC) Authentication-Results: imf19.hostedemail.com; dkim=none; spf=temperror (imf19.hostedemail.com: error in processing during lookup of hdanton@sina.com: DNS error) smtp.mailfrom=hdanton@sina.com; dmarc=none ARC-Seal: i=1; s=arc-20220608; d=hostedemail.com; t=1675346511; a=rsa-sha256; cv=none; b=3r1Ut4sZ+wWS6bwPwBXcSW0+HeRJZYMvjNCKaGtppOzx/aGS/rGPcifbYOIF/wH8lCwlls ai9IHuTg3b3LE0u0BfPAFVaWuDapivmkdZjqZeYO2qck0GnLGZzFd2IffBGTOABjpkGy7K GO75Q2L49qqtJi1naYj2kzmNK2HPSdE= ARC-Authentication-Results: i=1; imf19.hostedemail.com; dkim=none; spf=temperror (imf19.hostedemail.com: error in processing during lookup of hdanton@sina.com: DNS error) smtp.mailfrom=hdanton@sina.com; dmarc=none ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=hostedemail.com; s=arc-20220608; t=1675346511; h=from:from:sender:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:cc:mime-version:mime-version: content-type:content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=bcipgXWW55GikBe3mBlSvgqcHfunmsRV9vHCNjqHNgI=; b=OpKa3sa91vBtf5nBE5nZhPtVoxuf1Ulrso5ZN6OFm+C+okOy022YDtin9K2e+ZjlfPGBDH PqRnL0tHVGH5v1zX0srwBrM8dN5798wLcr1r/X17HshG4OF3XyQNFDISwu7I1ojQXdWqOk Hmqr/g5gcXH4DEBK/MWP0AMFkO2/Md4= Received: from unknown (HELO localhost.localdomain)([114.249.61.130]) by sina.com (172.16.97.27) with ESMTP id 63DBC1D400003518; Thu, 2 Feb 2023 21:59:51 +0800 (CST) X-Sender: hdanton@sina.com X-Auth-ID: hdanton@sina.com X-SMAIL-MID: 7253949283559 From: Hillf Danton To: syzbot Cc: edumazet@google.com, linux-bluetooth@vger.kernel.org, linux-kernel@vger.kernel.org, luiz.dentz@gmail.com, marcel@holtmann.org, linux-mm@kvack.org, syzkaller-bugs@googlegroups.com, yinghsu@chromium.org Subject: Re: [syzbot] INFO: task hung in rfcomm_process_sessions (2) Date: Thu, 2 Feb 2023 22:01:30 +0800 Message-Id: <20230202140130.828-1-hdanton@sina.com> In-Reply-To: <000000000000b09dc705f3b05f9b@google.com> References: MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-Rspam-User: X-Rspamd-Queue-Id: E3E411A0005 X-Rspamd-Server: rspam01 X-Stat-Signature: ztxupi77rpzxb6sowrzxmfzm5tjpyxp5 X-HE-Tag: 1675346508-334021 X-HE-Meta: U2FsdGVkX1/1GLyal8IafJVpm4US4kYgvcmMJZAgpcSleDd77HaMp06eLBF/ioHsWqlv5wx1j70NE8Q0NYM39dhwDxU3hZ3XsJvfUYE2se8eeEZ9NzxwmkWfL8nh6bztgIXoB/owEui/XsIE8pWX8Fp6fCsKRAtKMJZ8QrPLUyn4zFB3fDvRG2lcYlezI9SxQRJ1QknkfRzTSKapjMRYkNVvEholbeF6EfT2L4v4Sd8IEAcHxN8Re0T0sEvXv3sKzLx726SuTMf+U73zyhniKYSv3PNY0nXnOoh06gLl/NSpUkdg6zf3co9K3oQl+yJ9tM5/fccUROD5IjMcxeCWn1AaThkIOJskTNedG/iJ4itRuom/++cuMlwMkPvd+I4naATG99kap7zyj9NnBrHvLxxmhU1YkMCGq00KlinDWUlYL3e3tnFM4bw/auXkkBF4MwSGjialTRU9aAoSt2mIpSkcjP3xpCAdi9Ax+KUTHLozOrWqLVUvxksVUb+i3xmrjf9eUFu8/QBOI+0YHrzupazOUlaZipRmXX1aXzBjvdC8YDtgQflhCZco3U0PPpcgifinaUkUgxlnirN2cd3U6cYrjmvegv7eYFVwnZetctkK/wdrmV8YRJtBppv8Sexrk5rDKfZxP8vjV4IFyHgmKa4pQaETbyg6/ffCha2A0puHzL7gWRZCw6VLA2fyHzHclJb+ouSkV5hMIWaAryde+h38Kc7YaSO/MK2EUvNBTUfk/OoOdJbbhcW9EX5S1/S0mvqOUfNIerX4q8Y0Hx9zCkAXy1POy1wtVU5GFmQeerJ2ZTvJH9kL0nSG5Xg/x6WDd0IfBlPIUar5YJPpTClyZleAHMtJQoE2z1qjMnh58OlJhcoRCb2T0bzybIexEwNnEBe3dwfoPa3SyNxWb2Dr6DN9sm8Urv4clbo48TDh4h4JRe/HJV0L6jRRx3C+DAf3j6YrCriDjPrrYbaZ6Zp fikM1SzI SUl+VrduB7Brfxk+w1N3dXUn9oBvzC0dZL2aCU3S1cN46hnrFjXvyVfaoHRhXwcZJw23Lwxa7G2tYp3tVJSdh5LhdGRL2tTYtQmhlLtuOUpJJK4rafXsp1W7clYMbsfvBF0PBjujIQMAuWOMWBjK24cHuB5JVnyh/fOVJRHuHcTo/XKec65IkX7wYylOJJ0VzXey8DlzLB+iXnTvsIqBDADCgDZImmiV3UW1WsnVGlLDhmDQVR0AqEQWWHKKngYMd8wq+sd3y0bIlm+3yXjoIOhyAVEMuxY/OlLOHpbq+UCjXtOeshLL9B8JAEF3XQ711CaYAbRCECOBQ18H0un7HY9drf9fugwsgeg8FJXKjR0HYeHkLcvA5CCRUaOwXfoiotcMrllssDjeLi5RIn2Cc1D2PJVDArdr7zN/+SWTL8Ny6fm9h3ZgdSBx+YFFc1PqZbERJimXOVB5Mtz7doX0rH4/Dpg8CBRJkX3L4Qxp0SRomfF02cBVhHnuEqme0Xyv63dcI9osvWZkVMFwDHGjWIsb/Po1IsIUiey1MJGlsT8uBz6s= X-Bogosity: Ham, tests=bogofilter, spamicity=0.000000, version=1.2.4 Sender: owner-linux-mm@kvack.org Precedence: bulk X-Loop: owner-majordomo@kvack.org List-ID: On Wed, 01 Feb 2023 20:55:28 -0800 > syzbot suspects this issue was fixed by commit: > > commit 1d80d57ffcb55488f0ec0b77928d4f82d16b6a90 > Author: Ying Hsu > Date: Wed Jan 11 03:16:14 2023 +0000 > > Bluetooth: Fix possible deadlock in rfcomm_sk_state_change > > bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=154b77b5480000 > start commit: d888c83fcec7 fs: fix fd table size alignment properly > git tree: upstream > kernel config: https://syzkaller.appspot.com/x/.config?x=69c8957f4ac2dea6 > dashboard link: https://syzkaller.appspot.com/bug?extid=d761775dff24be3ad4be > syz repro: https://syzkaller.appspot.com/x/repro.syz?x=162ca1fd700000 > C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1036182d700000 > > If the result looks correct, please mark the issue as fixed by replying with: > > #syz fix: Bluetooth: Fix possible deadlock in rfcomm_sk_state_change > > For information about bisection process see: https://goo.gl/tpsmEJ#bisection If it is the correct fix then why was task hung reported instead of deadlock? What went wrong with lockdep at cffb2b72d3ed upstream? Hillf