From: David Miller <davem@davemloft.net>
To: nhorman@tuxdriver.com
Cc: netdev@vger.kernel.org, vladislav.yasevich@hp.com,
sri@us.ibm.com, linux-sctp@vger.kernel.org
Subject: Re: [PATCH] sctp: fixed missing fixup of sctp_local_addr_free
Date: Fri, 27 May 2011 13:40:04 -0400 (EDT) [thread overview]
Message-ID: <20110527.134004.1654129007987862831.davem@davemloft.net> (raw)
In-Reply-To: <1306517820-4793-1-git-send-email-nhorman@tuxdriver.com>
From: Neil Horman <nhorman@tuxdriver.com>
Date: Fri, 27 May 2011 13:37:00 -0400
> commit 1231f0baa547a541a7481119323b7f964dda4788 Converted sctp to use
> kfree_rcu from sctp_local_addr_free but missed this one call point. Fix it up
> accordingly.
>
> Signed-off-by: Neil Horman <nhorman@tuxdriver.com>
This has been fixed for several days now.
If you're using the net-next-2.6 tree, don't, when it's not active
it's just a dummy tree for Stephen Rothwell to pull into -next
and it will be rebuilt as soon as the merge window is over.
next prev parent reply other threads:[~2011-05-27 17:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-27 17:37 [PATCH] sctp: fixed missing fixup of sctp_local_addr_free Neil Horman
2011-05-27 17:40 ` David Miller [this message]
2011-05-27 17:42 ` 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=20110527.134004.1654129007987862831.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=linux-sctp@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=nhorman@tuxdriver.com \
--cc=sri@us.ibm.com \
--cc=vladislav.yasevich@hp.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).