| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <jbcmfguk7sfgpf4b5jsdjvuz7nzs34yhre3dokehrzm42dj4s7@fbpzrahozjay> Date: Tue, 24 Jun 2025 19:26:28 +0530 From: Brahmajit Das <listout@...tout.xyz> To: "Rafael J. Wysocki" <rafael@...nel.org> Cc: linux-hardening@...r.kernel.org, linux-kernel@...r.kernel.org, linux-acpi@...r.kernel.org, lenb@...nel.org, lv.zheng@...el.com, kees@...nel.org, rui.zhang@...el.com, len.brown@...el.com Subject: Re: [PATCH] ACPI / sysfs: Replace deprecated and unsafe functions with sysfs_emit On 24.06.2025 15:46, Rafael J. Wysocki wrote: > On Tue, Jun 24, 2025 at 3:38 PM Brahmajit Das <listout@...tout.xyz> wrote: > > > > acpi/sysfs.c has many instances of unsafe or deprecated functions such > > as sprintf, strcpy. This patch relaces them with sysfs_emit to safer > > "replaces" > > > alternavtive and better following of kernel API. > > "alternative" > > 1. Have you tested all of the affected interfaces and verified that > they still work as expected after the changes? > 2. While the replaced functions are unsafe in principle, is the usage > of them in any places affected by this patch actually unsafe? > I meant to send this as RFC. Sorry. But I guess the questions still holds. -- Regards, listout
Powered by blists - more mailing lists