From owner-freebsd-current@FreeBSD.ORG  Thu Mar 25 03:28:00 2004
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP
	id 74A4716A4CE; Thu, 25 Mar 2004 03:28:00 -0800 (PST)
Received: from novacom.pl (foo.frob.nl [212.106.140.230])
	by mx1.FreeBSD.org (Postfix) with ESMTP
	id 374CE43D39; Thu, 25 Mar 2004 03:28:00 -0800 (PST)
	(envelope-from nils@novacom.pl)
Received: from nils by novacom.pl with local (Exim 4.30)
	id 1B6T3i-0002EE-Bl; Thu, 25 Mar 2004 12:30:02 +0100
Date: Thu, 25 Mar 2004 12:30:02 +0100
From: Rafal Skoczylas <nils@secprog.org>
To: Pawel Jakub Dawidek <pjd@FreeBSD.org>
Message-ID: <20040325113002.GA8161@secprog.org>
References: <20040323223020.GA2931@secprog.org>
	<20040324225318.GS8930@darkness.comp.waw.pl>
	<20040325103222.GA7210@secprog.org>
	<20040325110457.GX8930@darkness.comp.waw.pl>
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-2
Content-Disposition: inline
In-Reply-To: <20040325110457.GX8930@darkness.comp.waw.pl>
User-Agent: Mutt/1.5.5i
Sender: <nils@novacom.pl>
cc: freebsd-current@freebsd.org
Subject: Re: [UFS] Broken suiddir? (+patch)
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
Reply-To: Rafal Skoczylas <nils@secprog.org>
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 25 Mar 2004 11:28:00 -0000

On Thu, Mar 25, 2004 at 12:04:57PM +0100, Pawel Jakub Dawidek wrote:
> On Thu, Mar 25, 2004 at 11:32:22AM +0100, Rafal Skoczylas wrote:
> +> Indeed, but somehow it wasn't.
> +> [...]
> I've just tried and it works.
> Are you sure you have added +s bit on this directory?
> [...]
> Or maybe your file system isn't mounted with MNT_SUIDDIR flag?

It definitely was mounted MNT_SUIDDIR and the directory was +s.
Two things come to my mind:
1. I mounted MNT_SUIDDIR option with "mount -o suiddir,update"
   not at the system boot or umount->mount. But I don't
   actually believe this is the reason as the mount command
   is so widely used so it would come out before if it had
   such error.
2. I did some stupid mistake (overlooked or misinterpreted something)
   while testing or my system is broken somewhere else.
   I'll investigate this in the evening when I come back home.
In the latter case, I am sorry for the noise.

-- 
Rafal Skoczylas