From: Rusty Russell <rusty@rustcorp.com.au>
To: Doug Ledford <dledford@redhat.com>
Cc: Alexander Viro <viro@math.psu.edu>,
Linux Scsi Mailing List <linux-scsi@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linus Torvalds <torvalds@transmeta.com>
Subject: Re: Why /dev/sdc1 doesn't show up...
Date: Wed, 20 Nov 2002 07:58:13 +1100 [thread overview]
Message-ID: <20021120072653.E1EC72C060@lists.samba.org> (raw)
In-Reply-To: Your message of "Mon, 18 Nov 2002 19:09:24 CDT." <20021119000924.GD6989@redhat.com>
In message <20021119000924.GD6989@redhat.com> you write:
> On Tue, Nov 19, 2002 at 10:49:21AM +1100, Rusty Russell wrote:
> > In message <Pine.GSO.4.21.0211180403440.23400-100000@steklov.math.psu.edu>
you
> > write:
> > > Not really. For case in question (block devices) there is only one path
> > > and I'd rather keep it that way, thank you very much.
> >
> > See other posting. This is a fundamental design decision, and it's
> > not changing. Sorry.
>
> Then you'll have to back out the patch to module.c because it's already
> changed.
Yeah, I just noticed. To be honest, I was wrong. And the code
shouldn't be put back until (if ever) I have a solution which solves
the races and *doesn't* break working code.
And meanwhile, there are more important things (like reducing the 400k
overhead of CONFIG_KALLSYMS adds to the kernel).
Sorry for the overzealousness,
Rusty.
--
Anyone who quotes me in their sig is an idiot. -- Rusty Russell.
next prev parent reply other threads:[~2002-11-19 20:58 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-17 19:52 Why /dev/sdc1 doesn't show up Doug Ledford
2002-11-17 20:01 ` Alexander Viro
2002-11-17 20:12 ` Doug Ledford
2002-11-17 20:16 ` Alexander Viro
2002-11-17 23:20 ` Andries Brouwer
2002-11-17 23:45 ` Doug Ledford
2002-11-18 8:52 ` Rusty Russell
2002-11-18 9:51 ` Alexander Viro
2002-11-18 23:49 ` Rusty Russell
2002-11-19 0:08 ` Linus Torvalds
2002-11-19 20:54 ` Rusty Russell
2002-11-20 15:45 ` Linus Torvalds
2002-11-24 22:30 ` Rusty Russell
2002-11-19 0:09 ` Doug Ledford
2002-11-19 20:58 ` Rusty Russell [this message]
2002-11-19 0:32 ` Alan Cox
2002-11-18 10:02 ` Roman Zippel
-- strict thread matches above, loose matches on Subject: below --
2002-11-19 5:52 Rusty Russell
2002-11-19 7:12 ` Alexander Viro
2002-11-19 21:29 ` Rusty Russell
2002-11-19 22:33 ` Andries Brouwer
2002-11-19 16:06 ` Doug Ledford
2002-11-19 17:55 ` Jeff Garzik
2002-11-19 21:42 ` Rusty Russell
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=20021120072653.E1EC72C060@lists.samba.org \
--to=rusty@rustcorp.com.au \
--cc=dledford@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=torvalds@transmeta.com \
--cc=viro@math.psu.edu \
/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