On Wed, Mar 23, 2005 at 09:29:12AM -0600, Tom Zanussi wrote: > [email protected] writes: > > > > Now I understand that this is not the latest release of relayfs (there > > are the redux patches, which I have yet to try). Nonetheless I'd like > > to know whether this behaviour is deliberate. Is it? > > Nope, looks like you've found a bug - thanks for the patch. Any > chance you can send me your module so I can easily reproduce the > problem and test the fix? > > Thanks, > > Tom > Tom, Yes, well a cut down version of the kernel module anyway. Its in the attached tar ball. The kernel module requires pagg as well as relayfs to work. Basically the module tracks kernel events - in this case process execs. I've tested it on 2.6.10 with the pagg and relayfs patches from http://www.opersys.com/ftp/pub/relayfs/patch-relayfs-2.6.10-050113 and ftp://oss.sgi.com/projects/pagg/download/linux-2.6.10-pagg.patch-4 read() gives me a zero still once about a page of data has been read. Many thanks, -- Kingsley
Attachment:
RelayfsModule.tar.bz2
Description: BZip2 compressed data
- Follow-Ups:
- Re: read() on relayfs channel returns premature 0
- From: Tom Zanussi <[email protected]>
- Re: read() on relayfs channel returns premature 0
- From: Jan Engelhardt <[email protected]>
- Re: read() on relayfs channel returns premature 0
- References:
- Prev by Date: Re: 2.6.12-rc1-mm1: Kernel BUG at pci:389
- Next by Date: apm poweroff bug
- Previous by thread: Re: read() on relayfs channel returns premature 0
- Next by thread: Re: read() on relayfs channel returns premature 0
- Index(es):