netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jakub Kicinski <kuba@kernel.org>
To: wangyufen <wangyufen@huawei.com>
Cc: Paolo Abeni <pabeni@redhat.com>, <davem@davemloft.net>,
	<yoshfuji@linux-ipv6.org>, <dsahern@kernel.org>,
	<edumazet@google.com>, <ast@kernel.org>, <daniel@iogearbox.net>,
	<andrii@kernel.org>, <kafai@fb.com>, <songliubraving@fb.com>,
	<yhs@fb.com>, <john.fastabend@gmail.com>, <kpsingh@kernel.org>,
	<netdev@vger.kernel.org>, <bpf@vger.kernel.org>
Subject: Re: [PATCH net-next v4] ipv6: Fix signed integer overflow in __ip6_append_data
Date: Mon, 6 Jun 2022 07:24:13 -0700	[thread overview]
Message-ID: <20220606072413.284b10fa@kernel.org> (raw)
In-Reply-To: <9b09cb01-07ee-6b33-5351-74a40edbda3d@huawei.com>

On Mon, 6 Jun 2022 10:03:27 +0800 wangyufen wrote:
> > LGTM. Imho this can even land in a separated patch (whatever is easier)  
> 
> Thanks for all the feedback.
> So, Jakub will send a new patch to fix the l2tp_ip6_sendmsg issue?

That was just a suggestion, if possible I'd prefer if you double
checked the analysis, tested that or similar code, wrote a commit
message etc. and sent it.

  reply	other threads:[~2022-06-06 14:25 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-01  8:48 [PATCH net-next v4] ipv6: Fix signed integer overflow in __ip6_append_data Wang Yufen
2022-06-02 10:38 ` Paolo Abeni
2022-06-02 16:02   ` Jakub Kicinski
2022-06-03  8:58     ` Paolo Abeni
2022-06-06  2:03       ` wangyufen
2022-06-06 14:24         ` Jakub Kicinski [this message]
2022-06-07  1:16           ` wangyufen

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=20220606072413.284b10fa@kernel.org \
    --to=kuba@kernel.org \
    --cc=andrii@kernel.org \
    --cc=ast@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=davem@davemloft.net \
    --cc=dsahern@kernel.org \
    --cc=edumazet@google.com \
    --cc=john.fastabend@gmail.com \
    --cc=kafai@fb.com \
    --cc=kpsingh@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=songliubraving@fb.com \
    --cc=wangyufen@huawei.com \
    --cc=yhs@fb.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 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).