From: Guenter Roeck <linux@roeck-us.net>
To: Huacai Chen <chenhuacai@kernel.org>
Cc: Xi Ruoyao <xry111@xry111.site>,
loongarch@lists.linux.dev, WANG Xuerui <kernel@xen0n.name>,
Alexander Potapenko <glider@google.com>,
Marco Elver <elver@google.com>,
Dmitry Vyukov <dvyukov@google.com>,
kasan-dev@googlegroups.com
Subject: Re: Kernel BUG with loongarch and CONFIG_KFENCE and CONFIG_DEBUG_SG
Date: Fri, 29 Mar 2024 09:32:58 -0700 [thread overview]
Message-ID: <0e754d23-b2b0-4469-8deb-2e42796b30b0@roeck-us.net> (raw)
In-Reply-To: <CAAhV-H7Po9B5WQMAUfB9jUmGAVit0+NiDbhV4jG5xKJUbWEBOw@mail.gmail.com>
On 3/28/24 19:17, Huacai Chen wrote:
> Hi, Guenter,
>
> Thank you for your report, we find there are several kfence-related
> problems, and we have solved part of them.
> Link: https://github.com/chenhuacai/linux/commits/loongarch-next
>
Thanks a lot for the update.
A note regarding the patches in that tree, not related to the kfence
problem: I don't immediately see why the hwmon driver should reside
outside drivers/hwmon/, and hwmon_device_register_with_groups() is
deprecated and should not be used in new drivers.
On top of that, shutting off the system in case of thermal issues
is not the responsibility of a hardware monitoring driver.
That functionality should be handled by the thermal subsystem.
Thanks,
Guenter
prev parent reply other threads:[~2024-03-29 16:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-27 19:11 Kernel BUG with loongarch and CONFIG_KFENCE and CONFIG_DEBUG_SG Guenter Roeck
2024-03-27 19:33 ` Xi Ruoyao
2024-03-27 23:38 ` Guenter Roeck
2024-03-29 2:17 ` Huacai Chen
2024-03-29 16:32 ` Guenter Roeck [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=0e754d23-b2b0-4469-8deb-2e42796b30b0@roeck-us.net \
--to=linux@roeck-us.net \
--cc=chenhuacai@kernel.org \
--cc=dvyukov@google.com \
--cc=elver@google.com \
--cc=glider@google.com \
--cc=kasan-dev@googlegroups.com \
--cc=kernel@xen0n.name \
--cc=loongarch@lists.linux.dev \
--cc=xry111@xry111.site \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.