linux-um archives
 help / color / mirror / Atom feed
From: Jeff Dike <jdike@addtoit.com>
To: Doug Dumitru <doug@easyco.com>
Cc: user-mode-linux-devel@lists.sourceforge.net
Subject: [uml-devel] Re: Patch for buffer overrun in serial/console device logic
Date: Sat, 08 Nov 2003 20:53:25 -0500	[thread overview]
Message-ID: <200311090153.hA91rPiR003433@ccure.user-mode-linux.org> (raw)
In-Reply-To: Your message of "Tue, 07 Oct 2003 11:55:40 PDT." <3F830C2C.8010308@easyco.com>

doug@easyco.com said:
> After a lot of looking, it appears that the line_write routine in
> line.c  does not check to see if the buffer has enough room.  The
> buffer_data(...) routine does not appear to check for available space
> at  all and just overwrites old data. 

Indeed.  Thanks for chasing this down.  I fixed it, but in a different way.

				Jeff



-------------------------------------------------------
This SF.Net email sponsored by: ApacheCon 2003,
16-19 November in Las Vegas. Learn firsthand the latest
developments in Apache, PHP, Perl, XML, Java, MySQL,
WebDAV, and more! http://www.apachecon.com/
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel

      parent reply	other threads:[~2003-11-09  1:45 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-07 18:55 [uml-devel] Patch for buffer overrun in serial/console device logic Doug Dumitru
2003-10-07 21:51 ` [uml-devel] " Jeff Dike
2003-10-07 22:31   ` Doug Dumitru
2003-10-11  1:49     ` Jeff Dike
2003-10-12  3:39       ` Doug Dumitru
2003-10-13 20:43       ` BlaisorBlade
     [not found] ` <p05111b00bba97b88a68d@[10.96.96.13]>
2003-10-08 16:25   ` [uml-devel] " Doug Dumitru
2003-11-09  1:53 ` Jeff Dike [this message]

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=200311090153.hA91rPiR003433@ccure.user-mode-linux.org \
    --to=jdike@addtoit.com \
    --cc=doug@easyco.com \
    --cc=user-mode-linux-devel@lists.sourceforge.net \
    /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