From: "David S. Miller" <davem@redhat.com>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: kuznet@ms2.inr.ac.ru, jmorris@redhat.com, netdev@oss.sgi.com
Subject: Re: [IPSEC] Move hardware headers for decaped packets
Date: Sun, 7 Dec 2003 16:55:16 -0800 [thread overview]
Message-ID: <20031207165516.1edfde10.davem@redhat.com> (raw)
In-Reply-To: <20031207095527.GA2767@gondor.apana.org.au>
On Sun, 7 Dec 2003 20:55:27 +1100
Herbert Xu <herbert@gondor.apana.org.au> wrote:
> On Sun, Dec 07, 2003 at 01:47:14AM -0800, David S. Miller wrote:
> >
> > Ok, I'll review this again. Did you audit the tree to make sure you
> > updated mac_len everywhere that 'skb->mac.*' is modified?
>
> To be honest, no. The reason is that my use of mac_len starts from
> netif_receive_skb and ends just before the reentrance into netif_rx
> in xfrm[46]_input.
>
> At the start of that path, mac_len is initialised from a value that
> we know to be correct. I have also verified that within the path,
> nobody expands/contracts the MAC header.
Ok, we can make it a receive only thing at first, I guess.
But I think this will definitely need to be deferred to
2.6.1 at least, along with that XFRM device unload fix you
sent me the other week.
Linus really only wants the obvious one-liners at this point
for 2.6.0
Thanks.
next prev parent reply other threads:[~2003-12-08 0:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20030925121131.GA17968@gondor.apana.org.au>
[not found] ` <200309251228.QAA11650@yakov.inr.ac.ru>
[not found] ` <20030925124102.GA18188@gondor.apana.org.au>
2003-12-07 9:02 ` [IPSEC] Move hardware headers for decaped packets Herbert Xu
2003-12-07 9:47 ` David S. Miller
2003-12-07 9:55 ` Herbert Xu
2003-12-08 0:55 ` David S. Miller [this message]
2004-02-14 3:55 ` Herbert Xu
2004-02-14 7:10 ` David S. Miller
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=20031207165516.1edfde10.davem@redhat.com \
--to=davem@redhat.com \
--cc=herbert@gondor.apana.org.au \
--cc=jmorris@redhat.com \
--cc=kuznet@ms2.inr.ac.ru \
--cc=netdev@oss.sgi.com \
/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;
as well as URLs for NNTP newsgroup(s).