* Re: rcu stalls during fstests runs for xfs [not found] ` <aXyRRaOBkvENTlBE@shinmob> @ 2026-02-06 9:33 ` Matthieu Baerts 2026-02-06 10:02 ` Shinichiro Kawasaki 0 siblings, 1 reply; 3+ messages in thread From: Matthieu Baerts @ 2026-02-06 9:33 UTC (permalink / raw) To: Shinichiro Kawasaki Cc: Kunwu Chan, rcu@vger.kernel.org, linux-xfs@vger.kernel.org, hch, Paul E. McKenney, MPTCP Linux Hi Shinichiro, Sorry to jump in, but I *think* our CI for the MPTCP subsystem is hitting the same issue. On 30/01/2026 12:16, Shinichiro Kawasaki wrote: > On Jan 29, 2026 / 15:19, Paul E. McKenney wrote: > [...] >>>>> I have seen the static-key pattern called out by Dave Chinner when running >>>>> KASAN on large systems. We worked around this by disabling KASAN's use >>>>> of static keys. In case you were running KASAN in these tests. >>>> >>>> As to KASAN, yes, I enable it in my test runs. I find three static-keys under >>>> mm/kasan/*. I will think if they can be disabled in my test runs. Thanks. >>> >>> There is a set of Kconfig options that disables static branches. If you >>> cannot find them quickly, please let me know and I can look them up. > > Thank you. But now I know the fix series by Thomas is available. I prioritize > the evaluation of the fix series. Later on, I will try disabling the static-keys > if it is required. > >> >> And Thomas Gleixner posted an alleged fix to the CID issue here: >> >> https://lore.kernel.org/lkml/20260129210219.452851594@kernel.org/ >> >> Please let him know whether or not it helps. > > Good to see this fix candidate series, thanks :) I have set up the patches and > started my regular test runs. So far, the hangs have been observed once or twice > a week. To confirm the effect of the fix series, I think two weeks runs will be > required. Once I get the result, will share it on this thread and with Thomas. I know it is only one week now, but did you see any effects so far? On my side, I applied the v2 series -- which has been applied in tip/sched/urgent -- but I still have issues, and it looks like it is even more frequent. Maybe what I see is different. If you no longer see the issues on your side after one week, I'm going to start a new thread with my issues not to mix them. Note that in my case, the issue is visible on a system where nested VMs are used, with and without KASAN (enabled via debug.config), just after having started a VSOCK listening socket via socat. Cheers, Matt -- Sponsored by the NGI0 Core fund. ^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: rcu stalls during fstests runs for xfs 2026-02-06 9:33 ` rcu stalls during fstests runs for xfs Matthieu Baerts @ 2026-02-06 10:02 ` Shinichiro Kawasaki 2026-02-06 11:04 ` Matthieu Baerts 0 siblings, 1 reply; 3+ messages in thread From: Shinichiro Kawasaki @ 2026-02-06 10:02 UTC (permalink / raw) To: Matthieu Baerts Cc: Kunwu Chan, rcu@vger.kernel.org, linux-xfs@vger.kernel.org, hch, Paul E. McKenney, MPTCP Linux On Feb 06, 2026 / 10:33, Matthieu Baerts wrote: > Hi Shinichiro, > > Sorry to jump in, but I *think* our CI for the MPTCP subsystem is > hitting the same issue. Hi Matthieu, > On 30/01/2026 12:16, Shinichiro Kawasaki wrote: > > On Jan 29, 2026 / 15:19, Paul E. McKenney wrote: > > [...] > >>>>> I have seen the static-key pattern called out by Dave Chinner when running > >>>>> KASAN on large systems. We worked around this by disabling KASAN's use > >>>>> of static keys. In case you were running KASAN in these tests. > >>>> > >>>> As to KASAN, yes, I enable it in my test runs. I find three static-keys under > >>>> mm/kasan/*. I will think if they can be disabled in my test runs. Thanks. > >>> > >>> There is a set of Kconfig options that disables static branches. If you > >>> cannot find them quickly, please let me know and I can look them up. > > > > Thank you. But now I know the fix series by Thomas is available. I prioritize > > the evaluation of the fix series. Later on, I will try disabling the static-keys > > if it is required. > > > >> > >> And Thomas Gleixner posted an alleged fix to the CID issue here: > >> > >> https://lore.kernel.org/lkml/20260129210219.452851594@kernel.org/ > >> > >> Please let him know whether or not it helps. > > > > Good to see this fix candidate series, thanks :) I have set up the patches and > > started my regular test runs. So far, the hangs have been observed once or twice > > a week. To confirm the effect of the fix series, I think two weeks runs will be > > required. Once I get the result, will share it on this thread and with Thomas. > > I know it is only one week now, but did you see any effects so far? No, I do not see any hang so far. And I hope there will be no hang in the next week either. Fingers crossed... > On > my side, I applied the v2 series -- which has been applied i > tip/sched/urgent -- but I still have issues, and it looks like it is > even more frequent. Maybe what I see is different. If you no longer see > the issues on your side after one week, I'm going to start a new thread > with my issues not to mix them. > > Note that in my case, the issue is visible on a system where nested VMs > are used, with and without KASAN (enabled via debug.config), just after > having started a VSOCK listening socket via socat. I applied the v1 series on top of my test target xfs kernel branches enabling KASAN. ^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: rcu stalls during fstests runs for xfs 2026-02-06 10:02 ` Shinichiro Kawasaki @ 2026-02-06 11:04 ` Matthieu Baerts 0 siblings, 0 replies; 3+ messages in thread From: Matthieu Baerts @ 2026-02-06 11:04 UTC (permalink / raw) To: Shinichiro Kawasaki Cc: Kunwu Chan, rcu@vger.kernel.org, linux-xfs@vger.kernel.org, hch, Paul E. McKenney, MPTCP Linux On 06/02/2026 11:02, Shinichiro Kawasaki wrote: > On Feb 06, 2026 / 10:33, Matthieu Baerts wrote: >> Hi Shinichiro, >> >> Sorry to jump in, but I *think* our CI for the MPTCP subsystem is >> hitting the same issue. > > Hi Matthieu, > >> On 30/01/2026 12:16, Shinichiro Kawasaki wrote: >>> On Jan 29, 2026 / 15:19, Paul E. McKenney wrote: >>> [...] >>>>>>> I have seen the static-key pattern called out by Dave Chinner when running >>>>>>> KASAN on large systems. We worked around this by disabling KASAN's use >>>>>>> of static keys. In case you were running KASAN in these tests. >>>>>> >>>>>> As to KASAN, yes, I enable it in my test runs. I find three static-keys under >>>>>> mm/kasan/*. I will think if they can be disabled in my test runs. Thanks. >>>>> >>>>> There is a set of Kconfig options that disables static branches. If you >>>>> cannot find them quickly, please let me know and I can look them up. >>> >>> Thank you. But now I know the fix series by Thomas is available. I prioritize >>> the evaluation of the fix series. Later on, I will try disabling the static-keys >>> if it is required. >>> >>>> >>>> And Thomas Gleixner posted an alleged fix to the CID issue here: >>>> >>>> https://lore.kernel.org/lkml/20260129210219.452851594@kernel.org/ >>>> >>>> Please let him know whether or not it helps. >>> >>> Good to see this fix candidate series, thanks :) I have set up the patches and >>> started my regular test runs. So far, the hangs have been observed once or twice >>> a week. To confirm the effect of the fix series, I think two weeks runs will be >>> required. Once I get the result, will share it on this thread and with Thomas. >> >> I know it is only one week now, but did you see any effects so far? > > No, I do not see any hang so far. And I hope there will be no hang in the > next week either. Fingers crossed... Thank you for your reply! >> On >> my side, I applied the v2 series -- which has been applied i >> tip/sched/urgent -- but I still have issues, and it looks like it is >> even more frequent. Maybe what I see is different. If you no longer see >> the issues on your side after one week, I'm going to start a new thread >> with my issues not to mix them. >> >> Note that in my case, the issue is visible on a system where nested VMs >> are used, with and without KASAN (enabled via debug.config), just after >> having started a VSOCK listening socket via socat. > > I applied the v1 series on top of my test target xfs kernel branches enabling > KASAN. Sorry for the noise, I guess I have a different issue, even if the traces look similar [1]. Hopefully someone can help me find the root cause :) [1] https://github.com/multipath-tcp/mptcp_net-next/actions/runs/21723325004/job/62658752123#step:7:7288 Cheers, Matt -- Sponsored by the NGI0 Core fund. ^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2026-02-06 11:04 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
[not found] <aXdO52wh2rqTUi1E@shinmob>
[not found] ` <IA1PR14MB565903564F4AA105AF6A21099791A@IA1PR14MB5659.namprd14.prod.outlook.com>
[not found] ` <fc611e8e-0da9-4b88-83ef-092d300307e3@paulmck-laptop>
[not found] ` <aXrl46PxeHQSpYbX@shinmob>
[not found] ` <13b25e07-d7b8-4b4e-a249-b6826b2eea39@paulmck-laptop>
[not found] ` <c33c3d3e-a59c-4f5a-a562-13e2cabc2faf@paulmck-laptop>
[not found] ` <aXyRRaOBkvENTlBE@shinmob>
2026-02-06 9:33 ` rcu stalls during fstests runs for xfs Matthieu Baerts
2026-02-06 10:02 ` Shinichiro Kawasaki
2026-02-06 11:04 ` Matthieu Baerts
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox