From: Jan Kara <jack@suse.cz>
To: Clement Gallin-Douathe <c-gallin-douathe@ti.com>
Cc: tytso@mit.edu, adilger.kernel@dilger.ca, linux-ext4@vger.kernel.org
Subject: Re: kernel oops in jbd2_journal_get_descriptor_buffer
Date: Thu, 11 Oct 2012 11:59:32 +0200 [thread overview]
Message-ID: <20121011095932.GA16624@quack.suse.cz> (raw)
In-Reply-To: <50768765.8040406@ti.com>
Hi,
On Thu 11-10-12 10:46:29, Clement Gallin-Douathe wrote:
> I am working on ARMv7 dual-core board with android (ICS + kernel 3.4.9).
> I am randomly facing a kernel oops in fs/jbd2/journal.c: In the
> function jbd2_journal_get_descriptor_buffer, memset is called
> without checking bh->b_data which is NULL in my case.
>
> It seems to be a problem with the journal device block.
> It seems that the current memory zone is high memory zone, so the
> current buffer head referred to the used page is not correctly set
> (b_data is NULL).
>
> I could not find why the buffer cache tries to allocate and use a
> block in high memory zone.
> Any ideas, or tips/tricks for debugging ?
Well, the question is how a highmem page got to
jbd2_journal_get_descriptor_buffer(). In fs/block_dev.c:bdget() we do
mapping_set_gfp_mask(&inode->i_data, GFP_USER) where GFP_USER is
(__GFP_WAIT | __GFP_IO | __GFP_FS | __GFP_HARDWALL). That means
!__GFP_HIGH in particular. So does the device ext4 is mounted on play
some tricks with mapping flags? If not, I'd instrument grow_dev_page() in
fs/buffer.c to check whether the returned page is not highmem... If yes,
look further into the allocator. If no, it could be a bug in page migration
code from mm/migrate.c.
Honza
--
Jan Kara <jack@suse.cz>
SUSE Labs, CR
next prev parent reply other threads:[~2012-10-11 9:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-11 8:46 kernel oops in jbd2_journal_get_descriptor_buffer Clement Gallin-Douathe
2012-10-11 9:59 ` Jan Kara [this message]
2012-10-11 15:22 ` Clement Gallin-Douathe
2012-10-11 15:28 ` Jan Kara
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=20121011095932.GA16624@quack.suse.cz \
--to=jack@suse.cz \
--cc=adilger.kernel@dilger.ca \
--cc=c-gallin-douathe@ti.com \
--cc=linux-ext4@vger.kernel.org \
--cc=tytso@mit.edu \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.