All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christoph Rohland <cr@sap.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: cowboy@vnet.ibm.com (Richard A Nelson), linux-kernel@vger.kernel.org
Subject: Re: Linux 2.2.19pre10
Date: 13 Feb 2001 14:29:47 +0100	[thread overview]
Message-ID: <m37l2u7ltg.fsf@linux.local> (raw)
In-Reply-To: <E14Sf7T-0001ia-00@the-village.bc.nu>
In-Reply-To: <E14Sf7T-0001ia-00@the-village.bc.nu>

Hi Alan,

On Tue, 13 Feb 2001, Alan Cox wrote:
>> No, I do not think that it's minor. We had to bring down running
>> application servers to be able to start another one, because the
>> new one couldn't create or attach the systemwide os-monitoring
>> segment and thus refused to start. That's very bad behaviour.
> 
> Well I'll take corrected fixes, but Im not going to hold up a release for it

Yes, I understand that. But I never got any note that my fix is broken
and I still do not understand what's the concern. 

We are holding the BKL while doing this. And if shm_close does not get
called with it we should probably acquire it.

Greetings
		Christoph



  reply	other threads:[~2001-02-13 13:25 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-02-12 17:27 Linux 2.2.19pre10 Alan Cox
2001-02-12 18:00 ` Richard A Nelson
2001-02-12 18:06   ` Alan Cox
2001-02-12 18:33     ` Linux 2.2.19pre10:x! Richard A Nelson
2001-02-12 21:38       ` Alan Cox
2001-02-13 12:23     ` Linux 2.2.19pre10 Christoph Rohland
2001-02-13 13:03       ` Alan Cox
2001-02-13 13:29         ` Christoph Rohland [this message]
2001-02-13 13:27           ` Alan Cox
2001-02-13 13:59             ` Christoph Rohland

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=m37l2u7ltg.fsf@linux.local \
    --to=cr@sap.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=cowboy@vnet.ibm.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.