From: Zizhi Wo <wozizhi@huawei.com>
To: <dhowells@redhat.com>
Cc: <linux-cachefs@redhat.com>, <linux-kernel@vger.kernel.org>,
<yangerkun@huawei.com>, <hsiangkao@linux.alibaba.com>
Subject: Re: [PATCH -next,V2] cachefiles: support to disable assert macro
Date: Fri, 26 Jan 2024 10:49:43 +0800 [thread overview]
Message-ID: <b98dc776-99cd-4514-80e6-bdd4dbeb0e50@huawei.com> (raw)
In-Reply-To: <9f954701-62e0-4815-8e28-3ed75be07337@huawei.com>
friendly ping
在 2023/11/30 10:49, Zizhi Wo 写道:
> friendly ping
>
> 在 2023/11/7 18:17, Zizhi Wo 写道:
>> friendly ping
>>
>> 在 2023/11/2 0:34, WoZ1zh1 写道:
>>> In fs/cachefiles/internal.h, ASSERT macro is enabled by default and can
>>> not be disabled, then assert failure will crash the kernel as the BUG()
>>> is included in the ASSERT macro. Therefore, add CACHEFILES_ASSERT to
>>> control it.
>>>
>>> Signed-off-by: WoZ1zh1 <wozizhi@huawei.com>
>>> ---
>>> fs/cachefiles/Kconfig | 11 +++++++++++
>>> fs/cachefiles/internal.h | 2 +-
>>> 2 files changed, 12 insertions(+), 1 deletion(-)
>>>
>>> diff --git a/fs/cachefiles/Kconfig b/fs/cachefiles/Kconfig
>>> index 8df715640a48..83d8ec3ba2d8 100644
>>> --- a/fs/cachefiles/Kconfig
>>> +++ b/fs/cachefiles/Kconfig
>>> @@ -38,3 +38,14 @@ config CACHEFILES_ONDEMAND
>>> and is delegated to userspace.
>>> If unsure, say N.
>>> +
>>> +config CACHEFILES_ASSERT
>>> + bool "CACHEFILES asserts"
>>> + default n
>>> + depends on CACHEFILES
>>> + help
>>> + Support the ASSERT mode for failure behavior.
>>> + Say N here to disable the ASSERT by default.
>>> + Say Y to add assertion checks in some places. But the assertion
>>> + failure will result in fatal errors that BUG() the kernel.
>>> +
>>> diff --git a/fs/cachefiles/internal.h b/fs/cachefiles/internal.h
>>> index 2ad58c465208..263b1f13e943 100644
>>> --- a/fs/cachefiles/internal.h
>>> +++ b/fs/cachefiles/internal.h
>>> @@ -425,7 +425,7 @@ do { \
>>> #define _debug(FMT, ...) no_printk(FMT, ##__VA_ARGS__)
>>> #endif
>>> -#if 1 /* defined(__KDEBUGALL) */
>>> +#ifdef CONFIG_CACHEFILES_ASSERT
>>> #define ASSERT(X) \
>>> do { \
prev parent reply other threads:[~2024-01-26 2:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-01 16:34 WoZ1zh1
2023-11-07 10:17 ` Zizhi Wo
2023-11-30 2:49 ` Zizhi Wo
2024-01-26 2:49 ` Zizhi Wo [this message]
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=b98dc776-99cd-4514-80e6-bdd4dbeb0e50@huawei.com \
--to=wozizhi@huawei.com \
--cc=dhowells@redhat.com \
--cc=hsiangkao@linux.alibaba.com \
--cc=linux-cachefs@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=yangerkun@huawei.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
all inboxes | Powered by JetHome®