linux-kernel - Re: [PATCH v1] platform/chrome: use sysfs

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <ZfK2tmJ3c1Td2lVR@google.com>
Date: Thu, 14 Mar 2024 16:35:02 +0800
From: Tzung-Bi Shih <tzungbi@...nel.org>
To: Ai Chao <aichao@...inos.cn>
Cc: bleung@...omium.org, chrome-platform@...ts.linux.dev,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH v1] platform/chrome: use sysfs_emit() instead of sprintf()

On Thu, Mar 14, 2024 at 01:28:28PM +0800, Ai Chao wrote:
> Follow the advice in Documentation/filesystems/sysfs.rst:
> show() should only use sysfs_emit() or sysfs_emit_at() when formatting
> the value to be returned to user space.

It seems we overlooked the case when handling [1].  Will queue the patch
after for-next rebased to next -rc1.

[1] https://patchwork.kernel.org/project/chrome-platform/patch/202212021656040995199@zte.com.cn/