From: Willem de Bruijn <willemdebruijn.kernel@gmail.com>
To: Shreyansh Chouhan <chouhan.shreyansh630@gmail.com>
Cc: Jakub Kicinski <kuba@kernel.org>,
Willem de Bruijn <willemdebruijn.kernel@gmail.com>,
davem@davemloft.net, yoshfuji@linux-ipv6.org, dsahern@kernel.org,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
syzbot+ff8e1b9f2f36481e2efc@syzkaller.appspotmail.com
Subject: Re: [PATCH] ip_gre/ip6_gre: add check for invalid csum_start
Date: Sat, 21 Aug 2021 09:44:19 -0400 [thread overview]
Message-ID: <CA+FuTSceSFcRc-OxP=_1zAmBGckQL5gDsAScqoiGy2c4PLckWQ@mail.gmail.com> (raw)
In-Reply-To: <YSCos0Sdw7RYsNQu@fedora>
On Sat, Aug 21, 2021 at 3:18 AM Shreyansh Chouhan
<chouhan.shreyansh630@gmail.com> wrote:
>
> Hi,
>
> Thank you Jakub and Willem for your reviews. I have separated the
> changes into two differnet patches. Sorry for the delay.
Thanks Shreyansh
> Where can I read about patch targets? I have seen patches with differnet
> targets but I do not know what they mean/how they work. I was not able
> to find the documentation for these.
Targeting these bug fixed to net was the right destination.
Documentation/networking/netdev-FAQ.rst has more context on the net vs
net-next distinction.
prev parent reply other threads:[~2021-08-21 13:45 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-19 14:34 [PATCH] ip_gre/ip6_gre: add check for invalid csum_start Shreyansh Chouhan
2021-08-19 16:56 ` Willem de Bruijn
2021-08-19 17:04 ` Jakub Kicinski
2021-08-21 7:14 ` [PATCH 1/2 net] ip_gre: add validation for csum_start Shreyansh Chouhan
2021-08-21 13:41 ` Willem de Bruijn
2021-09-01 11:53 ` Ido Schimmel
2021-09-01 13:46 ` Willem de Bruijn
2021-09-01 15:53 ` Ido Schimmel
2021-09-01 21:39 ` Willem de Bruijn
2021-08-22 20:30 ` patchwork-bot+netdevbpf
2021-08-21 7:14 ` [PATCH 2/2 net] ip6_gre: " Shreyansh Chouhan
2021-08-21 13:42 ` Willem de Bruijn
2021-08-21 7:18 ` [PATCH] ip_gre/ip6_gre: add check for invalid csum_start Shreyansh Chouhan
2021-08-21 13:44 ` Willem de Bruijn [this message]
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='CA+FuTSceSFcRc-OxP=_1zAmBGckQL5gDsAScqoiGy2c4PLckWQ@mail.gmail.com' \
--to=willemdebruijn.kernel@gmail.com \
--cc=chouhan.shreyansh630@gmail.com \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=syzbot+ff8e1b9f2f36481e2efc@syzkaller.appspotmail.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).