From: Bart Van Assche <bvanassche@acm.org>
To: Charles Bertsch <cbertsch@cox.net>,
justinstitt@google.com, linux-scsi@vger.kernel.org,
MPT-FusionLinux.pdl@broadcom.com
Subject: Re: startup BUG at lib/string_helpers.c from scsi fusion mptsas
Date: Wed, 3 Apr 2024 16:20:47 -0700 [thread overview]
Message-ID: <2a17e63b-6567-4d6c-abe2-309304bc9ea2@acm.org> (raw)
In-Reply-To: <5445ba0f-3e27-4d43-a9ba-0cc22ada2fce@cox.net>
On 4/1/24 3:43 PM, Charles Bertsch wrote:
> 45e833f0e5bb1985721d4a52380db47c5dad2d49 is the first bad commit
> commit 45e833f0e5bb1985721d4a52380db47c5dad2d49
> Author: Justin Stitt <justinstitt@google.com>
> Date: Tue Oct 3 22:15:45 2023 +0000
>
> scsi: message: fusion: Replace deprecated strncpy() with strscpy()
>
> strncpy() is deprecated for use on NUL-terminated destination
> strings [1]
> and as such we should prefer more robust and less ambiguous string
> interfaces.
Justin, can you please take a look at this email and its attachments?
Thanks,
Bart.
next prev parent reply other threads:[~2024-04-03 23:20 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-01 22:43 startup BUG at lib/string_helpers.c from scsi fusion mptsas Charles Bertsch
2024-04-03 23:20 ` Bart Van Assche [this message]
2024-04-04 19:58 ` Justin Stitt
2024-04-04 21:38 ` Justin Stitt
2024-04-04 21:53 ` James Bottomley
2024-04-04 22:04 ` Justin Stitt
2024-04-04 22:29 ` James Bottomley
2024-04-04 22:33 ` James Bottomley
2024-04-04 22:43 ` Martin K. Petersen
2024-04-04 22:47 ` Justin Stitt
2024-04-04 23:39 ` Kees Cook
2024-04-05 0:10 ` Justin Stitt
2024-04-05 0:12 ` Justin Stitt
2024-04-04 23:57 ` Kees Cook
2024-04-06 20:42 ` Charles Bertsch
2024-04-08 19:59 ` Justin Stitt
2024-04-08 23:19 ` Kees Cook
2024-04-10 20:51 ` Justin Stitt
2024-04-10 21:14 ` Charles Bertsch
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=2a17e63b-6567-4d6c-abe2-309304bc9ea2@acm.org \
--to=bvanassche@acm.org \
--cc=MPT-FusionLinux.pdl@broadcom.com \
--cc=cbertsch@cox.net \
--cc=justinstitt@google.com \
--cc=linux-scsi@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