NetBSD Problem Report #49577

From dholland@netbsd.org  Thu Jan 15 23:06:56 2015
Return-Path: <dholland@netbsd.org>
Received: from mail.netbsd.org (mail.netbsd.org [149.20.53.66])
	(using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
	(Client CN "mail.netbsd.org", Issuer "Postmaster NetBSD.org" (verified OK))
	by mollari.NetBSD.org (Postfix) with ESMTPS id 38F31A654D
	for <gnats-bugs@gnats.NetBSD.org>; Thu, 15 Jan 2015 23:06:56 +0000 (UTC)
Message-Id: <20150115230655.F0AD714A248@mail.netbsd.org>
Date: Thu, 15 Jan 2015 23:06:55 +0000 (UTC)
From: dholland@netbsd.org
Reply-To: dholland@netbsd.org
To: gnats-bugs@gnats.NetBSD.org
Subject: fts(3) is not robust in the face of errors
X-Send-Pr-Version: 3.95

>Number:         49577
>Category:       lib
>Synopsis:       fts(3) is not robust in the face of errors
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    lib-bug-people
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Thu Jan 15 23:10:00 +0000 2015
>Originator:     David A. Holland
>Release:        NetBSD 7.99.4 (20150115)
>Organization:
>Environment:
System: n/a
Architecture: all
Machine: all
>Description:

fts(3) is not robust in the face of errors. If it gets a directory
read error while scanning, it discards the error and generates an
empty listing instead.

See PR 38265 for an example -- the issue there was that fetching the
root device vnodes failed, so reading /kern failed; the result was
that the error got swallowed and ls printed nothing.

>How-To-Repeat:

Code reading.

>Fix:
hack hack hack

Home	PR Database Search