linux-kernel - Re: kernel panic with simple driver

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: <20110810021630.GA23748@kroah.com>
Date:	Tue, 9 Aug 2011 19:16:30 -0700
From:	Greg KH <greg@...ah.com>
To:	"Murali K. Vemuri" <vemuri.muralikrishna@...il.com>
Cc:	Ryan Mallon <rmallon@...il.com>, linux-kernel@...r.kernel.org
Subject: Re: kernel panic with simple driver

On Wed, Aug 10, 2011 at 10:33:28AM +0900, Murali K. Vemuri wrote:
> There is no concurrent access to the timer. The design is that:
> 1.Driver provides an IOCTL for start / stop
> 2. when the driver receives START IOCTL, it toggles some GPIOs to ON / OFF.
> 3. the GPIOs will be ON for 500 MSec and OFF for 500 MSec.
> 4. Two successive START IOCTLs will not be honored.
> 5. There is only one application that uses these IOCTLs
> 6. When I receive a STOP IOCTL, I am doing :
> if (timer_pending (&my_timer))
> del_timer(&my_timer);

What kind of driver is this?  For what type of hardware?

Can't you control the gpios from userspace with out any need to write a
kernel driver?

thanks,

greg k-h
--
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/