ip_reass: explain why we should not always update the q pointer

Closes #10

Signed-off-by: Samuel Thibault <samuel.thibault@ens-lyon.org>

1 files changed, 4 insertions, 5 deletions

diff --git a/src/ip_input.c b/src/ip_input.c
index 8c75d91..7364ce0 100644
--- a/src/ip_input.c
+++ b/src/ip_input.c
@@ -344,11 +344,10 @@ insert:
     q = fp->frag_link.next;
 
     /*
-     * If the fragments concatenated to an mbuf that's
-     * bigger than the total size of the fragment, then and
-     * m_ext buffer was alloced. But fp->ipq_next points to
-     * the old buffer (in the mbuf), so we must point ip
-     * into the new buffer.
+     * If the fragments concatenated to an mbuf that's bigger than the total
+     * size of the fragment and the mbuf was not already using an m_ext buffer,
+     * then an m_ext buffer was alloced. But fp->ipq_next points to the old
+     * buffer (in the mbuf), so we must point ip into the new buffer.
      */
     if (!was_ext && m->m_flags & M_EXT) {
         int delta = (char *)q - m->m_dat;