public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Willy Tarreau <w@1wt.eu>
To: David Newall <davidn@davidnewall.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Greg Kroah-Hartman <greg@kroah.com>
Subject: Re: [PATCH] 2.4: Back-port of pl2303.c from 2.6.23.14
Date: Sat, 2 Feb 2008 08:44:06 +0100	[thread overview]
Message-ID: <20080202074406.GA31516@1wt.eu> (raw)
In-Reply-To: <479A83DE.8020002@davidnewall.com>

Hi David,

I've CC'd Greg, author of the driver.

On Sat, Jan 26, 2008 at 11:20:38AM +1030, David Newall wrote:
> I experienced major major data loss on a PL-2303 USB-serial converter
> under 2.4.36, which I remedied by back-porting the pl2303.c from the
> latest 2.6 kernel tree.

I'm OK to merge your work in 2.4.36.1 if it fixes bugs for you. I would have
hoped a little more feedback from other users, but let's face it, people
using USB are most often on desktops running 2.6.

I've noticed your other mail about the buffer overflow (which does not
sound like an overflow as we call it in security terms, so it's not
critical). It would be better to merge your work with the fix in it,
but I'll wait for the fix to be in 2.6 first (so that people upgrading
from 2.4 to 2.6 never experience a regression).

If this buffer overflow was not present in 2.4 driver but only in 2.6
(and in the backport), I'd rather wait in order not to break behaviour
for current users of the driver. If both have the same bug, and if Greg
is OK, then let's merge your work as a first evolution before a common
fix.

Based on the above conditions, I'd like you to tell Greg and I if you
consider it worth to merge this backport in 2.4 now. From my point of
view, your work looks OK but I want your feedback as a user (and not
as the backporter), then Greg's approval.

Thanks,
Willy


  reply	other threads:[~2008-02-02  8:26 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-26  0:50 [PATCH] 2.4: Back-port of pl2303.c from 2.6.23.14 David Newall
2008-02-02  7:44 ` Willy Tarreau [this message]
2008-02-02 13:11   ` David Newall
2008-02-02 14:57     ` Willy Tarreau
2008-02-21 20:21     ` [PATCH] 2.4: Back-port of pl2303.c from 2.6.24.1 David Newall
2008-02-21 20:30       ` David Newall
2008-02-21 20:36       ` Greg KH
2008-02-21 21:00         ` Willy Tarreau
2008-02-21 21:33           ` Greg KH
2008-02-22  1:33             ` David Newall
2008-02-22 10:02               ` Willy Tarreau
2008-02-22 17:47                 ` Gene Heskett
2008-03-19 14:24                   ` David Newall

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=20080202074406.GA31516@1wt.eu \
    --to=w@1wt.eu \
    --cc=davidn@davidnewall.com \
    --cc=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.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