[Bug 246350] kqueue fails to report pipe writable after the read end is closed
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=246350
Bug ID: 246350
Summary: kqueue fails to report pipe writable after the read
end is closed
Product: Base System
Version: 12.1-RELEASE
Hardware: Any
OS: Any
Status: New
Severity: Affects Only Me
Priority: ---
Component: kern
Assignee: b...@freebsd.org
Reporter: n...@pobox.com
Attachment #214335 text/plain
mime type:
Created attachment 214335
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=214335&action=edit
fbsd-kqueue-pipe-bug-demo.py
Consider the following sequence of events:
1. Call pipe() to open a pipe
2. Set the write side to non-blocking
3. Write into the write side until the pipe buffer is full and write() returns
EWOULDBLOCK
4. Use kqueue to register a wait for the write end to become writable again
(EVFILT_WRITE)
5. Close the read end of the pipe
At this point, I would expect that kqueue would return an event to report that
the pipe is "writable". The man page says it will ("The filter will set EV_EOF
when the reader disconnects"). On the same pipe, in this situation, select()
reports that it's writable. On macOS, kqueue reports that it's writable.
However, on FreeBSD 12, kqueue does *not* report any event in this situation.
I've attached a minimal Python script to demonstrate.
Output from the script when running on macOS:
filling pipe buffer
select() says the write pipe is NOT writable
closing read end of pipe
select() says the write pipe is writable
waiting for kqueue to report the write end is writable
done!
[]
Output from the script when running on FreeBSD 12.1-RELEASE:
filling pipe buffer
select() says the write pipe is NOT writable
closing read end of pipe
select() says the write pipe is writable
waiting for kqueue to report the write end is writable
[...hangs forever...]
--
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 246356] PCAP(3) SEE ALSO
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=246356 Bug ID: 246356 Summary: PCAP(3) SEE ALSO Product: Documentation Version: Latest Hardware: Any OS: Any Status: New Severity: Affects Only Me Priority: --- Component: Manual Pages Assignee: b...@freebsd.org Reporter: p5b2e9...@t-online.de CC: d...@freebsd.org SEE ALSO autoconf(1), tcpdump(1), tcpslice(1), pcap-filter(@MAN_MISC_INFO@), pfconfig(8), usermod(@MAN_ADMIN_COMMANDS@) but there is nothing for: $ man 1 autoconf No manual entry for autoconf $ man 8 pfconfig No manual entry for pfconfig $ apropos usermod apropos: nothing appropriate $ man usermod No manual entry for usermod -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 246279] ciss driver unable to present more than 48(?) physical drives per controller to the CAM layer
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=246279 --- Comment #11 from Peter Eriksson --- Just verified that the patched driver also works on an old HP DL380G5 with a HP Smart Array P400 controller with four drives and it worked there too. Not much of a test though but at least that part is the same as before (the old P400 doesn't really support a true JBOD mode anyway). -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 246309] r360637 kern.evdev.rcpt_mask=12 by default breaks doubletap on Thinkpad T400 synaptic touchpad
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=246309 --- Comment #6 from jakub_l...@mailplus.pl --- (In reply to Andriy Gapon from comment #5) Thanks, Unfortunately, There is no change with added file - Section "InputClass" Identifier "The touchpad" MatchDriver "libinput" MatchIsTouchpad "on" Option "ScrollMethod" "none" EndSection e.g.: Device: SynPS/2 Synaptics TouchPad Kernel: /dev/input/event5 Group:6 Seat: seat0, default Size: 62x29mm Capabilities: pointer Tap-to-click: disabled Tap-and-drag: enabled Tap drag lock:disabled Left-handed: disabled Nat.scrolling:disabled Middle emulation: n/a Calibration: n/a Scroll methods: *two-finger edge Click methods:none Disable-w-typing: enabled Accel profiles: none Rotation: n/a -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 246356] pcap(3) SEE ALSO contains invalid references
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=246356 Mark Linimon changed: What|Removed |Added Summary|PCAP(3) SEE ALSO|pcap(3) SEE ALSO contains ||invalid references -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 246350] kqueue fails to report pipe writable after the read end is closed
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=246350 Mark Johnston changed: What|Removed |Added CC||ma...@freebsd.org --- Comment #1 from Mark Johnston --- This was recently fixed in head by r360380 and some related revisions. I tried your test case: markj@biggie> python test.py filling pipe buffer select() says the write pipe is NOT writable closing read end of pipe select() says the write pipe is writable waiting for kqueue to report the write end is writable done! [] The fixes will be available in 12.2. -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 246327] Invalid partition table after all-default installation of 13.0-CURRENT
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=246327 --- Comment #1 from Yuri Pankov --- - Is laptop set to BIOS or UEFI boot? - What partition scheme is chosen (there's no default, IIRC, as it changes according to boot type)? - If you boot from installation media after install, escape to shell, what is the `gpart show` output for UFS (successful) and ZFS (unsuccessful) installs? - If GPT/UEFI was chosen, what is the `efibootmgr` and contents of EFI system partition (it can be mounted using mount_msdosfs) are? -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 243136] factor(6) gives inconsistent results with and without OpenSSL compiled int
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=243136 Kirk McKusick changed: What|Removed |Added Resolution|--- |FIXED Status|In Progress |Closed --- Comment #4 from Kirk McKusick --- MFC'ed to 12-stable with -r360835. -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 246350] kqueue fails to report pipe writable after the read end is closed
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=246350 --- Comment #2 from Nathaniel Smith --- I just tested on using the latest 12.1-STABLE release snapshot (FreeBSD-12.1-STABLE-amd64-20200507-r360721-disc1.iso). Since r360721 is higher than r360380, I would expect this to include the fix? But I still get the same result: root@:/host-files # uname -a FreeBSD 12.1-STABLE FreeBSD 12.1-STABLE r360721 GENERIC amd64 root@:/host-files # python3.8 notes-to-self/fbsd-pipe-close-notify.py filling pipe buffer select() says the write pipe is NOT writable closing read end of pipe select() says the write pipe is writable waiting for kqueue to report the write end is writable [... hang ...] -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 246350] kqueue fails to report pipe writable after the read end is closed
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=246350 --- Comment #3 from Nathaniel Smith --- Ah-ha, but I can confirm that the problem *is* fixed in 13.0-CURRENT r360723. The reproducer script passes, and my real program also works correctly. So I guess the STABLE backport just hasn't made it into a STABLE snapshot yet? -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 246350] kqueue fails to report pipe writable after the read end is closed
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=246350 --- Comment #4 from Mark Johnston --- (In reply to Nathaniel Smith from comment #3) I just haven't backported the changes to stable/12 yet - I will do so this week. -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 246350] kqueue fails to report pipe writable after the read end is closed
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=246350 Mark Johnston changed: What|Removed |Added Assignee|b...@freebsd.org|ma...@freebsd.org Status|New |In Progress -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
Problem reports for b...@freebsd.org that need special attention
To view an individual PR, use: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id). The following is a listing of current problems submitted by FreeBSD users, which need special attention. These represent problem reports covering all versions including experimental development code and obsolete releases. Status |Bug Id | Description +---+--- In Progress |221973 | cam iosched: BIO_ZONE commands probably shouldn't In Progress |221974 | cam iosched: The iops limiter should enforce limi In Progress |244867 | Provide sysctl kern.boot_id New |197876 | [devfs] an error in devfs leads to data loss and New |198797 | [PATCH] Added an option to install BSDstats to bs New |202362 | ntp: restore refclocks selection (10.2-RELEASE re New |202740 | vi/ex string substitution problem when there is m New |204097 | witness_initialize() does not perform bound check New |206336 | [patch] usr.sbin/freebsd-update allow proxy confi New |209213 | UEFI Loader shows only black screen with Nvidia G New |210804 | installerconfig - using ZFS create in custom scri New |223470 | freebsd-update: Cannot identify running kernel (/ New |224436 | vt: CONS_CLRHIST (vidcontrol -C) not implemented New |230620 | "install -d" issue New |235085 | [PATCH] Option to make rc.d/sysctl more verbose ( Open| 71667 | [patch] cleanup of the usr.sbin/bootparamd code Open|182466 | [headers] [patch] make self-contained Open|183618 | [panic] Dell PowerEdge R620 -- PERC H710 Mini (mf Open|187015 | agpgart: Panic make_dev_credv: bad si_name (error Open|194925 | [pf] [ifconfig] interface group keywords do not w Open|197921 | scheduler: Allow non-migratable threads to bind t Open|206528 | Emulex LPe 16002 FC HBA Not Recognized by oce(4) Open|206649 | cyapa(4): Add common gestures for Cypress APA I2C Open|207248 | [patch] daemon(8): Add option to redirect stdout Open|207940 | stand/efi/boot1: Add boot partition selection Open|212608 | sockstat(1) and lsof(8) can not identity the owne Open|220246 | syslogd does not send RFC3164-conformant messages Open|221305 | Mouse cursor loss when moving cursor while loadin Open|221550 | kern.bootfile returns only /kernel on mips64 (ERL Open|221854 | makefs: Reject UFS labels that are too long to fi Open|222632 | connect(2) not available in capability mode Open|226893 | freebsd-update: Support patchlevel argument for f Open|231810 | [build] release always fails with "mkimg: partiti Open|233578 | Unprivileged local user can prevent other users l Open|233988 | freebsd-update: Improve progress output on termin Open|236718 | system panics with message: vm_fault_hold: fault Open|237271 | Radeon video card no longer works on 12-STABLE (a Open|237287 | moused(8) ignores button release events in virtua Open|237924 | Possible infinite loop in function empty_aux_buff Open|237981 | cxgb(4): Driver doesn't work with latest (7.12) C Open|238183 | cam/scsi/scsi_sa.c: warnings issued by static ana Open|238486 | Possible buffer overflow bug in sc_allocate_keybo Open|238550 | Touchpad (via SMBus) not working: Synaptics (SYN1 Open|238638 | mfi: Remove unnecessary pointer printing in mfi.c Open|238837 | init: Remove P_SYSTEM flag from PID 1 to allow ea Open|239976 | Integer Overflow: ping(8) option "-s", bypass the Open|239977 | Integer Overflow: ping(8) option "-G" and "-g", b Open|239978 | Integer Overflow: ping(8) option "-h", bypass the Open|240572 | libefi: FreeBSD cannot boot with U-Boot patch efi Open|241697 | i915kms: Kernel panic loading module on custom ke Open|242212 | usr.sbin/mergemaster/mergemaster.sh: There is no Open|243357 | 11.3-RELEASE base sendmail fails to compile with Open|244181 | unzip: Add passphrase and GLIBC build support Open|244706 | panic: NULL dereference inside __mtx_lock_sleep() Open|244838 | "bectl activate -t" does not honor the -t flag in Open|245679 | periodic.conf.5: daily_status_ntpd variable typo New |230955 | [patch] Some speedup mergemaster 57 problems total for which you should take action. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebs
[Bug 245630] sysutils/bastille: Update to 0.6.20200414
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=245630 Automation User changed: What|Removed |Added Keywords||buildisok -- You are receiving this mail because: You are on the CC list for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 245630] sysutils/bastille: Update to 0.6.20200414
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=245630 --- Comment #5 from Automation User --- Build info is available at https://gitlab.com/swills/freebsd-ports/pipelines/144523896 -- You are receiving this mail because: You are on the CC list for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 246366] Unclear and/or wrong kevent vs EINTR manual
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=246366 Bug ID: 246366 Summary: Unclear and/or wrong kevent vs EINTR manual Product: Documentation Version: Latest Hardware: Any OS: Any Status: New Severity: Affects Some People Priority: --- Component: Manual Pages Assignee: b...@freebsd.org Reporter: a...@playground.ru CC: d...@freebsd.org man kevent(2) says: > Cancellation can only occur before any changes are made to the kqueue, or > when the call was blocked and no changes to the queue were requested. and > [EINTR] A cancellation request was delivered to the thread, but not yet > handled. > When kevent() call fails with EINTR error, all changes in the changelist have > been applied. I think that both these statements can't be true at the same time, because the first says that kevent() can be cancelled BEFORE changes are made, and the second says that changes are always applied when EINTR that could be result of cancellation. Another possibility is that this manpage is just very unclear about EINTR behaviour. I don't know what case is right one but I'm sure that there is something wrong here. -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
