linux-kernel - Re: 2.6.36/2.6.37: broken compatibility with userspace input-utils ?

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 for Android: free password hash cracker in your pocket

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

Message-ID: <20110128210958.GJ6252@core.coreip.homeip.net>
Date:	Fri, 28 Jan 2011 13:09:58 -0800
From:	Dmitry Torokhov <dmitry.torokhov@...il.com>
To:	Mark Lord <kernel@...savvy.com>
Cc:	Mauro Carvalho Chehab <mchehab@...hat.com>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	Linux Kernel <linux-kernel@...r.kernel.org>,
	linux-input@...r.kernel.org, linux-media@...r.kernel.org
Subject: Re: 2.6.36/2.6.37: broken compatibility with userspace input-utils ?

On Fri, Jan 28, 2011 at 04:03:07PM -0500, Mark Lord wrote:
> On 11-01-28 03:55 PM, Mark Lord wrote:
> > On 11-01-28 11:42 AM, Dmitry Torokhov wrote:
> >> On Thu, Jan 27, 2011 at 11:53:25AM -0800, Dmitry Torokhov wrote:
> >>> On Thu, Jan 27, 2011 at 01:12:48PM -0500, Mark Lord wrote:
> >>>> On 11-01-27 11:39 AM, Dmitry Torokhov wrote:
> > ..
> >>>>> Hmm, what about compiling with debug and getting a core then?
> >>>>
> >>>> Sure.  debug is easy, -g, but you'll have to tell me how to get it
> >>>> do produce a core dump.
> >>>>
> >>>
> >>> See if adjusting /etc/security/limits.conf will enable it to dump core.
> >>> Otherwise you'll have to stick 'ulimit -c unlimited' somewhere...
> > ..
> >> Any luck with getting the core? I'd really like to resolve this issue.
> > ..
> > 
> > I'm upgrading the box to new userspace now.
> > But I still have the old installation drive,
> > so perhaps I'll go there now and try this.
> > 
> > My plan is to replace /usr/bin/ir-keytable with a script
> > that issues the 'ulimit -c unlimited' command and then
> > invokes the original /usr/bin/ir-keytable binary.
> > 
> > Should take half an hour or so before I get back here again.
> 
> No-go.  According to the syslog, the segfault has not happened
> since I reconfigured the kernel and startup sequence two days
> ago to resolve an XFS mount issue.
> 
> Something in there changed the init timing just enough to make
> it go away, I believe.

OK, this reinforces my suspicion that the cause of segfault is the race
we were discussing with Mauro, not the keymap retrieval fix.

I shall be sending the patch to Linus/stable in the next pull then.

Thank you for your help.

-- 
Dmitry
--
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/