https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212716
Lewis Donzis changed:
What|Removed |Added
Version|11.0-RELEASE|12.2-RELEASE
--
You are receiving
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212716
Lewis Donzis changed:
What|Removed |Added
Version|12.2-RELEASE|13.2-RELEASE
--
You are receiving
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212716
--- Comment #4 from Lewis Donzis ---
This bug still occurs in FreeBSD 13.2, seven years since it was first reported.
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212716
Greg Becker changed:
What|Removed |Added
CC||g...@codeconcepts.com
--- Comment #5
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212716
--- Comment #6 from Greg Becker ---
I am also able to repro with 15.0-CURRENT.
The problem seems to be that we are not rechecking the socket receive buffer
for errors or to see if the peer closed after calling pr_rcvd() (around line
2430 i
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212716
--- Comment #7 from Greg Becker ---
Created attachment 244510
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=244510&action=edit
echeck socket receive buffer for errors after dropping then regaining the lock
in soreceive_generic()
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212716
Greg Becker changed:
What|Removed |Added
Attachment #244510|0 |1
is obsolete|
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212716
Mark Johnston changed:
What|Removed |Added
Status|New |Open
CC|
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212716
--- Comment #10 from Mark Johnston ---
Created attachment 244533
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=244533&action=edit
regression tests
Here's a patch which adds regression tests to exercise the bug. The seqpacket
t
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212716
--- Comment #11 from Greg Becker ---
Thanks Mark, agreed. I've moved the check up to the pr_rcvd'd block and made
it contingent upon sb_mb being NULL (which is what I was trying to leverage in
the original patch), and that seems to be work
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212716
Greg Becker changed:
What|Removed |Added
Attachment #244523|0 |1
is obsolete|
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212716
--- Comment #13 from Greg Becker ---
I went ahead and created a differential for this bug:
https://reviews.freebsd.org/D41783
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212716
--- Comment #14 from Greg Becker ---
Created attachment 244732
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=244732&action=edit
ockets: re-check socket state after call to pr_rcvd()
This patch reflects the differential at https
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212716
--- Comment #15 from commit-h...@freebsd.org ---
A commit in branch main references this bug:
URL:
https://cgit.FreeBSD.org/src/commit/?id=38426b32e106cf251520259b29779372eda7a5f8
commit 38426b32e106cf251520259b29779372eda7a5f8
Author:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212716
--- Comment #16 from commit-h...@freebsd.org ---
A commit in branch main references this bug:
URL:
https://cgit.FreeBSD.org/src/commit/?id=f44102411e1b16363e91a074c9c403069c550e4d
commit f44102411e1b16363e91a074c9c403069c550e4d
Author:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212716
--- Comment #17 from commit-h...@freebsd.org ---
A commit in branch stable/13 references this bug:
URL:
https://cgit.FreeBSD.org/src/commit/?id=e4ed8e67e206c069955d541de41addcd0da05b82
commit e4ed8e67e206c069955d541de41addcd0da05b82
Author
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212716
--- Comment #18 from commit-h...@freebsd.org ---
A commit in branch stable/13 references this bug:
URL:
https://cgit.FreeBSD.org/src/commit/?id=862d2d514cb782353bce1af99d670db08b1e6c3c
commit 862d2d514cb782353bce1af99d670db08b1e6c3c
Author
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212716
--- Comment #19 from commit-h...@freebsd.org ---
A commit in branch stable/14 references this bug:
URL:
https://cgit.FreeBSD.org/src/commit/?id=811b3d0f0fe5f1cf6b6fbe4a14103bcab9c400df
commit 811b3d0f0fe5f1cf6b6fbe4a14103bcab9c400df
Author
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212716
--- Comment #20 from commit-h...@freebsd.org ---
A commit in branch stable/14 references this bug:
URL:
https://cgit.FreeBSD.org/src/commit/?id=caaea455773898bee9a0c59466a84256192e0980
commit caaea455773898bee9a0c59466a84256192e0980
Author
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212716
Mark Johnston changed:
What|Removed |Added
Assignee|b...@freebsd.org|ma...@freebsd.org
Resoluti
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212716
Bug ID: 212716
Summary: recv() with MSG_WAITALL doesn't always unblock on EOF
Product: Base System
Version: 10.3-RELEASE
Hardware: Any
OS: Any
Status: New
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212716
--- Comment #1 from Lewis Donzis ---
btw, it makes no difference whether it's run in the same machine (to localhost
or to the machine's own IP address) or across the network, or whether it's IPv4
or IPv6. In all cases, the recv() never unb
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212716
--- Comment #2 from Lewis Donzis ---
The same thing happens if we change the test to use a UNIX domain socket. So
it's unrelated to TCP and appears to be a more general problem in the socket
layer.
--
You are receiving this mail because:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212716
Lewis Donzis changed:
What|Removed |Added
Version|10.3-RELEASE|11.0-RELEASE
--
You are receiving
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212716
--- Comment #3 from Lewis Donzis ---
A little more info... the problem appears to occur only if exactly one segment
has been sent from server to client when the connection is closed. If no data
has been sent, or if more than one segment ha
25 matches
Mail list logo
