Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 11 Dec 2017 04:33:02 +0000
From:      bugzilla-noreply@freebsd.org
To:        freebsd-net@FreeBSD.org
Subject:   [Bug 224218] Kernel panic in SCTP/IpV6 server mode
Message-ID:  <bug-224218-2472-fONv3u8a9h@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-224218-2472@https.bugs.freebsd.org/bugzilla/>
References:  <bug-224218-2472@https.bugs.freebsd.org/bugzilla/>

next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D224218

--- Comment #18 from commit-hook@freebsd.org ---
A commit references this bug:

Author: cem
Date: Mon Dec 11 04:32:37 UTC 2017
New revision: 326758
URL: https://svnweb.freebsd.org/changeset/base/326758

Log:
  i386: Bump KSTACK_PAGES default to match amd64

  Logically, extend r286288 to cover all threads, by default.

  The world has largely moved on from i386.  Most FreeBSD users and develop=
ers
  test on amd64 hardware.  For better or worse, we have written a non-trivi=
al
  amount of kernel code that relies on stacks larger than 8 kB, and it "just
  works" on amd64, so there has been little incentive to shrink it.

  amd64 had its KSTACK_PAGES bumped to 4 back in Peter's initial AMD64 comm=
it,
  r114349, in 2003.  Since that time, i386 has limped along on a stack half
  the size.  We've even observed the stack overflows years ago, but neglect=
ed
  to fix the issue; see the 20121223 and 20150728 entries in UPDATING.

  If anyone is concerned with this change, I suggest they configure their
  AMD64 kernels with KSTACK_PAGES 2 and fix the fallout there first.  Eugene
  has identified a list of high stack usage functions in the first PR below.

  PR:           219476, 224218
  Reported by:  eugen@, Shreesh Holla <hshreesh AT yahoo.com>
  Relnotes:     maybe
  Sponsored by: Dell EMC Isilon

Changes:
  head/sys/i386/conf/NOTES
  head/sys/i386/include/param.h

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



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-224218-2472-fONv3u8a9h>