From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Lee Jones <lee@kernel.org>
Cc: jejb@linux.ibm.com, martin.petersen@oracle.com,
linux-kernel@vger.kernel.org, linux-scsi@vger.kernel.org,
Adam Radford <aradford@gmail.com>,
Adaptec OEM Raid Solutions <aacraid@microsemi.com>,
Andre Hedrick <andre@suse.com>, de Melo <acme@conectiva.com.br>,
Joel Jacobson <linux@3ware.com>,
"PMC-Sierra, Inc" <aacraid@pmc-sierra.com>,
Richard Hirst <rhirst@linuxcare.com>
Subject: Re: [PATCH 0/5] scsi: Replace {v}snprintf() variants with safer alternatives
Date: Mon, 29 Jan 2024 20:35:28 -0500 [thread overview]
Message-ID: <yq1le87txgx.fsf@ca-mkp.ca.oracle.com> (raw)
In-Reply-To: <20240111131732.1815560-1-lee@kernel.org> (Lee Jones's message of "Thu, 11 Jan 2024 13:17:21 +0000")
Lee,
> 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].
Applied to 6.9/scsi-staging, thanks!
--
Martin K. Petersen Oracle Linux Engineering
next prev parent reply other threads:[~2024-01-30 1:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-11 13:17 [PATCH 0/5] scsi: Replace {v}snprintf() variants with safer alternatives Lee Jones
2024-01-11 13:17 ` [PATCH 1/5] scsi: 3w-9xxx: Remove snprintf() from sysfs call-backs and replace with sysfs_emit() Lee Jones
2024-01-11 13:17 ` [PATCH 2/5] scsi: 3w-sas: " Lee Jones
2024-01-11 13:17 ` [PATCH 3/5] scsi: 3w-xxxx: " Lee Jones
2024-01-11 13:17 ` [PATCH 4/5] scsi: 53c700: " Lee Jones
2024-01-11 13:17 ` [PATCH 5/5] scsi: aacraid: aachba: Replace snprintf() with the safer scnprintf() variant Lee Jones
2024-01-30 1:35 ` Martin K. Petersen [this message]
2024-02-06 2:07 ` [PATCH 0/5] scsi: Replace {v}snprintf() variants with safer alternatives Martin K. Petersen
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=yq1le87txgx.fsf@ca-mkp.ca.oracle.com \
--to=martin.petersen@oracle.com \
--cc=aacraid@microsemi.com \
--cc=aacraid@pmc-sierra.com \
--cc=acme@conectiva.com.br \
--cc=andre@suse.com \
--cc=aradford@gmail.com \
--cc=jejb@linux.ibm.com \
--cc=lee@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=linux@3ware.com \
--cc=rhirst@linuxcare.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 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.