public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
	Al Viro <viro@ftp.linux.org.uk>, James Morris <jmorris@namei.org>
Subject: Re: linux-next: build failure after merge of the tmem tree
Date: Wed, 15 Feb 2012 11:07:07 -0500	[thread overview]
Message-ID: <20120215160707.GB4093@phenom.dumpdata.com> (raw)
In-Reply-To: <20120215144131.e1c3b7bbe9c30f6b622872c2@canb.auug.org.au>

On Wed, Feb 15, 2012 at 02:41:31PM +1100, Stephen Rothwell wrote:
> Hi Konrad,
> 
> After merging the tmem tree, today's linux-next build (x86_64
> allmodconfig) failed like this:
> 
> mm/frontswap.c: In function 'frontswap_shrink':
> mm/frontswap.c:217:3: error: implicit declaration of function 'security_vm_enough_memory_kern' [-Werror=implicit-function-declaration]
> 
> Caused by commit 8174e70a6bde ("mm: frontswap: core frontswap
> functionality") interacting with commit 191c542442fd ("mm: collapse
> security_vm_enough_memory() variants into a single function") from the
> security tree.
> 
> I applied the following merge fix:
> 

Sweeet. Thanks!

> From: Stephen Rothwell <sfr@canb.auug.org.au>
> Date: Wed, 15 Feb 2012 14:35:31 +1100
> Subject: [PATCH] mm: frontswap: update for security_vm_enough_memory API change
> 
> Signed-off-by: Stephen Rothwell <sfr@canb.auug.org.au>
> ---
>  mm/frontswap.c |    2 +-
>  1 files changed, 1 insertions(+), 1 deletions(-)
> 
> diff --git a/mm/frontswap.c b/mm/frontswap.c
> index d7c91e3..2b80c5a 100644
> --- a/mm/frontswap.c
> +++ b/mm/frontswap.c
> @@ -214,7 +214,7 @@ void frontswap_shrink(unsigned long target_pages)
>  			pages_to_unuse = 0; /* unuse all */
>  		}
>  		/* ensure there is enough RAM to fetch pages from frontswap */
> -		if (security_vm_enough_memory_kern(pages))
> +		if (security_vm_enough_memory_mm(current->mm, pages))
>  			continue;
>  		vm_unacct_memory(pages);
>  		break;
> -- 
> 1.7.9
> 
> -- 
> Cheers,
> Stephen Rothwell                    sfr@canb.auug.org.au
> http://www.canb.auug.org.au/~sfr/



  reply	other threads:[~2012-02-15 16:10 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-15  3:41 linux-next: build failure after merge of the tmem tree Stephen Rothwell
2012-02-15 16:07 ` Konrad Rzeszutek Wilk [this message]
  -- strict thread matches above, loose matches on Subject: below --
2011-06-02  2:02 Stephen Rothwell

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=20120215160707.GB4093@phenom.dumpdata.com \
    --to=konrad.wilk@oracle.com \
    --cc=jmorris@namei.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    --cc=viro@ftp.linux.org.uk \
    /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