From: Florin Malita <fmalita@gmail.com>
To: Trent Piepho <xyzzy@speakeasy.org>
Cc: Mauro Carvalho Chehab <mchehab@infradead.org>,
v4l-dvb maintainer list <v4l-dvb-maintainer@linuxtv.org>,
linux-kernel@vger.kernel.org
Subject: Re: [v4l-dvb-maintainer] [PATCH] V4L/DVB: potential leak in dvb-bt8xx
Date: Sun, 15 Oct 2006 12:02:38 -0400 [thread overview]
Message-ID: <45325B9E.1030808@gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.58.0610141720560.13331@shell2.speakeasy.net>
Trent Piepho wrote:
> I believe that 'state' will be kfree'd by the dst_attach() function if there
> is a failure. Not what you would expect, to have it allocated in the bt8xx
> driver (why do is there??) and freed on error in a different function.
>
Hm, you're right - it is kfreed in dst_attach(). But we're still missing
the kmalloc result check...
Signed-off-by: Florin Malita <fmalita@gmail.com>
---
dvb-bt8xx.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/drivers/media/dvb/bt8xx/dvb-bt8xx.c b/drivers/media/dvb/bt8xx/dvb-bt8xx.c
index fb6c4cc..d22ba4e 100644
--- a/drivers/media/dvb/bt8xx/dvb-bt8xx.c
+++ b/drivers/media/dvb/bt8xx/dvb-bt8xx.c
@@ -665,6 +665,9 @@ static void frontend_init(struct dvb_bt8
case BTTV_BOARD_TWINHAN_DST:
/* DST is not a frontend driver !!! */
state = (struct dst_state *) kmalloc(sizeof (struct dst_state), GFP_KERNEL);
+ if (!state)
+ break;
+
/* Setup the Card */
state->config = &dst_config;
state->i2c = card->i2c_adapter;
next prev parent reply other threads:[~2006-10-15 16:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-14 17:39 [PATCH] V4L/DVB: potential leak in dvb-bt8xx Florin Malita
2006-10-15 0:33 ` [v4l-dvb-maintainer] " Trent Piepho
2006-10-15 16:02 ` Florin Malita [this message]
2006-10-15 16:35 ` Manu Abraham
2006-10-15 17:18 ` Mauro Carvalho Chehab
2006-10-15 17:39 ` Manu Abraham
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=45325B9E.1030808@gmail.com \
--to=fmalita@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab@infradead.org \
--cc=v4l-dvb-maintainer@linuxtv.org \
--cc=xyzzy@speakeasy.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