From: "Denis V. Lunev" <den@openvz.org>
To: Vlad Yasevich <vladislav.yasevich@hp.com>
Cc: Netdev List <netdev@vger.kernel.org>,
lksctp-developers@lists.sourceforge.net
Subject: Re: SCTP control socket question
Date: Thu, 27 Mar 2008 16:43:25 +0300 [thread overview]
Message-ID: <1206625405.2109.7.camel@iris.sw.ru> (raw)
In-Reply-To: <47EB9E0B.2030400@hp.com>
[-- Attachment #1: Type: text/plain, Size: 1131 bytes --]
On Thu, 2008-03-27 at 09:15 -0400, Vlad Yasevich wrote:
> Denis V. Lunev wrote:
> > On Thu, 2008-03-27 at 08:48 -0400, Vlad Yasevich wrote:
> >> Denis V. Lunev wrote:
> >>> Hello, Vlad!
> >>>
> >>> I have read SCTP sources and found that SCTP control socket
> >>> (sctp_ctl_socket) remains hashed unlike similar staff in UDP/TCP etc.
> >>>
> >>> Am I wrong, that it should not be hashed or not?
> >> Why do you believe that the socket is hashed? That socket is only
> >> allocated and referenced. It's should not be in any hash tables
> >> since we hold a global reference on it.
> >
> > sctp_ctl_sock_init
> > __sock_create
> > inet(6)_create
> > sk->sk_prot->hash(sk);
> >
> > For this purpose sk->sk_prot->unhash is explicitly called for ICMP/TCP
> > etc cases.
> >
> > Regards,
> > Den
> >
>
> Ahhh... ;-)
>
> struct proto sctp_prot = {
> ...
> .hash = sctp_hash,
> ...
> }
>
> static void sctp_hash(struct sock *sk)
> {
> /* STUB */
> }
>
>
> SCTP currently does't do any hashing on the sockets. It hashes SCTP structures
> that live under the socket.
will you mind against this?
[-- Attachment #2: 1.txt --]
[-- Type: text/x-patch, Size: 655 bytes --]
diff --git a/net/sctp/protocol.c b/net/sctp/protocol.c
index 5aea911..8d1b2bc 100644
--- a/net/sctp/protocol.c
+++ b/net/sctp/protocol.c
@@ -680,16 +680,13 @@ static int sctp_ctl_sock_init(void)
else
family = PF_INET;
- err = sock_create_kern(family, SOCK_SEQPACKET, IPPROTO_SCTP,
- &sctp_ctl_socket);
+ err = inet_csk_ctl_sock_create(&sctp_ctl_socket,
+ family, SOCK_SEQPACKET, IPPROTO_SCTP);
if (err < 0) {
printk(KERN_ERR
"SCTP: Failed to create the SCTP control socket.\n");
return err;
}
- sctp_ctl_socket->sk->sk_allocation = GFP_ATOMIC;
- inet_sk(sctp_ctl_socket->sk)->uc_ttl = -1;
-
return 0;
}
next prev parent reply other threads:[~2008-03-27 13:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-27 12:03 SCTP control socket question Denis V. Lunev
2008-03-27 12:48 ` Vlad Yasevich
2008-03-27 13:09 ` Denis V. Lunev
2008-03-27 13:15 ` Vlad Yasevich
2008-03-27 13:43 ` Denis V. Lunev [this message]
2008-03-27 14:01 ` Vlad Yasevich
2008-03-27 14:15 ` Pavel Emelyanov
2008-03-28 3:30 ` 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=1206625405.2109.7.camel@iris.sw.ru \
--to=den@openvz.org \
--cc=lksctp-developers@lists.sourceforge.net \
--cc=netdev@vger.kernel.org \
--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).