public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Rusty Russell <rusty@linuxcare.com.au>
To: Jeff Garzik <jgarzik@mandrakesoft.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Linux 2.4 Status/TODO page (test11-pre3)
Date: Tue, 14 Nov 2000 15:07:38 +1100	[thread overview]
Message-ID: <20001114040738.D28BE81F1@halfway.linuxcare.com.au> (raw)
In-Reply-To: Your message of "Sun, 12 Nov 2000 22:09:39 CDT." <3A0F5B73.E613050B@mandrakesoft.com>

In message <3A0F5B73.E613050B@mandrakesoft.com> you write:
> > 12. Probably Post 2.4
> 
> >      * module remove race bugs (ipchains modules -- Rusty; won't fix for
> >        2.4)
> 
> Is this an ipchains bug, or a more general module subsystem bug?

There's a fundamental problem with any module which reduces counts in
interrupts.  Viro's `solution' doesn't apply here; there is a real
solution but I Believed In The Code Freeze.

Rusty.
--
Hacking time.
-
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/

  parent reply	other threads:[~2000-11-14  4:38 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-11-12 19:39 Linux 2.4 Status/TODO page (test11-pre3) tytso
2000-11-12 19:51 ` adrian
2000-11-12 20:21   ` adrian
2000-11-12 20:38     ` adrian
2000-11-12 22:31 ` Erik Mouw
2000-11-13 22:58   ` Roger Larsson
2000-11-13 23:19     ` Erik Mouw
2000-11-13  2:26 ` Keith Owens
2000-11-13 17:33   ` James Simmons
2000-11-13  3:09 ` Jeff Garzik
2000-11-13  3:36   ` David Ford
2000-11-14  1:32   ` Michal Jaegermann
2000-11-14  4:07   ` Rusty Russell [this message]
2000-11-13  3:26 ` David Ford
2000-11-13  8:32   ` Matti Aarnio
2000-11-13 13:14     ` David Ford
2000-11-13  5:14 ` Greg KH
2000-11-13 17:46 ` Tim Waugh

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=20001114040738.D28BE81F1@halfway.linuxcare.com.au \
    --to=rusty@linuxcare.com.au \
    --cc=jgarzik@mandrakesoft.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox