linux-kernel - Re: linux-next: Tree for Apr 29

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: <517EE01B.80109@infradead.org>
Date:	Mon, 29 Apr 2013 14:03:23 -0700
From:	Randy Dunlap <rdunlap@...radead.org>
To:	Stephen Rothwell <sfr@...b.auug.org.au>
CC:	linux-next@...r.kernel.org, linux-kernel@...r.kernel.org,
	Linux MM <linux-mm@...ck.org>
Subject: Re: linux-next: Tree for Apr 29

On 04/29/13 13:05, Randy Dunlap wrote:
> On 04/29/13 02:17, Stephen Rothwell wrote:
>> Hi all,
>>
>> Changes since 20130426:
>>
> 
> 
> (who is responsible for MEM_SOFT_DIRTY?)
> 
> 
> on x86_64:
> 
> warning: (HWPOISON_INJECT && MEM_SOFT_DIRTY) selects PROC_PAGE_MONITOR which has unmet direct dependencies (PROC_FS && MMU)
> 
> because MEM_SOFT_DIRTY selects PROC_PAGE_MONITOR when CONFIG_PROC_FS is not enabled.
> 
> 
> Can MEM_SOFT_DIRTY depend on PROC_FS?
> 
> and the help text for MEM_SOFT_DIRTY refers to Documentation/vm/soft-dirty.txt,
> which does not exist.  Please add the file.

Oops, sorry, I looked in the wrong place for that file, which DOES exist.


-- 
~Randy
--
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/