[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1f43c4a4-ee6b-f760-b7a8-c2651f077596@huawei.com>
Date: Wed, 9 Nov 2022 11:57:57 +0800
From: Wei Yongjun <weiyongjun1@...wei.com>
To: Jason Gunthorpe <jgg@...dia.com>
CC: Qi Zheng <zhengqi.arch@...edance.com>, <dvyukov@...gle.com>,
<willy@...radead.org>, <akinobu.mita@...il.com>,
<akpm@...ux-foundation.org>, <linux-kernel@...r.kernel.org>,
<linux-mm@...ck.org>, <linux-fsdevel@...r.kernel.org>,
<stable@...r.kernel.org>
Subject: Re: [PATCH v2] mm: fix unexpected changes to
{failslab|fail_page_alloc}.attr
On 2022/11/8 20:04, Jason Gunthorpe wrote:
> On Tue, Nov 08, 2022 at 05:32:52PM +0800, Wei Yongjun wrote:
>>> So you want to set/clear this no_warn attr through the procfs or sysfs
>>> interface, so that you can easily disable/enable the slab/page fault
>>> warning message from the user mode. Right?
>>
>> Yes, just like:
>>
>> echo 1 > /sys/kernel/debug/failslab/no_warn #disable message
>> echo 0 > /sys/kernel/debug/failslab/no_warn #enable message
>
> You can already do that:
>
> echo 0 > /sys/kernel/debug/failslab/verbose #disable message
Got it, thanks.
Wei Yongjun
Powered by blists - more mailing lists