On 10/6/07 5:23, "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> wrote:
> >> On 9/6/07 10:01, "Eric Schrock" <[EMAIL PROTECTED]> wrote: >> >>> On Sat, Jun 09, 2007 at 01:56:35PM -0700, Ed Ravin wrote: >>>> >>>> I encountered the problem in NetBSD's scandir(), when reading off >>>> a Solaris NFS fileserver with ZFS filesystems. I've already filed a >>>> bug report with NetBSD. They were using the st_size, divided by 24, to >>>> determine how much memory to allocate with malloc() before reading in >>>> the directory entries. All without any sanity checking. >>> >>> Ah, so the original bug should never been filed against our scandir(3c), >>> which is resilient to this type of failure. >> >> I think when I originally filed this bug I was looking at the wrong scandir >> implementation, ie the one in >> /onnv/onnv-gate/usr/src/lib/libbc/libc/gen/common/scandir.c instead of the >> one in /onnv/onnv-gate/usr/src/lib/libc/port/gen/scandir.c >> >> Is there any way to mark the bug as resolved? Or maybe to change the >> category etc? > > Possibly; it would still need to be fixed if folks encountered this > on their old SunOS 4.x app running on Solaris. I can't see that being too high up on Sun's agenda :-) Cheers, Chris _______________________________________________ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
