From: Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>
To: Michal Hocko <mhocko@kernel.org>,
Matthias Dahl <ml_linux-kernel@binary-island.eu>
Cc: linux-raid@vger.kernel.org, linux-mm@kvack.org,
dm-devel@redhat.com, linux-kernel@vger.kernel.org,
Mike Snitzer <snitzer@redhat.com>
Subject: Re: Page Allocation Failures/OOM with dm-crypt on software RAID10 (Intel Rapid Storage)
Date: Thu, 14 Jul 2016 20:18:49 +0900 [thread overview]
Message-ID: <9074e82f-bf52-011e-8bd7-5731d2b0dcaa@I-love.SAKURA.ne.jp> (raw)
In-Reply-To: <20160713134717.GL28723@dhcp22.suse.cz>
On 2016/07/13 22:47, Michal Hocko wrote:
> On Wed 13-07-16 15:18:11, Matthias Dahl wrote:
>> I tried to figure this out myself but
>> couldn't find anything -- what does the number "-3" state? It is the
>> position in some chain or has it a different meaning?
>
> $ git grep "kmem_cache_create.*bio"
> block/bio-integrity.c: bip_slab = kmem_cache_create("bio_integrity_payload",
>
> so there doesn't seem to be any cache like that in the vanilla kernel.
>
It is
snprintf(bslab->name, sizeof(bslab->name), "bio-%d", entry);
line in bio_find_or_create_slab() in block/bio.c.
I think you can identify who is creating it by printing backtrace at that line.
next prev parent reply other threads:[~2016-07-14 11:19 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-12 8:27 Page Allocation Failures/OOM with dm-crypt on software RAID10 (Intel Rapid Storage) Matthias Dahl
2016-07-12 9:50 ` Michal Hocko
2016-07-12 11:28 ` Matthias Dahl
2016-07-12 11:49 ` Michal Hocko
2016-07-12 11:59 ` Michal Hocko
2016-07-12 12:42 ` Matthias Dahl
2016-07-12 14:07 ` Michal Hocko
2016-07-12 14:56 ` Matthias Dahl
2016-07-13 11:21 ` Michal Hocko
2016-07-13 12:18 ` Michal Hocko
2016-07-13 13:18 ` Matthias Dahl
2016-07-13 13:47 ` Michal Hocko
2016-07-13 15:32 ` Matthias Dahl
2016-07-13 16:24 ` [dm-devel] " Ondrej Kozina
2016-07-13 18:24 ` Matthias Dahl
2016-07-14 11:18 ` Tetsuo Handa [this message]
2016-07-15 7:11 ` Page Allocation Failures/OOM with dm-crypt on software RAID10 (Intel Rapid Storage) with check/repair/sync Matthias Dahl
2016-07-18 7:24 ` Matthias Dahl
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=9074e82f-bf52-011e-8bd7-5731d2b0dcaa@I-love.SAKURA.ne.jp \
--to=penguin-kernel@i-love.sakura.ne.jp \
--cc=dm-devel@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-raid@vger.kernel.org \
--cc=mhocko@kernel.org \
--cc=ml_linux-kernel@binary-island.eu \
--cc=snitzer@redhat.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).