We've found a recurring problem where some userland process would be
stuck spinning at 100% cpu around sbcut_internal(). Inside sbflush_internal(), sb_ccc reached to about 4GB and before passing it to sbcut_internal(), we type-cast it from uint to int making it -ve. The root cause of sockbuf growing this large is unknown. Correct fix is also not clear but based on mailing list discussions, adding KASSERTs to panic instead of looping endlessly. Reviewed by: glebius Sponsored by: Limelight Networks
This commit is contained in:
parent
22986c6740
commit
b5b023b91e
@ -1043,6 +1043,11 @@ sbcut_internal(struct sockbuf *sb, int len)
|
||||
{
|
||||
struct mbuf *m, *next, *mfree;
|
||||
|
||||
KASSERT(len > 0, ("%s: len is %d but it is supposed to be +ve",
|
||||
__func__, len));
|
||||
KASSERT(len <= sb->sb_ccc, ("%s: len: %d is > ccc: %u",
|
||||
__func__, len, sb->sb_ccc));
|
||||
|
||||
next = (m = sb->sb_mb) ? m->m_nextpkt : 0;
|
||||
mfree = NULL;
|
||||
|
||||
|
Loading…
Reference in New Issue
Block a user