From: Jakub Kicinski <kuba@kernel.org>
To: David Wilder <wilder@us.ibm.com>
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"jv@jvosburgh.net" <jv@jvosburgh.net>,
"pradeeps@linux.vnet.ibm.com" <pradeeps@linux.vnet.ibm.com>,
Pradeep Satyanarayana <pradeep@us.ibm.com>,
"i.maximets@ovn.org" <i.maximets@ovn.org>,
Adrian Moreno Zapata <amorenoz@redhat.com>,
Hangbin Liu <haliu@redhat.com>,
"stephen@networkplumber.org" <stephen@networkplumber.org>,
"horms@kernel.org" <horms@kernel.org>
Subject: Re: [PATCH net-next v6 7/7] bonding: Selftest and documentation for the arp_ip_target parameter.
Date: Mon, 21 Jul 2025 13:08:00 -0700 [thread overview]
Message-ID: <20250721130800.021609ee@kernel.org> (raw)
In-Reply-To: <MW3PR15MB3913774256A62C63A607245EFA5DA@MW3PR15MB3913.namprd15.prod.outlook.com>
On Mon, 21 Jul 2025 19:23:19 +0000 David Wilder wrote:
> >This test seems to reliably trigger a crash in our CI. Not sure if
> >something is different in our build... or pebkac?
> >
> >[ 17.977269] RIP: 0010:bond_fill_info+0x21b/0x890
> >[ 17.977325] Code: b3 38 0b 00 00 31 d2 41 8b 06 85 c0 0f 84 2a 06 00 00 89 44 24 0c 41 f6 46 10 02 74 5c 49 8b 4e 08 31 c0 ba 04 00 00 00 eb 16 <8b> 34 01 83 c2 04 89 74 04 10 48 83 c0 04 66 83 7c 01 fc ff 74 3e
>
> Hi Jakub
>
> What version of iproute2 is running in your CI?
> Has my iproute2 change been applied? it's ok if not.
>
> Send:
> ip -V (please)
iproute2 is built from source a month ago, with some pending patches,
but not yours. Presumably building from source without your patches
should give similar effect (IIRC the patches I applied related
to MC routing)
> Can I access the logs from the CI run?
Yes
https://netdev.bots.linux.dev/contest.html?pw-n=0&branch=net-next-2025-07-19--00-00
> Is there a way I can debug in you CI environment?
Not at this point, unfortunately.
> Can I submit debug patches?
https://github.com/linux-netdev/nipa/wiki/How-to-run-netdev-selftests-CI-style
next prev parent reply other threads:[~2025-07-21 20:08 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-18 21:23 [PATCH net-next v6 0/7] bonding: Extend arp_ip_target format to allow for a list of vlan tags David Wilder
2025-07-18 21:23 ` [PATCH net-next v6 1/7] bonding: Adding struct bond_arp_target David Wilder
2025-07-18 21:23 ` [PATCH net-next v6 2/7] bonding: Adding extra_len field to struct bond_opt_value David Wilder
2025-07-18 21:23 ` [PATCH net-next v6 3/7] bonding: arp_ip_target helpers David Wilder
2025-07-18 21:23 ` [PATCH net-next v6 4/7] bonding: Processing extended arp_ip_target from user space David Wilder
2025-07-18 21:23 ` [PATCH net-next v6 5/7] bonding: Update to bond_arp_send_all() to use supplied vlan tags David Wilder
2025-07-18 21:23 ` [PATCH net-next v6 6/7] bonding: Update for extended arp_ip_target format David Wilder
2025-07-18 21:23 ` [PATCH net-next v6 7/7] bonding: Selftest and documentation for the arp_ip_target parameter David Wilder
2025-07-19 1:33 ` Jakub Kicinski
2025-07-21 19:23 ` David Wilder
2025-07-21 20:08 ` Jakub Kicinski [this message]
2025-08-08 17:32 ` David Wilder
2025-08-08 17:43 ` Jakub Kicinski
2025-07-20 10:37 ` Simon Horman
2025-07-21 17:47 ` David Wilder
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=20250721130800.021609ee@kernel.org \
--to=kuba@kernel.org \
--cc=amorenoz@redhat.com \
--cc=haliu@redhat.com \
--cc=horms@kernel.org \
--cc=i.maximets@ovn.org \
--cc=jv@jvosburgh.net \
--cc=netdev@vger.kernel.org \
--cc=pradeep@us.ibm.com \
--cc=pradeeps@linux.vnet.ibm.com \
--cc=stephen@networkplumber.org \
--cc=wilder@us.ibm.com \
/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).