All of lore.kernel.org
 help / color / mirror / Atom feed
From: Yujie Liu <yujie.liu@intel.com>
To: lkp@lists.01.org
Subject: Re: [vrf] 2ef23e860e: kernel-selftests.net.fcnal-test.sh.fail
Date: Mon, 22 Aug 2022 16:09:47 +0800	[thread overview]
Message-ID: <70e690da-df88-5d78-d25c-b01ce1f3f886@intel.com> (raw)
In-Reply-To: <c9451365-e582-3bb0-0180-462d0a4069ed@gnuweeb.org>

[-- Attachment #1: Type: text/plain, Size: 2692 bytes --]

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

=========================================================================================
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


Do you suggest that if we find any issue on the branches like "for-5.*-lts", we could also
run a test on corresponding stable branch? We will consider this step in the future.

--
Thanks,
Yujie

  reply	other threads:[~2022-08-22  8:09 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20220822065003.GA33158@inn2.lkp.intel.com>
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     ` Yujie Liu [this message]
2022-08-22  8:17       ` Yujie Liu
2022-08-22  9:53         ` Ammar Faizi
2022-08-22  9:53           ` [LKP] " Ammar Faizi
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 \
    --in-reply-to=70e690da-df88-5d78-d25c-b01ce1f3f886@intel.com \
    --to=yujie.liu@intel.com \
    --cc=lkp@lists.01.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.