All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: linux-ext4@vger.kernel.org
Subject: [Bug 14620] WARNING: at mm/page_alloc.c:1805 __alloc_pages_nodemask
Date: Tue, 17 Nov 2009 22:51:54 GMT	[thread overview]
Message-ID: <200911172251.nAHMpsae011703@demeter.kernel.org> (raw)
In-Reply-To: <bug-14620-13602@http.bugzilla.kernel.org/>

http://bugzilla.kernel.org/show_bug.cgi?id=14620





--- Comment #1 from Rafael J. Wysocki <rjw@sisk.pl>  2009-11-17 22:51:54 ---
On Tuesday 17 November 2009, Theodore Tso wrote:
> On Mon, Nov 16, 2009 at 11:37:47PM +0100, Rafael J. Wysocki wrote:
> > This message has been generated automatically as a part of a report
> > of recent regressions.
> > 
> > The following bug entry is on the current list of known regressions
> > from 2.6.31.  Please verify if it still should be listed and let me know
> > (either way).
> > 
> > 
> > Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=14620
> > Subject		: WARNING: at mm/page_alloc.c:1805 __alloc_pages_nodemask
> > Submitter	: Rogério Brito <rbrito@ime.usp.br>
> > Date		: 2009-11-06 23:10 (11 days old)
> > References	: http://marc.info/?l=linux-kernel&m=125754907413892&w=4
> 
> This isn't technically a regression, since the warning is simply
> complaining about something that apparently ext4 has been doing for a
> long time, which is that it allocates some very large order data
> buffers.  So the change referenced simply printed a warning message
> that complained about the fact.
> 
> The actual problem will be fixed in 2.6.32, as we no longer allocate
> the big data buffers at mount time.

-- 
Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2009-11-17 22:51 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-16 21:30 [Bug 14620] New: WARNING: at mm/page_alloc.c:1805 __alloc_pages_nodemask bugzilla-daemon
2009-11-17 22:51 ` bugzilla-daemon [this message]
2009-11-17 22:52 ` [Bug 14620] " bugzilla-daemon
2009-11-17 22:52 ` bugzilla-daemon
  -- strict thread matches above, loose matches on Subject: below --
2009-11-16 22:33 2.6.32-rc7-git1: Reported regressions from 2.6.31 Rafael J. Wysocki
2009-11-16 22:37 ` [Bug #14620] WARNING: at mm/page_alloc.c:1805 __alloc_pages_nodemask Rafael J. Wysocki
2009-11-16 22:37   ` Rafael J. Wysocki
2009-11-17  2:43   ` Theodore Tso
2009-11-17  2:43     ` Theodore Tso
     [not found]     ` <20091117024318.GC23066-3s7WtUTddSA@public.gmane.org>
2009-11-17 22:53       ` Rafael J. Wysocki
2009-11-17 22:53         ` Rafael J. Wysocki

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=200911172251.nAHMpsae011703@demeter.kernel.org \
    --to=bugzilla-daemon@bugzilla.kernel.org \
    --cc=linux-ext4@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 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.