linux-kernel - Re: [PATCH v2] gpiolib: allow poll(2) on gpio value

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: <200907021516.17510.david-b@pacbell.net>
Date:	Thu, 2 Jul 2009 15:16:17 -0700
From:	David Brownell <david-b@...bell.net>
To:	Jani Nikula <ext-jani.1.nikula@...ia.com>
Cc:	Daniel Glöckner <dg@...ix.com>,
	Ben Nizette <bn@...sdigital.com>, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2] gpiolib: allow poll(2) on gpio value

On Thursday 02 July 2009, Jani Nikula wrote:
> I'm trying to say that if you call gpio_export() to create a sysfs
> node, a subsequent poll() in user space won't work because there is no
> irq set up, and sysfs_notify_dirent() won't be called. The patch
> doesn't provide an interface for setting that up from kernel after
> gpio_export() call - it's only possible to set up edge triggering and
> sysfs notify by writing to the "edge" node from user space.

OK, now I understand.  :)

Yeah, that seems fixable in followups.
--
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/