From: Huang Ying <ying.huang@intel.com>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: lkp@01.org, LKML <linux-kernel@vger.kernel.org>,
"David S. Miller" <davem@davemloft.net>,
netdev@vger.kernel.org
Subject: Re: [lkp] [rhashtable] 9d901bc0515: WARNING: CPU: 0 PID: 1 at arch/x86/mm/ioremap.c:63 __ioremap_check_ram+0x6a/0x99()
Date: Fri, 21 Aug 2015 15:09:42 +0800 [thread overview]
Message-ID: <1440140982.8683.32.camel@intel.com> (raw)
In-Reply-To: <20150821064207.GA5835@gondor.apana.org.au>
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
next prev parent reply other threads:[~2015-08-21 7:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87fv3dkwgw.fsf@yhuang-dev.intel.com>
2015-08-21 6:42 ` [lkp] [rhashtable] 9d901bc0515: WARNING: CPU: 0 PID: 1 at arch/x86/mm/ioremap.c:63 __ioremap_check_ram+0x6a/0x99() Herbert Xu
2015-08-21 7:09 ` Huang Ying [this message]
2015-08-21 7:22 ` Herbert Xu
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=1440140982.8683.32.camel@intel.com \
--to=ying.huang@intel.com \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@01.org \
--cc=netdev@vger.kernel.org \
/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