From: Mikael Pettersson <mikpe@csd.uu.se>
To: torvalds@transmeta.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.5.33-bk testing
Date: Sun, 1 Sep 2002 21:16:49 +0200 (MET DST) [thread overview]
Message-ID: <200209011916.VAA18956@harpo.it.uu.se> (raw)
On Sun, 1 Sep 2002 11:03:44 -0700 (PDT), Linus Torvalds wrote:
>On Sun, 1 Sep 2002, Mikael Pettersson wrote:
>>
>> The patch below is an update of the floppy workarounds patch
>> I've been maintaining since the problems began in 2.5.13.
>> With this patch I'm able to reliably read and write to the
>> raw /dev/fd0 device. I'm not suggesting that my hack to
>> bdev->bd_block_size is the correct fix, but maybe someone who
>> understands the block I/O system can see what's going on and
>> do a proper fix.
>
>It looks like what your fix does is to force a 512-byte blocksize on the
>floppy.
>
>Which implies to me that the floppy driver is broken for other blocksizes.
I did not test other block sizes. I just tested with the hardsect size
and noticed that that combo worked.
>Does your patch still leave the floppy driver broken for something like a
>mounted minix or ext2 filesystem? Those have 1kB blocksizes, and will set
>it to that. If the non-512B blocksize in the floppy driver is broken, then
>such mounted filesystems should not work reliably either.
In kernels 2.5.13--2.5.32, it was always the case that with my hack,
a mounted ext2 would seem to work for a while and then break down,
e.g. when unmounted and fsck:d. I haven't checked 2.5.33.
Also, attempts to put lilo on ext2 on /dev/fd0 would throw the
kernel into an infinite stream of "buffer layer error!" from
buffer.c:__find_get_block_slow().
/Mikael
next reply other threads:[~2002-09-01 19:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-01 19:16 Mikael Pettersson [this message]
2002-09-01 19:34 ` Linus Torvalds
-- strict thread matches above, loose matches on Subject: below --
2002-09-01 11:59 Mikael Pettersson
2002-09-01 16:31 ` Thomas Molina
2002-09-01 18:03 ` Linus Torvalds
2002-09-01 19:00 ` Thomas Molina
2002-09-01 3:23 Thomas Molina
2002-09-01 5:24 ` Linus Torvalds
2002-09-01 6:06 ` David S. Miller
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=200209011916.VAA18956@harpo.it.uu.se \
--to=mikpe@csd.uu.se \
--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®