From: Thorsten Glaser <t.glaser@tarent.de>
To: netdev@vger.kernel.org
Subject: RFH, where did I go wrong?
Date: Thu, 8 Sep 2022 23:01:31 +0200 (CEST) [thread overview]
Message-ID: <42776059-242c-cf49-c3ed-31e311b91f1c@tarent.de> (raw)
Hi,
under high load, my homegrown qdisc causes a system crash,
but I’m a bit baffled at the message and location. Perhaps
anyone has directly an idea where I could have messed up?
Transcription of the most relevant info from the screen photo:
virt_to_cache: Object is not a Slab page!
… at mm/slab.h:435 kmem_cache_free+…
Call Trace:
__rtnl_unlock+0x34/0x40
netdev_run_todo+…
rtnetlink_rcv_msg
? _copy_to_iter
? __free_one_page
? rtnl_calcit.isra.0
netlink_rcv_skb
netlink_unicast
netlink_sendmsg
sock_sendmsg
____sys_sendmsg
[…]
The trace is followed by two…
BUG: Bad rss-counter state mm:0000000001b817b09
first one is type:MM_FILEPAGES val:81
second one is type:MM_ANONPAGES val:30
I guess I either messed up with pointers or locking, but I don’t
have the Linux kernel coding experience to know where to even start
looking for causes.
Source in question is…
https://github.com/tarent/sch_jens/blob/iproute2_5.10.0-4jens14/janz/sch_janz.c
… though I don’t exactly ask for someone to solve this for me (though
that would, obviously, also be welcome ☺) but to get to know enough
for me to figure out the bug.
I probably would start by adding lots of debugging printks, but the
problem occurs when throwing iperf with 40 Mbit/s on this set to limit
to 20 Mbit/s, which’d cause a lot of information — plus I don’t even
know what kind of error “Object is not a Slab page” is (i.e. what wrong
thing is passed where or written to where).
Thanks in advance,
//mirabilos
--
Infrastrukturexperte • tarent solutions GmbH
Am Dickobskreuz 10, D-53121 Bonn • http://www.tarent.de/
Telephon +49 228 54881-393 • Fax: +49 228 54881-235
HRB AG Bonn 5168 • USt-ID (VAT): DE122264941
Geschäftsführer: Dr. Stefan Barth, Kai Ebenrett, Boris Esser, Alexander Steeg
****************************************************
/⁀\ The UTF-8 Ribbon
╲ ╱ Campaign against Mit dem tarent-Newsletter nichts mehr verpassen:
╳ HTML eMail! Also, https://www.tarent.de/newsletter
╱ ╲ header encryption!
****************************************************
next reply other threads:[~2022-09-08 21:11 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <FR2P281MB2959684780DC911876D2465590419@FR2P281MB2959.DEUP281.PROD.OUTLOOK.COM>
[not found] ` <FR2P281MB2959EBC7E6CE9A1A8D01A01F90419@FR2P281MB2959.DEUP281.PROD.OUTLOOK.COM>
2022-09-08 21:01 ` Thorsten Glaser [this message]
2022-09-10 23:38 ` RFH, where did I go wrong? Sergey Ryazanov
2022-09-10 23:43 ` Thorsten Glaser
2022-09-13 6:39 ` AW: " Haye.Haehne
2022-09-13 18:37 ` Thorsten Glaser
[not found] ` <FR2P281MB2959289F36EFC955105DD1DF90469@FR2P281MB2959.DEUP281.PROD.OUTLOOK.COM>
[not found] ` <bd8c8a7f-8a8e-3992-d631-d2f74d38483@tarent.de>
[not found] ` <FR2P281MB2959185CA486AB5A5868C4D490529@FR2P281MB2959.DEUP281.PROD.OUTLOOK.COM>
[not found] ` <1b62f51-a017-e21-31f3-2ccd72b6c8ad@tarent.de>
[not found] ` <FR2P281MB29596B8EA9AC8940C5A95B7690559@FR2P281MB2959.DEUP281.PROD.OUTLOOK.COM>
2022-10-05 18:47 ` Thorsten Glaser
2022-10-11 18:08 ` Thorsten Glaser
[not found] ` <CAA93jw5J5XzhKb_L0C5uw1e3yz_4ithUnWO6nAmeeAEn7jyYiQ@mail.gmail.com>
[not found] ` <1a1214b6-fc29-1e11-ec21-682684188513@tarent.de>
[not found] ` <CAA93jw6ReJPD=5oQ8mvcDCMNV8px8pB4UBjq=PDJvfE=kwxCRg@mail.gmail.com>
2022-10-11 20:35 ` Thorsten Glaser
2022-10-11 20:38 ` Thorsten Glaser
2022-10-12 20:17 ` Thorsten Glaser
2022-10-12 20:41 ` Eric Dumazet
2022-10-12 20:48 ` Thorsten Glaser
2022-10-12 21:40 ` Andrew Lunn
2022-10-12 21:56 ` Thorsten Glaser
2022-10-13 7:38 ` Vladimir Oltean
2022-10-13 13:19 ` Andrew Lunn
2022-10-12 21:05 ` Thorsten Glaser
2022-10-12 21:08 ` Eric Dumazet
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=42776059-242c-cf49-c3ed-31e311b91f1c@tarent.de \
--to=t.glaser@tarent.de \
--cc=netdev@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