From: Jakub Kicinski <kuba@kernel.org>
To: Kuniyuki Iwashima <kuniyu@amazon.com>
Cc: "David S. Miller" <davem@davemloft.net>,
David Ahern <dsahern@kernel.org>,
Eric Dumazet <edumazet@google.com>,
"Paolo Abeni" <pabeni@redhat.com>,
Simon Horman <horms@kernel.org>,
Kuniyuki Iwashima <kuni1840@gmail.com>, <netdev@vger.kernel.org>
Subject: Re: [PATCH v1 net-next 0/7] ipv6: Follow up for RTNL-free RTM_NEWROUTE series.
Date: Wed, 14 May 2025 18:45:02 -0700 [thread overview]
Message-ID: <20250514184502.22f4c4e6@kernel.org> (raw)
In-Reply-To: <20250514201943.74456-1-kuniyu@amazon.com>
On Wed, 14 May 2025 13:18:53 -0700 Kuniyuki Iwashima wrote:
> Patch 1 removes rcu_read_lock() in fib6_get_table().
> Patch 2 removes rtnl_is_held arg for lwtunnel_valid_encap_type(), which
> was short-term fix and is no longer used.
> Patch 3 fixes RCU vs GFP_KERNEL report by syzkaller.
> Patch 4~7 reverts GFP_ATOMIC uses to GFP_KERNEL.
Hi! Something in the following set of patches is making our CI time out.
The problem seems to be:
[ 0.751266] virtme-init: waiting for udev to settle
Timed out for waiting the udev queue being empty.
[ 120.826428] virtme-init: udev is done
+team: grab team lock during team_change_rx_flags
+net: mana: Add handler for hardware servicing events
+ipv6: Revert two per-cpu var allocation for RTM_NEWROUTE.
+ipv6: Pass gfp_flags down to ip6_route_info_create_nh().
+Revert "ipv6: Factorise ip6_route_multipath_add()."
+Revert "ipv6: sr: switch to GFP_ATOMIC flag to allocate memory during seg6local LWT setup"
+ipv6: Narrow down RCU critical section in inet6_rtm_newroute().
+inet: Remove rtnl_is_held arg of lwtunnel_valid_encap_type(_attr)?().
+ipv6: Remove rcu_read_lock() in fib6_get_table().
+net/mlx5e: Reuse per-RQ XDP buffer to avoid stack zeroing overhead
amd-xgbe: read link status twice to avoid inconsistencies
+net: phy: fixed_phy: remove fixed_phy_register_with_gpiod
drivers: net: mvpp2: attempt to refill rx before allocating skb
+selftest: af_unix: Test SO_PASSRIGHTS.
+af_unix: Introduce SO_PASSRIGHTS.
+af_unix: Inherit sk_flags at connect().
+af_unix: Move SOCK_PASS{CRED,PIDFD,SEC} to struct sock.
+net: Restrict SO_PASS{CRED,PIDFD,SEC} to AF_{UNIX,NETLINK,BLUETOOTH}.
+tcp: Restrict SO_TXREHASH to TCP socket.
+scm: Move scm_recv() from scm.h to scm.c.
+af_unix: Don't pass struct socket to maybe_add_creds().
+af_unix: Factorise test_bit() for SOCK_PASSCRED and SOCK_PASSPIDFD.
I haven't dug into it, gotta review / apply other patches :(
Maybe you can try to repro?
next prev parent reply other threads:[~2025-05-15 1:45 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-14 20:18 [PATCH v1 net-next 0/7] ipv6: Follow up for RTNL-free RTM_NEWROUTE series Kuniyuki Iwashima
2025-05-14 20:18 ` [PATCH v1 net-next 1/7] ipv6: Remove rcu_read_lock() in fib6_get_table() Kuniyuki Iwashima
2025-05-14 20:18 ` [PATCH v1 net-next 2/7] inet: Remove rtnl_is_held arg of lwtunnel_valid_encap_type(_attr)?() Kuniyuki Iwashima
2025-05-14 20:18 ` [PATCH v1 net-next 3/7] ipv6: Narrow down RCU critical section in inet6_rtm_newroute() Kuniyuki Iwashima
2025-05-14 20:18 ` [PATCH v1 net-next 4/7] Revert "ipv6: sr: switch to GFP_ATOMIC flag to allocate memory during seg6local LWT setup" Kuniyuki Iwashima
2025-05-14 20:18 ` [PATCH v1 net-next 5/7] Revert "ipv6: Factorise ip6_route_multipath_add()." Kuniyuki Iwashima
2025-05-14 20:18 ` [PATCH v1 net-next 6/7] ipv6: Pass gfp_flags down to ip6_route_info_create_nh() Kuniyuki Iwashima
2025-05-14 20:19 ` [PATCH v1 net-next 7/7] ipv6: Revert two per-cpu var allocation for RTM_NEWROUTE Kuniyuki Iwashima
2025-05-15 1:45 ` Jakub Kicinski [this message]
2025-05-15 2:05 ` [PATCH v1 net-next 0/7] ipv6: Follow up for RTNL-free RTM_NEWROUTE series Kuniyuki Iwashima
2025-05-15 2:22 ` Jakub Kicinski
2025-05-15 9:02 ` Paolo Abeni
2025-05-15 16:46 ` Kuniyuki Iwashima
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=20250514184502.22f4c4e6@kernel.org \
--to=kuba@kernel.org \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kuni1840@gmail.com \
--cc=kuniyu@amazon.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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).