linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jan Kara <jack@suse.cz>
To: Clement Gallin-Douathe <c-gallin-douathe@ti.com>
Cc: Jan Kara <jack@suse.cz>,
	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 17:28:28 +0200	[thread overview]
Message-ID: <20121011152828.GA8001@quack.suse.cz> (raw)
In-Reply-To: <5076E449.5000004@ti.com>

On Thu 11-10-12 17:22:49, Clement Gallin-Douathe wrote:
> Jan,
> 
> Thanks for your answer.
> I have checked and I have no tricks with mapping flags (mount ext4
> options : rw,nosuid,nodev,noatime,errors=continue,data=ordered)
> I have added high mem verification on grow_dev_page function just
> after the page creation with find_or_create_page function.
> PageHighMem() is not null.
> So you think, it's a good idea to look into mm/page_alloc.c and
> verify gfp flags?
  Yep. Check what gfp flags are passed to find_or_create_page() and if
there if no __GFP_HIGH set, drill down into find_or_create_page() and
further to mm/page_alloc.c to find out where we get the page from.

								Honza
> On 10/11/2012 11:59 AM, Jan Kara wrote:
> >!__GFP_HIGH in particular. So does the device ext4 is mounted on play
> >some tricks with mapping fl
> 
> 
-- 
Jan Kara <jack@suse.cz>
SUSE Labs, CR

      reply	other threads:[~2012-10-11 15:28 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
2012-10-11 15:22   ` Clement Gallin-Douathe
2012-10-11 15:28     ` Jan Kara [this message]

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=20121011152828.GA8001@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 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).