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: <4BA7CF53.7040504@windriver.com>
Date:	Mon, 22 Mar 2010 15:13:07 -0500
From:	Jason Wessel <jason.wessel@...driver.com>
To:	Jesse Barnes <jbarnes@...tuousgeek.org>
CC:	torvalds@...ux-foundation.org,
	kgdb-bugreport@...ts.sourceforge.net,
	lkml <linux-kernel@...r.kernel.org>,
	Dmitry Torokhov <dmitry.torokhov@...il.com>
Subject: Re: [RESEND] Re: [Kgdb-bugreport] [GIT PULL] V2 kdb / early debug
 (1 of 2) for 2.6.34

On 03/22/2010 03:05 PM, Jesse Barnes wrote:
> On Sat, 20 Mar 2010 21:14:24 -0500
> Jason Wessel <jason.wessel@...driver.com> wrote:
>
>   
>> On 02/28/2010 11:09 PM, Jason Wessel wrote:
>>     
>>> Linus please pull the kdb-merge tree which merges the kdb front end
>>> into the kernel debug core for 7 architectures.
>>>
>>> git://git.kernel.org/pub/scm/linux/kernel/git/jwessel/linux-2.6-kgdb.git kdb-merge
>>>   
>>>       
>> What is the status of this pull request?  Was some part of the process
>> missed here that there has been no response on this pull request?
>>
>> Please let me know what is wrong here.   I have a number of other fixes
>> pending to the tree at this point.
>>
>> Would it be possible to merge part of the tree that is only related to
>> kgdb, in particular the directory re-organization?
>>     
>
> IIRC he still had some issues with the keyboard/input handling.  We
> discussed it briefly a couple of weeks ago and he was worried about
> potential duplication.
>
>   

I worked with Dmitry Torokhov to come to some agreement with respect to
the kdb keyboard handling.  This resulted in dropping one of the
keyboard patches entirely, and it will be done another way.  There are
RFC patches from me on this, as well as Dmitry's own RFC patches for
sysrq handling.

The discussion with Dmitry also resulted in the cleanup of the current
kdb low level PS/2 kdb keyboard driver to an acceptable state.  I was
waiting to hear back on the response to the pull request before
investing further effort here.  I am always open to suggestions of how
to solve this tricky problem.

Thanks,
Jason.
--
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ