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: Windows password security audit tool. GUI, reports in PDF.

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

Message-ID: <20110128164244.GB6252@core.coreip.homeip.net>
Date:	Fri, 28 Jan 2011 08:42:44 -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 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:
> > > On Wed, Jan 26, 2011 at 10:18:53PM -0500, Mark Lord wrote:
> > >> No, it does not seem to segfault when I unload/reload ir-kbd-i2c
> > >> and then invoke it by hand with the same parameters.
> > >> Quite possibly the environment is different when udev invokes it,
> > >> and my strace attempt with udev killed the system, so no info there.
> > >>
> > > 
> > > 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...
> 

Mark,

Any luck with getting the core? I'd really like to resolve this issue.

Thanks.

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