From: Vladislav Yasevich <vladislav.yasevich@hp.com>
To: Benjamin Poirier <bpoirier@suse.de>
Cc: "David S. Miller" <davem@davemloft.net>,
Christine Caulfield <ccaulfie@redhat.com>,
David Teigland <teigland@redhat.com>,
Sridhar Samudrala <sri@us.ibm.com>,
cluster-devel@redhat.com, linux-sctp@vger.kernel.org,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 2/2] dlm: Do not allocate a fd for peeloff
Date: Thu, 08 Mar 2012 15:08:17 -0500 [thread overview]
Message-ID: <4F5911B1.6050600@hp.com> (raw)
In-Reply-To: <1331222159-28980-2-git-send-email-bpoirier@suse.de>
On 03/08/2012 10:55 AM, Benjamin Poirier wrote:
> avoids allocating a fd that a) propagates to every kernel thread and
> usermodehelper b) is not properly released.
>
> References: http://article.gmane.org/gmane.linux.network.drbd/22529
> Signed-off-by: Benjamin Poirier <bpoirier@suse.de>
Looks much better.
-vlad
> ---
> fs/dlm/lowcomms.c | 22 ++++++++--------------
> 1 files changed, 8 insertions(+), 14 deletions(-)
>
> diff --git a/fs/dlm/lowcomms.c b/fs/dlm/lowcomms.c
> index 0b3109e..ca0c59a 100644
> --- a/fs/dlm/lowcomms.c
> +++ b/fs/dlm/lowcomms.c
> @@ -52,6 +52,7 @@
> #include <linux/mutex.h>
> #include <linux/sctp.h>
> #include <linux/slab.h>
> +#include <net/sctp/sctp.h>
> #include <net/sctp/user.h>
> #include <net/ipv6.h>
>
> @@ -474,9 +475,6 @@ static void process_sctp_notification(struct connection *con,
> int prim_len, ret;
> int addr_len;
> struct connection *new_con;
> - sctp_peeloff_arg_t parg;
> - int parglen = sizeof(parg);
> - int err;
>
> /*
> * We get this before any data for an association.
> @@ -525,23 +523,19 @@ static void process_sctp_notification(struct connection *con,
> return;
>
> /* Peel off a new sock */
> - parg.associd = sn->sn_assoc_change.sac_assoc_id;
> - ret = kernel_getsockopt(con->sock, IPPROTO_SCTP,
> - SCTP_SOCKOPT_PEELOFF,
> - (void *)&parg, &parglen);
> + sctp_lock_sock(con->sock->sk);
> + ret = sctp_do_peeloff(con->sock->sk,
> + sn->sn_assoc_change.sac_assoc_id,
> + &new_con->sock);
> + sctp_release_sock(con->sock->sk);
> if (ret < 0) {
> log_print("Can't peel off a socket for "
> "connection %d to node %d: err=%d",
> - parg.associd, nodeid, ret);
> - return;
> - }
> - new_con->sock = sockfd_lookup(parg.sd, &err);
> - if (!new_con->sock) {
> - log_print("sockfd_lookup error %d", err);
> + (int)sn->sn_assoc_change.sac_assoc_id,
> + nodeid, ret);
> return;
> }
> add_sock(new_con->sock, new_con);
> - sockfd_put(new_con->sock);
>
> log_print("connecting to %d sctp association %d",
> nodeid, (int)sn->sn_assoc_change.sac_assoc_id);
next prev parent reply other threads:[~2012-03-08 20:08 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-07 15:41 [PATCH] dlm, sctp: Do not allocate a fd for peeloff Benjamin Poirier
2012-03-07 16:29 ` Vladislav Yasevich
2012-03-08 8:24 ` David Miller
2012-03-08 15:55 ` [PATCH v2 1/2] sctp: Export sctp_do_peeloff Benjamin Poirier
2012-03-08 15:55 ` [PATCH v2 2/2] dlm: Do not allocate a fd for peeloff Benjamin Poirier
2012-03-08 20:08 ` Vladislav Yasevich [this message]
2012-03-08 21:52 ` David Miller
2012-03-08 20:07 ` [PATCH v2 1/2] sctp: Export sctp_do_peeloff Vladislav Yasevich
2012-03-08 21:52 ` David Miller
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=4F5911B1.6050600@hp.com \
--to=vladislav.yasevich@hp.com \
--cc=bpoirier@suse.de \
--cc=ccaulfie@redhat.com \
--cc=cluster-devel@redhat.com \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sctp@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=sri@us.ibm.com \
--cc=teigland@redhat.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