From mboxrd@z Thu Jan  1 00:00:00 1970
From: greg@kroah.com (Greg Kroah-Hartman)
Date: Wed, 8 Oct 2014 09:25:45 -0700
Subject: User space <==> kernel space for device wakeups.
In-Reply-To: <20141008155750.GF2017@vega.codepro.be>
References: <CAB6A5-ALq0WT2CKAOYX-O+-OgYJcr0G8OWz6EFkqb-Z6QGA2Bw@mail.gmail.com>
	<20141008132941.GB5119@kroah.com>
	<CAC-LjFv7pDX0RRup7tywrRRJEf6_tCoVaTgqFCd0fVxZSMkbhA@mail.gmail.com>
	<20141008155750.GF2017@vega.codepro.be>
Message-ID: <20141008162545.GA22573@kroah.com>
To: kernelnewbies@lists.kernelnewbies.org
List-Id: kernelnewbies.lists.kernelnewbies.org

On Wed, Oct 08, 2014 at 05:57:50PM +0200, Kristof Provost wrote:
> On 2014-10-08 21:14:43 (+0530), Jeshwanth Kumar N K <jeshkumar555@gmail.com> wrote:
> > Wayback when I was working on some project to wake up userspace program for
> > every rising edge in GPIO pin (hall sensor), I use to send signal to the
> > PID from kernel, before that userspace has to register its PID with kernel
> > module. 
> > 
> I've seen a certain vendor[1] do something similar. They saved the task
> pointer for whichever process made the magical ioctl() call and used it
> to send signals from the interrupt handler. It worked, right up to the
> point where the process went away and then the kernel panicked.

Exactly, don't do that :)

Finding out the real problem that is attempting to be solved would be
good...

greg k-h