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 89CBEDF49 for ; Sat, 11 Jan 2025 13:17:53 +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=1736601481; cv=none; b=mswkrcENVK7jNVjVOYVhiSPUdqMpJ3ZYLmloZdjf/WkSpFbcqtVGWPKNRqlTtP49JUwuge+VNQtcTKXMbjDvXB3xLQH8J+Vn/wVNBxBnwktlO0MdIVfWKGBE9sNBBliLUZMona7Ba+LNqIXqA627Gieo6AX5/iovYfFlxEsBdHs= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1736601481; c=relaxed/simple; bh=bvUXMtJUahATzXdiNbL22HbfeWD65m4o99GrhuCo0OE=; h=From:To:Cc:Subject:Date:Message-ID:In-Reply-To:References: MIME-Version; b=g/WQmXr/S47Kh3KP0y3DpF1ooFs3P/CQcLffp7pJszrwXeS6qfti3m/Zl5j3AWetHQkJF5HFHArTDN3F5QE0FY6XBPjimxV7pZoSBQrjNx6zvjyCeGKweu3UWWuxZBwt9cLVQTolI/5FKzSOlXCwch/sMi5LevroGdUJEHxMT1s= 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.71.135]) by sina.com (10.185.250.24) with ESMTP id 67826EE90000049D; Sat, 11 Jan 2025 21:15:25 +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: 30400610748437 X-SMAIL-UIID: C9FB74BBEDC44ECABBBEE03187EC2205-20250111-211525-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: Sat, 11 Jan 2025 21:15:10 +0800 Message-ID: <20250111131512.1713-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 @@ -1247,9 +1247,10 @@ void binder_alloc_init(struct binder_all int binder_alloc_shrinker_init(void) { + static struct lock_class_key key; int ret; - ret = list_lru_init(&binder_freelist); + ret = __list_lru_init(&binder_freelist, false, &key, NULL); if (ret) return ret; --