[Bug 213232] [tcp] [panic] tcp_output() Panic String: tcp_output: len > IP_MAXPACKET on -head and stable/11

2021-03-02 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213232

Michael Tuexen  changed:

   What|Removed |Added

 Resolution|--- |Overcome By Events
 CC||tue...@freebsd.org
 Status|New |Closed

--- Comment #9 from Michael Tuexen  ---
I think a lot has changed in the area. Please re-open, if the problem still
exists.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-net@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"


[Bug 213232] [tcp] [panic] tcp_output() Panic String: tcp_output: len > IP_MAXPACKET on -head and stable/11

2016-10-13 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213232

Hiren Panchasara  changed:

   What|Removed |Added

Summary|[tcp] [panic] tcp_output()  |[tcp] [panic] tcp_output()
   |Panic String: tcp_output:   |Panic String: tcp_output:
   |len > IP_MAXPACKET (at  |len > IP_MAXPACKET on -head
   |r306658)|and stable/11

--- Comment #4 from Hiren Panchasara  ---
Just hit this on uptodate stable/11 system.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-net@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"


[Bug 213232] [tcp] [panic] tcp_output() Panic String: tcp_output: len > IP_MAXPACKET on -head and stable/11

2016-10-13 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213232

--- Comment #5 from Hiren Panchasara  ---

r306769 | jtl | 2016-10-06 09:28:34 -0700 (Thu, 06 Oct 2016) | 8 lines

Remove "long" variables from the TCP stack (not including the modular
congestion control framework).

may help. Updating my box and trying again if I get the same crash.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-net@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"


[Bug 213232] [tcp] [panic] tcp_output() Panic String: tcp_output: len > IP_MAXPACKET on -head and stable/11

2016-10-15 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213232

Hiren Panchasara  changed:

   What|Removed |Added

 CC||gleb...@freebsd.org

--- Comment #6 from Hiren Panchasara  ---
Now with r306769, len is int32_t so it can actually have -ve value, I am seeing
panic at


/*
 * This KASSERT is here to catch edge cases at a well defined place.
 * Before, those had triggered (random) panic conditions further down.
 */
KASSERT(len >= 0, ("[%s:%d]: len < 0", __func__, __LINE__));

Now, putting a bit of debugs above that I figured that at following path in
'else' case the len becomes -ve

if (tso) {

   

} else {
len = tp->t_maxseg - optlen - ipoptlen;
sendalot = 1;
}

I found that tp-t_maxseg = 2, optlen = 12, ipoptlen = 0 resulting in len = -10.

Clearly, t_maxseg which is supposed to be representing MSS at '2' looks wrong.

I wonder if the changes in
https://svnweb.freebsd.org/base?view=revision&revision=293284 somewhere caused
this.

Still investigating.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-net@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"


[Bug 213232] [tcp] [panic] tcp_output() Panic String: tcp_output: len > IP_MAXPACKET on -head and stable/11

2016-10-17 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213232

--- Comment #7 from commit-h...@freebsd.org ---
A commit references this bug:

Author: hiren
Date: Tue Oct 18 02:40:25 UTC 2016
New revision: 307545
URL: https://svnweb.freebsd.org/changeset/base/307545

Log:
  Make sure tcp_mss() has the same check as tcp_mss_update() to have t_maxseg
set
  to at least 64.

  This is still just a coverup to avoid kernel panic and not an actual fix.

  PR:   213232
  Reviewed by:  glebius
  MFC after:1 week
  Sponsored by: Limelight Networks
  Differential Revision:https://reviews.freebsd.org/D8272

Changes:
  head/sys/netinet/tcp_input.c

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-net@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"


[Bug 213232] [tcp] [panic] tcp_output() Panic String: tcp_output: len > IP_MAXPACKET on -head and stable/11

2016-11-01 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213232

--- Comment #8 from commit-h...@freebsd.org ---
A commit references this bug:

Author: hiren
Date: Tue Nov  1 22:40:25 UTC 2016
New revision: 308184
URL: https://svnweb.freebsd.org/changeset/base/308184

Log:
  MFC r307545
  Make sure tcp_mss() has the same check as tcp_mss_update() to have t_maxseg
set
  to at least 64.

  This is still just a coverup to avoid kernel panic and not an actual fix.

  PR:   213232
  Sponsored by: Limelight Networks

Changes:
_U  stable/11/
  stable/11/sys/netinet/tcp_input.c

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-net@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"