From: Paul Bolle <pebolle@tiscali.nl>
To: Dmitry Vyukov <dvyukov@google.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Jiri Slaby <jslaby@suse.com>, LKML <linux-kernel@vger.kernel.org>,
Peter Hurley <peter@hurleysoftware.com>,
One Thousand Gnomes <gnomes@lxorguk.ukuu.org.uk>,
J Freyensee <james_p_freyensee@linux.intel.com>,
Alexander Potapenko <glider@google.com>,
Kostya Serebryany <kcc@google.com>,
Sasha Levin <sasha.levin@oracle.com>,
syzkaller <syzkaller@googlegroups.com>
Subject: Re: tty: memory leak in tty_register_driver
Date: Sat, 27 Feb 2016 22:20:19 +0100 [thread overview]
Message-ID: <1456608019.2651.20.camel@tiscali.nl> (raw)
In-Reply-To: <CACT4Y+a-MEdAj4Dr7tqD6EEuD4KsrhOqyk+-m+Uq9+aao9rmfg@mail.gmail.com>
(I was AFK this week. So my reply is a bit late.)
On ma, 2016-02-22 at 10:53 +0100, Dmitry Vyukov wrote:
> On Thu, Feb 18, 2016 at 11:45 PM, Paul Bolle <pebolle@tiscali.nl>
> > Fascinating issue. Makes zero sense to me. sysfs_init? Anyhow, since
> > the
> > people actually familiar with this code have stayed silent until
> > now, I
> > have some obvious questions:
> > - does this only trigger with line discipline N_GSM0710?
> > - is this a new issue or do older trees also trigger it (in other
> > words: have you tried bisecting this)?
>
> I can say that it does not happen with 1, 2, 3, 4 and 7.
Side note: 4 (N_STRIP) is unused. As are 8 (N_MASC), 10
(N_PROFIBUS_FDL), and 12 (N_SMSBLOCK). So you could as well skip these
for syzkaller's tests.
> So there are
> chances that it is N_GSM0710-specific. 5 and 6 trigger lots of leaks,
> but they are different. I did not try to bisect it.
I've looked into this the previous week (because your reproducer
resembled the code that triggered the recent N_GIGASET_M101 leak). I was
unable to reproduce the issue myself. And, as far as I can remember now,
N_GSM0710's open() operation is rather non-trivial. So I soon gave up on
hoping to find a leak or any other obvious issue by, well, reviewing the
code involved. Sorry about that.
Thanks,
Paul Bolle
next prev parent reply other threads:[~2016-02-27 21:20 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-15 10:42 tty: memory leak in tty_register_driver Dmitry Vyukov
2016-02-18 22:45 ` Paul Bolle
2016-02-22 9:53 ` Dmitry Vyukov
2016-02-27 21:20 ` Paul Bolle [this message]
2016-02-28 16:42 ` Dmitry Vyukov
2016-02-28 23:47 ` Catalin Marinas
2016-02-29 10:22 ` Dmitry Vyukov
2016-02-29 10:24 ` Dmitry Vyukov
2016-02-29 11:34 ` Catalin Marinas
2016-03-01 15:27 ` Dmitry Vyukov
2016-03-01 15:55 ` Catalin Marinas
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=1456608019.2651.20.camel@tiscali.nl \
--to=pebolle@tiscali.nl \
--cc=dvyukov@google.com \
--cc=glider@google.com \
--cc=gnomes@lxorguk.ukuu.org.uk \
--cc=gregkh@linuxfoundation.org \
--cc=james_p_freyensee@linux.intel.com \
--cc=jslaby@suse.com \
--cc=kcc@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=peter@hurleysoftware.com \
--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