From: Andi Kleen <andi@firstfloor.org>
To: Stephen Hemminger <shemminger@linux-foundation.org>
Cc: "David S. Miller" <davem@davemloft.net>,
Al Viro <viro@ftp.linux.org.uk>,
netdev@vger.kernel.org
Subject: Re: Files, sockets, and closing
Date: Sat, 27 Oct 2007 20:03:34 +0200 [thread overview]
Message-ID: <p73wst8o2o9.fsf@bingen.suse.de> (raw)
In-Reply-To: <20071026140319.5bcc8ac0@freepuppy.rosehill> (Stephen Hemminger's message of "Fri\, 26 Oct 2007 14\:03\:19 -0700")
This particular problem has come up many times over the years. So far
the standard strategy has been to ignore it. It's doubtful that the
complexity needed for a fix is worth it.
Workaround at user space level: call shutdown() first instead of close()
-Andi
prev parent reply other threads:[~2007-10-27 18:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-26 21:03 Files, sockets, and closing Stephen Hemminger
2007-10-26 21:45 ` Al Viro
2007-10-26 22:09 ` Stephen Hemminger
2007-10-26 22:46 ` Al Viro
2007-10-27 18:03 ` Andi Kleen [this message]
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=p73wst8o2o9.fsf@bingen.suse.de \
--to=andi@firstfloor.org \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=shemminger@linux-foundation.org \
--cc=viro@ftp.linux.org.uk \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).