From: Wei Yongjun <weiyongjun1@huawei.com>
To: Jason Gunthorpe <jgg@nvidia.com>
Cc: Qi Zheng <zhengqi.arch@bytedance.com>, <dvyukov@google.com>,
<willy@infradead.org>, <akinobu.mita@gmail.com>,
<akpm@linux-foundation.org>, <linux-kernel@vger.kernel.org>,
<linux-mm@kvack.org>, <linux-fsdevel@vger.kernel.org>,
<stable@vger.kernel.org>
Subject: Re: [PATCH v2] mm: fix unexpected changes to {failslab|fail_page_alloc}.attr
Date: Wed, 9 Nov 2022 11:57:57 +0800 [thread overview]
Message-ID: <1f43c4a4-ee6b-f760-b7a8-c2651f077596@huawei.com> (raw)
In-Reply-To: <Y2pF4x4gsKjaHJaE@nvidia.com>
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
next prev parent reply other threads:[~2022-11-09 3:59 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CACT4Y+Zc21Aj+5KjeTEsvOysJGHRYDSKgu_+_xN1LUYfG_H0sg@mail.gmail.com>
2022-11-07 3:31 ` [PATCH] " Qi Zheng
2022-11-07 12:42 ` Jason Gunthorpe
2022-11-07 15:05 ` Qi Zheng
2022-11-07 16:26 ` Jason Gunthorpe
2022-11-08 2:47 ` Qi Zheng
2022-11-08 3:52 ` [PATCH v2] " Qi Zheng
2022-11-08 8:44 ` Wei Yongjun
2022-11-08 8:58 ` Qi Zheng
2022-11-08 9:32 ` Wei Yongjun
2022-11-08 9:45 ` Qi Zheng
2022-11-08 12:04 ` Jason Gunthorpe
2022-11-09 3:57 ` Wei Yongjun [this message]
2022-11-08 17:36 ` Akinobu Mita
2022-11-14 3:59 ` Qi Zheng
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1f43c4a4-ee6b-f760-b7a8-c2651f077596@huawei.com \
--to=weiyongjun1@huawei.com \
--cc=akinobu.mita@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=dvyukov@google.com \
--cc=jgg@nvidia.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=stable@vger.kernel.org \
--cc=willy@infradead.org \
--cc=zhengqi.arch@bytedance.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox