public inbox for [email protected]
 help / color / mirror / Atom feed
From: Ammar Faizi <[email protected]>
To: Yujie Liu <[email protected]>
Cc: kernel test robot <[email protected]>,
	Linux Kernel Mailing List <[email protected]>,
	netdev Mailing List <[email protected]>,
	[email protected], [email protected],
	Greg Kroah-Hartman <[email protected]>,
	GNU/Weeb Mailing List <[email protected]>,
	Stephen Suryaputra <[email protected]>,
	Paolo Abeni <[email protected]>,
	"David S. Miller" <[email protected]>,
	Jakub Kicinski <[email protected]>,
	David Ahern <[email protected]>
Subject: Re: [LKP] Re: [vrf] 2ef23e860e: kernel-selftests.net.fcnal-test.sh.fail
Date: Mon, 22 Aug 2022 16:53:10 +0700	[thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>


+ Adding stable and netdev people to the participants.

Full story here:

    https://lore.gnuweeb.org/gwml/[email protected]

If you fix the issue, kindly add following tag
Reported-by: kernel test robot <[email protected]>

On 8/22/22 3:17 PM, Yujie Liu wrote:
> On 8/22/2022 16:09, Yujie Liu wrote:
>> On 8/22/2022 15:15, Ammar Faizi wrote:
>>> On 8/22/22 2:03 PM, kernel test robot wrote:
>>>> =========================================================================================
>>>> tbox_group/testcase/rootfs/kconfig/compiler/group/test/atomic_test/ucode:
>>>>    lkp-skl-d01/kernel-selftests/debian-12-x86_64-20220629.cgz/x86_64-rhel-8.3-kselftests/gcc-11/net/fcnal-test.sh/use_cases/0xf0
>>>>
>>>> commit:
>>>>    cae90bd22cffb ("net: bridge: vlan: fix error return code in __vlan_add()")
>>>>    2ef23e860e765 ("vrf: packets with lladdr src needs dst at input with orig_iif when needs strict")
>>>>
>>>> cae90bd22cffb1e1 2ef23e860e765eb1dd287492206
>>>> ---------------- ---------------------------
>>>>         fail:runs  %reproduction    fail:runs
>>>>             |             |             |
>>>>             :6          100%           6:6     kernel-selftests.net.fcnal-test.sh.fail
>>>>
>>>>
>>>> FYI, we noticed that this is a backport commit of upstream 205704c618af0ab2366015d2281a3b0814d918a0
>>>> (merged by v5.10), so we also test this case on mainline, and this issue doesn't exist.
>>>
>>> Can you test the latest linux-5.4.y branch and see whether the issue
>>> exists on there?
>>>
>>> You can pull from:
>>>
>>>    https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git linux-5.4.y
>>>
>>> The HEAD commit is:
>>>
>>>     de0cd3ea700d1e8ed76705d02e33b524cbb84cf3 ("Linux 5.4.210")
>>>
>>
>> The issue doesn't exist on latest head of linux-5.4.y branch
> 
> Sorry, I made a mistake, the issue still exists on linux-5.4-y head.

Thanks for testing, unfortunately, I am not the committer nor author of
the offending commit. This should have been reported to the netdev list.

I have added them to the CC list. Can you resend the reproducer and
detailed test output with them CC'ed?

>>
>> =========================================================================================
>> atomic_test/compiler/group/kconfig/rootfs/tbox_group/test/testcase/ucode:
>>    use_cases/gcc-11/net/x86_64-rhel-8.3-kselftests/debian-12-x86_64-20220629.cgz/lkp-skl-d01/fcnal-test.sh/kernel-selftests/0xf0
>>
>> commit:
>>    2ef23e860e765 ("vrf: packets with lladdr src needs dst at input with orig_iif when needs strict")
>>    cae90bd22cffb ("net: bridge: vlan: fix error return code in __vlan_add()")
>>    de0cd3ea700d1 ("Linux 5.4.210")
>>
>> 2ef23e860e765eb1 cae90bd22cffb1e19a83a794ad5                    v5.4.210
>> ---------------- --------------------------- ---------------------------
>>         fail:runs  %reproduction    fail:runs  %reproduction    fail:runs
>>             |             |             |             |             |
>>             :6          100%           6:6            0%            :2     kernel-selftests.net.fcnal-test.sh.pass
> 
> for this stat, only cae90bd22cffb can pass the test, while 2ef23e860e765 and v5.4.210
> all failed.

FYI, I found a backported commit with a Fixes tag contains
205704c618af (commit upstream):

    https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=e245ea3b524069e1a264bb50190dceedd59c36fb

But the 5.4.y HEAD that already includes that commit still fails
based on your report. Let's wait for netdev people' response on
this. As the mainline doesn't have this issue, maybe something
need to get backported?

Summary:

These commits only live in 5.4.x stable branch (backport from upstream):

(notice the "Upstream commit")

# Known good commit:

     commit cae90bd22cffb1e19a83a794ad5f57dafb3e76ad
     Author:     Zhang Changzhong <[email protected]>
     AuthorDate: Fri Dec 4 16:48:56 2020 +0800
     Commit:     Greg Kroah-Hartman <[email protected]>
     CommitDate: Mon Dec 21 13:27:03 2020 +0100

     net: bridge: vlan: fix error return code in __vlan_add()
     
     [ Upstream commit ee4f52a8de2c6f78b01f10b4c330867d88c1653a ]
     ...

# The next commit after that one fails (first bad commit):

     commit 2ef23e860e765eb1dd287492206d833f04eae9df
     Author:     Stephen Suryaputra <[email protected]>
     AuthorDate: Thu Dec 3 22:06:04 2020 -0500
     Commit:     Greg Kroah-Hartman <[email protected]>
     CommitDate: Mon Dec 21 13:27:03 2020 +0100

     vrf: packets with lladdr src needs dst at input with orig_iif when needs strict
     
     [ Upstream commit 205704c618af0ab2366015d2281a3b0814d918a0 ]
     ...

# The HEAD of linux-5.4.x still fails:

     commit de0cd3ea700d1e8ed76705d02e33b524cbb84cf3
     Author:     Greg Kroah-Hartman <[email protected]>
     AuthorDate: Thu Aug 11 12:57:53 2022 +0200
     Commit:     Greg Kroah-Hartman <[email protected]>
     CommitDate: Thu Aug 11 12:57:53 2022 +0200

     Linux 5.4.210
     ...

netdev folks, any comment on this?

-- 
Ammar Faizi

  reply	other threads:[~2022-08-22  9:53 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <[email protected]>
2022-08-22  7:03 ` [vrf] 2ef23e860e: kernel-selftests.net.fcnal-test.sh.fail kernel test robot
2022-08-22  7:15   ` Ammar Faizi
2022-08-22  8:09     ` [LKP] " Yujie Liu
2022-08-22  8:17       ` Yujie Liu
2022-08-22  9:53         ` Ammar Faizi [this message]
2022-08-22  9:57       ` Ammar Faizi

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 \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    /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