From: Herbert Xu <herbert@gondor.apana.org.au>
To: Eric Dumazet <eric.dumazet@gmail.com>
Cc: Young Xiao <92siuyang@gmail.com>,
davem@davemloft.net, kuznet@ms2.inr.ac.ru,
yoshfuji@linux-ipv6.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org,
Steffen Klassert <steffen.klassert@secunet.com>
Subject: Re: [PATCH] ipv6: Prevent overrun when parsing v6 header options
Date: Fri, 31 May 2019 22:54:28 +0800 [thread overview]
Message-ID: <20190531145428.ngwrgbnk2a7us5cy@gondor.apana.org.au> (raw)
In-Reply-To: <727c4b18-0d7b-b3c6-e0bb-41b3fe5902d3@gmail.com>
On Fri, May 31, 2019 at 07:50:06AM -0700, Eric Dumazet wrote:
>
> What do you mean by should ?
>
> Are they currently already linearized before the function is called,
> or is it missing and a bug needs to be fixed ?
AFAICS this is the code-path for locally generated outbound packets.
Under what circumstances can the IPv6 header be not in the head?
Cheers,
--
Email: Herbert Xu <herbert@gondor.apana.org.au>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt
next prev parent reply other threads:[~2019-05-31 14:54 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-30 15:28 [PATCH] ipv6: Prevent overrun when parsing v6 header options Young Xiao
2019-05-30 17:17 ` Eric Dumazet
2019-05-31 3:04 ` Yang Xiao
2019-05-31 17:35 ` Eric Dumazet
2019-06-04 6:59 ` Yang Xiao
2019-06-04 13:29 ` Eric Dumazet
2019-05-31 6:29 ` Herbert Xu
2019-05-31 14:50 ` Eric Dumazet
2019-05-31 14:54 ` Herbert Xu [this message]
2019-05-31 15:57 ` Eric Dumazet
2019-05-31 16:12 ` Yang Xiao
-- strict thread matches above, loose matches on Subject: below --
2020-12-27 14:11 Defang Bo
2020-12-28 23:03 ` David Miller
2019-04-12 3:34 Young Xiao
2019-04-17 3:45 ` David 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=20190531145428.ngwrgbnk2a7us5cy@gondor.apana.org.au \
--to=herbert@gondor.apana.org.au \
--cc=92siuyang@gmail.com \
--cc=davem@davemloft.net \
--cc=eric.dumazet@gmail.com \
--cc=kuznet@ms2.inr.ac.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=steffen.klassert@secunet.com \
--cc=yoshfuji@linux-ipv6.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.