SCTP sockets were or were not supported by sendfile() in the past. However, at least since the rewrite of sendfile(), SCTP sockets can't be used in combination with sendfile(). So fail such calls indicating EINVAL.
Details
Details
- Reviewers
markj glebius - Group Reviewers
manpages - Commits
- rS358965: sendfile() does currently not support SCTP sockets.
Diff Detail
Diff Detail
- Repository
- rS FreeBSD src repository - subversion
- Lint
Lint Not Applicable - Unit
Tests Not Applicable
Event Timeline
sys/kern/kern_sendfile.c | ||
---|---|---|
581 ↗ | (On Diff #69473) | What exactly is the problem? |
sys/kern/kern_sendfile.c | ||
---|---|---|
581 ↗ | (On Diff #69473) | Haven't looked at it, never used sendfile in combination with SCTP. If I remember it correctly, when @glebius rewrote the code, we had to do some changes related to sb_acc and sb_ccc. Right now we use #define sb_cc sb_acc At that point there was a discussion (if I remember it correctly) between rrs@ and glebius@ whether sendfile worked with SCTP before the rewrite or not. However, sendfile support doesn't work with SCTP sockets now as you can see in your syzkaller instance. |
sys/kern/kern_sendfile.c | ||
---|---|---|
581 ↗ | (On Diff #69473) | I see. Right, SCTP does not implement pru_ready, which is certainly a prerequisite. |