Re: [PATCH] greybus: fw-management: Replace strncpy with strlcpy

2017-02-21 Thread Tobin Harding
On Thu, Feb 16, 2017, at 03:03 PM, Viresh Kumar wrote:
> Hi Tobin,
> 
> On Wed, Feb 15, 2017 at 5:39 AM, Tobin C. Harding  wrote:
> > Greybus currently uses strncpy() coupled with a check for '\0' on the
> > last byte of various buffers. strncpy() is passed size parameter equal
> > to the size of the buffer in all instances. If the source string is
> > larger than the destination buffer the check catches this and, after
> > logging the error, returns an error value. In one instance the
> > immediate return is not required. Using strncpy() with the manual check
> > adds code that could be removed by the use of strlcpy(), although truncation
> > then needs to be checked.
> >
> > Replace calls to strncpy() with calls to strlcpy(). Replace null
> > termination checks  with checks for truncated string. Add log message
> > if string is truncated but do not return an error code.
> >
> > Signed-off-by: Tobin C. Harding 
> > ---
> >  drivers/staging/greybus/fw-management.c | 59 
> > +++--
> >  1 file changed, 19 insertions(+), 40 deletions(-)
> >
> > diff --git a/drivers/staging/greybus/fw-management.c 
> > b/drivers/staging/greybus/fw-management.c
> > index 3cd6cf0..1cd5a45 100644
> > --- a/drivers/staging/greybus/fw-management.c
> > +++ b/drivers/staging/greybus/fw-management.c
> > @@ -108,6 +108,7 @@ static int 
> > fw_mgmt_interface_fw_version_operation(struct fw_mgmt *fw_mgmt,
> > struct gb_connection *connection = fw_mgmt->connection;
> > struct gb_fw_mgmt_interface_fw_version_response response;
> > int ret;
> > +   size_t len;
> >
> > ret = gb_operation_sync(connection,
> > GB_FW_MGMT_TYPE_INTERFACE_FW_VERSION, NULL, 
> > 0,
> > @@ -121,18 +122,11 @@ static int 
> > fw_mgmt_interface_fw_version_operation(struct fw_mgmt *fw_mgmt,
> > fw_info->major = le16_to_cpu(response.major);
> > fw_info->minor = le16_to_cpu(response.minor);
> >
> > -   strncpy(fw_info->firmware_tag, response.firmware_tag,
> > +   len = strlcpy(fw_info->firmware_tag, response.firmware_tag,
> > GB_FIRMWARE_TAG_MAX_SIZE);
> > -
> > -   /*
> > -* The firmware-tag should be NULL terminated, otherwise throw 
> > error but
> > -* don't fail.
> > -*/
> > -   if (fw_info->firmware_tag[GB_FIRMWARE_TAG_MAX_SIZE - 1] != '\0') {
> > +   if (len >= GB_FIRMWARE_TAG_MAX_SIZE)
> 
> I am not sure if the new code you have written is any better than what
> was already there.
> We still have a strcpy variant followed by a check. What has improved ?
> 
> 
> > @@ -142,6 +136,7 @@ static int fw_mgmt_load_and_validate_operation(struct 
> > fw_mgmt *fw_mgmt,
> >  {
> > struct gb_fw_mgmt_load_and_validate_fw_request request;
> > int ret;
> > +   size_t len;
> >
> > if (load_method != GB_FW_LOAD_METHOD_UNIPRO &&
> > load_method != GB_FW_LOAD_METHOD_INTERNAL) {
> > @@ -151,16 +146,10 @@ static int fw_mgmt_load_and_validate_operation(struct 
> > fw_mgmt *fw_mgmt,
> > }
> >
> > request.load_method = load_method;
> > -   strncpy(request.firmware_tag, tag, GB_FIRMWARE_TAG_MAX_SIZE);
> > -
> > -   /*
> > -* The firmware-tag should be NULL terminated, otherwise throw 
> > error and
> > -* fail.
> > -*/
> > -   if (request.firmware_tag[GB_FIRMWARE_TAG_MAX_SIZE - 1] != '\0') {
> > -   dev_err(fw_mgmt->parent, "load-and-validate: firmware-tag 
> > is not NULL terminated\n");
> > -   return -EINVAL;
> 
> Sorry but the error returns here and at other places were very
> intentional. I
> wrote them to make sure the protocol is followed properly, and the other
> side doesn't break it.
> 
> So far its a NAK from me.
> 
> --
> viresh

thanks for taking the time to review Viresh. I'll drop this patch.

thanks,
Tobin.
___
devel mailing list
de...@linuxdriverproject.org
http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel


Re: [PATCH] staging: lustre: llite: kzalloc/copy_to_user to memdup_user

2016-05-22 Thread Tobin Harding
On Sun, May 22, 2016 at 03:25:38PM -0700, Greg Kroah-Hartman wrote:
> On Mon, May 23, 2016 at 07:49:29AM +1000, Tobin C Harding wrote:
> > kzalloc call followed by copy_to_user can be replaced by call to 
> > memdup_user.
> > 
> > Signed-off-by: Tobin C Harding 
>
> Why did you send this twice?

Because I'm a git send-email amateur.

> > ---
> >  drivers/gpu/drm/gma500/gma_display.c  |  2 +-
> >  drivers/staging/lustre/lustre/llite/dir.c | 22 +++---
> >  2 files changed, 8 insertions(+), 16 deletions(-)
> > 
> > diff --git a/drivers/gpu/drm/gma500/gma_display.c 
> > b/drivers/gpu/drm/gma500/gma_display.c
> > index 5bf765d..8a1fb25 100644
> > --- a/drivers/gpu/drm/gma500/gma_display.c
> > +++ b/drivers/gpu/drm/gma500/gma_display.c
> > @@ -285,7 +285,7 @@ void gma_crtc_dpms(struct drm_crtc *crtc, int mode)
> >  
> > /* Wait for vblank for the disable to take effect */
> > gma_wait_for_vblank(dev);
> > -
> > +l
>
> What?  What does this have to do with lustre?

Turns out I'm a git amateur in general, the gma_display changes should not have
been committed on this branch.

> It's kind of obvious you didn't build this :(

Epic fail.

> Please be more careful in the future.
>
> greg k-h

I am humbly attempting to learn the way of kernel dev, thank you for your
patience, I will endeavor to be more careful.

Regards,
Tobin Harding.
___
devel mailing list
de...@linuxdriverproject.org
http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel