From owner-freebsd-stable@FreeBSD.ORG Mon Oct 10 12:08:37 2011 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 64DB3106564A for ; Mon, 10 Oct 2011 12:08:37 +0000 (UTC) (envelope-from patfbsd@davenulle.org) Received: from smtp.lamaiziere.net (net.lamaiziere.net [94.23.254.147]) by mx1.freebsd.org (Postfix) with ESMTP id 256DA8FC16 for ; Mon, 10 Oct 2011 12:08:37 +0000 (UTC) Received: from baby-jane.lamaiziere.net (unknown [192.168.1.10]) by smtp.lamaiziere.net (Postfix) with ESMTP id 2C9EDFAA2C87; Mon, 10 Oct 2011 14:08:36 +0200 (CEST) Received: from localhost (localhost [127.0.0.1]) by baby-jane.lamaiziere.net (Postfix) with ESMTP id 7AF5B2CEC1E; Mon, 10 Oct 2011 14:11:48 +0200 (CEST) Date: Mon, 10 Oct 2011 14:11:45 +0200 From: Patrick Lamaiziere To: Kostik Belousov Message-ID: <20111010141145.1d500c9e@davenulle.org> In-Reply-To: <20111009142131.GQ1511@deviant.kiev.zoral.com.ua> References: <4E8CC6BC.9040605@sh.cvut.cz> <20111006064038.CFB34B852@mail.bitblocks.com> <4E91A0C3.7030305@sh.cvut.cz> <4E91A649.5060207@sh.cvut.cz> <20111009141117.GA47243@icarus.home.lan> <4E91AD48.5070906@sh.cvut.cz> <20111009142131.GQ1511@deviant.kiev.zoral.com.ua> X-Mailer: Claws Mail 3.7.9 (GTK+ 2.22.1; i386-portbld-freebsd8.2) Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Cc: V??clav Zeman , freebsd-stable@freebsd.org Subject: Re: valgrind on FreeBSD? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 10 Oct 2011 12:08:37 -0000 Le Sun, 9 Oct 2011 17:21:31 +0300, Kostik Belousov a écrit : > > > If this isn't a known issue, please file a PR for the issue with > > > nullfs(5). The issue is not within valgrind, so the PR should > > > not be for that. > > I have filled a PR: > > > Nullfs VNTOCNP implementation has a known deficiency. I've filled a PR for a similar issue with nullfs (can't get the path of a binary on a nullfs fs) with a suggestion to document this in the nullfs man page. http://www.freebsd.org/cgi/query-pr.cgi?pr=157234 > Working on the item is in my TODO list. Thanks! Regards.