Re: SELECT() returns 1 But FIONREAD says (Input/output error)

David Schwartz wrote:

Nope. An errored connection is always ready for read/write -- there is
nothing to wait for as far as the kernel is concerned. Your code keeps
asking the kernel if something interesting has happened, the kernel keeps
telling it yes, and it refuses to do anything about it.

The select() returns because i pulled the USB cable from hub. Seems reasonable.

The next select() found what? to be interesting in order to prematurely terminate the select-wait? As far as I can tell, nothing interesting has happened since the previous select(). In this case the select() is only looking at read()'s.

-
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: SELECT() returns 1 But FIONREAD says (Input/output error)
    • From: "David Schwartz" <[email protected]>

• References:
  • RE: SELECT() returns 1 But FIONREAD says (Input/output error)
    • From: "David Schwartz" <[email protected]>

• Prev by Date: Re: 2.6.22-rc3-mm1 - page_mkwrite() breakage
• Next by Date: Re: 2.6.22-rc3-mm1
• Previous by thread: RE: SELECT() returns 1 But FIONREAD says (Input/output error)
• Next by thread: RE: SELECT() returns 1 But FIONREAD says (Input/output error)
• 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]