All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: "Aviraj Cj (acj)" <acj@cisco.com>
Cc: "davem@davemloft.net" <davem@davemloft.net>,
	"kuznet@ms2.inr.ac.ru" <kuznet@ms2.inr.ac.ru>,
	"yoshfuji@linux-ipv6.org" <yoshfuji@linux-ipv6.org>,
	"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"xe-linux-external(mailer list)" <xe-linux-external@cisco.com>,
	Hangbin Liu <liuhangbin@gmail.com>,
	Jakub Kicinski <kuba@kernel.org>
Subject: Re: [Internal review][PATCH stable v5.4 1/2] ICMPv6: Add ICMPv6 Parameter Problem, code 3 definition
Date: Sat, 30 Jan 2021 12:51:14 +0100	[thread overview]
Message-ID: <YBVIMvTN8ZFC+54U@kroah.com> (raw)
In-Reply-To: <D6F3B42A-95E1-4B8D-8556-E29F195C69D3@cisco.com>

On Sat, Jan 30, 2021 at 11:31:11AM +0000, Aviraj Cj (acj) wrote:
> 
> 
> On 30/01/21, 2:06 PM, "Greg KH" <gregkh@linuxfoundation.org> wrote:
> 
> On Sat, Jan 30, 2021 at 12:57:40AM +0530, Aviraj CJ wrote:
> > From: Hangbin Liu <liuhangbin@gmail.com>
> > 
> > commit b59e286be280fa3c2e94a0716ddcee6ba02bc8ba upstream.
> > 
> > Based on RFC7112, Section 6:
> > 
> >    IANA has added the following "Type 4 - Parameter Problem" message to
> >    the "Internet Control Message Protocol version 6 (ICMPv6) Parameters"
> >    registry:
> > 
> >       CODE     NAME/DESCRIPTION
> >        3       IPv6 First Fragment has incomplete IPv6 Header Chain
> > 
> > Signed-off-by: Hangbin Liu <liuhangbin@gmail.com>
> > Signed-off-by: Jakub Kicinski <kuba@kernel.org>
> > Signed-off-by: Aviraj CJ <acj@cisco.com>
> > ---
> >  include/uapi/linux/icmpv6.h | 1 +
> >  1 file changed, 1 insertion(+)
> > 
> > diff --git a/include/uapi/linux/icmpv6.h b/include/uapi/linux/icmpv6.h
> > index 2622b5a3e616..9a31ea2ad1cf 100644
> > --- a/include/uapi/linux/icmpv6.h
> > +++ b/include/uapi/linux/icmpv6.h
> > @@ -137,6 +137,7 @@ struct icmp6hdr {
> >  #define ICMPV6_HDR_FIELD		0
> >  #define ICMPV6_UNK_NEXTHDR		1
> >  #define ICMPV6_UNK_OPTION		2
> > +#define ICMPV6_HDR_INCOMP		3
> >  
> >  /*
> >   *	constants for (set|get)sockopt
> > -- 
> > 2.26.2.Cisco
> > 
> 
> What do you mean by "internal review" and what am I supposed to do with
> this patch?  Same for the 2/2 patch in this series...
> <ACJ> Sorry " internal review" added by mistake, this is the correct patch for v5.4 branch, pls let me if u want me to send it by correcting...

Please fix and resend.

thanks,

greg k-h

      reply	other threads:[~2021-01-30 11:52 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-29 19:27 [Internal review][PATCH stable v5.4 1/2] ICMPv6: Add ICMPv6 Parameter Problem, code 3 definition Aviraj CJ
2021-01-29 19:27 ` [Internal review][PATCH stable v5.4 2/2] IPv6: reply ICMP error if the first fragment don't include all headers Aviraj CJ
2021-01-30  8:36 ` [Internal review][PATCH stable v5.4 1/2] ICMPv6: Add ICMPv6 Parameter Problem, code 3 definition Greg KH
2021-01-30 11:31   ` Aviraj Cj (acj)
2021-01-30 11:51     ` Greg KH [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=YBVIMvTN8ZFC+54U@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=acj@cisco.com \
    --cc=davem@davemloft.net \
    --cc=kuba@kernel.org \
    --cc=kuznet@ms2.inr.ac.ru \
    --cc=linux-kernel@vger.kernel.org \
    --cc=liuhangbin@gmail.com \
    --cc=netdev@vger.kernel.org \
    --cc=xe-linux-external@cisco.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.