From: Ryo Takakura <ryotkkr98@gmail.com>
To: peterz@infradead.org
Cc: boqun.feng@gmail.com, bp@alien8.de, davem@davemloft.net,
edumazet@google.com, horms@kernel.org, kuba@kernel.org,
kuniyu@amazon.com, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org, pabeni@redhat.com, ryotkkr98@gmail.com,
x86@kernel.org
Subject: Re: request_irq() with local bh disabled
Date: Sat, 8 Mar 2025 00:50:12 +0900 [thread overview]
Message-ID: <20250307155012.84673-1-ryotkkr98@gmail.com> (raw)
In-Reply-To: <20250307135959.GL16878@noisy.programming.kicks-ass.net>
Hi Peter,
On Fri, 7 Mar 2025 14:59:59 +0100, Peter Zijlstra wrote:
>On Fri, Mar 07, 2025 at 02:13:19PM +0100, Borislav Petkov wrote:
>> On Fri, Mar 07, 2025 at 09:58:51PM +0900, Ryo Takakura wrote:
>> > I'm so sorry that the commit caused this problem...
>> > Please let me know if there is anything that I should do.
>>
>> It is gone from the tip tree so you can take your time and try to do it right.
>>
>> Peter and/or I could help you reproduce the issue and try to figure out what
>> needs to change there.
>
>.config attached; I used gcc-14.2.0-8 (debian).
>
>Simply booting it should reproduce; it goes boom when trying to
>initialize INET6.
Thanks for the config. I got the error now!
I'll take a further look later on.
Sincerely,
Ryo Takakura
prev parent reply other threads:[~2025-03-07 15:50 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-06 12:24 request_irq() with local bh disabled Borislav Petkov
2025-03-06 13:45 ` Eric Dumazet
2025-03-06 16:19 ` Borislav Petkov
2025-03-07 11:55 ` Borislav Petkov
2025-03-07 12:58 ` Ryo Takakura
2025-03-07 13:13 ` Borislav Petkov
2025-03-07 13:39 ` Ryo Takakura
2025-03-07 15:57 ` Boqun Feng
2025-03-07 18:33 ` Boqun Feng
2025-03-07 19:29 ` Boqun Feng
2025-03-07 23:08 ` Boqun Feng
2025-03-08 8:09 ` Ryo Takakura
2025-03-07 13:59 ` Peter Zijlstra
2025-03-07 15:50 ` Ryo Takakura [this message]
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=20250307155012.84673-1-ryotkkr98@gmail.com \
--to=ryotkkr98@gmail.com \
--cc=boqun.feng@gmail.com \
--cc=bp@alien8.de \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=kuniyu@amazon.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=peterz@infradead.org \
--cc=x86@kernel.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 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).