linux-kernel - Re: 2.6.26-rc5-mm2 compile error in vmscan.c

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <87hcc1jx6p.fsf@saeurebad.de>
Date:	Tue, 10 Jun 2008 14:23:26 +0200
From:	Johannes Weiner <hannes@...urebad.de>
To:	Helge Hafting <helge.hafting@...el.hist.no>
Cc:	Andrew Morton <akpm@...ux-foundation.org>,
	linux-kernel@...r.kernel.org, kernel-testers@...r.kernel.org,
	linux-mm@...ck.org
Subject: Re: 2.6.26-rc5-mm2  compile error in vmscan.c

Hi,

Helge Hafting <helge.hafting@...el.hist.no> writes:

> Andrew Morton wrote:
>> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.26-rc5/2.6.26-rc5-mm2/
>>
>> - This is a bugfixed version of 2.6.26-rc5-mm1 - mainly to repair a
>>   vmscan.c bug which would have prevented testing of the other vmscan.c
>>   bugs^Wchanges.
>>
>
> Interesting to try out, but I got this:
>
>  $ make
>   CHK     include/linux/version.h
>   CHK     include/linux/utsrelease.h
>   CALL    scripts/checksyscalls.sh
>   CHK     include/linux/compile.h
>   CC      mm/vmscan.o
> mm/vmscan.c: In function 'show_page_path':
> mm/vmscan.c:2419: error: 'struct mm_struct' has no member named 'owner'
> make[1]: *** [mm/vmscan.o] Error 1
> make: *** [mm] Error 2
>
>
> I then tried to configure with "Track page owner", but that did not
> change anything.

CONFIG_PAGE_OWNER is something else, owner is only active if
CONFIG_MM_OWNER is set.

	Hannes
--
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/