From: Andries.Brouwer@cwi.nl
To: dalecki@evision-ventures.com, torvalds@transmeta.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] 2.5.18 IDE 73
Date: Wed, 29 May 2002 20:07:13 +0200 (MEST) [thread overview]
Message-ID: <UTC200205291807.g4TI7DN15827.aeb@smtp.cwi.nl> (raw)
- Don't allow check_partition to be more clever then the writer of a driver.
It was interfering with drivers which check partitions as they go and
finally if we want to spew something about it - we can do it ourself.
- Eliminate ide_geninit(). We scan for partitions now inside the recently
introduced attach method. register_disk() is broken by the way and 90% of
places where it's used it is doing literally nothing. Either some one didn't
finish some code or the code is basically just junk from the past.
Anyway we grok the partitions now one by one as we detect the channels.
Pity you send this gzipped, otherwise I would have looked at the code.
Yes, 90% of the uses of register_disk() are empty. I submitted a patch
to remove this cruft last year, but Al was attached to it - wanted to
make them nonempty.
About scanning for partitions I say the same thing I said to Al a few
days ago:
Several partitioning schemes exist, and reading partition tables is not
something a driver should do without getting explicit requests.
For all we know the disk contents may be completely random.
You should offer the list of disks seen to user space, and user space
should decide which disks have to be investigated, and tell the kernel
about the partitions it wants to have on these disks.
That way all knowledge about partitioning, dynamic disks, disk managers
and the like is removed from the kernel, and moved into partx-type code.
Andries
next reply other threads:[~2002-05-29 18:07 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-29 18:07 Andries.Brouwer [this message]
2002-05-29 21:57 ` Martin Dalecki
-- strict thread matches above, loose matches on Subject: below --
2002-05-30 15:56 Andries.Brouwer
2002-05-30 14:43 Andries.Brouwer
2002-05-30 14:01 ` Martin Dalecki
2002-05-30 15:09 ` Rene Rebe
2002-05-31 13:25 ` Denis Vlasenko
2002-05-30 12:35 Bartlomiej Zolnierkiewicz
2002-05-30 0:19 Andries.Brouwer
2002-05-30 13:02 ` Martin Dalecki
2002-05-30 15:32 ` Alan Cox
2002-05-30 13:54 ` Martin Dalecki
2002-05-30 15:05 ` Tomas Szepe
2002-05-30 15:13 ` Rene Rebe
2002-05-30 15:39 ` Wichert Akkerman
2002-05-30 16:13 ` Alan Cox
2002-05-30 14:20 ` Martin Dalecki
2002-05-30 15:31 ` Linus Torvalds
2002-05-30 18:55 ` Martin Dalecki
2002-05-30 15:25 ` Linus Torvalds
2002-05-29 23:40 Andries.Brouwer
2002-05-29 22:53 ` Martin Dalecki
2002-05-29 18:16 Andries.Brouwer
2002-05-29 13:59 Gerald Champagne
2002-05-29 13:03 ` Martin Dalecki
2002-05-29 14:26 ` Gerald Champagne
2002-05-29 14:35 ` Russell King
2002-05-29 13:40 ` Martin Dalecki
2002-05-29 16:33 ` Vojtech Pavlik
2002-05-29 15:46 ` Martin Dalecki
2002-05-29 18:47 ` Alan Cox
2002-05-30 8:48 ` David Woodhouse
2002-05-30 12:22 ` Martin Dalecki
2002-05-29 17:55 ` Alan Cox
2002-05-29 17:01 ` Vojtech Pavlik
2002-05-29 16:05 ` Martin Dalecki
2002-05-29 17:05 ` Vojtech Pavlik
2002-05-29 18:43 ` Alan Cox
2002-05-25 2:02 Linux-2.5.18 Linus Torvalds
2002-05-29 12:11 ` [PATCH] 2.5.18 IDE 73 Martin Dalecki
2002-05-29 12:58 ` Zwane Mwaikambo
2002-05-29 12:52 ` Martin Dalecki
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=UTC200205291807.g4TI7DN15827.aeb@smtp.cwi.nl \
--to=andries.brouwer@cwi.nl \
--cc=dalecki@evision-ventures.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.com \
/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®