2003-09-09 19:29:30

by Erik A. Hendriks

[permalink] [raw]
Subject: 2.4.21 -> 2.4.22 kernel thread oddities

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.


As far as I can tell the following is going on:

Those kernel threads are started from process 1 before starting init.
They are started with CLONE_FILES so they share a file table with
init.

Right before init is started, the kernel does open("/dev/console").
The kernel threads end up with this in their file table because of the
CLONE_FILES.

On Linux 2.4.22, execve("/sbin/init") causes the file table to be
unshared which leaves no way of closing those file descriptors. This
in turn, means I have no way to unmount the file system.

On Linux 2.4.21, the file table was still shared so closing the file
descriptors in init, closed them for the threads as well and
everything was fine.


A quick one line hack around this would be to "unshare_files" right
before doing the open("/dev/console"). This doesn't strike me as
being a particularly good answer.

It seems like kernel_threads should be responsible for cleaning up
what they don't need with __exit_files() and so on.

- Erik



2003-09-09 21:26:52

by Alan

[permalink] [raw]
Subject: Re: 2.4.21 -> 2.4.22 kernel thread oddities

On Maw, 2003-09-09 at 20:29, [email protected] 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


2003-09-10 10:35:56

by joe patiani

[permalink] [raw]
Subject: kernel panic linux-2.4.22

I got problem when booting from my new kernel. I`ve
compile linux-2.4.22 kernel, but I can`t use it correctly.
The error says that Kernel Panic VFS cannot mount root.

Can linux-2.4.22 kernel read the ext2 fs partition. How
the solution to handle the problem. Please if anyone know
about it send email to my addr. I`m a newbies, so I need a
clear explanation

===========================================================================================
"Instan Diskon Setiap Hari"...
Setiap hari jam 10 malam sampai jam 7 pagi
Dan setiap Hari Libur..
berlaku mulai 1 September - 31 Desember 2003,
Khusus Jawa Timur...
===========================================================================================

2003-09-10 10:53:27

by Muthukumar

[permalink] [raw]
Subject: Re: kernel panic linux-2.4.22


Hai all ..,

Regarding to the kernel panic on linux-2.4.22,pls enable the file
system support of MINIX in the make menuconfig and also enable the
ROM DISK support in the menuconfig.

The error is occuring because of the inavailability of support to
the MINIX support ,in my view.

In the menuconfig use filesystem support to select or in config
file check for this.


REgards
Mvthv