From: Lee Jones <lee@kernel.org>
To: lee@kernel.org
Cc: linux-kernel@vger.kernel.org,
Damien Bergamini <damien.bergamini@free.fr>,
Dmitry Bogdanov <d.bogdanov@yadro.com>,
Feng-Hsin Chiang <john453@faraday-tech.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Linus Walleij <linus.walleij@linaro.org>,
linux-usb@vger.kernel.org,
"Martin K. Petersen" <martin.petersen@oracle.com>,
Matthieu CASTET <castet.matthieu@free.fr>,
Pawel Laszczak <pawell@cadence.com>,
Po-Yu Chuang <ratbert.chuang@gmail.com>,
Stanislaw Gruszka <stf_xl@wp.pl>,
Yuan-Hsin Chen <yhchen@faraday-tech.com>
Subject: [PATCH 0/5] usb: Replace {v}snprintf() variants with safer alternatives
Date: Thu, 30 Nov 2023 10:54:34 +0000 [thread overview]
Message-ID: <20231130105459.3208986-1-lee@kernel.org> (raw)
This series is part of an effort to rid {v}snprintf() where possible.
For a far better description of the problem than I could author, see
Jon's write-up on LWN [1] and/or Alex's on the Kernel Self Protection
Project [1].
[0] https://lwn.net/Articles/69419/
[1] https://github.com/KSPP/linux/issues/105
Lee Jones (5):
usb: atm: Remove snprintf() from sysfs call-backs and replace with
sysfs_emit()
usb: cdnsp: Replace snprintf() with the safer scnprintf() variant
usb: fotg210-hcd: Replace snprintf() with the safer scnprintf()
variant
usb: gadget: Remove snprintf() from sysfs call-backs and replace with
sysfs_emit()
usb: gadget: f_tcm: Remove snprintf() from sysfs call-backs and
replace with sysfs_emit()
drivers/usb/atm/ueagle-atm.c | 16 +-
drivers/usb/cdns3/cdnsp-debug.h | 354 ++++++++++++++--------------
drivers/usb/fotg210/fotg210-hcd.c | 12 +-
drivers/usb/gadget/configfs.c | 2 +-
drivers/usb/gadget/function/f_tcm.c | 4 +-
5 files changed, 192 insertions(+), 196 deletions(-)
Cc: Damien Bergamini <damien.bergamini@free.fr>
Cc: Dmitry Bogdanov <d.bogdanov@yadro.com>
Cc: Feng-Hsin Chiang <john453@faraday-tech.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Linus Walleij <linus.walleij@linaro.org>
Cc: linux-usb@vger.kernel.org
Cc: "Martin K. Petersen" <martin.petersen@oracle.com>
Cc: Matthieu CASTET <castet.matthieu@free.fr>
Cc: Pawel Laszczak <pawell@cadence.com>
Cc: Po-Yu Chuang <ratbert.chuang@gmail.com>
Cc: Stanislaw Gruszka <stf_xl@wp.pl>
Cc: Yuan-Hsin Chen <yhchen@faraday-tech.com>
--
2.43.0.rc1.413.gea7ed67945-goog
next reply other threads:[~2023-11-30 10:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-30 10:54 Lee Jones [this message]
2023-11-30 10:54 ` [PATCH 1/5] usb: atm: Remove snprintf() from sysfs call-backs and replace with sysfs_emit() Lee Jones
2023-11-30 10:54 ` [PATCH 2/5] usb: cdnsp: Replace snprintf() with the safer scnprintf() variant Lee Jones
2023-11-30 10:54 ` [PATCH 3/5] usb: fotg210-hcd: " Lee Jones
2023-11-30 14:40 ` David Laight
2023-11-30 14:48 ` Linus Walleij
2023-11-30 10:54 ` [PATCH 4/5] usb: gadget: Remove snprintf() from sysfs call-backs and replace with sysfs_emit() Lee Jones
2023-11-30 10:54 ` [PATCH 5/5] usb: gadget: f_tcm: " Lee Jones
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=20231130105459.3208986-1-lee@kernel.org \
--to=lee@kernel.org \
--cc=castet.matthieu@free.fr \
--cc=d.bogdanov@yadro.com \
--cc=damien.bergamini@free.fr \
--cc=gregkh@linuxfoundation.org \
--cc=john453@faraday-tech.com \
--cc=linus.walleij@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=pawell@cadence.com \
--cc=ratbert.chuang@gmail.com \
--cc=stf_xl@wp.pl \
--cc=yhchen@faraday-tech.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