mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@osdl.org>
To: lepton <lepton@mail.goldenhope.com.cn>
Cc: linux-kernel@vger.kernel.org, Nikita Danilov <Nikita@Namesys.COM>
Subject: Re: [BUG]kmalloc memory in reiserfs code failed on a dual amd64/4G linux 2.6.2 box
Date: Thu, 12 Feb 2004 22:31:39 -0800	[thread overview]
Message-ID: <20040212223139.61c3c349.akpm@osdl.org> (raw)
In-Reply-To: <20040213031653.GA25623@lepton.goldenhope.com.cn>

lepton <lepton@mail.goldenhope.com.cn> wrote:
>
>  I seen such dmesg in mu dual amd64/4G memory box.
> 
>  I am running kernel 2.6.2
> 
>  This is the second time I saw some problems about __alloc_pages on this
>  amd 64 box...
> 
> 
>  sort: page allocation failure. order:1, mode:0x20
> 
>  Call Trace:<ffffffff8014e5f0>{__alloc_pages+816} <ffffffff8014e65e>{__get_free_pages+78} 
>         <ffffffff80151921>{cache_grow+177} <ffffffff80151e78>{cache_alloc_refill+440} 
>         <ffffffff801521c6>{__kmalloc+102} <ffffffff801b44f6>{get_mem_for_virtual_node+102} 
>         <ffffffff801b49a8>{fix_nodes+232} <ffffffff801c08c5>{reiserfs_insert_item+149} 
>         <ffffffff801acf2c>{reiserfs_new_inode+892} <ffffffff801bd6a8>{pathrelse+40} 
>         <ffffffff801a834b>{reiserfs_create+171} <ffffffff8017690c>{vfs_create+140} 
>         <ffffffff80176ca8>{open_namei+424} <ffffffff801675a7>{filp_open+39} 
>         <ffffffff801210a8>{sys32_open+56} <ffffffff8011e25e>{ia32_do_syscall+30}

Nikita, why cannot get_mem_for_virtual_node() use GFP_KERNEL?

  reply	other threads:[~2004-02-13  6:31 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-13  3:16 lepton
2004-02-13  6:31 ` Andrew Morton [this message]
2004-02-13 10:46   ` Nikita Danilov
2004-02-13 10:57   ` Oleg Drokin

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=20040212223139.61c3c349.akpm@osdl.org \
    --to=akpm@osdl.org \
    --cc=Nikita@Namesys.COM \
    --cc=lepton@mail.goldenhope.com.cn \
    --cc=linux-kernel@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

all inboxes | Powered by JetHome®