linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "davor emard" <davoremard@gmail.com>
To: Aristeu Rozanski <aris@cathedrallabs.org>
Cc: linux-input@vger.kernel.org
Subject: Re: uinput oopses and bugs
Date: Fri, 28 Mar 2008 01:55:19 +0100	[thread overview]
Message-ID: <beee72200803271755u468f5d0djd10d282593644a7d@mail.gmail.com> (raw)
In-Reply-To: <20080327202245.GK25854@cathedrallabs.org>

HI Aristeu

> first, please keep the mailing list on Cc. two reasons: first, I may not
> be able to answer other questions; second, other people may have the
> same problems you do and this discussion can be useful for them.

Last time the mail from the list bounced again although I've explicitely
subscribed to linux-input@vger.kernel.org but nevermind

>
> > Still the EV_FF makes EV_LED and EV_SND not working.
> will work on that next.

Hope the reproducer works for you, it's a bit clumsy written
but I hope it's useful to track this LED and SND disabling by
FF

> > There is also a still issue with segfault and unkillable driver.
> > I upload custom FF effect, driver segfaults but doesn't exit
> > and becomes zombie
> please test the attached patch

The patch now avoids the zombie lockup coming from segmentation
fault.  Thanks a lot, that is great step forward!

However it's still not clear to me why do I get this segmentation
fault when I try to upload a block of FF_CUSTOM sample data.
I made my code mainly from looking at the kernel source without
having any example - anyone on the list can point link to some small
code example?

in uinput-zombie, I've prepared the data in application, ioctl'ed them
to uinput event device and the uinput driver segfaults when
it tries to read the portion of  FF_CUSTOM data.

Best regards, Davor

       reply	other threads:[~2008-03-28  0:55 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <beee72200803260141y59b96c56n9fccfda6c72d1783@mail.gmail.com>
     [not found] ` <20080326132844.GC25854@cathedrallabs.org>
     [not found]   ` <beee72200803260709p7239ae8etb4e00b608bbfb6bc@mail.gmail.com>
     [not found]     ` <20080326182314.GF25854@cathedrallabs.org>
     [not found]       ` <beee72200803270115v72eb1cd3s38ae90a4efd6acd1@mail.gmail.com>
     [not found]         ` <20080327202245.GK25854@cathedrallabs.org>
2008-03-28  0:55           ` davor emard [this message]
2008-03-28 18:46             ` uinput oopses and bugs Anssi Hannula
2008-03-28 19:07               ` davor emard

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=beee72200803271755u468f5d0djd10d282593644a7d@mail.gmail.com \
    --to=davoremard@gmail.com \
    --cc=aris@cathedrallabs.org \
    --cc=linux-input@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;
as well as URLs for NNTP newsgroup(s).