From: bugzilla-daemon@bugzilla.kernel.org
To: linux-bluetooth@vger.kernel.org
Subject: [Bug 204275] bluetoothd consumes 100% cpu on keyboard disconnect
Date: Thu, 01 Aug 2019 18:03:14 +0000 [thread overview]
Message-ID: <bug-204275-62941-JLpj1vDQDi@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-204275-62941@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=204275
--- Comment #12 from Steven Newbury (steve@snewbury.org.uk) ---
(In reply to Luiz Von Dentz from comment #11)
> (In reply to Steven Newbury from comment #10)
> > (In reply to Luiz Von Dentz from comment #9)
> > > Im not sure we even need the watch in the first place, the kernel should
> > > block any in/out until the connection is encrypted (BT_SK_SUSPEND) so it
> > > might be possible to get rid of sec_watch altogether.
> >
> > Going through the history it originally worked that way, I'm not sure why
> it
> > was changed..?
>
> Well lets try to remove it then and see if that fix the problem.
That works. I'll attach a patch on here.
--
You are receiving this mail because:
You are the assignee for the bug.
next prev parent reply other threads:[~2019-08-01 18:03 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-22 13:36 [Bug 204275] New: bluetoothd consumes 100% cpu on keyboard disconnect bugzilla-daemon
2019-07-22 14:22 ` [Bug 204275] " bugzilla-daemon
2019-07-22 19:36 ` bugzilla-daemon
2019-07-22 20:54 ` bugzilla-daemon
2019-07-22 21:00 ` bugzilla-daemon
2019-07-22 23:56 ` bugzilla-daemon
2019-07-24 11:14 ` bugzilla-daemon
2019-07-24 15:31 ` bugzilla-daemon
2019-07-25 9:04 ` bugzilla-daemon
2019-07-25 13:13 ` bugzilla-daemon
2019-07-29 13:52 ` bugzilla-daemon
2019-07-29 13:56 ` bugzilla-daemon
2019-08-01 18:03 ` bugzilla-daemon [this message]
2019-08-10 7:40 ` 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-204275-62941-JLpj1vDQDi@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=linux-bluetooth@vger.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox