[PATCH 1/1] hv: Use only one receive buffer and kmalloc on initialize

Greg KH
Mon, 13 Dec 2010 18:34:48 -0000

On Mon, Dec 13, 2010 at 09:45:50AM -0800, Hank Janssen
wrote:
> Correct issue with not checking kmalloc return value.
> This fix now only uses one receive buffer for all hv_utils
> channels, and will do only one kmalloc on init and will return
> with a -ENOMEM if kmalloc fails on initialize.
>
> Thanks to Evgeniy Polyakov <zbr at ioremap.net> for pointing this
out.
> And thanks to Jesper Juhl <jj at chaosbits.net> and Ky Srinivasan
> <ksrinivasan at novell.com> for suggesting a better implementation of
> my original patch.
>
> Signed-off-by: Haiyang Zhang <haiyangz at microsoft.com>
> Signed-off-by: Hank Janssen <hjanssen at microsoft.com>
> Cc:Evgeniy Polyakov <zbr at ioremap.net>
> Cc:Jesper Juhl <jj at chaosbits.net>
> Cc:Ky Srinivasan <ksrinivasan at novell.com>
>
> ---
>  drivers/staging/hv/hv_utils.c |   68
+++++++++++++++++++---------------------
>  1 files changed, 32 insertions(+), 36 deletions(-)
>
> diff --git a/drivers/staging/hv/hv_utils.c b/drivers/staging/hv/hv_utils.c
> index 53e1e29..4ed4ab8 100644
> --- a/drivers/staging/hv/hv_utils.c
> +++ b/drivers/staging/hv/hv_utils.c
> @@ -38,12 +38,15 @@
>  #include "vmbus_api.h"
>  #include "utils.h"
>
> +/*
> + * Buffer used to receive packets from Hyper-V
> + */
> +static u8 *chan_buf;

One buffer is nicer, yes, but what's controlling access to this buffer?
You use it in multiple functions, and what's to say those functions
can't be called at the same time on different cpus?  So, shouldn't you
either have some locking for access to the buffer, or have a
per-function buffer instead?

And if you have a per-function buffer, again, you might need to control
access to it as the functions could be called multiple times at the same
time, right?

thanks,

greg k-h