From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from sipsolutions.net (s3.sipsolutions.net [168.119.38.16]) (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 ADA602E628; Tue, 17 Dec 2024 10:46:41 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=168.119.38.16 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1734432403; cv=none; b=BjfqJgS/DRp4hoixoQ2eYABiyMZL5K+XPPE3Wpyv8bUG6qe2LCu9foIzPSQSLKAkqrBYmrvTyUsScc2t1XXlwfP3qgJMqiDdthXC3iCGNZ0mJLKzfoDrhsy0343TrjFQhsY4S9ayKZNOUdEH9F9HmpTsuK6BV69MrRCgspQyzMM= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1734432403; c=relaxed/simple; bh=sOmYwxhcs0Ck10oCwijJVOfj8Bp+RcsUy1ph6N0Pb0M=; h=Message-ID:Subject:From:To:Date:In-Reply-To:References: Content-Type:MIME-Version; b=CEDqwj3jJZUN5wIfxU7/DYSt+KRknfQsPnakl1idQYXPDAHMFRVqOEWscSxSgpul6U1bi9ykl6t4pfcV2A8i3dikZt9YeivWTcqQJIWTZzmgyt3eRgMQmzM2kkr2oKtB9CukrVB/0dObdRrT75q3QRy+jPhCIUkddEHHC/Gd9BY= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=sipsolutions.net; spf=pass smtp.mailfrom=sipsolutions.net; dkim=pass (2048-bit key) header.d=sipsolutions.net header.i=@sipsolutions.net header.b=xzO8HQai; arc=none smtp.client-ip=168.119.38.16 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=sipsolutions.net Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=sipsolutions.net Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=sipsolutions.net header.i=@sipsolutions.net header.b="xzO8HQai" DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=sipsolutions.net; s=mail; h=MIME-Version:Content-Transfer-Encoding: Content-Type:References:In-Reply-To:Date:To:From:Subject:Message-ID:Sender: Reply-To:Cc:Content-ID:Content-Description:Resent-Date:Resent-From:Resent-To: Resent-Cc:Resent-Message-ID; bh=sOmYwxhcs0Ck10oCwijJVOfj8Bp+RcsUy1ph6N0Pb0M=; t=1734432401; x=1735642001; b=xzO8HQai+5VwFRs9vZk0gR4ZQLq17V4qY6x65kYivGp8uWZ r0fhRkwwocpxgCdX4jsZwyUfUHFVssEOZR3C+68G5LMJZWO34Mmau9DSemacjQRNv4BwmphiOpYUa SzSZekl2WRNPGIeR8rMMWr87nswG7rIns4IoPzeutS2jUgZWobqLgJQH+XIgygg3KEsjGgvRY9RvR PA3kvoWebVmqG5YArGLRooqMz/1amKszGF4PlB8i+G2ojVC93UskLQYpe48tXFfC6Cu1yQXiddF9K TNbTxIZXQ6Ztm5M23cHV+J90q8Tv36OA7HoO3OPBh/8dpO9sVtqwLm+n7OHZyJsQ==; Received: by sipsolutions.net with esmtpsa (TLS1.3:ECDHE_X25519__RSA_PSS_RSAE_SHA256__AES_256_GCM:256) (Exim 4.98) (envelope-from ) id 1tNV65-000000024ou-3dEz; Tue, 17 Dec 2024 11:46:38 +0100 Message-ID: Subject: Re: [Bug] Deadlock between rfkill_fop_write() and nfc_unregister_device() From: Johannes Berg To: Sam Sun , linux-kernel@vger.kernel.org, linux-wireless@vger.kernel.org, netdev@vger.kernel.org, Simon Horman , pabeni@redhat.com, kuba@kernel.org, Eric Dumazet , davem@davemloft.net, krzk@kernel.org Date: Tue, 17 Dec 2024 11:46:36 +0100 In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable User-Agent: Evolution 3.54.2 (3.54.2-1.fc41) Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 X-malware-bazaar: not-scanned On Tue, 2024-12-17 at 17:33 +0800, Sam Sun wrote: > Dear developers and maintainers, >=20 > We originally encountered a task hung while using our modified > syzkaller. It was tested against the latest upstream kernel. We > analyzed the root cause and pinpoint the kernel crash log to the > following two tasks. >=20 This issue has been known a very long time and should be fixed in NFC, but I guess nobody is around to do it. https://syzkaller.appspot.com/bug?extid=3Dbb540a4bbfb4ae3b425d johannes