All of lore.kernel.org
 help / color / mirror / Atom feed
From: Al Viro <viro@ZenIV.linux.org.uk>
To: Richard Weinberger <richard@nod.at>
Cc: Randy Dunlap <rdunlap@xenotime.net>,
	Stephen Rothwell <sfr@canb.auug.org.au>,
	linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: Tree for Mar 19 (uml)
Date: Mon, 19 Mar 2012 16:44:51 +0000	[thread overview]
Message-ID: <20120319164451.GI6589@ZenIV.linux.org.uk> (raw)
In-Reply-To: <4F675B78.8060300@nod.at>

On Mon, Mar 19, 2012 at 05:14:48PM +0100, Richard Weinberger wrote:
> Looks like this commit introduced the issue:
> 
> commit 1ed71e0439cba3609d3c69bf04795e0389cd35e4
> Author: Al Viro <viro@zeniv.linux.org.uk>
> Date:   Thu Feb 23 01:33:19 2012 -0500
> 
>     um: embed ->stub_pages[] into mmu_context
> 
>     seriously, kmalloc() for two-element array of pointers?
> 
>     Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
> 
> The size of struct page is not known to all users of asm/mmu.h

Aaargh...  Dumb braino, fixed in the local queue back in Feb 25, fix
not folded into commit and missed on cherry-pick ;-/

It's
        struct page *stub_pages[2];
of course...

OK, fix properly folded into that sucker, for-next repushed.

  reply	other threads:[~2012-03-19 16:44 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-19  7:48 linux-next: Tree for Mar 19 Stephen Rothwell
2012-03-19 15:01 ` linux-next: Tree for Mar 19 (uml) Randy Dunlap
2012-03-19 16:14   ` Richard Weinberger
2012-03-19 16:44     ` Al Viro [this message]
2012-03-19 20:16       ` Randy Dunlap
2012-03-19 15:15 ` linux-next: Tree for Mar 19 (net/usb) Randy Dunlap
2012-03-19 17:48 ` [PATCH] net: qmi_wwan: fix build error due to cdc-wdm dependecy Bjørn Mork
2012-03-19 20:16   ` Randy Dunlap
2012-03-19 22:17     ` David Miller

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=20120319164451.GI6589@ZenIV.linux.org.uk \
    --to=viro@zeniv.linux.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=rdunlap@xenotime.net \
    --cc=richard@nod.at \
    --cc=sfr@canb.auug.org.au \
    /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.