linux-kernel - Re: linux-next: build failure after merge of the akpm-current tree

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: Windows password security audit tool. GUI, reports in PDF.

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

Date:	Fri, 17 Jul 2015 00:17:45 +0200
From:	Oleg Nesterov <oleg@...hat.com>
To:	Stephen Rothwell <sfr@...b.auug.org.au>
Cc:	Andrew Morton <akpm@...ux-foundation.org>,
	linux-next@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: linux-next: build failure after merge of the akpm-current tree

On 07/17, Stephen Rothwell wrote:
>
> Hi Andrew,
>
> After merging the akpm-current tree, today's linux-next build (lots with
> CONFIG_MMU not set) failed like this:
>
> fs/built-in.o:(.rodata+0x1060): undefined reference to `filemap_page_mkwrite'
>
> Caused by commit
>
>   fb416a02f75c ("mm: move ->mremap() from file_operations to vm_operations_struct").

Yes, please see

	[mmotm:master 140/321] fs/built-in.o:undefined reference to `filemap_page_mkwrite'
	http://marc.info/?t=143700878100001

sorry. I'll send the fix soon.

> filemap_page_mkwrite only exists when CONFIG_MMU is set.

Yes, and I still think CONFGI_AIO makes no sense in this case.

Oleg.

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/