summaryrefslogtreecommitdiff
path: root/META.yml
diff options
context:
space:
mode:
authorDaniel Kahn Gillmor <dkg@fifthhorseman.net>2012-02-17 14:29:14 -0800
committerRicardo Signes <rjbs@cpan.org>2012-05-10 09:53:14 -0400
commit271d04eee1933df0971f54f7bf9a5ca3575e7e6a (patch)
tree75270f1a3be0ff4d47e8ec9aa6fbaa8fae48a54d /META.yml
parentbe109f01e91266a4cf170323c0a8f0d915bae205 (diff)
downloadperl-271d04eee1933df0971f54f7bf9a5ca3575e7e6a.tar.gz
[rt.cpan.org #61577] sockdomain and socktype undef on newly accepted sockets
There appears to be a flaw in IO::Socket where some IO::Socket objects are unable to properly report their socktype, sockdomain, or protocol (they return undef, even when the underlying socket is sufficiently initialized to have these properties). The attached patch should cover IO::Socket objects created via accept(), new_from_fd(), new(), and anywhere else whose details haven't been properly cached. No new code should be executed on IO::Socket objects whose details are already cached and present.
Diffstat (limited to 'META.yml')
-rw-r--r--META.yml3
1 files changed, 3 insertions, 0 deletions
diff --git a/META.yml b/META.yml
index 9271e61e8a..faa01d5af3 100644
--- a/META.yml
+++ b/META.yml
@@ -78,6 +78,9 @@ no_index:
- dist/IO/poll.c
- dist/IO/poll.h
- dist/IO/README
+ - dist/IO/t/cachepropagate-tcp.t
+ - dist/IO/t/cachepropagate-udp.t
+ - dist/IO/t/cachepropagate-unix.t
- dist/IO/t/IO.t
- dist/IO/t/io_const.t
- dist/IO/t/io_dir.t