From: Martin Dalecki <dalecki@evision-ventures.com>
To: Andries.Brouwer@cwi.nl
Cc: linux-kernel@vger.kernel.org, torvalds@transmeta.com, viro@math.psu.edu
Subject: Re: [PATCH] struct char_device
Date: Wed, 23 May 2001 00:47:18 +0200 [thread overview]
Message-ID: <3B0AEC76.F5B425F5@evision-ventures.com> (raw)
In-Reply-To: <UTC200105222217.AAA79157.aeb@vlet.cwi.nl>
And if we are at the topic... Those are the places where blk_size[]
get's
abused, since it's in fact a property of a FS in fact and not the
property of
a particular device... blksect_size is the array describing the physical
access limits of a device and blk_size get's usually checked against it.
However due to the bad naming and the fact that this information is
associated with major/minor number usage same device driver writers got
*very* confused as you can see below:
./fs/block_dev.c: Here this information should be passed entierly insice
the request.
./fs/partitions/check.c: Here it basically get's reset or ignored
Here it's serving the purpose of a sector size, which is bogous!
./mm/swapfile.c:#include <linux/blkdev.h> /* for blk_size */
./mm/swapfile.c: if (!dev || (blk_size[MAJOR(dev)] &&
./mm/swapfile.c: !blk_size[MAJOR(dev)][MINOR(dev)]))
./mm/swapfile.c: if (blk_size[MAJOR(dev)])
./mm/swapfile.c: swapfilesize = blk_size[MAJOR(dev)][MINOR(dev)]
Here it shouldn't be needed
./drivers/block/ll_rw_blk.c:
./drivers/block/floppy.c: blk_size[MAJOR_NR] = floppy_sizes;
./drivers/block/nbd.c: blk_size[MAJOR_NR] = nbd_sizes;
./drivers/block/rd.c: * and set blk_size for -ENOSPC, Werner Fink
<werner@suse.de>, Apr '99
./drivers/block/amiflop.c: blk_size[MAJOR_NR] = floppy_sizes;
./drivers/block/loop.c: if (blk_size[MAJOR(lodev)])
./drivers/block/ataflop.c: * - Set blk_size for proper size checking
./drivers/block/ataflop.c: blk_size[MAJOR_NR] = floppy_sizes;
./drivers/block/cpqarray.c: drv->blk_size;
./drivers/block/z2ram.c: blk_size[ MAJOR_NR ] = z2_sizes;
./drivers/block/swim3.c: blk_size[MAJOR_NR] = floppy_sizes;
./drivers/block/swim_iop.c: blk_size[MAJOR_NR] = floppy_sizes;
./drivers/char/raw.c: if (blk_size[MAJOR(dev)])
./drivers/scsi/advansys.c: ASC_DCNT blk_size;
./drivers/scsi/sd.c: blk_size[SD_MAJOR(i)] = NULL;
./drivers/scsi/sr.c: blk_size[MAJOR_NR] = sr_sizes;
./drivers/scsi/sr.c: blk_size[MAJOR_NR] = NULL;
./drivers/sbus/char/jsflash.c: blk_size[JSFD_MAJOR] = jsfd_sizes;
./drivers/ide/ide-cd.c: blk_size[HWIF(drive)->major] =
HWIF(drive)->gd->sizes;
./drivers/ide/ide-floppy.c: * Revalidate the new media. Should set
blk_size[]
./drivers/acorn/block/fd1772.c: blk_size[MAJOR_NR] = floppy_sizes;
./drivers/i2o/i2o_block.c: blk_size[MAJOR_NR] = i2ob_sizes;
In the following they are REALLY confusing it and then compensating for
this misunderstanding in lvm.h by redefining the corresponding default
values.
./drivers/s390/*
And then some minor confusions follow...
./drivers/mtd/mtdblock.c: blk_size[MAJOR_NR] = NULL;
./drivers/md/md.c: if (blk_size[MAJOR(dev)])
./arch/m68k/atari/stram.c: blk_size[STRAM_MAJOR] = stram_sizes;
Basically one should just stop setting blk_size[][] inside *ANY* driver
and anything should still work fine unless the driver is broken...
Well that's the point for another fine kernel experiment I will do
and report whatever it works really out like this in reality 8-)
next prev parent reply other threads:[~2001-05-22 22:48 UTC|newest]
Thread overview: 55+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-22 22:17 [PATCH] struct char_device Andries.Brouwer
2001-05-22 22:34 ` Martin Dalecki
2001-05-22 22:47 ` Martin Dalecki [this message]
2001-05-23 0:02 ` Jeff Garzik
2001-05-23 0:14 ` Jens Axboe
2001-05-23 2:40 ` Linus Torvalds
2001-05-23 12:35 ` Martin Dalecki
-- strict thread matches above, loose matches on Subject: below --
2001-05-23 20:01 Andries.Brouwer
2001-05-23 18:28 Andries.Brouwer
2001-05-23 18:42 ` Alexander Viro
2001-05-23 15:24 Wayne.Brown
2001-05-23 13:34 Andries.Brouwer
2001-05-23 17:54 ` Alexander Viro
2001-05-24 10:35 ` Stephen C. Tweedie
2001-05-23 12:29 Andries.Brouwer
2001-05-23 12:30 ` Alan Cox
2001-05-23 13:26 ` Helge Hafting
2001-05-23 11:57 Andries.Brouwer
2001-05-23 12:13 ` Alan Cox
2001-05-23 6:47 Andries.Brouwer
2001-05-23 0:28 Andries.Brouwer
2001-05-23 0:38 ` Alexander Viro
2001-05-23 0:22 Andries.Brouwer
2001-05-23 0:29 ` Martin Dalecki
2001-05-23 0:20 Andries.Brouwer
2001-05-23 2:43 ` Linus Torvalds
2001-05-23 0:01 Andries.Brouwer
2001-05-22 23:33 Andries.Brouwer
2001-05-23 0:03 ` Alexander Viro
2001-05-22 21:35 Andries.Brouwer
2001-05-22 22:00 ` Martin Dalecki
2001-05-22 20:54 Andries.Brouwer
2001-05-22 21:17 ` Martin Dalecki
2001-05-22 22:37 ` Linus Torvalds
2001-05-22 23:51 ` Alexander Viro
2001-05-23 0:06 ` Jeff Garzik
2001-05-23 0:14 ` Jens Axboe
2001-05-23 2:37 ` Linus Torvalds
2001-05-23 3:04 ` Jeff Garzik
2001-05-23 3:21 ` Jeff Garzik
2001-05-23 9:05 ` Alan Cox
2001-05-23 2:35 ` Linus Torvalds
2001-05-22 19:52 Andries.Brouwer
2001-05-22 20:10 ` Alexander Viro
[not found] <Pine.GSO.4.21.0105221007460.15685-100000@weyl.math.psu.edu >
2001-05-22 15:26 ` Anton Altaparmakov
2001-05-22 16:08 ` Oliver Xymoron
2001-05-22 16:12 ` Alexander Viro
2001-05-22 17:30 ` Oliver Xymoron
2001-05-22 17:41 ` Alexander Viro
2001-05-22 19:22 ` Guest section DW
2001-05-22 19:25 ` Alexander Viro
2001-05-22 19:38 ` Oliver Xymoron
[not found] <Pine.LNX.4.10.10105221050080.8984-100000@coffee.psychology.mcmaster.ca>
2001-05-22 14:59 ` Tommy Hallgren
2001-05-22 14:40 Tommy Hallgren
2001-05-22 14:18 Alexander Viro
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=3B0AEC76.F5B425F5@evision-ventures.com \
--to=dalecki@evision-ventures.com \
--cc=Andries.Brouwer@cwi.nl \
--cc=linux-kernel@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