From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Konstantin Shelekhin <k.shelekhin@yadro.com>
Cc: "Martin K . Petersen" <martin.petersen@oracle.com>,
target-devel@vger.kernel.org, linux-scsi@vger.kernel.org,
linux@yadro.com
Subject: Re: [PATCH 0/2] scsi: target: iscsi: Get rid of sprintf in iscsi_target_configfs.c
Date: Mon, 7 Aug 2023 22:50:27 -0400 [thread overview]
Message-ID: <169146270849.4040832.10944640625308030970.b4-ty@oracle.com> (raw)
In-Reply-To: <20230722152657.168859-1-k.shelekhin@yadro.com>
On Sat, 22 Jul 2023 18:26:36 +0300, Konstantin Shelekhin wrote:
> This patch series cleanses iscsi_target_configfs.c of sprintf usage. The
> first patch fixes the real problem, the second just makes sure we are on
> the safe side from now on.
>
> I've reproduced the issue fixed in the first patch by utilizing this
> cool thing:
>
> [...]
Applied to 6.6/scsi-queue, thanks!
[1/2] scsi: target: iscsi: Fix buffer overflow in lio_target_nacl_info_show
https://git.kernel.org/mkp/scsi/c/801f287c93ff
[2/2] scsi: target: iscsi: Stop using sprintf in iscsi_target_configfs.c
https://git.kernel.org/mkp/scsi/c/c0431feb0a75
--
Martin K. Petersen Oracle Linux Engineering
prev parent reply other threads:[~2023-08-08 2:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-22 15:26 [PATCH 0/2] scsi: target: iscsi: Get rid of sprintf in iscsi_target_configfs.c Konstantin Shelekhin
2023-07-22 15:26 ` [PATCH 1/2] scsi: target: iscsi: Fix buffer overflow in lio_target_nacl_info_show Konstantin Shelekhin
2023-07-22 15:26 ` [PATCH 2/2] scsi: target: iscsi: Stop using sprintf in iscsi_target_configfs.c Konstantin Shelekhin
2023-07-31 16:13 ` [PATCH 0/2] scsi: target: iscsi: Get rid of " Martin K. Petersen
2023-08-08 2:50 ` Martin K. Petersen [this message]
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=169146270849.4040832.10944640625308030970.b4-ty@oracle.com \
--to=martin.petersen@oracle.com \
--cc=k.shelekhin@yadro.com \
--cc=linux-scsi@vger.kernel.org \
--cc=linux@yadro.com \
--cc=target-devel@vger.kernel.org \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).