[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20141021141724.GM23154@mwanda>
Date: Tue, 21 Oct 2014 17:17:24 +0300
From: Dan Carpenter <dan.carpenter@...cle.com>
To: Matej Mužila <mmuzila@...hat.com>
Cc: One Thousand Gnomes <gnomes@...rguk.ukuu.org.uk>,
devel@...uxdriverproject.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 1/3] tools: hv: fcopy_daemon: Check buffer limits
On Tue, Oct 21, 2014 at 02:59:58PM +0200, Matej Mužila wrote:
> > sizeof(__u8) is by definition 1 so it's perhaps surplus ?
> Now the size is now determined from the structure definition in
> include/uapi/linux/hyperv.h
>
> > - C style comments for coding style
> Fixed
>
> > Also your patch block is devoid of a few thins like the file name...
> I'm sorry, the (missing) filename mistake occured in copy-paste process.
>
Copy and paste is very error prone...
>
> Here is the patch as it (I hope) should look like:
This patch looks good, but please resend it as a proper v2 patch.
https://www.google.com/search?q=how+to+send+a+v2+patch
> ---
> From: Matej Mužila <mmuzila@...hat.com>
>
> Check if cpmsg->size is in limits of DATA_FRAGMENT
>
> Signed-off-by: Matej Mužila <mmuzila@...hat.com>
> ---
> If corrupted data are read from /dev/vmbus/hv_fcopy, pwrite can
> read from memory outside of the buffer (defined at line 138).
> Added check.
Put this information in the patch description and not beyond the cut
off. That information is useful.
The cut off is meant for meta comentary to say what changed between v1
and v2 etc, which is nice to have but we don't want to preserve it.
regards,
dan carpenter
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists