From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:46486) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aLMLN-0000Mr-3b for qemu-devel@nongnu.org; Mon, 18 Jan 2016 21:48:29 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1aLMLM-0004oL-7O for qemu-devel@nongnu.org; Mon, 18 Jan 2016 21:48:29 -0500 References: <1452764448-17953-1-git-send-email-mst@redhat.com> <569C8B29.4040300@redhat.com> <569C9E87.2030001@redhat.com> <569CB702.1060803@redhat.com> From: Jason Wang Message-ID: <569DA3E6.5020407@redhat.com> Date: Tue, 19 Jan 2016 10:48:06 +0800 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] [Qemu-arm] [PATCH] cadence_gem: fix buffer overflow List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Peter Maydell Cc: "Michael S. Tsirkin" , Alistair Francis , "qemu-devel@nongnu.org Developers" , Prasad Pandit , Peter Crosthwaite , qemu-arm , =?UTF-8?B?5YiY5Luk?= On 01/18/2016 06:06 PM, Peter Maydell wrote: > On 18 January 2016 at 09:57, Jason Wang wrote: >> Thanks for the pointer. >> >> In section 16.1.5, it said >> >> "Jumbo frames are not supported." >> >> So it was in fact not an unimplemented feature? > I have a vague feeling from the last time I looked at something like > this that what often happens is the hardware happily goes on dumping > data out on the wire but this is a violation of the ethernet protocol, > ie a guest error. But I'm no ethernet expert... > > thanks > -- PMM > I think it's a guest error (unless we find a guest/driver that depends on this). Anyway, fixing the buffer overflow should be fine.