mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: hendriks@lanl.gov
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: 2.4.21 -> 2.4.22 kernel thread oddities
Date: Tue, 09 Sep 2003 22:25:08 +0100	[thread overview]
Message-ID: <1063142708.30962.24.camel@dhcp23.swansea.linux.org.uk> (raw)
In-Reply-To: <20030909192913.GE10623@lanl.gov>

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



  reply	other threads:[~2003-09-09 21:26 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-09 19:29 hendriks
2003-09-09 21:25 ` Alan Cox [this message]
2003-09-10 10:40 ` kernel panic linux-2.4.22 joe patiani 

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1063142708.30962.24.camel@dhcp23.swansea.linux.org.uk \
    --to=alan@lxorguk.ukuu.org.uk \
    --cc=hendriks@lanl.gov \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®