netdev - Re: [lkp] [rhashtable] 9d901bc0515: WARNING: CPU: 0 PID: 1 at arch/x86/mm/ioremap.c:63 __ioremap_check

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Fri, 21 Aug 2015 15:09:42 +0800
From:	Huang Ying <ying.huang@...el.com>
To:	Herbert Xu <herbert@...dor.apana.org.au>
Cc:	lkp@...org, LKML <linux-kernel@...r.kernel.org>,
	"David S. Miller" <davem@...emloft.net>, netdev@...r.kernel.org
Subject: Re: [lkp] [rhashtable] 9d901bc0515: WARNING: CPU: 0 PID: 1 at
 arch/x86/mm/ioremap.c:63 __ioremap_check_ram+0x6a/0x99()

On Fri, 2015-08-21 at 14:42 +0800, Herbert Xu wrote:
> On Fri, Aug 21, 2015 at 02:05:19PM +0800, kernel test robot wrote:
> > FYI, we noticed the below changes on
> > 
> > git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git 
> > master
> > commit 9d901bc05153bbf33b5da2cd6266865e531f0545 ("rhashtable: Free 
> > bucket tables asynchronously after rehash")
> > 
> > With the commit, the possibility of OOM is increased under our boot 
> > testing.
> 
> Can you gather some stats on how much memory rhashtable is actually
> using? With that kernel you've probably got only one rhashtable user
> which is netlink.
> 
> Bear in mind that this is a fairly low-memory machine (< 300M) so
> it's not clear to me that this patch is the root cause of your OOM
> problem.

Sorry, my fault.  There are OOM for parent commit too, just some dmesg
difference, which I miss understood.  Please ignore this report.  I
will be more careful next time.

Best Regards,
Huang, Ying

--
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