[Bug 213903] Kernel crashes from turnstile_broadcast (/usr/src/sys/kern/subr_turnstile.c:837)
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213903 --- Comment #12 from Franco Fichtner--- r301157 was backported to 10-STABLE, but 10.3 is unaffected. There is no 10.3-STABLE. Which one did you mean? >From our experience r301157 is the bad commit as the panics have disappeared in our latest OPNsense version which reverted the rwlock bits of this particular patch. -- You are receiving this mail because: You are on the CC list for the bug. ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
[Bug 213903] Kernel crashes from turnstile_broadcast (/usr/src/sys/kern/subr_turnstile.c:837)
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213903 Cassiano Peixotochanged: What|Removed |Added CC||freebsd-stable@FreeBSD.org, ||peixoto.cassi...@gmail.com --- Comment #11 from Cassiano Peixoto --- Guys, I'm having the same issue here on FreeBSD 10.3-STABLE. I'm using Atom C2758 as well. It has began after 10.3 update. It's very serious issue because many production servers are crashing. Can someone take a look please? Thanks. -- You are receiving this mail because: You are on the CC list for the bug. ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
[Bug 211491] System hangs after "Uptime" on reboot with iSCSI, zfs, and altroot
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211491 Ngie Cooperchanged: What|Removed |Added CC|freebsd-b...@freebsd.org, |n...@freebsd.org |freebsd-stable@FreeBSD.org | Severity|Affects Many People |Affects Some People --- Comment #13 from Ngie Cooper --- Please don't add -current or -stable to bugs like this; it spams the list unnecessarily (this issue impacts users of iSCSI + ZFS -- which seems a bit niche right now) -- You are receiving this mail because: You are on the CC list for the bug. ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
[Bug 211491] System hangs after "Uptime" on reboot with iSCSI, zfs, and altroot
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211491 --- Comment #12 from Eric van Gyzen--- I just reproduced this on 12-CURRENT r303626. I'm now updating that machine to the latest head. -- You are receiving this mail because: You are on the CC list for the bug. ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
[Bug 211491] System hangs after "Uptime" on reboot with iSCSI, zfs, and altroot
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211491 --- Comment #11 from Eric van Gyzen--- I just reproduced this on 10.3-STABLE r303633. I'll try to reproduce on 10.3-RELEASE to see if it would be a new regression in 11.0-RELEASE. -- You are receiving this mail because: You are on the CC list for the bug. ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
[Bug 211491] System hangs after "Uptime" on reboot with iSCSI, zfs, and altroot
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211491 Xin LIchanged: What|Removed |Added CC||delp...@freebsd.org Assignee|freebsd-b...@freebsd.org|freebsd...@freebsd.org Severity|Affects Some People |Affects Many People --- Comment #10 from Xin LI --- I noticed this too but not 100% reproducible. I don't have iSCSI setup, but do have zvol. It was a fresh -CURRENT. -- You are receiving this mail because: You are on the CC list for the bug. ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
[Bug 211491] System hangs after "Uptime" on reboot with iSCSI, zfs, and altroot
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211491 Eric van Gyzenchanged: What|Removed |Added Hardware|amd64 |Any -- You are receiving this mail because: You are on the CC list for the bug. ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
[Bug 211491] System hangs after "Uptime" on reboot with iSCSI, zfs, and altroot
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211491 Eric van Gyzenchanged: What|Removed |Added Summary|System hangs after "Uptime" |System hangs after "Uptime" |on reboot |on reboot with iSCSI, zfs, ||and altroot -- You are receiving this mail because: You are on the CC list for the bug. ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
[Bug 211491] System hangs after "Uptime" on reboot
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211491 --- Comment #9 from Eric van Gyzen--- Steps to reproduce on a stable/11 r303878 GENERIC kernel (and many earlier revs): 1. Attach to an iSCSI LUN with /etc/iscsi.conf and iscsid. 2. Create a ZFS pool on that LUN: zpool create iscsi_test da0 3. Export the pool: zpool export iscsi_test 4. Import the pool with an altroot: zpool import -R /blah iscsi_test 5. shutdown -r now The system will hang after printing Uptime: XdYmZs. iSCSI and altroot are key to producing the hang. -- You are receiving this mail because: You are on the CC list for the bug. ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
[Bug 211491] System hangs after "Uptime" on reboot
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211491 --- Comment #8 from Eric van Gyzen--- The debugging kernel options are not part of the problem. I removed them and still reproduced the hang. -- You are receiving this mail because: You are on the CC list for the bug. ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
[Bug 211491] System hangs after "Uptime" on reboot
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211491 --- Comment #7 from Eric van Gyzen--- So far, I've been importing the volume using the iSCSI initiator in a bhyve guest. To determine whether iSCSI is really involved, I reconfigured to import the volume onto the bhyve host and pass it to the VM as a virtio block device. I failed to reproduce the hang. (I'm still importing with altroot.) Also, I have only reproduced the hang on systems with debugging kernel options such as INVARIANTS and WITNESS. To determine whether they're really involved, I'm rebuilding my VM's kernel without these options. -- You are receiving this mail because: You are on the CC list for the bug. ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
[Bug 211491] System hangs after "Uptime" on reboot
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211491 --- Comment #6 from Eric van Gyzen--- One of those systems is a bhyve VM. On the host, I see that all CPU threads are "vmidle" and consuming no CPU time, so they're blocked on some event, not spinning. (I realize this doesn't help much.) -- You are receiving this mail because: You are on the CC list for the bug. ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
[Bug 211491] System hangs after "Uptime" on reboot
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211491 --- Comment #5 from Eric van Gyzen--- As an amendment to my last comment, the zpool has to be imported with altroot: zpool import -R /foo bar_pool I was failing to reproduce this on two other systems by having the pool imported without -R (altroot). When I added the altroot, those two systems began reproducing it consistenly. -- You are receiving this mail because: You are on the CC list for the bug. ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
[Bug 211491] System hangs after "Uptime" on reboot
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211491 --- Comment #4 from Eric van Gyzen--- I think I've narrowed it down to having a ZFS pool imported from an iSCSI LUN using the in-kernel software initiator. g_amanakis: Is this true on your system, too? -- You are receiving this mail because: You are on the CC list for the bug. ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
[Bug 211491] System hangs after "Uptime" on reboot
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211491 Kubilay Kocakchanged: What|Removed |Added CC|freebsd-am...@freebsd.org |r...@freebsd.org Flags||mfc-stable10?, ||mfc-stable11? Keywords||needs-qa Status|New |Open -- You are receiving this mail because: You are on the CC list for the bug. ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
[Bug 211491] System hangs after "Uptime" on reboot
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211491 Eric van Gyzenchanged: What|Removed |Added Severity|Affects Only Me |Affects Some People CC||vangy...@freebsd.org --- Comment #3 from Eric van Gyzen --- I have also seen this on a Dell Precision Workstation running 11-CURRENT. It doesn't always happen, but it seems more likely after a buildworld/installworld. I'm using ZFS on a single SSD and an iSCSI LUN using the in-kernel initiator. I'm also using the nvidia driver, since this is my main desktop. I'll try to reproduce and get more details (i.e. a core dump). -- You are receiving this mail because: You are on the CC list for the bug. ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
[Bug 211491] System hangs after "Uptime" on reboot
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211491 g_amana...@yahoo.com changed: What|Removed |Added CC||freebsd-b...@freebsd.org, ||freebsd-stable@FreeBSD.org -- You are receiving this mail because: You are on the CC list for the bug. ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
[Bug 207463] [patch] stable/10/sys/netpfil/pf/pf_ioctl.c:pfioctl(DIOCRSETADDRS) buffer overflow
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=207463 Kristof Provostchanged: What|Removed |Added Resolution|--- |FIXED Status|New |Closed -- You are receiving this mail because: You are on the CC list for the bug. ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
[Bug 207463] [patch] stable/10/sys/netpfil/pf/pf_ioctl.c:pfioctl(DIOCRSETADDRS) buffer overflow
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=207463 --- Comment #5 from commit-h...@freebsd.org --- A commit references this bug: Author: kp Date: Thu Mar 3 07:16:36 UTC 2016 New revision: 296340 URL: https://svnweb.freebsd.org/changeset/base/296340 Log: MFC: r296025: pf: Fix possible out-of-bounds write In the DIOCRSETADDRS ioctl() handler we allocate a table for struct pfr_addrs, which is processed in pfr_set_addrs(). At the users request we also provide feedback on the deleted addresses, by storing them after the new list ('bcopy(, addr + size + i, sizeof(ad));' in pfr_set_addrs()). This means we write outside the bounds of the buffer we've just allocated. We need to look at pfrio_size2 instead (i.e. the size the user reserved for our feedback). That'd allow a malicious user to specify a smaller pfrio_size2 than pfrio_size though, in which case we'd still read outside of the allocated buffer. Instead we allocate the largest of the two values. Reported By:Paul J MurphyPR: 207463 Approved by: re (marius) Changes: _U stable/10/ stable/10/sys/netpfil/pf/pf_ioctl.c -- You are receiving this mail because: You are on the CC list for the bug. ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
[Bug 207463] [patch] stable/10/sys/netpfil/pf/pf_ioctl.c:pfioctl(DIOCRSETADDRS) buffer overflow
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=207463 --- Comment #4 from Kristof Provost--- I'll talk to re@ about MFCing this after the BETA3 builds are done (so in a couple of days). -- You are receiving this mail because: You are on the CC list for the bug. ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
[Bug 207463] [patch] stable/10/sys/netpfil/pf/pf_ioctl.c:pfioctl(DIOCRSETADDRS) buffer overflow
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=207463 --- Comment #3 from commit-h...@freebsd.org --- A commit references this bug: Author: kp Date: Thu Feb 25 07:33:59 UTC 2016 New revision: 296025 URL: https://svnweb.freebsd.org/changeset/base/296025 Log: pf: Fix possible out-of-bounds write In the DIOCRSETADDRS ioctl() handler we allocate a table for struct pfr_addrs, which is processed in pfr_set_addrs(). At the users request we also provide feedback on the deleted addresses, by storing them after the new list ('bcopy(, addr + size + i, sizeof(ad));' in pfr_set_addrs()). This means we write outside the bounds of the buffer we've just allocated. We need to look at pfrio_size2 instead (i.e. the size the user reserved for our feedback). That'd allow a malicious user to specify a smaller pfrio_size2 than pfrio_size though, in which case we'd still read outside of the allocated buffer. Instead we allocate the largest of the two values. Reported By: Paul J MurphyPR: 207463 MFC after:5 days Differential Revision:https://reviews.freebsd.org/D5426 Changes: head/sys/netpfil/pf/pf_ioctl.c -- You are receiving this mail because: You are on the CC list for the bug. ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
[Bug 207463] [patch] stable/10/sys/netpfil/pf/pf_ioctl.c:pfioctl(DIOCRSETADDRS) buffer overflow
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=207463 --- Comment #2 from Paul J Murphy--- Yes, you are correct. My patch was sufficient only for the default usage by /sbin/pfctl, but left scope for other usage to cause problems. I've looked over your patch, and it looks good to me. The existing buffer protection code in pfr_set_addrs() also looks like it will handle a smaller size2 cleanly. I have just updated my releng/10.2 system to stable/10's sys/netpfil/pf and sbin/pfctl, with your patch applied to it, and it seems to both pass a quick and basic functionality test, and fix bug #192677 (it is now successfully replacing a pf table with over 130,000 addrs, where 10.2-p12 fails for anything over around 65,000). Thanks. -- You are receiving this mail because: You are on the CC list for the bug. ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
[Bug 207463] [patch] stable/10/sys/netpfil/pf/pf_ioctl.c:pfioctl(DIOCRSETADDRS) buffer overflow
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=207463 Kristof Provostchanged: What|Removed |Added CC||k...@freebsd.org Assignee|freebsd-b...@freebsd.org|k...@freebsd.org --- Comment #1 from Kristof Provost --- I think your analysis is correct. The intention of the bcopy() appears to be to copy additional addresses behind the original list (hence the adds + size + i construction). You're correct that the buffer allocated by 'totlen = io->pfrio_size * sizeof(struct pfr_addr);' is too small for that. It's possible to panic a box that way. I don't think your fix is sufficient though. If user space provides a smaller pfrio_size2 than pfrio_size (remember that all user space programmers are out to get us!) then we'd still end up running outsize the allocated buffer. I think we need to allocate the largest of pfrio_size and pfrio_size2: https://reviews.freebsd.org/D5426 -- You are receiving this mail because: You are on the CC list for the bug. ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
[Bug 207463] [patch] stable/10/sys/netpfil/pf/pf_ioctl.c:pfioctl(DIOCRSETADDRS) buffer overflow
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=207463 Bug ID: 207463 Summary: [patch] stable/10/sys/netpfil/pf/pf_ioctl.c:pfioctl(DIOCRSETAD DRS) buffer overflow Product: Base System Version: 10.3-BETA2 Hardware: Any OS: Any Status: New Keywords: patch Severity: Affects Many People Priority: --- Component: kern Assignee: freebsd-b...@freebsd.org Reporter: p...@inetstat.net CC: freebsd-stable@FreeBSD.org Keywords: patch Created attachment 167367 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=167367=edit stable/10/sys/netpfil/pf/pf_ioctl.c patch While investigating bug #192677 (pfctl iotcl buffer to small for bigger spamd blacklists) on releng/10.2, I believe I have spotted a kernel buffer overflow in stable/10/sys/netpfil/pf/pf_ioctl.c / stable/10/sys/netpfil/pf/pf_table.c, introduced by base r286862 / base r286961. stable/10/sys/netpfil/pf/pf_ioctl.c:pfioctl(DIOCRSETADDRS): totlen = io->pfrio_size * sizeof(struct pfr_addr); pfras = malloc(totlen, M_TEMP, M_WAITOK); stable/10/sys/netpfil/pf/pf_table.c:pfr_set_addrs(): bcopy(, addr + size + i, sizeof(ad)); Inside pfr_set_addrs(), pfioctl()'s "pfras" becomes "addr", "io->pfrio_size" becomes "size", and "io->pfrio_size2" becomes "size2". pfr_set_addrs() uses size2 to protect the buffer just above that bcopy. Looking carefully at stable/10/sys/sbin/pfctl/pfctl_table.c:pfctl_table("replace") and stable/10/sys/sbin/pfctl/pfctl_radix.c:pfr_buf_grow(), io->pfrio_buffer passed into the ioctl is size2. This is theoretical, based on simulating the code mentally. I'm fairly certain that my analysis is correct, but I've not verified it via compiled stable/10 code. The bcopy seems to fairly obviously run off the end of the buffer when it is only "size". The fix should be quite simple, by just changing the buffer to be "size2" in stable/10/sys/netpfil/pf/pf_ioctl.c:pfioctl(DIOCRSETADDRS): totlen = io->pfrio_size2 * sizeof(struct pfr_addr); Untested patch attached. I believe this applies to both stable/10 and head. I have tagged it as 10.3-BETA, as that seems to be the places where the more urgent attention is needed, as it would be quite unfortunate for 10.3 to be released with this bug (if my analysis is correct). -- You are receiving this mail because: You are on the CC list for the bug. ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
[Bug 183817] [patch] [mac] [panic] kernel compiled with options INVARIANTS and MAC_PORTACL panices if loader loads mac_portacl.ko too
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=183817 Kubilay Kocakchanged: What|Removed |Added Flags||mfc-stable9?, mfc-stable10? Status|In Progress |Open Keywords||easy, needs-qa, patch --- Comment #2 from Kubilay Kocak --- Reset to Open (No In Progress without Assignee) Thank you for the update Eugen! -- You are receiving this mail because: You are on the CC list for the bug. ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
[Bug 183817] [patch] [mac] [panic] kernel compiled with options INVARIANTS and MAC_PORTACL panices if loader loads mac_portacl.ko too
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=183817 eu...@grosbein.net changed: What|Removed |Added CC||freebsd-stable@FreeBSD.org --- Comment #1 from eu...@grosbein.net --- As 2 years ago for 9.2-STABLE, there is still the same problem for 10.2-STABLE and attached patch helps. -- You are receiving this mail because: You are on the CC list for the bug. ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
[Bug 183817] [patch] [mac] [panic] kernel compiled with options INVARIANTS and MAC_PORTACL panices if loader loads mac_portacl.ko too
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=183817 Kubilay Kocakchanged: What|Removed |Added Keywords||crash -- You are receiving this mail because: You are on the CC list for the bug. ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
[Bug 194534] [freebsd-update] upgrade from FreeBSD-10-RELEASE to FreeBSD-10.1RC2 system fail to boot.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=194534 Glen Barber g...@freebsd.org changed: What|Removed |Added Status|New |Closed Resolution|--- |Feedback Timeout --- Comment #4 from Glen Barber g...@freebsd.org --- I am unsure if this is still an issue, given the feedback provided, however 10.1-RC2 is no longer supported, and several freebsd-update(8) ENs have been issued since the 10.1-RELEASE to address several issues. -- You are receiving this mail because: You are on the CC list for the bug. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
[Bug 193367] [panic] sleeping thread
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=193367 --- Comment #18 from commit-h...@freebsd.org --- A commit references this bug: Author: dumbbell Date: Tue Apr 28 12:37:10 UTC 2015 New revision: 282141 URL: https://svnweb.freebsd.org/changeset/base/282141 Log: DRM2: fix off-by-one overflow in ioctl processing Call to the driver-specific ioctl used to process ioctl number that will lead to the out-of-bounds access to the ioctl handler array. PR: 193367 Approved by:kib MFC of:r275209 (original commit by rea) Changes: _U stable/10/ stable/10/sys/dev/drm2/drm_drv.c -- You are receiving this mail because: You are on the CC list for the bug. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
[Bug 199310] Font rendering problem -STABLE
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=199310 sasamotik...@gmail.com changed: What|Removed |Added CC||freebsd-stable@FreeBSD.org, ||ge...@freebsd.org, ||sasamotik...@gmail.com, ||x...@freebsd.org -- You are receiving this mail because: You are on the CC list for the bug. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
[Bug 198549] [build] FreeBSD -STABLE r280855 world fail to build.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=198549 Dimitry Andric d...@freebsd.org changed: What|Removed |Added Status|In Progress |Closed Resolution|--- |Unable to Reproduce --- Comment #8 from Dimitry Andric d...@freebsd.org --- (In reply to sasamotikomi from comment #6) Let's not mix different issues here. I'm quite convinced that your hardware is faulty. Please fix your hardware first, and it it still occurs, reopen the bug. -- You are receiving this mail because: You are on the CC list for the bug. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
[Bug 198549] [build] FreeBSD -STABLE r280855 world fail to build.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=198549 Dimitry Andric d...@freebsd.org changed: What|Removed |Added CC|sta...@freebsd.org | -- You are receiving this mail because: You are on the CC list for the bug. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
[Bug 198549] [build] FreeBSD -STABLE r279935 world fail to build lib/libmagic.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=198549 Dimitry Andric d...@freebsd.org changed: What|Removed |Added CC||d...@freebsd.org Status|New |In Progress --- Comment #3 from Dimitry Andric d...@freebsd.org --- Is your source tree completely up-to-date? The fields in your error messages were added to contrib/file/src/file.h in r276415. Maybe your source tree was updated just partially? Try removing it completely, and checking it out from scratch. -- You are receiving this mail because: You are on the CC list for the bug. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
[Bug 199014] [build] r280833 world fail to build with clang35 on -STABLE
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=199014 Dimitry Andric d...@freebsd.org changed: What|Removed |Added Status|New |Closed Resolution|--- |Not A Bug CC||d...@freebsd.org --- Comment #1 from Dimitry Andric d...@freebsd.org --- This is an operator error. You need to specify the full path to clang35 in ${CC}, ${CXX} and ${CPP}, as /usr/local/bin is *not* in the PATH during buildworld. E.g, try setting: CC=/usr/local/bin/clang35 CXX=/usr/local/bin/clang++35 CPP=/usr/local/bin/clang-cpp35 Note that you will most likely run into various other issues when building world with an external toolchain, since it does not even always work on head. -- You are receiving this mail because: You are on the CC list for the bug. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
[Bug 198549] [build] FreeBSD -STABLE r280855 world fail to build.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=198549 sasamotik...@gmail.com changed: What|Removed |Added Summary|[build] FreeBSD -STABLE |[build] FreeBSD -STABLE |r279935 world fail to build |r280855 world fail to |lib/libmagic. |build. --- Comment #4 from sasamotik...@gmail.com --- Thank, previous failure is gone but here is another one... :/usr # rm -rf src # svn checkout https://svn0.us-west.FreeBSD.org/base/stable/10 /usr/src # make -j4 buildworld --- LegacyPassManager.o --- c++ -O2 -pipe -I/usr/src/lib/clang/libllvmcore/../../../contrib/llvm/include -I/usr/src/lib/clang/libllvmcore/../../../contrib/llvm/tools/clang/include -I/usr/src/lib/clang/libllvmcore/../../../contrib/llvm/lib/IR -I. -I/usr/src/lib/clang/libllvmcore/../../../contrib/llvm/../../lib/clang/include -DLLVM_ON_UNIX -DLLVM_ON_FREEBSD -D__STDC_LIMIT_MACROS -D__STDC_CONSTANT_MACROS -DNDEBUG -fno-strict-aliasing -DLLVM_DEFAULT_TARGET_TRIPLE=\i386-unknown-freebsd10.1\ -DLLVM_HOST_TRIPLE=\i386-unknown-freebsd10.1\ -DDEFAULT_SYSROOT=\/usr/obj/usr/src/tmp\ -I/usr/obj/usr/src/tmp/legacy/usr/include -fno-exceptions -fno-rtti -c /usr/src/lib/clang/libllvmcore/../../../contrib/llvm/lib/IR/LegacyPassManager.cpp -o LegacyPassManager.o --- all_subdir_libllvmanalysis --- --- TargetTransformInfo.o --- c++ -O2 -pipe -I/usr/src/lib/clang/libllvmanalysis/../../../contrib/llvm/include -I/usr/src/lib/clang/libllvmanalysis/../../../contrib/llvm/tools/clang/include -I/usr/src/lib/clang/libllvmanalysis/../../../contrib/llvm/lib/Analysis -I. -I/usr/src/lib/clang/libllvmanalysis/../../../contrib/llvm/../../lib/clang/include -DLLVM_ON_UNIX -DLLVM_ON_FREEBSD -D__STDC_LIMIT_MACROS -D__STDC_CONSTANT_MACROS -DNDEBUG -fno-strict-aliasing -DLLVM_DEFAULT_TARGET_TRIPLE=\i386-unknown-freebsd10.1\ -DLLVM_HOST_TRIPLE=\i386-unknown-freebsd10.1\ -DDEFAULT_SYSROOT=\/usr/obj/usr/src/tmp\ -I/usr/obj/usr/src/tmp/legacy/usr/include -fno-exceptions -fno-rtti -c /usr/src/lib/clang/libllvmanalysis/../../../contrib/llvm/lib/Analysis/TargetTransformInfo.cpp -o TargetTransformInfo.o --- all_subdir_libllvmcodegen --- --- LiveDebugVariables.o --- c++ -O2 -pipe -I/usr/src/lib/clang/libllvmcodegen/../../../contrib/llvm/include -I/usr/src/lib/clang/libllvmcodegen/../../../contrib/llvm/tools/clang/include -I/usr/src/lib/clang/libllvmcodegen/../../../contrib/llvm/lib/CodeGen -I. -I/usr/src/lib/clang/libllvmcodegen/../../../contrib/llvm/../../lib/clang/include -DLLVM_ON_UNIX -DLLVM_ON_FREEBSD -D__STDC_LIMIT_MACROS -D__STDC_CONSTANT_MACROS -DNDEBUG -fno-strict-aliasing -DLLVM_DEFAULT_TARGET_TRIPLE=\i386-unknown-freebsd10.1\ -DLLVM_HOST_TRIPLE=\i386-unknown-freebsd10.1\ -DDEFAULT_SYSROOT=\/usr/obj/usr/src/tmp\ -I/usr/obj/usr/src/tmp/legacy/usr/include -fno-exceptions -fno-rtti -c /usr/src/lib/clang/libllvmcodegen/../../../contrib/llvm/lib/CodeGen/LiveDebugVariables.cpp -o LiveDebugVariables.o --- all_subdir_libllvmanalysis --- --- ValueTracking.o --- c++ -O2 -pipe -I/usr/src/lib/clang/libllvmanalysis/../../../contrib/llvm/include -I/usr/src/lib/clang/libllvmanalysis/../../../contrib/llvm/tools/clang/include -I/usr/src/lib/clang/libllvmanalysis/../../../contrib/llvm/lib/Analysis -I. -I/usr/src/lib/clang/libllvmanalysis/../../../contrib/llvm/../../lib/clang/include -DLLVM_ON_UNIX -DLLVM_ON_FREEBSD -D__STDC_LIMIT_MACROS -D__STDC_CONSTANT_MACROS -DNDEBUG -fno-strict-aliasing -DLLVM_DEFAULT_TARGET_TRIPLE=\i386-unknown-freebsd10.1\ -DLLVM_HOST_TRIPLE=\i386-unknown-freebsd10.1\ -DDEFAULT_SYSROOT=\/usr/obj/usr/src/tmp\ -I/usr/obj/usr/src/tmp/legacy/usr/include -fno-exceptions -fno-rtti -c /usr/src/lib/clang/libllvmanalysis/../../../contrib/llvm/lib/Analysis/ValueTracking.cpp -o ValueTracking.o --- all_subdir_libllvmcodegen --- /usr/src/lib/clang/libllvmcodegen/../../../contrib/llvm/lib/CodeGen/LiveDebugVariables.cpp:242:29: error: no template named 'SmallVectorYmpl'; did you mean 'SmallVectorImpl'? const SmallVectorYmplSlotIndex Kills, ^~~ SmallVectorImpl /usr/src/lib/clang/libllvmcodegen/../../../contrib/llvm/include/llvm/Target/TargetInstrInfo.h:40:25: note: 'SmallVectorImpl' declared here templateclass T class SmallVectorImpl; ^ --- all_subdir_libllvmcore --- --- Metadata.o --- c++ -O2 -pipe -I/usr/src/lib/clang/libllvmcore/../../../contrib/llvm/include -I/usr/src/lib/clang/libllvmcore/../../../contrib/llvm/tools/clang/include -I/usr/src/lib/clang/libllvmcore/../../../contrib/llvm/lib/IR -I. -I/usr/src/lib/clang/libllvmcore/../../../contrib/llvm/../../lib/clang/include -DLLVM_ON_UNIX -DLLVM_ON_FREEBSD -D__STDC_LIMIT_MACROS -D__STDC_CONSTANT_MACROS -DNDEBUG -fno-strict-aliasing -DLLVM_DEFAULT_TARGET_TRIPLE=\i386-unknown-freebsd10.1\ -DLLVM_HOST_TRIPLE=\i386-unknown-freebsd10.1\
[Bug 198549] [build] FreeBSD -STABLE r280855 world fail to build.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=198549 --- Comment #5 from Dimitry Andric d...@freebsd.org --- (In reply to sasamotikomi from comment #4) --- all_subdir_libllvmcodegen --- /usr/src/lib/clang/libllvmcodegen/../../../contrib/llvm/lib/CodeGen/LiveDebugVariables.cpp:242:29: error: no template named 'SmallVectorYmpl'; did you mean 'SmallVectorImpl'? const SmallVectorYmplSlotIndex Kills, ^~~ SmallVectorImpl /usr/src/lib/clang/libllvmcodegen/../../../contrib/llvm/include/llvm/Target/TargetInstrInfo.h:40:25: note: 'SmallVectorImpl' declared here templateclass T class SmallVectorImpl; ^ There is definitely something not right with your system, as my copy of LiveDebugVariables has the correct spelling of 'SmallVectorImpl': void addDefsFromCopies(LiveInterval *LI, unsigned LocNo, const SmallVectorImplSlotIndex Kills, SmallVectorImplstd::pairSlotIndex, unsigned NewDefs, MachineRegisterInfo MRI, LiveIntervals LIS); Note that 'Y' (0x59) is just one bit difference from 'I' (0x49), so I suspect that your RAM is randomly flipping bits. Please run a thorough memory test, and replace any faulty hardware. -- You are receiving this mail because: You are on the CC list for the bug. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
[Bug 198549] [build] FreeBSD -STABLE r280855 world fail to build.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=198549 --- Comment #6 from sasamotik...@gmail.com --- (In reply to Dimitry Andric from comment #5) Sorry, I forgot I has difference COLLATE, also forgot many open program... So it's will be just lack of memory. # locale LANG=en_US.UTF-8 LC_CTYPE=en_US.UTF-8 LC_COLLATE=en_US.UTF-8 LC_TIME=en_US.UTF-8 LC_NUMERIC=en_US.UTF-8 LC_MONETARY=en_US.UTF-8 LC_MESSAGES=en_US.UTF-8 LC_ALL=en_US.UTF-8 And another problem wihtout_openssl isn't enforces disable openssl support or usage openssl from port/not build program who request it by default? -- You are receiving this mail because: You are on the CC list for the bug. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
[Bug 198549] [build] FreeBSD -STABLE r280855 world fail to build.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=198549 --- Comment #7 from sasamotik...@gmail.com --- Created attachment 155033 -- https://bugs.freebsd.org/bugzilla/attachment.cgi?id=155033action=edit without_openssl -- You are receiving this mail because: You are on the CC list for the bug. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
[Bug 198549] [build] FreeBSD -STABLE r279935 world fail to build lib/libmagic.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=198549 sasamotik...@gmail.com changed: What|Removed |Added Summary|FreeBSD -STABLE r279935 |[build] FreeBSD -STABLE |world fail to build.|r279935 world fail to build ||lib/libmagic. --- Comment #2 from sasamotik...@gmail.com --- Without -j even without src.conf and optimization flag, failure still repeatable. -- You are receiving this mail because: You are on the CC list for the bug. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
[Bug 199014] [build] r280833 world fail to build with clang35 on -STABLE
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=199014 sasamotik...@gmail.com changed: What|Removed |Added Summary|[build] world fail to build |[build] r280833 world fail |with clang35 on -STABLE |to build with clang35 on ||-STABLE CC||sta...@freebsd.org -- You are receiving this mail because: You are on the CC list for the bug. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
[Bug 198549] FreeBSD -STABLE r279935 world fail to build.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=198549 --- Comment #1 from sasamotik...@gmail.com --- Problem still not fixed for me. Also strange allergy to in argument: /etc/make.conf CPUTYPE?=athlon-xp ok CPUTYPE?=athlon-xp --- buildworld --- make[1]: /usr/src/Makefile.inc1 line 169: CPUTYPE global should be set with ?=. *** [buildworld] Error code 1 make: stopped in /usr/src 1 error make: stopped in /usr/src and NO_PROFILE=true is required in make.conf or need only WITHOUT_PROFILE=true in src.conf? And my src.conf: WITHOUT_PROFILE=true WITHOUT_GAMES=true WITHOUT_HTML=true WITHOUT_HYPERV=true WITHOUT_OPENSSH=true WITHOUT_OPENSSL=true WITHOUT_KVM=true WITHOUT_MAIL=true -- You are receiving this mail because: You are on the CC list for the bug. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
[Bug 198549] FreeBSD -STABLE r279935 world fail to build.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=198549 sasamotik...@gmail.com changed: What|Removed |Added CC||sasamotik...@gmail.com, ||sta...@freebsd.org -- You are receiving this mail because: You are on the CC list for the bug. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org