linux-kernel - Re: [PATCH v3 2/3] mm, slub: don't combine pr

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: <20210208172600.GU308988@casper.infradead.org>
Date:   Mon, 8 Feb 2021 17:26:00 +0000
From:   Matthew Wilcox <willy@...radead.org>
To:     Yafang Shao <laoar.shao@...il.com>
Cc:     andriy.shevchenko@...ux.intel.com, david@...hat.com,
        vbabka@...e.cz, cl@...ux.com, linmiaohe@...wei.com,
        penberg@...nel.org, rientjes@...gle.com, iamjoonsoo.kim@....com,
        akpm@...ux-foundation.org, pmladek@...e.com, rostedt@...dmis.org,
        sergey.senozhatsky@...il.com, joe@...ches.com, linux-mm@...ck.org,
        linux-kernel@...r.kernel.org
Subject: Re: [PATCH v3 2/3] mm, slub: don't combine pr_err with INFO

On Mon, Feb 08, 2021 at 06:14:38PM +0800, Yafang Shao wrote:
> It is strange to combine "pr_err" with "INFO", so let's remove the
> prefix completely.

So is this the right thing to do?  Should it be pr_info() instead?
Many of these messages do not appear to be error messages, but
rather informational messages.