From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mail78-58.sinamail.sina.com.cn (mail78-58.sinamail.sina.com.cn [219.142.78.58]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id B8C2EA41 for ; Sun, 12 Jan 2025 00:11:47 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=219.142.78.58 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1736640713; cv=none; b=LdVBZO0hbW3dczQr5uE3ETAOrj7ojQiPPsKJWXmLgDRYCtYkXyb8K8+JVbkAFNY++VrBa0pGB+P3ugWn5AytE/WbR4n/Hv5TV9lJejmR8WMTwfLVkk8+m5HCOKozmUjKE+SDQWWK9cWv0ePghMl1U5/yLmEODBTP0FB/vmToyWc= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1736640713; c=relaxed/simple; bh=TqDRSyTEm2s3IijjPpgSlT2l/DuwvehgxbSxSxcTwwU=; h=From:To:Cc:Subject:Date:Message-ID:In-Reply-To:References: MIME-Version; b=GNfzvTvZNOlFBgy6x3JhNrNolQg/FxTT3JpNk4B4TAXXVjicE3+Y02TVkHipuPOUBlUMDA70NUXLQlZa+s8ONEohRqZDLBdLpD2QUnsbE5zjlgXQMDcQmQXg5umH4uRHoMT1HiHucWhXTlW7d92VyzJNl7cR/JzFxjHwJgIYDHE= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=none (p=none dis=none) header.from=sina.com; spf=pass smtp.mailfrom=sina.com; arc=none smtp.client-ip=219.142.78.58 Authentication-Results: smtp.subspace.kernel.org; dmarc=none (p=none dis=none) header.from=sina.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=sina.com X-SMAIL-HELO: localhost.localdomain Received: from unknown (HELO localhost.localdomain)([113.118.69.152]) by sina.com (10.185.250.24) with ESMTP id 678308BE000056DA; Sun, 12 Jan 2025 08:11:45 +0800 (CST) X-Sender: hdanton@sina.com X-Auth-ID: hdanton@sina.com Authentication-Results: sina.com; spf=none smtp.mailfrom=hdanton@sina.com; dkim=none header.i=none; dmarc=none action=none header.from=hdanton@sina.com X-SMAIL-MID: 4870210748371 X-SMAIL-UIID: 8D35FF4CE1A2432D8C495A7470A643CC-20250112-081145-1 From: Hillf Danton To: syzbot Cc: linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com Subject: Re: [syzbot] [kernel?] possible deadlock in binder_alloc_free_page Date: Sun, 12 Jan 2025 08:11:32 +0800 Message-ID: <20250112001134.1770-1-hdanton@sina.com> In-Reply-To: <6782483e.050a0220.216c54.001d.GAE@google.com> References: Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Transfer-Encoding: 8bit On Sat, 11 Jan 2025 02:30:22 -0800 > syzbot found the following issue on: > > HEAD commit: 7b4b9bf203da Add linux-next specific files for 20250107 > git tree: linux-next > syz repro: https://syzkaller.appspot.com/x/repro.syz?x=10302dc4580000 #syz test --- x/drivers/android/binder_alloc.c +++ y/drivers/android/binder_alloc.c @@ -1245,10 +1245,12 @@ void binder_alloc_init(struct binder_all INIT_LIST_HEAD(&alloc->buffers); } +static struct lock_class_key key; int binder_alloc_shrinker_init(void) { int ret; + binder_freelist.key = &key; ret = list_lru_init(&binder_freelist); if (ret) return ret; --