From: David Miller <davem@davemloft.net>
To: mk@lab.zgora.pl
Cc: yevgenyp@mellanox.co.il, rolandd@cisco.com,
alekseys@voltaire.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mlx4: fix kfree on error path in new_steering_entry()
Date: Sun, 03 Apr 2011 22:04:10 -0700 (PDT) [thread overview]
Message-ID: <20110403.220410.123991133.davem@davemloft.net> (raw)
In-Reply-To: <1301865983-6584-1-git-send-email-mk@lab.zgora.pl>
From: Mariusz Kozlowski <mk@lab.zgora.pl>
Date: Sun, 3 Apr 2011 23:26:23 +0200
> On error path kfree() should get pointer to memory allocated by
> kmalloc() not the address of variable holding it (which is on stack).
>
> Signed-off-by: Mariusz Kozlowski <mk@lab.zgora.pl>
Applied, thanks.
prev parent reply other threads:[~2011-04-04 5:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-03 21:26 [PATCH] mlx4: fix kfree on error path in new_steering_entry() Mariusz Kozlowski
2011-04-04 5:04 ` David Miller [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=20110403.220410.123991133.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=alekseys@voltaire.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mk@lab.zgora.pl \
--cc=netdev@vger.kernel.org \
--cc=rolandd@cisco.com \
--cc=yevgenyp@mellanox.co.il \
/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).