All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: linux-bluetooth@vger.kernel.org
Subject: [Bug 120691] UART HCI memory leak
Date: Wed, 22 Jun 2016 10:00:48 +0000	[thread overview]
Message-ID: <bug-120691-62941-knfMUCR4hh@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-120691-62941@https.bugzilla.kernel.org/>

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

Loic Poulain <loic.poulain@intel.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |loic.poulain@intel.com

--- Comment #1 from Loic Poulain <loic.poulain@intel.com> ---
Seems that this memory leak is due to the hci_ll (TI) proto.
Don't think this comes from the generic hci-uart/ldisc part.
To be sure, are you able to reproduce this issue with any other proto (hci_h4,
hci_bcm, hci_intel..)?

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

  reply	other threads:[~2016-06-22 10:00 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-20 13:46 [Bug 120691] New: UART HCI memory leak bugzilla-daemon
2016-06-22 10:00 ` bugzilla-daemon [this message]
2016-06-22 16:38 ` [Bug 120691] " bugzilla-daemon
2016-07-10  3:11 ` bugzilla-daemon
2016-07-10  3:12 ` bugzilla-daemon
2016-07-19 20:57 ` bugzilla-daemon
2016-07-20  8:06 ` bugzilla-daemon
2016-08-01 15:55 ` bugzilla-daemon
2016-08-01 17:35 ` bugzilla-daemon
2016-08-04 13:57 ` bugzilla-daemon
2016-08-04 14:52 ` bugzilla-daemon
2016-08-04 14:53 ` bugzilla-daemon
2016-08-07  0:58 ` bugzilla-daemon
2016-08-07  0:58 ` bugzilla-daemon
2016-08-17 21:30 ` bugzilla-daemon
2016-08-22 12:39 ` bugzilla-daemon
2016-08-22 14:18 ` bugzilla-daemon
2016-08-23  9:35 ` 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-120691-62941-knfMUCR4hh@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 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.