linux-kernel - Re: [PATCH] mm: alloc_contig_range: demote pages busy message from warn to info

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: <5458C501.3040505@hurleysoftware.com>
Date:	Tue, 04 Nov 2014 07:22:25 -0500
From:	Peter Hurley <peter@...leysoftware.com>
To:	Minchan Kim <minchan@...nel.org>,
	Andrew Morton <akpm@...ux-foundation.org>
CC:	Michal Nazarewicz <mina86@...a86.com>,
	Laurent Pinchart <laurent.pinchart@...asonboard.com>,
	linux-kernel@...r.kernel.org, linux-mm@...ck.org
Subject: Re: [PATCH] mm: alloc_contig_range: demote pages busy message from
 warn to info

On 11/04/2014 12:43 AM, Minchan Kim wrote:
> Hello,
> 
> On Mon, Nov 03, 2014 at 05:57:53PM +0100, Michal Nazarewicz wrote:
>> Having test_pages_isolated failure message as a warning confuses
>> users into thinking that it is more serious than it really is.  In
>> reality, if called via CMA, allocation will be retried so a single
>> test_pages_isolated failure does not prevent allocation from
>> succeeding.
>>
>> Demote the warning message to an info message and reformat it such
>> that the text “failed” does not appear and instead a less worrying
>> “PFNS busy” is used.
> 
> What do you expect from this message? Please describe it so that we can
> review below message helps your goal.

I expect this message to not show up in logs unless there is a real problem.

This message is trivially reproducible on a 10GB x86 machine on 3.16.y
kernels configured with CONFIG_DMA_CMA.


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