From: Daniel Borkmann <dborkman@redhat.com>
To: vyasevich@gmail.com
Cc: davem@davemloft.net, netdev@vger.kernel.org, linux-sctp@vger.kernel.org
Subject: [PATCH net 0/2] fixes for net/sctp/auth.c
Date: Thu, 7 Feb 2013 11:55:35 +0100 [thread overview]
Message-ID: <cover.1360231701.git.dborkman@redhat.com> (raw)
This set fixes two issues in the net/sctp/auth.c implementation.
Daniel Borkmann (2):
net: sctp: sctp_auth_make_key_vector: fix undefined ref-count behaviour
net: sctp: sctp_auth_key_put: use kzfree instead of kfree
net/sctp/auth.c | 6 ++----
1 file changed, 2 insertions(+), 4 deletions(-)
--
1.7.11.7
next reply other threads:[~2013-02-07 10:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-07 10:55 Daniel Borkmann [this message]
2013-02-07 10:55 ` [PATCH net 1/2] net: sctp: sctp_auth_make_key_vector: fix undefined ref-count behaviour Daniel Borkmann
2013-02-07 15:04 ` Vlad Yasevich
2013-02-07 15:24 ` Daniel Borkmann
2013-02-07 15:45 ` Vlad Yasevich
2013-02-07 10:55 ` [PATCH net 2/2] net: sctp: sctp_auth_key_put: use kzfree instead of kfree Daniel Borkmann
2013-02-07 15:05 ` Vlad Yasevich
2013-02-08 4:45 ` David Miller
2013-02-07 14:52 ` [PATCH net 0/2] fixes for net/sctp/auth.c Neil Horman
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.1360231701.git.dborkman@redhat.com \
--to=dborkman@redhat.com \
--cc=davem@davemloft.net \
--cc=linux-sctp@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=vyasevich@gmail.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;
as well as URLs for NNTP newsgroup(s).