[Bug 183294] VIA VX900 - SATA hang
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=183294 ross.stormc...@gmail.com changed: What|Removed |Added CC||ross.stormc...@gmail.com --- Comment #1 from ross.stormc...@gmail.com --- Can confirm this problem still exists from Release 9.x to 10.0 on an ECS VX900-I v1.0a motherboard. FreeBSD 8.x does not have this bug. As a side note, OpenBSD 5.4 and 5.5 exibit the same behavior (hangs on SATA initialization) but NetBSD 6.1.4 does not. -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to freebsd-bugs-unsubscr...@freebsd.org
[Bug 190735] truncate(1) integer overflow issues with size command line arg -- diff with unit tests attached
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=190735 Jilles Tjoelker jil...@freebsd.org changed: What|Removed |Added Status|Needs Triage|In Discussion CC||jil...@freebsd.org --- Comment #1 from Jilles Tjoelker jil...@freebsd.org --- This looks useful. Is it possible to do without the new undocumented -D option? Perhaps you could ktrace for truncate(2) calls or add numbers to error messages. (A truncate() to something close to OFF_MAX should certainly not be expected to work, so checking for sizes of files may not be sufficient.) Instead of the PRIdMAX macro from inttypes.h, please use jd. -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to freebsd-bugs-unsubscr...@freebsd.org
[Bug 190735] truncate(1) integer overflow issues with size command line arg -- diff with unit tests attached
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=190735 --- Comment #2 from Kirk Russell bugmeis...@ba23.org --- Jilles, thanks for looking! I have removed the new undocumented -D option and stopped using the macro from inttypes.h. I like your idea of using ktrace but I will want to research that idea before including that in a diff -- I will remove this ktrace/-D stuff from the patch -- I hope that is okay. I will attach a new patch to this bug, with the new changes. You can clarify your comment the expectations of off_t being OFF_MAX? My idea is the truncate utility needs to indicate an error if OFF_MAX size OFF_MIN. The function humanize_number() will allow numbers out-of-range for off_t and we should tell the user as soon as possible about this conversion problem. What the OS does with an large off_t passed to truncate() is the OS's business. For example, it is possible to create a huge sparse file in ZFS. I am not sure what this sparse file is useful for, but it is nice to see that ls -h works. # printf %d\n 0x7fff 9223372036854775807 # /usr/obj/usr/src/usr.bin/truncate/truncate -s 9223372036854775807 sparse.txt # ls -l sparse.txt -rw-r--r-- 1 root wheel 9223372036854775807 Jun 7 18:30 sparse.txt # ls -lh sparse.txt -rw-r--r-- 1 root wheel 8.0E Jun 7 18:33 sparse.txt -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to freebsd-bugs-unsubscr...@freebsd.org
[Bug 190735] truncate(1) integer overflow issues with size command line arg -- diff with unit tests attached
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=190735 --- Comment #3 from Kirk Russell bugmeis...@ba23.org --- Created attachment 143501 -- https://bugs.freebsd.org/bugzilla/attachment.cgi?id=143501action=edit A second patch with the recommend changes. -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to freebsd-bugs-unsubscr...@freebsd.org
[Bug 190765] New: Added posix_fallocate support and tests to tools/regression/pjdfstest
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=190765 Bug ID: 190765 Summary: Added posix_fallocate support and tests to tools/regression/pjdfstest Product: Base System Version: 10.0-RELEASE Hardware: Any OS: Any Status: Needs Triage Severity: Affects Only Me Priority: --- Component: misc Assignee: freebsd-bugs@FreeBSD.org Reporter: bugmeis...@ba23.org Created attachment 143502 -- https://bugs.freebsd.org/bugzilla/attachment.cgi?id=143502action=edit Added posix_fallocate support to pjdfstest Here is a patch that adds support for posix_fallocate() to pjdfstest I did an svn copy of regression/pjdfstest/tests/ftruncate/00.t to create regression/pjdfstest/tests/posix_fallocate/00.t -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to freebsd-bugs-unsubscr...@freebsd.org
[Bug 190784] New: gpart crash after drive removed
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=190784 Bug ID: 190784 Summary: gpart crash after drive removed Product: Base System Version: 10.0-RELEASE Hardware: Any OS: Any Status: Needs Triage Severity: Affects Many People Priority: --- Component: bin Assignee: freebsd-bugs@FreeBSD.org Reporter: a...@ish.com.au This is reproducible by me on three different RELEASE-10.0 systems. How to reproduce: -- Remove a disk (eg. by unplugging SATA) # gpart show Segmentation fault (core dumped) # gdb /sbin/gpart /tmp/gpart.core GNU gdb 6.1.1 [FreeBSD] Copyright 2004 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type show copying to see the conditions. There is absolutely no warranty for GDB. Type show warranty for details. This GDB was configured as amd64-marcel-freebsd...(no debugging symbols found)... Core was generated by `gpart'. Program terminated with signal 11, Segmentation fault. Reading symbols from /lib/libgeom.so.5...(no debugging symbols found)...done. Loaded symbols for /lib/libgeom.so.5 Reading symbols from /lib/libsbuf.so.6...(no debugging symbols found)...done. Loaded symbols for /lib/libsbuf.so.6 Reading symbols from /lib/libbsdxml.so.4...(no debugging symbols found)...done. Loaded symbols for /lib/libbsdxml.so.4 Reading symbols from /lib/libutil.so.9...(no debugging symbols found)...done. Loaded symbols for /lib/libutil.so.9 Reading symbols from /lib/libc.so.7...(no debugging symbols found)...done. Loaded symbols for /lib/libc.so.7 Reading symbols from /lib/geom/geom_part.so...(no debugging symbols found)...done. Loaded symbols for /lib/geom/geom_part.so Reading symbols from /libexec/ld-elf.so.1...(no debugging symbols found)...done. Loaded symbols for /libexec/ld-elf.so.1 #0 0x000801160623 in strtoimax_l () from /lib/libc.so.7 I don't have src on these machines to easily rebuild gpart in debug, so hopefully the above reference is enough to locate the bug. The above dump was from a machine on 10.0-RELEASE-p4 using freebsd-update binary release mechanism. -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to freebsd-bugs-unsubscr...@freebsd.org
