From: Ingo Molnar <mingo@elte.hu>
To: netdev@oss.sgi.com, linux-net@vger.kernel.org
Subject: KERNEL: assertion (!atomic_read(&sk->sk_rmem_alloc)) failed at net/netlink/af_netlink.c (126)
Date: Sun, 27 Mar 2005 11:15:24 +0200 [thread overview]
Message-ID: <20050327091524.GA23215@elte.hu> (raw)
i got one such message:
KERNEL: assertion (!atomic_read(&sk->sk_rmem_alloc)) failed at
net/netlink/af_netlink.c (126)
this was on a box that is DSL connected and thus gets lots of trash
packets over the wire. It is running -RT ontop of 2.6.12-rc1, and got
this message after 2 days of uptime.
There was no apparent bad side-effect after this happened - no crash, no
hung applications, no hung connections, the box is still up and running
fine. The message is not reproducible, unfortunately. Never saw this
message with 2.6.11-ish kernels on the same box.
since the locking is so different under PREEMPT_RT it may very well be
caused by PREEMPT_RT itself - but it could also be some real bug that
only triggers under PREEMPT_RT. Based on current bug trends i'd say the
likelyhood is 70% for this to be a genuine upstream bug, and 30% for
this to be a PREEMPT_RT artifact. (These days most PREEMPT_RT artifacts
get detected by PREEMPT_RT's own debugging features - and all of them
were enabled on this box. Due to its preemption model, PREEMPT_RT is
pretty good at catching races that are near-impossible to trigger on the
stock kernel. It already caught more than a dozen such upstream races in
various kernel subsystems.)
Ingo
next reply other threads:[~2005-03-27 9:15 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-27 9:15 Ingo Molnar [this message]
2005-03-27 10:01 ` KERNEL: assertion (!atomic_read(&sk->sk_rmem_alloc)) failed at net/netlink/af_netlink.c (126) Herbert Xu
2005-03-27 13:38 ` Ingo Molnar
2005-03-29 10:49 ` Herbert Xu
2005-03-29 11:49 ` Ingo Molnar
2005-03-30 8:26 ` Herbert Xu
2005-03-31 1:02 ` David S. Miller
2005-03-31 1:10 ` Herbert Xu
2005-03-31 19:19 ` David S. Miller
2005-03-31 23:19 ` Herbert Xu
2005-03-31 23:23 ` Herbert Xu
2005-04-01 4:33 ` David S. Miller
2005-04-01 9:36 ` [NETLINK] cb_lock does not needs ref count on sk Herbert Xu
2005-05-03 21:42 ` David S. Miller
2005-03-31 20:00 ` KERNEL: assertion (!atomic_read(&sk->sk_rmem_alloc)) failed at net/netlink/af_netlink.c (126) Krzysztof Oledzki
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=20050327091524.GA23215@elte.hu \
--to=mingo@elte.hu \
--cc=linux-net@vger.kernel.org \
--cc=netdev@oss.sgi.com \
/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).