Re: read() on relayfs channel returns premature 0

[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


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

---

• Follow-Ups:
  • Re: read() on relayfs channel returns premature 0
    • From: Kingsley Cheung <[email protected]>

• References:
  • read() on relayfs channel returns premature 0
    • From: [email protected]

• Prev by Date: [PATCH] I2C Part 1 - Remove some redundancy from the i2c-core.c file
• Next by Date: [PATCH] I2C Part 2 - Break up the formatting code into individual functions
• Previous by thread: read() on relayfs channel returns premature 0
• Next by thread: Re: read() on relayfs channel returns premature 0
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]