Date: Wed, 10 Feb 2021 23:33:50 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 253422] unnecessary "signal SIGPIPE" sending in dofilewrite. Message-ID: <bug-253422-227@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D253422 Bug ID: 253422 Summary: unnecessary "signal SIGPIPE" sending in dofilewrite. Product: Base System Version: Unspecified Hardware: Any OS: Any Status: New Severity: Affects Many People Priority: --- Component: kern Assignee: bugs@FreeBSD.org Reporter: shichun_ma@dell.com Created attachment 222347 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D222347&action= =3Dedit diff for this bug. current code in dofilewrite will send SIGPIPE once there is error of EPIPE, While SIGPIPE is just needed on socket and pipe operation. this is defined = in POSIX standard, also with change it can be compatible with more Linux application. Here is one example: in function nfslock_write, it call nfslockdans, and it's possible that nfslockdans encounter EPIPE error. application's expectation is jut got write error with return error EPIP= E, while freeBSD kernel send extra signal SIGPIPE, this will cause application killed by unexpected signal. https://reviews.freebsd.org/D28562 --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-253422-227>