Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S266753AbUFYPLU (ORCPT ); Fri, 25 Jun 2004 11:11:20 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S266754AbUFYPLU (ORCPT ); Fri, 25 Jun 2004 11:11:20 -0400 Received: from mail.njit.edu ([128.235.251.173]:5030 "EHLO mail-gw5.njit.edu") by vger.kernel.org with ESMTP id S266753AbUFYPLT (ORCPT ); Fri, 25 Jun 2004 11:11:19 -0400 Date: Fri, 25 Jun 2004 11:11:17 -0400 (EDT) From: rahul b jain cs student To: linux-kernel@vger.kernel.org Subject: sk_buff understanding Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 866 Lines: 24 Hi, I just want to know if my understanding of how the sk_buff structure works is correct. When data arrives at the TCP layer it is pointed to by the data pointer and the TCP header goes in the skb->data-skb->head area. When this packet is passed to the IP layer, skb->tail-skb->data section will now contain the TCP header + TCP data and now the IP header will be put in the new skb->data-skb->head area. Please let me know if this understanding is correct. I also wanted to know does psk_may_pull() only check for correct header length or does it (thought some func calls) strip off the IP header ? Thanks, Rahul. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/