[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <02a101da9227$bda04cb0$38e0e610$@trustnetic.com>
Date: Fri, 19 Apr 2024 15:03:54 +0800
From: Jiawen Wu <jiawenwu@...stnetic.com>
To: <brgl@...ev.pl>
Cc: <andriy.shevchenko@...ux.intel.com>,
<bartosz.golaszewski@...aro.org>,
<elder@...aro.org>,
<geert+renesas@...der.be>,
<linus.walleij@...aro.org>,
<linux-gpio@...r.kernel.org>,
<linux-kernel@...r.kernel.org>,
<paulmck@...nel.org>,
<warthog618@...il.com>,
<wsa@...-dreams.de>
Subject: Re: [PATCH v3 00/24] gpio: rework locking and object life-time control
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
Powered by blists - more mailing lists