linux-ext4 - Re: kernel oops in jbd2_journal_get_descriptor

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 for Android: free password hash cracker in your pocket

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

Date:	Thu, 11 Oct 2012 17:28:28 +0200
From:	Jan Kara <jack@...e.cz>
To:	Clement Gallin-Douathe <c-gallin-douathe@...com>
Cc:	Jan Kara <jack@...e.cz>, tytso@....edu, adilger.kernel@...ger.ca,
	linux-ext4@...r.kernel.org
Subject: Re: kernel oops in jbd2_journal_get_descriptor_buffer

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@...e.cz>
SUSE Labs, CR
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html