linux-kernel - Re: Relay Subsystem the 2nd.

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:	Wed, 23 Aug 2006 09:57:36 +0900
From:	Paul Mundt <lethal@...ux-sh.org>
To:	Bjo Breiskoll <bjo@...kom.net>
Cc:	"Linux-Kernel@...r. Kernel. Org" <linux-kernel@...r.kernel.org>
Subject: Re: Relay Subsystem the 2nd.

On Wed, Aug 23, 2006 at 01:49:29AM +0200, Bjo Breiskoll wrote:
> back to my question last week. I would like to implement a new kernel-modul
> with the ability to write data from kernelspace to userspace via the new
> relay subsystem. The less info from block/blktrace.c is insufficient
> unfortunately. The userspace-program should be able to "listen" to the
> kernel-modul if there is new data written. My first Implementation with data
> exchange over copy_to_user() and a char-device is insufficient. So i need an
> hint for something like blocked-IO for relay-files. Is this possible with
> the new relay-subsystem?
>  
Is there something insufficient with poll() on relay files?
-
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/