From: Samuel Thibault <samuel.thibault@ens-lyon.org>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] usb-serial: Fix memory overruns with usb serial emulation
Date: Wed, 17 Sep 2008 22:01:02 +0200 [thread overview]
Message-ID: <20080917200102.GB4204@implementation> (raw)
In-Reply-To: <48D0F007.1070903@windriver.com>
Jason Wessel, le Wed 17 Sep 2008 06:54:47 -0500, a écrit :
> * Remove the unused send_buf variable and its constant.
>
> * Fix a math error
> The variables recv_ptr and recv_used are not large enough to hold
> the constant 384, which causes data corruption when the pointer is
> reset with: s->recv_ptr = (s->recv_ptr + len) % RECV_BUF;
>
> Signed-off-by: Jason Wessel <jason.wessel@windriver.com>
Acked-by: Samuel Thibault <samuel.thibault@ens-lyon.org>
Samuel
next prev parent reply other threads:[~2008-09-17 20:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-17 5:00 [Qemu-devel] [PATCH] usb-serial: Fix memory overruns with usb serial emulation Jason Wessel
2008-09-17 10:18 ` Paul Brook
2008-09-17 10:38 ` Paul Brook
2008-09-17 11:54 ` Jason Wessel
2008-09-17 20:01 ` Samuel Thibault [this message]
2008-09-17 22:04 ` Aurelien Jarno
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=20080917200102.GB4204@implementation \
--to=samuel.thibault@ens-lyon.org \
--cc=qemu-devel@nongnu.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).