From: Mariia Nikitash <nikitash.mariiaw@gmail.com>
To: anil.gurumurthy@qlogic.com, sudarsana.kalluru@qlogic.com,
James.Bottomley@HansenPartnership.com, mkp@kernel.org
Cc: linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-hardening@vger.kernel.org, morbo@google.com,
kees@kernel.org, justinstitt@google.com,
codemender-patching+linux@google.com,
Mariia Nikitash <nikitash.mariiaw@gmail.com>
Subject: [PATCH v2 0/2] scsi: bfa: Replace strlcat() in symbolic name construction
Date: Mon, 28 Sep 2026 02:00:28 -0700 [thread overview]
Message-ID: <20260928090031.712418-1-nikitash.mariiaw@gmail.com> (raw)
This series replaces the strlcat() uses in BFA symbolic name
construction with snprintf().
Patch 1 converts bfa_fcs_fabric_nsymb_init().
Patch 2 converts bfa_fcs_fabric_psymb_init().
---
Changes since v1:
- Split the BFA changes out of the original cross-subsystem series.
- Patch 1: no code changes.
- Patch 2: use a single snprintf() call for both host_os_patch cases
and drop the explicit final NUL assignment.
Original series:
https://lore.kernel.org/all/20260915081910.4142719-1-morbo@google.com/
Original bfa_fcs_fabric_psymb_init() patch:
https://lore.kernel.org/all/20260915081910.4142719-8-morbo@google.com/
Bill Wendling (2):
scsi: bfa: Use snprintf() in bfa_fcs_fabric_nsymb_init()
scsi: bfa: Use snprintf() in bfa_fcs_fabric_psymb_init()
drivers/scsi/bfa/bfa_fcs.c | 88 ++++++++------------------------------
1 file changed, 17 insertions(+), 71 deletions(-)
--
2.43.0
next reply other threads:[~2026-09-28 9:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-28 9:00 Mariia Nikitash [this message]
2026-09-28 9:00 ` [PATCH v2 1/2] scsi: bfa: Use snprintf() in bfa_fcs_fabric_nsymb_init() Mariia Nikitash
2026-09-28 17:36 ` Bart Van Assche
2026-09-28 9:00 ` [PATCH v2 2/2] scsi: bfa: Use snprintf() in bfa_fcs_fabric_psymb_init() Mariia Nikitash
2026-09-28 17:38 ` Bart Van Assche
2026-10-06 2:07 ` [PATCH v2 0/2] scsi: bfa: Replace strlcat() in symbolic name construction 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=20260928090031.712418-1-nikitash.mariiaw@gmail.com \
--to=nikitash.mariiaw@gmail.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=anil.gurumurthy@qlogic.com \
--cc=codemender-patching+linux@google.com \
--cc=justinstitt@google.com \
--cc=kees@kernel.org \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=mkp@kernel.org \
--cc=morbo@google.com \
--cc=sudarsana.kalluru@qlogic.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.