From: Paul Bolle <pebolle@tiscali.nl>
To: Dmitry Vyukov <dvyukov@google.com>
Cc: Karsten Keil <isdn@linux-pingi.de>,
"David S. Miller" <davem@davemloft.net>,
gigaset307x-common@lists.sourceforge.net, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, syzkaller@googlegroups.com,
Kostya Serebryany <kcc@google.com>,
Alexander Potapenko <glider@google.com>,
Sasha Levin <sasha.levin@oracle.com>
Subject: Re: gigaset: memory leak in gigaset_initcshw
Date: Thu, 04 Feb 2016 16:06:15 +0100 [thread overview]
Message-ID: <1454598375.14366.72.camel@tiscali.nl> (raw)
In-Reply-To: <CACT4Y+b2z0NHVPQbyYP1CA_80hXxhk+VOG6dzduMEsi+27Pi7Q@mail.gmail.com>
On do, 2016-02-04 at 15:54 +0100, Dmitry Vyukov wrote:
> One TIOCSETD is enough to trigger the leak.
> I've tested with different line disciplines and only N_GIGASET_M101
> triggers the leak.
So things appear to be just on my plate now. I'll see what I can come up
with. Feel free to prod me if I stay silent for too long.
Thanks for narrowing things down!
Paul Bolle
next prev parent reply other threads:[~2016-02-04 15:06 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-03 15:31 gigaset: memory leak in gigaset_initcshw Dmitry Vyukov
2016-02-03 16:16 ` Paul Bolle
2016-02-03 19:11 ` Paul Bolle
2016-02-04 10:40 ` Dmitry Vyukov
2016-02-04 13:09 ` Paul Bolle
2016-02-04 13:15 ` Dmitry Vyukov
2016-02-04 13:46 ` Paul Bolle
2016-02-04 14:54 ` Dmitry Vyukov
2016-02-04 15:06 ` Paul Bolle [this message]
2016-02-05 13:28 ` Dmitry Vyukov
2016-02-05 16:06 ` Paul Bolle
2016-02-05 18:36 ` Paul Bolle
2016-02-05 21:25 ` Dmitry Vyukov
2016-02-11 22:34 ` Paul Bolle
2016-02-11 22:54 ` Paul Bolle
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=1454598375.14366.72.camel@tiscali.nl \
--to=pebolle@tiscali.nl \
--cc=davem@davemloft.net \
--cc=dvyukov@google.com \
--cc=gigaset307x-common@lists.sourceforge.net \
--cc=glider@google.com \
--cc=isdn@linux-pingi.de \
--cc=kcc@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=sasha.levin@oracle.com \
--cc=syzkaller@googlegroups.com \
/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;
as well as URLs for NNTP newsgroup(s).