From: Thomas Graf <tgraf@suug.ch>
To: Ying Xue <ying.xue@windriver.com>
Cc: "richard.alpe@ericsson.com >> Richard Alpe"
<richard.alpe@ericsson.com>, Netdev <netdev@vger.kernel.org>,
tipc-discussion@lists.sourceforge.net
Subject: Re: [3.19.0-rc4+] rhashtable: BUG kmalloc-2048 (Not tainted): Poison overwritten
Date: Mon, 19 Jan 2015 12:59:28 +0000 [thread overview]
Message-ID: <20150119125928.GB7672@casper.infradead.org> (raw)
In-Reply-To: <54BCBA35.2080103@windriver.com>
On 01/19/15 at 04:03pm, Ying Xue wrote:
> On 3.19.0-rc4+, I encountered below error with attached test
> case(bind_netlink.c). Please execute the following commands to reproduce
> the error:
>
> gcc -Wall -o bind_netlink bind_netlink.c
> ./bind_netlink 1000
>
> By the way, if we run another test case(bind_tipc.c), the similar issue
> will happen on TIPC socket.
>
> Therefore, it seems that the issue is closely associated with rhashtable
> instead of specific stacks like netlink or tipc.
Looks like a RCU read side critical section was missed. Does the TIPC
poision warning look the same? offset 2048?
next prev parent reply other threads:[~2015-01-19 12:59 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-19 8:03 [3.19.0-rc4+] rhashtable: BUG kmalloc-2048 (Not tainted): Poison overwritten Ying Xue
2015-01-19 12:59 ` Thomas Graf [this message]
2015-01-20 2:53 ` Ying Xue
2015-01-20 16:58 ` [PATCH net-next] rhashtable: rhashtable_remove() must unlink in both tbl and future_tbl Thomas Graf
2015-01-20 18:44 ` Sergei Shtylyov
2015-01-21 11:54 ` [PATCH net-next v2] " Thomas Graf
2015-01-26 19:57 ` David Miller
2015-01-21 8:39 ` [PATCH net-next] " Ying Xue
2015-01-21 11:56 ` Thomas Graf
2015-01-30 8:37 ` Ying Xue
2015-01-21 8:51 ` Ying Xue
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=20150119125928.GB7672@casper.infradead.org \
--to=tgraf@suug.ch \
--cc=netdev@vger.kernel.org \
--cc=richard.alpe@ericsson.com \
--cc=tipc-discussion@lists.sourceforge.net \
--cc=ying.xue@windriver.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).