[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20150402073356.GC19425@casper.infradead.org>
Date: Thu, 2 Apr 2015 08:33:56 +0100
From: Thomas Graf <tgraf@...g.ch>
To: Herbert Xu <herbert@...dor.apana.org.au>
Cc: Fengguang Wu <fengguang.wu@...el.com>, LKP <lkp@...org>,
netdev@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [rhashtable] [ INFO: suspicious RCU usage. ]
On 04/02/15 at 12:29pm, Herbert Xu wrote:
> On Thu, Apr 02, 2015 at 12:11:35PM +0800, Fengguang Wu wrote:
> >
> > Yes it is contained in next-20150401 which is bad:
> >
> > # extra tests on tree/branch next/master
> > git bisect bad e954104e2b634b42811dad8d502cbf240f206df2 # 21:22 0- 60 Add linux-next specific files for 20150401
> >
> > The dmesg there is
> >
> > [ 1.149409] test_firmware: interface ready
> > [ 1.150293] Running resizable hashtable tests...
> > [ 1.151209] Adding 2048 keys
> > [ 1.152069] ------------[ cut here ]------------
> > [ 1.152978] WARNING: CPU: 0 PID: 1 at lib/rhashtable.c:409 rhashtable_insert_rehash+0x9d/0x1d0()
>
> I see. This is actually a completely different problem.
>
> ---8<---
> test_rhashtable: Remove bogus max_size setting
>
> Now that resizing is completely automatic, we need to remove
> the max_size setting or the test will fail.
>
> Reported-by: Fengguang Wu <fengguang.wu@...el.com>
> Signed-off-by: Herbert Xu <herbert@...dor.apana.org.au>
Acked-by: Thomas Graf <tgraf@...g.ch>
Had the same fix queued up in an upcoming series ;-)
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists