From: Bart Van Assche <bvanassche@acm.org>
To: target-devel@vger.kernel.org
Subject: Re: [PATCH v3 3/4] target: add device vendor_id configfs attribute
Date: Wed, 28 Nov 2018 16:08:30 +0000 [thread overview]
Message-ID: <1543421310.185366.96.camel@acm.org> (raw)
In-Reply-To: <20181119210636.22979-4-ddiss@suse.de>
On Wed, 2018-11-28 at 16:37 +-0100, David Disseldorp wrote:
+AD4 On Tue, 20 Nov 2018 19:00:57 +-0100, David Disseldorp wrote:
+AD4
+AD4 +AD4 +AD4 +AD4 +- strncpy(buf, page, sizeof(buf))+ADs
+AD4 +AD4 +AD4
+AD4 +AD4 +AD4 Isn't strncpy() deprecated? How about using strlcpy() instead?
+AD4 +AD4
+AD4 +AD4 Will change to use strlcpy in the next round.
+AD4
+AD4 Just a follow up here. I think it's safer to retain strncpy() in this
+AD4 function for the purpose of zero filling. scsi+AF8-dump+AF8-inquiry() and
+AD4 target+AF8-stat+AF8-lu+AF8-vend+AF8-show() walk the entire length of the t10+AF8-wwn.vendor
+AD4 buffer.
How about adding a comment about above struct t10+AF8-wwn that vendor+AFsAXQ, model+AFsAXQ
and revision+AFsAXQ in that structure may but do not have to be terminated with a
trailing '+AFw-0' and also that unit+AF8-serial+AFsAXQ is '+AFw-0'-terminated?
It would make me happy if the size of the character arrays in that structure
would be increased by one and if the target code would be modified such that
these strings are always '+AFw-0'-terminated.
Thanks,
Bart.
next prev parent reply other threads:[~2018-11-28 16:08 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-19 21:06 [PATCH v3 3/4] target: add device vendor_id configfs attribute David Disseldorp
2018-11-20 17:24 ` Bart Van Assche
2018-11-20 18:00 ` David Disseldorp
2018-11-20 18:03 ` Bart Van Assche
2018-11-28 15:37 ` David Disseldorp
2018-11-28 16:08 ` Bart Van Assche [this message]
2018-11-28 16:28 ` David Disseldorp
2018-11-28 16:36 ` Bart Van Assche
2018-11-28 16:44 ` David Disseldorp
2018-11-28 16:47 ` Bart Van Assche
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=1543421310.185366.96.camel@acm.org \
--to=bvanassche@acm.org \
--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 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.