From: Gao Xiang <hsiangkao@linux.alibaba.com>
To: Zizhi Wo <wozizhi@huawei.com>, dhowells@redhat.com
Cc: linux-cachefs@redhat.com, linux-kernel@vger.kernel.org,
yangerkun@huawei.com
Subject: Re: [PATCH -next,V2] fscache: support to disable assert macro
Date: Tue, 7 Nov 2023 20:39:12 +0800 [thread overview]
Message-ID: <32abf57d-d3bc-d812-c70f-bba8356162ff@linux.alibaba.com> (raw)
In-Reply-To: <d3a50c46-93c9-4b60-8609-9465e1605f77@huawei.com>
On 2023/11/7 18:16, Zizhi Wo wrote:
> friendly ping
>
> 在 2023/11/2 0:34, WoZ1zh1 写道:
>> In fs/fscache/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 FSCACHE_ASSERT to control it.
Personally it looks good to me, yet we could also turn
them into WARN_ON_ONCE case by case? Anyway, it depends
on how David thinks...
Thanks,
Gao Xiang
>>
>> Signed-off-by: WoZ1zh1 <wozizhi@huawei.com>
>> ---
>> fs/fscache/Kconfig | 10 ++++++++++
>> fs/fscache/internal.h | 2 +-
>> 2 files changed, 11 insertions(+), 1 deletion(-)
>>
>> diff --git a/fs/fscache/Kconfig b/fs/fscache/Kconfig
>> index b313a978ae0a..7ff844038bc3 100644
>> --- a/fs/fscache/Kconfig
>> +++ b/fs/fscache/Kconfig
>> @@ -38,3 +38,13 @@ config FSCACHE_DEBUG
>> enabled by setting bits in /sys/modules/fscache/parameter/debug.
>> See Documentation/filesystems/caching/fscache.rst for more information.
>> +
>> +config FSCACHE_ASSERT
>> + bool "FSCACHE asserts"
>> + default n
>> + depends on FSCACHE
>> + 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/fscache/internal.h b/fs/fscache/internal.h
>> index 1336f517e9b1..951166ed772f 100644
>> --- a/fs/fscache/internal.h
>> +++ b/fs/fscache/internal.h
>> @@ -225,7 +225,7 @@ do { \
>> /*
>> * assertions
>> */
>> -#if 1 /* defined(__KDEBUGALL) */
>> +#ifdef CONFIG_FSCACHE_ASSERT
>> #define ASSERT(X) \
>> do { \
next prev parent reply other threads:[~2023-11-07 12:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-01 16:34 WoZ1zh1
2023-11-07 10:16 ` Zizhi Wo
2023-11-07 12:39 ` Gao Xiang [this message]
2023-11-08 2:25 ` Zizhi Wo
2023-11-30 2:50 ` Zizhi Wo
2024-01-26 2:51 ` Zizhi Wo
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=32abf57d-d3bc-d812-c70f-bba8356162ff@linux.alibaba.com \
--to=hsiangkao@linux.alibaba.com \
--cc=dhowells@redhat.com \
--cc=linux-cachefs@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=wozizhi@huawei.com \
--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®