[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20150121115607.GB12570@casper.infradead.org>
Date: Wed, 21 Jan 2015 11:56:07 +0000
From: Thomas Graf <tgraf@...g.ch>
To: Ying Xue <ying.xue@...driver.com>
Cc: davem@...emloft.net,
"richard.alpe@...csson.com >> Richard Alpe"
<richard.alpe@...csson.com>, Netdev <netdev@...r.kernel.org>,
tipc-discussion@...ts.sourceforge.net
Subject: Re: [PATCH net-next] rhashtable: rhashtable_remove() must unlink in
both tbl and future_tbl
On 01/21/15 at 04:39pm, Ying Xue wrote:
> Your below changes are reasonable for me. But after I applied the patch,
> my reported two issues still happened :( And failure logs are completely
> same before.
Correct. The patch fixes the panic that you reported as well:
[ 17.033416] BUG: unable to handle kernel paging request at
ffffffffffffff77
[ 17.034009] IP: [<ffffffffa0019b8c>] jhash+0xec/0x160 [tipc]
[...]
[ 17.034009] Call Trace:
[ 17.034009] [<ffffffff813b38e9>] head_hashfn+0x29/0x50
[ 17.034009] [<ffffffff813b475b>] rhashtable_expand+0x37b/0x680
[ 17.034009] [<ffffffff813b4b38>] rht_deferred_worker+0xd8/0xe0
[ 17.034009] [<ffffffff81074d10>] process_one_work+0x200/0x800
[ 17.034009] [<ffffffff81074c71>] ? process_one_work+0x161/0x800
[ 17.034009] [<ffffffff81074c71>] ? process_one_work+0x161/0x800
[ 17.034009] [<ffffffff8107533c>] process_scheduled_works+0x2c/0x40
[ 17.034009] [<ffffffff810758d3>] worker_thread+0x253/0x4b0
[ 17.034009] [<ffffffff81075680>] ? rescuer_thread+0x330/0x330
[ 17.034009] [<ffffffff8107bb6f>] kthread+0xef/0x110
[ 17.034009] [<ffffffff8107ba80>] ? flush_kthread_work+0x170/0x170
[ 17.034009] [<ffffffff81a44a2c>] ret_from_fork+0x7c/0xb0
[ 17.034009] [<ffffffff8107ba80>] ? flush_kthread_work+0x170/0x170
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists