svn commit: r252533 - stable/8/sys/kern

Lawrence Stewart lstewart at
Wed Jul 3 03:40:06 UTC 2013

Author: lstewart
Date: Wed Jul  3 03:40:06 2013
New Revision: 252533

  When a previous call to sbsndptr() leaves sb->sb_sndptroff at the start of an
  mbuf that was fully consumed by the previous call, the mbuf ptr returned by the
  current call ends up being the previous mbuf in the sb chain to the one that
  contains the data we want.
  This does not cause any observable issues because the mbuf copy routines happily
  walk the mbuf chain to get to the data at the moff offset, which in this case
  means they effectively skip over the mbuf returned by sbsndptr().
  We can't adjust sb->sb_sndptr during the previous call for this case because the
  next mbuf in the chain may not exist yet. We therefore need to detect the
  condition and make the adjustment during the current call.
  Fix by detecting the special case of moff being at the start of the next mbuf in
  the chain and adjust the required accounting variables accordingly.
  Reviewed by:	andre

Directory Properties:
  stable/8/sys/   (props changed)
  stable/8/sys/kern/   (props changed)

Modified: stable/8/sys/kern/uipc_sockbuf.c
--- stable/8/sys/kern/uipc_sockbuf.c	Wed Jul  3 03:36:36 2013	(r252532)
+++ stable/8/sys/kern/uipc_sockbuf.c	Wed Jul  3 03:40:06 2013	(r252533)
@@ -939,6 +939,13 @@ sbsndptr(struct sockbuf *sb, u_int off, 
 	/* Return closest mbuf in chain for current offset. */
 	*moff = off - sb->sb_sndptroff;
 	m = ret = sb->sb_sndptr ? sb->sb_sndptr : sb->sb_mb;
+	if (*moff == m->m_len) {
+		*moff = 0;
+		sb->sb_sndptroff += m->m_len;
+		m = ret = m->m_next;
+		KASSERT(ret->m_len > 0,
+		    ("mbuf %p in sockbuf %p chain has no valid data", ret, sb));
+	}
 	/* Advance by len to be as close as possible for the next transmit. */
 	for (off = off - sb->sb_sndptroff + len - 1;

More information about the svn-src-stable-8 mailing list