From: Marcel Holtmann <marcel@holtmann.org>
To: John Stultz <john.stultz@linaro.org>
Cc: Lukas Wunner <lukas@wunner.de>,
Rob Herring <rob.herring@linaro.org>,
Johan Hovold <johan@kernel.org>,
Ronald Tschalaer <ronald@innovation.ch>,
Sumit Semwal <sumit.semwal@linaro.org>,
"open list:BLUETOOTH DRIVERS" <linux-bluetooth@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Bluetooth: hci_serdev: Init hci_uart proto_lock to avoid oops
Date: Tue, 2 Jan 2018 21:45:44 +0100 [thread overview]
Message-ID: <D250C682-CAD9-48FD-9B82-25E6934AAC0D@holtmann.org> (raw)
In-Reply-To: <CALAqxLWbh=pmbZEfa03LvOTxBD7bnPVNdHs-os5xZjvhkSWT2Q@mail.gmail.com>
Hi John,
>>>> John Stultz reports a boot time crash with the HiKey board (which uses
>>>> hci_serdev) occurring in hci_uart_tx_wakeup(). That function is
>>>> contained in hci_ldisc.c, but also called from the newer hci_serdev.c.
>>>> It acquires the proto_lock in struct hci_uart and it turns out that we
>>>> forgot to init the lock in the serdev code path, thus causing the crash.
>>>>
>>>> John bisected the crash to commit 67d2f8781b9f ("Bluetooth: hci_ldisc:
>>>> Allow sleeping while proto locks are held"), but the issue was present
>>>> before and the commit merely exposed it. (Perhaps by luck, the crash
>>>> did not occur with rwlocks.)
>>>>
>>>> Init the proto_lock in the serdev code path to avoid the oops.
>>>>
>> [snip]
>>> patch has been applied to bluetooth-next tree.
>>
>> Sorry to be a nuisance if its just a timing thing, but I wanted to
>> follow up on this just to make sure it didn't fall through the cracks,
>> as I noticed w/ -rc3 it hasn't landed yet.
>
> Happy new year all,
> Just wanted to send another ping on this as it seems it hasn't made
> it into -rc6. Did this get missed as being tagged as a (at least
> functional) regression fix?
since it wasn’t marked as urgent fix, it never went on the path to -rc. It is on the path for the next release. And then can be included in -stable if needed.
Regards
Marcel
next prev parent reply other threads:[~2018-01-02 20:45 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-16 2:00 Boot crash @hci_uart_tx_wakeup+0x38/0x148 w/ Linus' HEAD? John Stultz
2017-11-16 20:58 ` John Stultz
2017-11-16 21:30 ` Lukas Wunner
2017-11-16 21:45 ` Lukas Wunner
2017-11-16 22:29 ` John Stultz
2017-11-16 23:54 ` [PATCH] Bluetooth: hci_serdev: Init hci_uart proto_lock to avoid oops Lukas Wunner
2017-11-16 23:59 ` Lukas Wunner
2017-11-17 6:07 ` Marcel Holtmann
2017-12-11 21:49 ` John Stultz
2018-01-02 20:39 ` John Stultz
2018-01-02 20:45 ` Marcel Holtmann [this message]
2018-02-01 5:50 ` Backport d73e17281665 to v4.15 stable Lukas Wunner
2018-02-01 6:42 ` Greg Kroah-Hartman
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=D250C682-CAD9-48FD-9B82-25E6934AAC0D@holtmann.org \
--to=marcel@holtmann.org \
--cc=johan@kernel.org \
--cc=john.stultz@linaro.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lukas@wunner.de \
--cc=rob.herring@linaro.org \
--cc=ronald@innovation.ch \
--cc=sumit.semwal@linaro.org \
/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
all inboxes | Powered by JetHome®