From: Tony Lindgren <tony@atomide.com>
To: Brian Norris <briannorris@chromium.org>
Cc: "Thomas Gleixner" <tglx@linutronix.de>,
"Heiko Stuebner" <heiko@sntech.de>,
"Linus Walleij" <linus.walleij@linaro.org>,
linux-rockchip@lists.infradead.org,
"Julia Cartwright" <julia@ni.com>,
LKML <linux-kernel@vger.kernel.org>,
linux-gpio@vger.kernel.org, "John Keeping" <john@metanate.com>,
linux-pm@vger.kernel.org, "Doug Anderson" <dianders@chromium.org>,
"Paul E. McKenney" <paulmck@linux.vnet.ibm.com>,
"Peter Zijlstra" <peterz@infradead.org>,
"David.Wu" <david.wu@rock-chips.com>,
'黄涛' <huangtao@rock-chips.com>
Subject: Re: [PATCH for 4.12] Revert "pinctrl: rockchip: avoid hardirq-unsafe functions in irq_chip"
Date: Mon, 26 Jun 2017 23:24:09 -0700 [thread overview]
Message-ID: <20170627062409.GX3730@atomide.com> (raw)
In-Reply-To: <20170627000622.GA63039@google.com>
* Brian Norris <briannorris@chromium.org> [170626 17:06]:
> So I agree that the above commit was problematic, and that you have
> fixed that in your patch ("PM / wakeirq: Convert to SRCU"). But I
> noticed there were other threads where people have complained about the
> $subject patch also causing problems with drivers that call
> disable_irq_nosync() from within an IRQ context. So I poked around with
> one such driver that calls disable_irq_nosync() from its ISR [1], and
> saw this:
>
> [ 14.524945] Bluetooth: : OOB Wake-on-BT configured at IRQ 56
> [ 14.531657] usbcore: registered new interface driver btusb
> [ 18.973886] BUG: sleeping function called from invalid context at kernel/locking/mutex.c:238
> [ 18.987695] in_atomic(): 1, irqs_disabled(): 128, pid: 0, name: swapper/0
> [ 18.995282] CPU: 0 PID: 0 Comm: swapper/0 Not tainted 4.12.0-rc6+ #1233
> [ 19.002669] Hardware name: Google Kevin (DT)
> [ 19.007435] Call trace:
> [ 19.010171] [<ffffff8008089928>] dump_backtrace+0x0/0x24c
> [ 19.016202] [<ffffff8008089b94>] show_stack+0x20/0x28
> [ 19.021846] [<ffffff8008371270>] dump_stack+0x90/0xb0
> [ 19.027488] [<ffffff80080cd2a0>] ___might_sleep+0x10c/0x124
> [ 19.033713] [<ffffff80080cd330>] __might_sleep+0x78/0x88
> [ 19.039647] [<ffffff800879e248>] mutex_lock+0x2c/0x64
> [ 19.045291] [<ffffff80083ad578>] rockchip_irq_bus_lock+0x30/0x3c
> [ 19.052003] [<ffffff80080f6c68>] __irq_get_desc_lock+0x78/0x98
> [ 19.058519] [<ffffff80080f8e90>] __disable_irq_nosync+0x38/0x80
> [ 19.065132] [<ffffff80080f8ef8>] disable_irq_nosync+0x20/0x2c
> [ 19.071555] [<ffffff8000a99f58>] btusb_oob_wake_handler+0x4c/0x68 [btusb]
Hmm so how come drivers/bluetooth/btusb.c can't use the generic
dev_pm_set_dedicated_wake_irq()? Can you please take a look?
If there are issues remaining let's rather fix them so we can get rid
of the custom tinkering of wake-up events in the drivers.
Regards,
Tony
next prev parent reply other threads:[~2017-06-27 6:24 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-17 22:56 [4.12 REGRESSION] pinctrl: rockchip: sleeping function called from atomic context Brian Norris
2017-05-27 2:19 ` Brian Norris
2017-06-23 20:59 ` [PATCH for 4.12] Revert "pinctrl: rockchip: avoid hardirq-unsafe functions in irq_chip" Brian Norris
2017-06-23 21:10 ` Heiko Stuebner
2017-06-23 22:12 ` Thomas Gleixner
2017-06-23 22:40 ` Paul E. McKenney
2017-06-24 9:21 ` Thomas Gleixner
2017-06-27 0:06 ` Brian Norris
2017-06-27 6:24 ` Tony Lindgren [this message]
2017-06-27 7:07 ` Brian Norris
2017-06-27 7:32 ` Tony Lindgren
2017-06-27 13:01 ` Thomas Gleixner
2017-06-27 13:06 ` Thomas Gleixner
2017-06-27 17:23 ` Brian Norris
2017-06-27 18:07 ` Thomas Gleixner
2017-06-27 13:26 ` Heiko Stübner
2017-06-27 16:35 ` Thomas Gleixner
2017-06-29 13:05 ` Linus Walleij
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=20170627062409.GX3730@atomide.com \
--to=tony@atomide.com \
--cc=briannorris@chromium.org \
--cc=david.wu@rock-chips.com \
--cc=dianders@chromium.org \
--cc=heiko@sntech.de \
--cc=huangtao@rock-chips.com \
--cc=john@metanate.com \
--cc=julia@ni.com \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=paulmck@linux.vnet.ibm.com \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.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
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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 NNTP newsgroup(s).