[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAKgHYH0nocPY5NBu-5Bmp8WMv2-mf-1Hj+_1=7ixzdGCm0XSqw@mail.gmail.com>
Date: Sat, 1 Jun 2019 00:12:19 +0800
From: Yang Xiao <92siuyang@...il.com>
To: Eric Dumazet <eric.dumazet@...il.com>
Cc: Herbert Xu <herbert@...dor.apana.org.au>,
David Miller <davem@...emloft.net>,
Alexey Kuznetsov <kuznet@....inr.ac.ru>,
Hideaki YOSHIFUJI <yoshfuji@...ux-ipv6.org>,
netdev <netdev@...r.kernel.org>,
LKML <linux-kernel@...r.kernel.org>,
Steffen Klassert <steffen.klassert@...unet.com>
Subject: Re: [PATCH] ipv6: Prevent overrun when parsing v6 header options
On Fri, May 31, 2019 at 11:57 PM Eric Dumazet <eric.dumazet@...il.com> wrote:
>
>
>
> On 5/31/19 7:54 AM, Herbert Xu wrote:
> > 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?
> >
> >
>
> I guess this means we had yet another random submission from Young Xiao :/
Excuse me, what do you mean about random submission from Young?
A month ago, I submitted the patch, and I was told that the format
should be correct.
Then, I resubmitted again.
>
> Thanks.
>
Powered by blists - more mailing lists