From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: Paul Thomas <pthomas8589@gmail.com>
Cc: Alexei Starovoitov <ast@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
David Miller <davem@davemloft.net>,
Jakub Kicinski <jakub.kicinski@netronome.com>,
Jesper Dangaard Brouer <hawk@kernel.org>,
John Fastabend <john.fastabend@gmail.com>,
netdev@vger.kernel.org, xdp-newbies@vger.kernel.org,
bpf@vger.kernel.org,
linux-rt-users <linux-rt-users@vger.kernel.org>
Subject: Re: xdpsock poll with 5.2.21rt kernel
Date: Mon, 2 Dec 2019 17:26:51 +0100 [thread overview]
Message-ID: <20191202162651.7jkyj52sny3yownr@linutronix.de> (raw)
In-Reply-To: <CAD56B7dtR4GtPUUmmPVcuc0L+7BixW9+S=CR1g4ub3_6ZgRobg@mail.gmail.com>
On 2019-12-02 10:36:54 [-0500], Paul Thomas wrote:
> On Fri, Nov 29, 2019 at 11:48 AM Sebastian Andrzej Siewior
> <bigeasy@linutronix.de> wrote:
> >
> > On 2019-11-12 17:42:42 [-0500], Paul Thomas wrote:
> > > Any thoughts would be appreciated.
> >
> > Could please enable CONFIG_DEBUG_ATOMIC_SLEEP and check if the kernel
> > complains?
>
> Hi Sebastian,
>
> Well, it does complain (report below), but I'm not sure it's related.
> The other thing I tried was the AF_XDP example here:
> https://github.com/xdp-project/xdp-tutorial/tree/master/advanced03-AF_XDP
>
> With this example poll() always seems to block correctly, so I think
> maybe there is something wrong with the xdpsock_user.c example or how
> I'm using it.
>
> [ 259.591480] BUG: assuming atomic context at net/core/ptp_classifier.c:106
> [ 259.591488] in_atomic(): 0, irqs_disabled(): 0, pid: 953, name: irq/22-eth%d
> [ 259.591494] CPU: 0 PID: 953 Comm: irq/22-eth%d Tainted: G WC
> 5.
>
> 2.21-rt13-00016-g93898e751d0e #90
> [ 259.591499] Hardware name: Enclustra XU5 SOM (DT)
> [ 259.591501] Call trace:
> [ 259.591503] dump_backtrace (/arch/arm64/kernel/traps.c:94)
> [ 259.591514] show_stack (/arch/arm64/kernel/traps.c:151)
> [ 259.591520] dump_stack (/lib/dump_stack.c:115)
> [ 259.591526] __cant_sleep (/kernel/sched/core.c:6386)
> [ 259.591531] ptp_classify_raw (/./include/linux/compiler.h:194
Is this the only splat? Nothing more? I would expect something at boot
time, too.
So this part expects disabled preemption. Other invocations disable
preemption. The whole BPF part is currently not working on -RT.
Sebastian
next prev parent reply other threads:[~2019-12-02 16:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-12 22:42 xdpsock poll with 5.2.21rt kernel Paul Thomas
2019-11-29 16:48 ` Sebastian Andrzej Siewior
2019-12-02 15:36 ` Paul Thomas
2019-12-02 16:26 ` Sebastian Andrzej Siewior [this message]
2019-12-02 17:11 ` Paul Thomas
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=20191202162651.7jkyj52sny3yownr@linutronix.de \
--to=bigeasy@linutronix.de \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=hawk@kernel.org \
--cc=jakub.kicinski@netronome.com \
--cc=john.fastabend@gmail.com \
--cc=linux-rt-users@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pthomas8589@gmail.com \
--cc=xdp-newbies@vger.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).