netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Lei Chen <chenl.lei@gmail.com>
Cc: davem@davemloft.net, netdev@vger.kernel.org
Subject: Re: ipv6 UNH-IOL Intact test cases failure on kernel 4.4.178
Date: Fri, 11 Oct 2019 11:11:48 +0200	[thread overview]
Message-ID: <20191011091148.GB1124173@kroah.com> (raw)
In-Reply-To: <CAB5AJuUgQaoWPqjw5dSkZR-dQOx+KKatNR0vz28Kqzq1QYJDzA@mail.gmail.com>

On Fri, Oct 11, 2019 at 05:00:32PM +0800, Lei Chen wrote:
> Hi David,
> Thanks in advance for reading my message.
> 
> We are running UNH-IOL test on our product which is based on kernel
> 4.4.178. The INTACT test cases failed on ipv6 verification. The same test
> cases just got pass on 4.4.153. (Sorry, the INTACT suite does not look to
> be open sourced. Hence I don't really know what the cases were indeed
> doing.)
> 
> Our verification engineer also mentioned: "The pattern of failures look
> eerily similar to a regression we recently discovered in SLES 12. I.e.,
> Failures related to “Parameter Problems”, as well as “Fragmentation“." We
> have tried to back out the defragment related patch:
> 
> commit 5f2d68b6b5a439c3223d8fa6ba20736f91fc58d8
> Author: Florian Westphal
> Date:   Wed Oct 10 12:30:10 2018 -0700
> 
>     ipv6: defrag: drop non-last frags smaller than min mtu
> 
>     commit 0ed4229b08c13c84a3c301a08defdc9e7f4467e6 upstream.
> 
>     don't bother with pathological cases, they only waste cycles.
>     IPv6 requires a minimum MTU of 1280 so we should never see fragments
>     smaller than this (except last frag).
> 
> 
> But it doesn't help. Could you please shed a light on which patch between
> 4.4.153 and 4.4.178 could have caused such a regression? Thanks again.

As you can run the test, why can't you run 'git bisect' to find the
offending patch?

thanks,

greg k-h

           reply	other threads:[~2019-10-11  9:11 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <CAB5AJuUgQaoWPqjw5dSkZR-dQOx+KKatNR0vz28Kqzq1QYJDzA@mail.gmail.com>]

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=20191011091148.GB1124173@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=chenl.lei@gmail.com \
    --cc=davem@davemloft.net \
    --cc=netdev@vger.kernel.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).