From: Paul Bolle <pebolle@tiscali.nl>
To: Dmitry Vyukov <dvyukov@google.com>
Cc: linux-kernel@vger.kernel.org
Subject: ser_gigaset: fix memory leak
Date: Mon, 15 Feb 2016 22:30:38 +0100 [thread overview]
Message-ID: <cover.1455570595.git.pebolle@tiscali.nl> (raw)
Hi Dmitry,
I've cobbled together a two part series to fix the leak syzkaller uncovered in
ser_gigaset. I'd really appreciate it if you'd unleash syzkaller on this small
series one more time. Just to be sure that this also fixes the leak on your box
and that it doesn't introduce neww horrors.
Thanks,
Paul Bolle
next reply other threads:[~2016-02-15 21:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-15 21:30 Paul Bolle [this message]
2016-02-15 21:30 ` [PATCH 1/2] ser_gigaset: bail out if gigaset_initcs() fails Paul Bolle
2016-02-15 21:30 ` [PATCH 2/2] ser_gigaset: use container_of() instead of detour Paul Bolle
2016-02-16 9:30 ` ser_gigaset: fix memory leak Dmitry Vyukov
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=cover.1455570595.git.pebolle@tiscali.nl \
--to=pebolle@tiscali.nl \
--cc=dvyukov@google.com \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®