All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jamie Lokier <jamie@shareable.org>
To: Paul Jakma <paul@clubi.ie>
Cc: David Schwartz <davids@webmaster.com>,
	hasso@estpak.ee, Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: raw sockets and blocking
Date: Thu, 19 Feb 2004 07:53:43 +0000	[thread overview]
Message-ID: <20040219075343.GA4113@mail.shareable.org> (raw)
In-Reply-To: <Pine.LNX.4.58.0402190622010.25392@fogarty.jakma.org>

Paul Jakma wrote:
> > 	It is, however, perfectly legal to say an operation can
> > complete without blocking (say, through 'select' or 'poll') and
> > later return EWOULDBLOCK. (So long as some operation could have
> > completed, not necessarily the one you tried.)
> 
> Right. But that's fine, we can deal with that, if the error is
> posted.
> 
> Problem is no error is posted when we sendmsg[1], yet the socket
> thereafter stays write-blocked, with (sane) way for us to recover.  

I hate to check the obvious, but did you try setting the O_NONBLOCK
flag for the socket?  Did you try setting the MSG_DONTWAIT flag for
the sendmsg operation?

-- Jamie

  reply	other threads:[~2004-02-19  7:53 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-18  1:33 raw sockets and blocking Paul Jakma
2004-02-18  5:37 ` David Schwartz
2004-02-18  6:42   ` Hasso Tepper
2004-02-18 11:42     ` David Schwartz
2004-02-19  6:28       ` Paul Jakma
2004-02-19  7:53         ` Jamie Lokier [this message]
2004-02-19  8:34           ` Paul Jakma
2004-02-19 12:40             ` Hasso Tepper
2004-02-19 12:54               ` Paul Jakma
2004-03-22  7:14                 ` Hasso Tepper
2004-02-18  8:43   ` Hasso Tepper
2004-02-19  6:20   ` Paul Jakma

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20040219075343.GA4113@mail.shareable.org \
    --to=jamie@shareable.org \
    --cc=davids@webmaster.com \
    --cc=hasso@estpak.ee \
    --cc=linux-kernel@vger.kernel.org \
    --cc=paul@clubi.ie \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.