Subject: Re: 2.4.21 -> 2.4.22 kernel thread oddities
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: hendriks@lanl.gov
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
In-Reply-To: <20030909192913.GE10623@lanl.gov>
References: <20030909192913.GE10623@lanl.gov>
Content-Type: text/plain
Content-Transfer-Encoding: 7bit
Message-Id: <1063142708.30962.24.camel@dhcp23.swansea.linux.org.uk>
Mime-Version: 1.0
Date: Tue, 09 Sep 2003 22:25:08 +0100
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 707
Lines: 16

On Maw, 2003-09-09 at 20:29, hendriks@lanl.gov wrote:
> The "unshare_files" addition to execve() is having some unexpected
> side effects for a funky init() program that I use on our clusters.
> Basically the problem is that standard-equipment type kernel threads
> (e.g. kupdated, bdflush) are ending up with open file descriptors on a
> file system that I wish to unmount.

I sent Marcelo a fix for this in 2.4.23pre/2.4.22-ac - see the change to
init/main.c


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/