Netdev List
 help / color / mirror / Atom feed
From: Cong Wang <xiyou.wangcong@gmail.com>
To: "J.J. Mars" <mars14850@gmail.com>
Cc: netdev@vger.kernel.org
Subject: Re: Confused about ip_summed member in sk_buff
Date: Sat, 22 Oct 2022 12:51:26 -0700	[thread overview]
Message-ID: <Y1RJvsTpbC6K5I9Y@pop-os.localdomain> (raw)
In-Reply-To: <CAHUXu_WyYzuTOiz75VfhST6nL3gm0B49dDMjgkzEQ0m_h4Rh1g@mail.gmail.com>

On Fri, Oct 21, 2022 at 02:29:26PM +0800, J.J. Mars wrote:
> Hi everyone, I'm new here and I hope this mail won't disturb you :)
> 
> Recently I was working with something about ip_summed, and I'm really
> confused about the question what does ip_summed exactly mean?
> This member is defined with comment Driver fed us an IP checksum'. So
> I guess it's about IP/L3 checksum status.
> But the possible value of ip_summed like CHECKSUM_UNNECESSARY is about L4.
> 
> What confused me a lot is ip_summed seems to tell us the checksum of
> IP/L3 layer is available from its name.
> But it seems to tell us the checksum status of L4 layer from its value.
> 
> Besides, in ip_rcv() it seems the ip_summed is not used before
> calculating the checksum of IP header.
> 
> So does ip_summed indicate the status of L3 checksum status or L4
> checksum status?
> If L4, why is it named like that?

The name itself is indeed confusing, however, there are some good
explanations in the code, at the beginning of include/linux/skbuff.h. I
think that could help you to clear your confusions here.

Thanks.

  reply	other threads:[~2022-10-22 19:51 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-21  6:29 Confused about ip_summed member in sk_buff J.J. Mars
2022-10-22 19:51 ` Cong Wang [this message]
2022-11-08 12:32   ` J.J. Mars
2022-11-08 17:12     ` Edward Cree
2022-11-09  7:22       ` J.J. Mars

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=Y1RJvsTpbC6K5I9Y@pop-os.localdomain \
    --to=xiyou.wangcong@gmail.com \
    --cc=mars14850@gmail.com \
    --cc=netdev@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox