From: Takashi Iwai <tiwai@suse.de>
To: Marcel Holtmann <marcel@holtmann.org>
Cc: Jiri Slaby <jslaby@suse.cz>,
Johan Hedberg <johan.hedberg@gmail.com>,
linux-kernel@vger.kernel.org,
"Gustavo F. Padovan" <gustavo@padovan.org>,
linux-bluetooth@vger.kernel.org,
"stable 3 . 13+" <stable@vger.kernel.org>
Subject: Re: [PATCH] Bluetooth: purge unhandled skbs
Date: Thu, 14 Apr 2016 16:36:33 +0200 [thread overview]
Message-ID: <s5htwj4i7f2.wl-tiwai@suse.de> (raw)
In-Reply-To: <90C446FD-8335-4AD7-B4A2-4DEAE610D33A@holtmann.org>
On Fri, 08 Apr 2016 19:23:45 +0200,
Marcel Holtmann wrote:
>
> Hi Jiri,
>
> > The write handler allocates skbs and queues them into data->readq.
> > Read side should read them, if there is any. If there is none, skbs
> > should be dropped by hdev->flush. But this happens only if the device
> > is HCI_UP, i.e. hdev->power_on work was triggered already. When it was
> > not, skbs stay allocated in the queue when /dev/vhci is closed. So
> > purge the queue in ->release.
> >
> > Program to reproduce:
> > #include <err.h>
> > #include <fcntl.h>
> > #include <stdio.h>
> > #include <unistd.h>
> >
> > #include <sys/stat.h>
> > #include <sys/types.h>
> > #include <sys/uio.h>
> >
> > int main()
> > {
> > char buf[] = { 0xff, 0 };
> > struct iovec iov = {
> > .iov_base = buf,
> > .iov_len = sizeof(buf),
> > };
> > int fd;
> >
> > while (1) {
> > fd = open("/dev/vhci", O_RDWR);
> > if (fd < 0)
> > err(1, "open");
> >
> > usleep(50);
> >
> > if (writev(fd, &iov, 1) < 0)
> > err(1, "writev");
> >
> > usleep(50);
> >
> > close(fd);
> > }
> >
> > return 0;
> > }
> >
> > Result:
> > kmemleak: 4609 new suspected memory leaks
> > unreferenced object 0xffff88059f4d5440 (size 232):
> > comm "vhci", pid 1084, jiffies 4294912542 (age 37569.296s)
> > hex dump (first 32 bytes):
> > 20 f0 23 87 05 88 ff ff 20 f0 23 87 05 88 ff ff .#..... .#.....
> > 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
> > backtrace:
> > ...
> > [<ffffffff81ece010>] __alloc_skb+0x0/0x5a0
> > [<ffffffffa021886c>] vhci_create_device+0x5c/0x580 [hci_vhci]
> > [<ffffffffa0219436>] vhci_write+0x306/0x4c8 [hci_vhci]
> >
> > Fixes: 23424c0d31 (Bluetooth: Add support creating virtual AMP controllers)
> > Signed-off-by: Jiri Slaby <jslaby@suse.cz>
> > Cc: Marcel Holtmann <marcel@holtmann.org>
> > Cc: Gustavo Padovan <gustavo@padovan.org>
> > Cc: Johan Hedberg <johan.hedberg@gmail.com>
> > Cc: <linux-bluetooth@vger.kernel.org>
> > Cc: stable 3.13+ <stable@vger.kernel.org>
> > ---
> > drivers/bluetooth/hci_vhci.c | 1 +
> > 1 file changed, 1 insertion(+)
>
> patch has been applied to bluetooth-next tree.
Could you check another race of vhci mentioned in the thread?
https://www.mail-archive.com/linux-kernel@vger.kernel.org/msg1106134.html
If the suggested fix is OK, I'll submit a properly cooked patch.
thanks,
Takashi
next prev parent reply other threads:[~2016-04-14 14:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-19 10:49 [PATCH] Bluetooth: purge unhandled skbs Jiri Slaby
2016-04-08 17:23 ` Marcel Holtmann
2016-04-14 14:36 ` Takashi Iwai [this message]
2016-04-14 14:41 ` Marcel Holtmann
2016-04-14 14:45 ` Takashi Iwai
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=s5htwj4i7f2.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=gustavo@padovan.org \
--cc=johan.hedberg@gmail.com \
--cc=jslaby@suse.cz \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marcel@holtmann.org \
--cc=stable@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