linux-kernel - Re: [PATCH] 2.4: Back-port of pl2303.c from 2.6.24.1

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-id: <200802221247.48178.gene.heskett@gmail.com>
Date:	Fri, 22 Feb 2008 12:47:47 -0500
From:	Gene Heskett <gene.heskett@...il.com>
To:	Willy Tarreau <w@....eu>
Cc:	David Newall <davidn@...idnewall.com>, Greg KH <greg@...ah.com>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] 2.4: Back-port of pl2303.c from 2.6.24.1

On Friday 22 February 2008, Willy Tarreau wrote:
>On Fri, Feb 22, 2008 at 12:03:50PM +1030, David Newall wrote:
>> Greg KH wrote:
>> > On Thu, Feb 21, 2008 at 10:00:58PM +0100, Willy Tarreau wrote:
>> >> I too agree to merge, it especially since it fixed several problems
>> >> for David. However, I would like to know first if the same problems
>> >> also happen with the 2.6 driver or if it is OK. The risk is getting
>> >> 2.4 fixed and not 2.6, which could cause regressions for people
>> >> upgrading from 2.4 to 2.6. Of course, a regression on a USB-serial
>> >> adapter is not dramatic, but it's a general principle to keep in mind
>> >> that 2.6 should be safe (or at least actively being fixed) when merging
>> >> driver changes in 2.4.
>> >
>> > As far as I can tell, this was a backport of the current 2.6 driver, so
>> > it should not have fixes that are not already in 2.6.
>> >
>> > David, is that true?
>>
>> That is true.
>
>OK that's perfect. I will merge it.
>
>Cheers,
>Willy

I was not successfull at testing it last night, even locally built versions of 
roadnav are segfaulting for me now.  Something still missing from the wxGTK 
camp I believe.

Feb 21 21:05:49 coyote kernel: [799800.925900] roadnav[30556]: segfault at 
00000041 eip 494b9d2f esp bf9d8570 error 4

But that may was well be swahili to me.  And it may run half an hour before it 
does it.  It seems to be related to trying to pull missing TIGER-line maps.  
Its also a serious cpu hog when its running.

-- 
Cheers, Gene
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
If the rich could pay the poor to die for them, what a living the poor
could make!
--
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/