linux-kernel - Re: Best method for sending messages to user space?

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]

Date:	Tue, 21 Oct 2008 15:23:16 -0500
From:	Timur Tabi <timur@...escale.com>
To:	Dan Williams <dan.j.williams@...el.com>
CC:	linux-kernel@...r.kernel.org, Kumar Gala <kumar.gala@...escale.com>
Subject: Re: Best method for sending messages to user space?

Dan Williams wrote:

> fd = open("/sys/block/md0/md/array_state");
> do {
> 	read(buf, fd, len);
> 	act_on_message(buf);
> 	select(...); /* wait for next sysfs_notify event */
> 	lseek(fd, 0, SEEK_SET); /* seek back so we can read the new state */
> } while (1);

I meant from the kernel side.  I added a call to sysfs_notify(), and I didn't
see any sysfs entries being created, so I presume I need to set up sysfs before
I call sysfs_notify(), but I can't figure out what that setup is.

-- 
Timur Tabi
Linux kernel developer at Freescale
--
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/