From: Vlad Yasevich <vyasevich@gmail.com>
To: David Laight <David.Laight@ACULAB.COM>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: Re: SCTP seems to lose its socket state.
Date: Fri, 13 Jun 2014 14:48:52 -0400 [thread overview]
Message-ID: <539B4794.4010700@gmail.com> (raw)
In-Reply-To: <063D6719AE5E284EB5DD2968C1650D6D1725C172@AcuExch.aculab.com>
On 06/13/2014 06:53 AM, David Laight wrote:
> From: Vlad Yasevich
>> Can you try the attached patch and let me know if it solves this problem
>> for you.
>
> I've finally got around to trying it, and then fighting grub2 to get a
> serial console (after finding a COM header and cables).
> (Why can't I configure two entries for the same kernel, with and without
> the serial console...)
>
> As soon as the COOKIE_ECHO is received I get:
>
> [ 65.756811] kernel BUG at /home/dsl/linux/net/sctp/command.c:50!
>
> It has hit the limit for SCTP_MAX_NUM_COMMANDS.
> I increased it to 20 and traced the entries when the exceeded
> the old limit (of 14).
>
> [ 102.250614] sctp_add_cmd_sf: seq 0, 36( (null))
> [ 102.266575] sctp_add_cmd_sf: seq 1, 15(0000000000000008)
> [ 102.282500] sctp_add_cmd_sf: seq 2, 2b( (null))
> [ 102.298426] sctp_add_cmd_sf: seq 3, 15(0000000000000005)
> [ 102.314352] sctp_add_cmd_sf: seq 4, 40( (null))
> [ 102.330279] sctp_add_cmd_sf: seq 5, 2a(ffff88022f3b4000)
> [ 102.346206] sctp_add_cmd_sf: seq 6, b(ffff8800bc4df128)
> [ 102.361874] sctp_add_cmd_sf: seq 7, c(ffff8800bc4de800)
> [ 102.377540] sctp_add_cmd_sf: seq 8, 2c(ffff8800bc4df000)
> [ 102.393470] sctp_add_cmd_sf: seq 9, 12(0000000000000003)
> [ 102.409397] sctp_add_cmd_sf: seq 10, 14(0000000000000006)
> [ 102.425583] sctp_add_cmd_sf: seq 11, 3(0000000000000005)
> [ 102.441510] sctp_add_cmd_sf: seq 12, 20( (null))
> [ 102.457699] sctp_add_cmd_sf: seq 13, c(ffff8800bc4df000)
> [ 102.521433] sctp_add_cmd_sf: seq 14, 41(ffff88022f3b4000)
> [ 102.538658] sctp_add_cmd_sf: seq 15, 2( (null))
> [ 102.555626] sctp_add_cmd_sf: seq 16, 41(ffff88023525e000)
>
> I've not tried to see what these are.
Yeah. We do end up queuing a bit more commands. Need to see if
all them are necessary..
>
> tcpdump then shows it sending a shutdown bundled with the cookie ack
> and the disconnect completes.
Thanks. I'll take a look at all the commands we queue up and make
an official submission.
-vlad
>
> David
>
>
>
>
next prev parent reply other threads:[~2014-06-13 18:48 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-27 15:10 SCTP seems to lose its socket state David Laight
2014-05-28 20:18 ` Vlad Yasevich
2014-05-29 9:03 ` David Laight
2014-05-29 9:12 ` Daniel Borkmann
2014-06-06 15:14 ` David Laight
2014-06-06 16:24 ` David Laight
2014-06-06 16:50 ` Vlad Yasevich
2014-06-09 12:49 ` David Laight
2014-06-09 18:37 ` Vlad Yasevich
2014-06-10 8:29 ` David Laight
2014-06-09 22:44 ` Vlad Yasevich
2014-06-13 10:53 ` David Laight
2014-06-13 18:48 ` Vlad Yasevich [this message]
2014-06-16 8:40 ` David Laight
2014-06-16 13:47 ` Vlad Yasevich
2014-06-16 14:46 ` David Laight
2014-06-17 11:28 ` 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=539B4794.4010700@gmail.com \
--to=vyasevich@gmail.com \
--cc=David.Laight@ACULAB.COM \
--cc=netdev@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.