From owner-freebsd-bugs@FreeBSD.ORG Fri Jan 24 20:40:01 2014 Return-Path: Delivered-To: freebsd-bugs@smarthost.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 9CB64935 for ; Fri, 24 Jan 2014 20:40:01 +0000 (UTC) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 6EFC4167B for ; Fri, 24 Jan 2014 20:40:01 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.7/8.14.7) with ESMTP id s0OKe17f062671 for ; Fri, 24 Jan 2014 20:40:01 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.7/8.14.7/Submit) id s0OKe1wk062670; Fri, 24 Jan 2014 20:40:01 GMT (envelope-from gnats) Date: Fri, 24 Jan 2014 20:40:01 GMT Message-Id: <201401242040.s0OKe1wk062670@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org Cc: From: Pedro Giffuni Subject: Re: kern/186066: can not change file permisions, owner for spacial files in ext2fs X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list Reply-To: Pedro Giffuni List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 24 Jan 2014 20:40:01 -0000 The following reply was made to PR kern/186066; it has been noted by GNATS. From: Pedro Giffuni To: bug-followup@FreeBSD.org, guru@unixarea.de Cc: Subject: Re: kern/186066: can not change file permisions, owner for spacial files in ext2fs Date: Fri, 24 Jan 2014 15:36:48 -0500 Hello; Unfortunately the HTree dirindex code included an unfortunate change that partially corrupted the inode flags. Such bug was fixed in r260545 and has already been merged to 10-stable and 9-stable. A cleaner fix is being worked on but it would be great to know if the simple fix in r260545 solves the issue.