All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wakko Warner <wakko@animx.eu.org>
To: Andrew Morton <andrewm@uow.edu.au>
Cc: linux-kernel@vger.kernel.org
Subject: Re: test12-pre6
Date: Wed, 6 Dec 2000 20:43:58 -0500	[thread overview]
Message-ID: <20001206204358.B8348@animx.eu.org> (raw)
In-Reply-To: <Pine.LNX.4.10.10012052318270.5786-100000@penguin.transmeta.com> <20001206064732.A6542@animx.eu.org> <3A2E2C16.80AF82BB@uow.edu.au>
In-Reply-To: <3A2E2C16.80AF82BB@uow.edu.au>; from Andrew Morton on Wed, Dec 06, 2000 at 11:07:50PM +1100

Andrew Morton wrote:
> Wakko Warner wrote:
> > 
> > >  - pre6:
> > >     - Andrew Morton: exec_usermodehelper fixes
> > 
> > pre4 oopsed all over the place on my alpha with modules and autoloading
> > turned on as soon as it mounted / and freed unused memory.  I take it this
> > was seen on i386 as well?
> 
> No...  The problems showed themselves a little more subtly than that,
> although in the pre5 version there was potential for schedule_task tasks to
> be queued before the kernel thread which handles them was started.
> 
> This shouldn't normally be a problem, but it becomes a fatal problem if
> someone tries to schedule a task and then synchronously waits
> for it to complete, as the new exec_usermodehelper does.
> 
> This change didn't affect module loading per-se.  But the
> kernel does try to run /sbin/hotplug from deep within sys_insert_module
> and sys_delete_module, so they're related.
> 
> > Will try pre6.
> 
> Please.

test12pre6 boots on my alpha and it works with modules enabled (and
autoloading).  Now, if I could only reiserfs worked on alpha!

-- 
 Lab tests show that use of micro$oft causes cancer in lab animals
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

  reply	other threads:[~2000-12-07  2:05 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-12-06  7:25 test12-pre6 Linus Torvalds
2000-12-06  7:50 ` test12-pre6 Alexander Viro
2000-12-06  7:54 ` [PATCH] test12-pre6 Alexander Viro
2000-12-06  8:03 ` Alexander Viro
2000-12-06  8:06 ` Alexander Viro
2000-12-06  8:26   ` Tigran Aivazian
2000-12-06  8:38     ` Tigran Aivazian
2000-12-06  8:56       ` Tigran Aivazian
2000-12-06  9:07         ` Alexander Viro
2000-12-06  9:29           ` Tigran Aivazian
2000-12-06  8:11 ` Alexander Viro
2000-12-06 11:47 ` test12-pre6 Wakko Warner
2000-12-06 12:04   ` test12-pre6 Andrew Morton
2000-12-07  1:43     ` Wakko Warner [this message]
2000-12-06 13:06 ` test12-pre6 Tobias Ringstrom
2000-12-06 13:29   ` test12-pre6 Miles Lane
2000-12-06 18:08 ` test12-pre6 Erik Mouw
2000-12-06 18:38   ` test12-pre6 Linus Torvalds
2000-12-06 19:08     ` test12-pre6 Erik Mouw
2000-12-06 19:38       ` test12-pre6 Linus Torvalds
2000-12-06 20:09         ` test12-pre6 Erik Mouw
2000-12-06 21:06           ` test12-pre6 Jeff Garzik
2000-12-06 22:57             ` test12-pre6 Miles Lane
2000-12-06 23:10               ` test12-pre6 Johannes Erdfelt
2000-12-06 23:13               ` test12-pre6 Jeff Garzik
2000-12-06 23:17                 ` test12-pre6 Miles Lane
2000-12-07  0:05           ` test12-pre6 Miles Lane
  -- strict thread matches above, loose matches on Subject: below --
2000-12-07  1:30 test12-pre6 Dunlap, Randy

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=20001206204358.B8348@animx.eu.org \
    --to=wakko@animx.eu.org \
    --cc=andrewm@uow.edu.au \
    --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.