Did you see Daniel's other reply? (attached) -Paul -----Original Message----- From: SPDK [mailto:spdk-bounces@lists.01.org] On Behalf Of Meneghini, John Sent: Wednesday, January 31, 2018 4:02 PM To: Storage Performance Development Kit <spdk(a)lists.01.org&gt; Subject: Re: [SPDK] strcpy forbidden How about using stpncpy or strncpy? This should be supported instead of strcpy. The stpncpy() and strncpy() functions copy at most len characters from src into dst. If src is less than len characters long, the remainder of dst is filled with `\0' characters. Otherwise, dst is not terminated. /John On 1/29/18, 4:50 PM, "SPDK on behalf of Luse, Paul E" <spdk-bounces(a)lists.01.org on behalf of paul.e.luse(a)intel.com&gt; wrote: LOL, it got me too Stephen. To avoid buffer overflow attacks. Use strdup instead.... -----Original Message----- From: SPDK [mailto:spdk-bounces@lists.01.org] On Behalf Of Stephen Bates Sent: Monday, January 29, 2018 2:48 PM To: Storage Performance Development Kit <spdk(a)lists.01.org&gt; Subject: [SPDK] strcpy forbidden Hi All I am sure there is a really good reason why strcpy is forbidden by check_format.sh but I cannot find it documented anywhere. Can someone enlighten me and point to the documentation if it exists? Cheers Stephen _______________________________________________ SPDK mailing list SPDK(a)lists.01.org https://lists.01.org/mailman/listinfo/spdk _______________________________________________ SPDK mailing list SPDK(a)lists.01.org https://lists.01.org/mailman/listinfo/spdk _______________________________________________ SPDK mailing list SPDK(a)lists.01.org https://lists.01.org/mailman/listinfo/spdk