Linux-GPIO Archive mirror
 help / color / mirror / Atom feed

From: "Jiawen Wu" <jiawenwu@trustnetic.com>
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	[thread overview]
Message-ID: <02a101da9227$bda04cb0$38e0e610$@trustnetic.com> (raw)

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

next             reply	other threads:[~2024-04-19  7:05 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-19  7:03 Jiawen Wu [this message]
2024-04-19 13:27 ` [PATCH v3 00/24] gpio: rework locking and object life-time control Andy Shevchenko
2024-04-19 21:29 ` Bartosz Golaszewski
2024-04-22  8:38   ` Jiawen Wu
  -- strict thread matches above, loose matches on Subject: below --
2024-02-08  9:58 Bartosz Golaszewski
2024-02-08 17:43 ` Andy Shevchenko
2024-02-12 10:07 ` Bartosz Golaszewski
     [not found] ` <CGME20240213120518eucas1p2d514aac6e6d1e29bbae05f32db6724db@eucas1p2.samsung.com>
2024-02-13 12:05   ` Marek Szyprowski
2024-02-13 12:08     ` Bartosz Golaszewski

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='02a101da9227$bda04cb0$38e0e610$@trustnetic.com' \
    --to=jiawenwu@trustnetic.com \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=bartosz.golaszewski@linaro.org \
    --cc=brgl@bgdev.pl \
    --cc=elder@linaro.org \
    --cc=geert+renesas@glider.be \
    --cc=linus.walleij@linaro.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=paulmck@kernel.org \
    --cc=warthog618@gmail.com \
    --cc=wsa@the-dreams.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).