From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: Alexei Starovoitov <alexei.starovoitov@gmail.com>
Cc: Bert Karwatzki <spasswolf@web.de>, Tejun Heo <tj@kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
Linux-Next Mailing List <linux-next@vger.kernel.org>,
bpf <bpf@vger.kernel.org>,
linux-rt-users <linux-rt-users@vger.kernel.org>,
linux-rt-devel@lists.linux.dev,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: BUG: scheduling while atomic with PREEMPT_RT=y and bpf selftests
Date: Tue, 27 May 2025 09:19:22 +0200 [thread overview]
Message-ID: <20250527071922.tMPqxpsB@linutronix.de> (raw)
In-Reply-To: <CAADnVQLv3aX0iOrkAZRgP2x8UAVvy7oYA8x0dUPn7B6FD-10-g@mail.gmail.com>
On 2025-05-25 18:32:28 [-0700], Alexei Starovoitov wrote:
> On Sun, May 25, 2025 at 3:48 PM Bert Karwatzki <spasswolf@web.de> wrote:
> >
> > [ T2916] rtlock_slowlock_locked+0x635/0x1d00
> > [ T2916] ? srso_alias_return_thunk+0x5/0xfbef5
> > [ T2916] ? lock_acquire+0xca/0x300
> > [ T2916] rt_spin_lock+0x99/0x190
> > [ T2916] task_get_cgroup1+0xe8/0x340
> > [ T2916] bpf_task_get_cgroup1+0xe/0x20
>
> Known issue.
> Please trim your emails.
This is the trace thingy. Let me take a look.
Sebastian
next prev parent reply other threads:[~2025-05-27 7:19 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-25 22:47 BUG: scheduling while atomic with PREEMPT_RT=y and bpf selftests Bert Karwatzki
2025-05-26 1:32 ` Alexei Starovoitov
2025-05-26 9:22 ` Bert Karwatzki
2025-05-27 7:19 ` Sebastian Andrzej Siewior [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-06-05 9:19 Bert Karwatzki
2025-06-05 12:48 ` Steven Rostedt
2025-06-05 12:51 ` Sebastian Andrzej Siewior
2025-06-08 8:45 ` Bert Karwatzki
2025-06-08 15:53 ` Bert Karwatzki
2025-06-09 11:37 ` Bert Karwatzki
2025-06-14 12:01 ` Bert Karwatzki
2025-06-15 22:12 ` Bert Karwatzki
2025-06-16 6:28 ` Sebastian Andrzej Siewior
2025-06-06 13:13 ` Bert Karwatzki
2025-06-06 13:57 ` Steven Rostedt
2025-05-25 12:14 Bert Karwatzki
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=20250527071922.tMPqxpsB@linutronix.de \
--to=bigeasy@linutronix.de \
--cc=alexei.starovoitov@gmail.com \
--cc=bpf@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-rt-devel@lists.linux.dev \
--cc=linux-rt-users@vger.kernel.org \
--cc=spasswolf@web.de \
--cc=tglx@linutronix.de \
--cc=tj@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).