All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: linux-bluetooth@kernel.org
Subject: [Bug 198043] Bluetooth mgmt api set powered causes kernel race condition
Date: Wed, 10 Jan 2018 17:21:54 +0000	[thread overview]
Message-ID: <bug-198043-62941-eJIDL6LyTI@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-198043-62941@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=198043

luc (l.perneel@luperco.com) changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |l.perneel@luperco.com

--- Comment #1 from luc (l.perneel@luperco.com) ---
Had a similar issue on a 4.9.60 build where the hci_sock_release and
hci_send_to_channel on two CPUs generate a soft lockup between them.
The hci_sock_release with the _raw_write_lock (like here) and the 
hci_sock_release with the _raw_read_lock (different than this case, but highly
probable caused by the same issue).
So it seems that the _raw_write_lock and the _raw_read_lock have a deadly race
between them.


Will dig deeper into the issue and post an update later.

-- 
You are receiving this mail because:
You are the assignee for the bug.

  reply	other threads:[~2018-01-10 17:21 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-30 13:22 [Bug 198043] New: Bluetooth mgmt api set powered causes kernel race condition bugzilla-daemon
2018-01-10 17:21 ` bugzilla-daemon [this message]
2018-01-17 13:11 ` [Bug 198043] " bugzilla-daemon
2018-01-17 13:27 ` bugzilla-daemon

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=bug-198043-62941-eJIDL6LyTI@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@bugzilla.kernel.org \
    --cc=linux-bluetooth@kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.