From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from bg1.exmail.qq.com (bg1.exmail.qq.com [114.132.67.179])
	(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 21DF915C3
	for <linux-kernel@vger.kernel.org>; Fri, 19 Apr 2024 07:04:16 +0000 (UTC)
Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=114.132.67.179
ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116;
	t=1713510261; cv=none; b=jo0VezSCww4RLhiWNqaeQu6XQc17IjyawAKsbdQvW8iXfM2a+0ZZ56XxINkR/Up9zzX+HE1q5UlnrCCqzGNMEbPuH0WiZ/J9QhsVdeRRYyx/Qqu+YMCQfbp9GKRu53VaXChPPqpFrByuYAOpjPGouuDgHda9AxKnmlVyOzDV2kc=
ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org;
	s=arc-20240116; t=1713510261; c=relaxed/simple;
	bh=8PYrVwihWEKnfBPv+dZo8Ce/XrKfV/qp4CBfZjoK42I=;
	h=From:To:Cc:Subject:Date:Message-ID:MIME-Version:Content-Type; b=XKz/7+nZaUmUehPl6alTxkEUrLKydR4zM6+n04GcusecY/uf5cRouK4SVsw1/7kTn0YgZQaOlGVhfZpePrzHsUxa6MROkDelfSs78EYHrYHGJDEOE6O4+3ocwVDAtSB6yBR/1eG4jR7bD2F6/6gZEvh2gCW0qxi+58ylaqTuH3I=
ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=none (p=none dis=none) header.from=trustnetic.com; spf=pass smtp.mailfrom=trustnetic.com; arc=none smtp.client-ip=114.132.67.179
Authentication-Results: smtp.subspace.kernel.org; dmarc=none (p=none dis=none) header.from=trustnetic.com
Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=trustnetic.com
X-QQ-mid:Yeas3t1713510235t323t22484
Received: from 3DB253DBDE8942B29385B9DFB0B7E889 (jiawenwu@trustnetic.com [125.119.247.132])
X-QQ-SSF:00400000000000F0FUF000000000000
From: =?utf-8?b?Smlhd2VuIFd1?= <jiawenwu@trustnetic.com>
X-BIZMAIL-ID: 15162911397788106260
To: <brgl@bgdev.pl>
Cc: <andriy.shevchenko@linux.intel.com>,
	<bartosz.golaszewski@linaro.org>,
	<elder@linaro.org>,
	<geert+renesas@glider.be>,
	<linus.walleij@linaro.org>,
	<linux-gpio@vger.kernel.org>,
	<linux-kernel@vger.kernel.org>,
	<paulmck@kernel.org>,
	<warthog618@gmail.com>,
	<wsa@the-dreams.de>
Subject: Re: [PATCH v3 00/24] gpio: rework locking and object life-time control
Date: Fri, 19 Apr 2024 15:03:54 +0800
Message-ID: <02a101da9227$bda04cb0$38e0e610$@trustnetic.com>
Precedence: bulk
X-Mailing-List: linux-kernel@vger.kernel.org
List-Id: <linux-kernel.vger.kernel.org>
List-Subscribe: <mailto:linux-kernel+subscribe@vger.kernel.org>
List-Unsubscribe: <mailto:linux-kernel+unsubscribe@vger.kernel.org>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 16.0
Thread-Index: AdqSJCuofj3/aB1TTmeRQb3sZM13Tw==
Content-Language: zh-cn
X-QQ-SENDSIZE: 520
Feedback-ID: Yeas:trustnetic.com:qybglogicsvrgz:qybglogicsvrgz8a-1

Hi Bartosz Golaszewski,

I ran into a kernel crash problem when I pull the latest net-next.git, and
finally it was found that is caused by this patch series merged.

The kernel crashed because I got gpio=0 when I called irq_find_mapping()
and then struct irq_data *d=null, as my driver describes:

	int gpio = irq_find_mapping(gc->irq.domain, hwirq);
	struct irq_data *d = irq_get_irq_data(gpio);

	txgbe_gpio_irq_ack(d);

The deeper positioning is this line in __irq_resolve_mapping().

	data = rcu_dereference(domain->revmap[hwirq]);
		
So, is it the addition of SRCU infrastructure that causes this issue?


Thanks,
Jiawen