Thread (17 messages) 17 messages, 7 authors, 2020-11-23

Re: [RFC] MAINTAINERS tag for cleanup robot

From: Joe Perches <joe@perches.com>
Date: 2020-11-22 18:24:18
Also in: alsa-devel, amd-gfx, bpf, dri-devel, intel-gfx, keyrings, kvm, linux-acpi, linux-bluetooth, linux-crypto, linux-fsdevel, linux-hyperv, linux-media, linux-nfs, linux-omap, linux-scsi, linux-usb, linux-wireless, lkml, netdev, netfilter-devel, platform-driver-x86, xen-devel

On Sun, 2020-11-22 at 08:49 -0800, James Bottomley wrote:
We can enforce sysfs_emit going forwards
using tools like checkpatch
It's not really possible for checkpatch to find or warn about
sysfs uses of sprintf. checkpatch is really just a trivial
line-by-line parser and it has no concept of code intent.

It just can't warn on every use of the sprintf family.
There are just too many perfectly valid uses.
but there's no benefit and a lot of harm to
be done by trying to churn the entire tree
Single uses of sprintf for sysfs is not really any problem.

But likely there are still several possible overrun sprintf/snprintf
paths in sysfs.  Some of them are very obscure and unlikely to be
found by a robot as the logic for sysfs buf uses can be fairly twisty.

But provably correct conversions IMO _should_ be done and IMO churn
considerations should generally have less importance.


Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help