All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Hemminger <stephen@networkplumber.org>
To: linux-sctp@vger.kernel.org
Subject: Fw: [Bug 205753] New: Incorrect SCTP DATA dispatching
Date: Tue, 03 Dec 2019 16:22:33 +0000	[thread overview]
Message-ID: <20191203082233.5c1525be@hermes.lan> (raw)

All networking bugzilla bugs go to me. This one is new and  SCTP related

Begin forwarded message:

Date: Tue, 03 Dec 2019 13:32:39 +0000
From: bugzilla-daemon@bugzilla.kernel.org
To: stephen@networkplumber.org
Subject: [Bug 205753] New: Incorrect SCTP DATA dispatching


https://bugzilla.kernel.org/show_bug.cgi?id 5753

            Bug ID: 205753
           Summary: Incorrect SCTP DATA dispatching
           Product: Networking
           Version: 2.5
    Kernel Version: 4.19.67
          Hardware: Intel
                OS: Linux
              Tree: Mainline
            Status: NEW
          Severity: normal
          Priority: P1
         Component: Other
          Assignee: stephen@networkplumber.org
          Reporter: evgenij.fokin@gmail.com
        Regression: No

I think that root cause in skipped messages.

For example, frame 56 in your debian10_sctp_test_to_sctp_test.pcapng shows that
the data message with sctp.data_tsn = 919935042 was received on server
interface but it was acked in frame 78 only.

It happens periodically with high-load traffic. The server can capture DATA on
network interface but SCTP level does not receive it.

-- 
You are receiving this mail because:
You are the assignee for the bug.

             reply	other threads:[~2019-12-03 16:22 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-03 16:22 Stephen Hemminger [this message]
2019-12-03 18:54 ` Fw: [Bug 205753] New: Incorrect SCTP DATA dispatching Vasil Velichkov
2019-12-05  9:57 ` Евгений Фокин

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=20191203082233.5c1525be@hermes.lan \
    --to=stephen@networkplumber.org \
    --cc=linux-sctp@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.