linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jiri Kosina <jkosina@suse.cz>
To: Mariusz Kozlowski <m.kozlowski@tuxland.pl>
Cc: linux-input@atrey.karlin.mff.cuni.cz, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] hid: hidraw_connect memleak fix
Date: Thu, 27 Sep 2007 11:40:19 +0200 (CEST)	[thread overview]
Message-ID: <Pine.LNX.4.64.0709271139380.7567@jikos.suse.cz> (raw)
In-Reply-To: <200709270933.13497.m.kozlowski@tuxland.pl>

On Thu, 27 Sep 2007, Mariusz Kozlowski wrote:

> It looks like hidraw_connect() is leaking memory in case of failure. 
> Also it should return -ENOMEM when kzalloc fails.

Mariusz,

good catch, will apply to me tree.

Thanks,

-- 
Jiri Kosina
SUSE Labs

      reply	other threads:[~2007-09-27  9:40 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-27  7:33 [PATCH] hid: hidraw_connect memleak fix Mariusz Kozlowski
2007-09-27  9:40 ` Jiri Kosina [this message]

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=Pine.LNX.4.64.0709271139380.7567@jikos.suse.cz \
    --to=jkosina@suse.cz \
    --cc=linux-input@atrey.karlin.mff.cuni.cz \
    --cc=linux-kernel@vger.kernel.org \
    --cc=m.kozlowski@tuxland.pl \
    /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).