[Bug 230323] Idea/Feature Request - include beadm in the base
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230323 Bug ID: 230323 Summary: Idea/Feature Request - include beadm in the base Product: Base System Version: CURRENT Hardware: Any URL: https://github.com/vermaden/beadm OS: Any Status: New Severity: Affects Many People Priority: --- Component: bin Assignee: b...@freebsd.org Reporter: verma...@interia.pl CC: osho...@freebsd.org Currently beadm is in Ports as sysutils/beadm. What do you think about including it in the base? % ls -lh /usr/local/man/man1/beadm.1.gz /usr/local/sbin/beadm -r--r--r-- 1 root wheel 1.8K 2018.07.10 04:45 /usr/local/man/man1/beadm.1.gz -r-xr-xr-x 1 root wheel28K 2018.07.10 04:45 /usr/local/sbin/beadm Basically its just these two files. -- 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 230323] Idea/Feature Request - include beadm in the base
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230323 Mariusz Zaborski changed: What|Removed |Added Assignee|b...@freebsd.org|osho...@freebsd.org -- 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"
USED GEAR WANTED FOR CASH!!
[[HEADLINE]] [[PERMALINK_FULL_LINK]] TITLE OF YOUR EMAIL The content of your email goes here. You can drag and drop blocks of text, images or other content elements to add them to your message. Customize the font and the colors. Add links to track clicks. This is a second paragraph you can customize as your please. If you have stored contact properties with your contacts, you can include personalization variables such as first name, last name in your message content. [[DELIVERY_INFO]] [[POSTAL_ADDRESS]] ___ 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 230286] panic: lookup: ni_pathlen underflow to -3
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230286 Peter Holm changed: What|Removed |Added CC||k...@freebsd.org --- Comment #2 from Peter Holm --- Seems to be introduced by r336876. -- 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 157700] tftpd(8) in 8.2-RELEASE expects more data after EOF
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=157700 --- Comment #7 from commit-h...@freebsd.org --- A commit references this bug: Author: asomers Date: Fri Aug 3 14:13:16 UTC 2018 New revision: 337246 URL: https://svnweb.freebsd.org/changeset/base/337246 Log: MFC r330696, r330709, r330742, r331358 r330696: Add some functional tests for tftpd(8) tftpd(8) is difficult to test in isolation due to its relationship with inetd. Create a test program that mimics the behavior of tftp(1) and inetd(8) and verifies tftpd's response in several different scenarios. These test cases cover all of the basic TFTP protocol, but not the optional parts. PR: 157700 PR: 225996 PR: 226004 PR: 226005 Differential Revision:https://reviews.freebsd.org/D14310 r330709: Commit missing file from r330696 X-MFC-With: 330696 r330742: tftpd: fix the build of tests on i386 after 330696 It's those darn printf format specifiers again Reported by: cy, kibab X-MFC-With: 330696 r331358: tftpd: misc Coverity cleanup in the tests A bunch of unchecked return values from open(2) and read(2) Reported by: Coverity CID: 1386900, 1386911, 1386926, 1386928, 1386932, 1386942 CID: 1386961, 1386979 X-MFC-With: 330696 Changes: _U stable/10/ stable/10/etc/mtree/BSD.tests.dist stable/10/libexec/tftpd/Makefile stable/10/libexec/tftpd/tests/ stable/10/libexec/tftpd/tests/functional.c -- 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 157700] tftpd(8) in 8.2-RELEASE expects more data after EOF
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=157700 --- Comment #8 from commit-h...@freebsd.org --- A commit references this bug: Author: asomers Date: Fri Aug 3 14:17:12 UTC 2018 New revision: 337247 URL: https://svnweb.freebsd.org/changeset/base/337247 Log: MFC r330710: tftpd: Flush files as soon as they are fully received On an RRQ, tftpd doesn't exit as soon as it's finished receiving a file. Instead, it waits five seconds just in case the client didn't receive the server's last ACK and decides to resend the final DATA packet. Unfortunately, this created a 5 second delay from when the client thinks it's done sending the file, and when the file is available for other processes. Fix this bug by closing the file as soon as receipt is finished. PR: 157700 Reported by: Barry Mishler Changes: stable/10/libexec/tftpd/tests/functional.c stable/10/libexec/tftpd/tftp-transfer.c stable/10/libexec/tftpd/tftpd.c stable/10/usr.bin/tftp/tftp.c -- 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 229106] intr_event_handle is unsafe with respect to interrupt handler list
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=229106 --- Comment #15 from commit-h...@freebsd.org --- A commit references this bug: Author: avg Date: Fri Aug 3 14:27:29 UTC 2018 New revision: 337255 URL: https://svnweb.freebsd.org/changeset/base/337255 Log: safer wait-free iteration of shared interrupt handlers The code that iterates a list of interrupt handlers for a (shared) interrupt, whether in the ISR context or in the context of an interrupt thread, does so in a lock-free fashion. Thus, the routines that modify the list need to take special steps to ensure that the iterating code has a consistent view of the list. Previously, those routines tried to play nice only with the code running in the ithread context. The iteration in the ISR context was left to a chance. After commit r336635 atomic operations and memory fences are used to ensure that ie_handlers list is always safe to navigate with respect to inserting and removal of list elements. There is still a question of when it is safe to actually free a removed element. The idea of this change is somewhat similar to the idea of the epoch based reclamation. There are some simplifications comparing to the general epoch based reclamation. All writers are serialized using a mutex, so we do not need to worry about concurrent modifications. Also, all read accesses from the open context are serialized too. So, we can get away just two epochs / phases. When a thread removes an element it switches the global phase from the current phase to the other and then drains the previous phase. Only after the draining the removed element gets actually freed. The code that iterates the list in the ISR context takes a snapshot of the global phase and then increments the use count of that phase before iterating the list. The use count (in the same phase) is decremented after the iteration. This should ensure that there should be no iteration over the removed element when its gets freed. This commit also simplifies the coordination with the interrupt thread context. Now we always schedule the interrupt thread when removing one of handlers for its interrupt. This makes the code both simpler and safer as the interrupt thread masks the interrupt thus ensuring that there is no interaction with the ISR context. P.S. This change matters only for shared interrupts and I realize that those are becoming a thing of the past (and quickly). I also understand that the problem that I am trying to solve is extremely rare. PR: 229106 Reviewed by: cem Discussed with: Samy Al Bahra MFC after:5 weeks Differential Revision: https://reviews.freebsd.org/D15905 Changes: head/sys/kern/kern_intr.c head/sys/sys/interrupt.h -- 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 229106] intr_event_handle is unsafe with respect to interrupt handler list
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=229106 Andriy Gapon changed: What|Removed |Added Assignee|b...@freebsd.org|a...@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"
[Bug 184733] bsdgrep(1) doesn't match a regular expression containing "|" against UTF-16 file [regression]
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=184733 Kyle Evans changed: What|Removed |Added Blocks||230332 --- Comment #4 from Kyle Evans --- Adding this to tracking PR; will mark fixed/overcome by events once bsdgrep loses the bits that allow it to be linked against gnuregex. Referenced Bugs: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230332 [Bug 230332] TRACKING: bsdgrep as /usr/bin/grep -- 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 223553] bsdgrep in -current is 10 times slower than before
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=223553 Kyle Evans changed: What|Removed |Added Blocks||230332 Referenced Bugs: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230332 [Bug 230332] TRACKING: bsdgrep as /usr/bin/grep -- 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 230334] busdma(9) is missing bus_dmamap_sync_range()
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230334 Bug ID: 230334 Summary: busdma(9) is missing bus_dmamap_sync_range() Product: Base System Version: CURRENT Hardware: Any OS: Any Status: New Severity: Affects Some People Priority: --- Component: kern Assignee: b...@freebsd.org Reporter: jhibb...@freebsd.org bus_dmamap_sync(9) syncs the entire page range in a mapping, which can be very costly if only a small range is needed. Some drivers, perhaps many, share DMA maps for multiple queues or entries, and only need to update one segment. Instead of syncing the full map, there should be a way to sync only the updated range. This is mentioned in https://reviews.freebsd.org/D16570 regarding NVMe performance implications, and in https://reviews.freebsd.org/D16517 as missing for sound buffers. -- 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 230286] panic: lookup: ni_pathlen underflow to -3
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230286 --- Comment #3 from commit-h...@freebsd.org --- A commit references this bug: Author: kib Date: Fri Aug 3 15:35:29 UTC 2018 New revision: 337261 URL: https://svnweb.freebsd.org/changeset/base/337261 Log: Fix typo in copyinstr_smap, resulting in mis-handling of too long strings. Reported and tested by: pho PR: 230286 Sponsored by: The FreeBSD Foundation Changes: head/sys/amd64/amd64/support.S -- 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 230332] TRACKING: bsdgrep as /usr/bin/grep
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230332 Bug ID: 230332 Summary: TRACKING: bsdgrep as /usr/bin/grep Product: Base System Version: CURRENT Hardware: Any OS: Any Status: New Severity: Affects Only Me Priority: --- Component: bin Assignee: b...@freebsd.org Reporter: kev...@freebsd.org This is a tracking PR for outstanding issues in installing bsdgrep as /usr/bin/grep -- 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 230332] TRACKING: bsdgrep as /usr/bin/grep
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230332 Kyle Evans changed: What|Removed |Added Depends on||229925, 228798 Status|New |In Progress Assignee|b...@freebsd.org|kev...@freebsd.org Referenced Bugs: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=228798 [Bug 228798] [exp-run] bsdgrep as /usr/bin/grep https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=229925 [Bug 229925] [EXP-RUN] Disallow escaping ordinary characters in regex(3) -- 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 230286] panic: lookup: ni_pathlen underflow to -3
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230286 Peter Holm changed: What|Removed |Added Status|New |Closed Resolution|--- |FIXED -- 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 230048] Document existence of new ipfw queue types
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230048 --- Comment #2 from Kevin Zheng --- (In reply to Rasool Al-Saadi from comment #1) Thanks for the update. I think this patch is still relevant because it mentions the existence of the prio scheduler, whatever that does. I think this should be kept open until the Phabricator review goes through? -- 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 223327] dhclient: close the pidfile before calling chroot(2)
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=223327 --- Comment #8 from Ed Maste --- (In reply to Goran Mekić from comment #7) > I would expect at least one more capsicumed app had the same problem? I think dhclient may be the only program that uses all of pidfile, capsicum, and chroot. -- 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 223327] dhclient: close the pidfile before calling chroot(2)
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=223327 --- Comment #9 from Ed Maste --- (In reply to Mark Johnston from comment #4) > I realize that this doesn't address the general problem, but what's > the reason for chrooting in the first place now that dhclient runs > in capability mode? Perhaps we could enter capability mode, and iff that fails try chroot? -- 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 223327] dhclient: close the pidfile before calling chroot(2)
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=223327 --- Comment #10 from Mark Johnston --- (In reply to Ed Maste from comment #9) In addition, how about we also keep dhclient pidfiles under /var/run/dhclient so that dhclient doesn't have access to /var/run/* via the directory descriptor? -- 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 230318] options EFIRT: immediate crash of CURRENT with aio boot(clover EFI + rEFInd)
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230318 Masachika ISHIZUKA changed: What|Removed |Added Component|conf|kern --- Comment #1 from Masachika ISHIZUKA --- (In reply to Masachika ISHIZUKA from comment #0) I can boot with aio boot if comment out the 'options EFIRT'. I tested on r337230. -- 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 230318] options EFIRT: immediate crash of CURRENT with aio boot(clover EFI + rEFInd)
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230318 Masachika ISHIZUKA changed: What|Removed |Added Summary|12-current after r336921 is |options EFIRT: immediate |not boot with aio |crash of CURRENT with aio |boot(clover EFI + rEFInd) |boot(clover EFI + rEFInd) -- 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 223327] dhclient: close the pidfile before calling chroot(2)
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=223327 --- Comment #11 from Mark Johnston --- I think that this represents the best compromise, and is relatively simple: https://reviews.freebsd.org/D16584 -- 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 229615] [patch] bin/dd: add status=progress support
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=229615 --- Comment #2 from Thomas Hurst --- This got 13 likes and 7 retweets on Twitter, that's enough for a review and commit, right? :P -- 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 230318] options EFIRT: immediate crash of CURRENT with aio boot(clover EFI + rEFInd)
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230318 Mark Linimon changed: What|Removed |Added Keywords||panic -- 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 230318] options EFIRT: immediate crash of CURRENT with aio boot(clover EFI + rEFInd)
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230318 Mark Linimon changed: What|Removed |Added Assignee|b...@freebsd.org|kev...@freebsd.org Keywords||regression --- Comment #2 from Mark Linimon --- Over to committer of r336921. -- 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"
