[Bug 253422] unnecessary "signal SIGPIPE" sending in dofilewrite.

bugzilla-noreply at freebsd.org bugzilla-noreply at freebsd.org
Wed Feb 10 23:33:50 UTC 2021


https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=253422

            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 at FreeBSD.org
          Reporter: shichun_ma at dell.com

Created attachment 222347
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=222347&action=edit
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 EPIPE,
while freeBSD kernel send extra signal SIGPIPE, this will cause application
killed by unexpected signal.


https://reviews.freebsd.org/D28562

-- 
You are receiving this mail because:
You are the assignee for the bug.


More information about the freebsd-bugs mailing list