All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@kernel.dk>
To: "René Rebe" <rene@exactco.de>
Cc: linux-block@vger.kernel.org, efremov@linux.com
Subject: Re: [PATCH] fix floppy for PAGE_SIZE != 4KB
Date: Mon, 17 Nov 2025 06:23:09 -0700	[thread overview]
Message-ID: <c8cbccc1-964c-43ce-a992-624d2efcfd4a@kernel.dk> (raw)
In-Reply-To: <708B7962-86CD-489B-AC33-4B929F2902B6@exactco.de>

On 11/17/25 2:56 AM, Ren? Rebe wrote:
> Hi,
> 
>>> 64k is 4% of a floppy disk! But I hear you, works for you.
>>
>> Again, still only 8k or 16k for most of such remaining workstation
>> floppy users.
>>
>>>> But if someone wants to refactor this code some more, ... I'm happy to
>>>> test it, too ;-)
>>>
>>> I don't think refactoring would be required here, it's probably just
>>> capping that probe read to something constant irrespective of hardware
>>> page sizes.
>>
>> Well, the floppy.c __floppy_read_block_0 does:
>>        bio_init(&bio, bdev, &bio_vec, 1, REQ_OP_READ);
>>        __bio_add_page(&bio, page, block_size(bdev), 0);
>>
>> Is there an easy way to limit that to less than a page without
>> refactoring it too much? Otherwise we could just apply this hotfix for
>> now.
> 
> 
> Any chance we can get my initial one liner constant PAGE_SIZE fix
> for this over a decade old bug in? I currently don?t have a budget
> to refactor the floppy driver probing for efficiency on bigger PAGE_SIZE
> configs I?m not even having a floppy controller on.

Yep we can do that. It'd be great if we could augment the change with
what commit broke it, so it can get backported to stable kernels as
well. Was it:

commit fe4ec12e1865a2114056b799e4869bf4c30e47df
Author: Christoph Hellwig <hch@lst.de>
Date:   Fri Jun 26 10:01:52 2020 +0200

    floppy: use block_size

?

-- 
Jens Axboe

  reply	other threads:[~2025-11-17 13:23 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-14 13:41 [PATCH] fix floppy for PAGE_SIZE != 4KB Rene Rebe
2025-11-14 16:11 ` Jens Axboe
2025-11-14 16:25   ` René Rebe
2025-11-14 17:39     ` Jens Axboe
2025-11-14 18:21       ` René Rebe
2025-11-17  9:56         ` René Rebe
2025-11-17 13:23           ` Jens Axboe [this message]
2025-11-17 13:57             ` René Rebe
2025-11-17 15:23               ` Jens Axboe
2025-11-19  9:00             ` John Paul Adrian Glaubitz
2025-11-19  9:12               ` René Rebe
2025-11-19  9:22                 ` John Paul Adrian Glaubitz
2025-11-19  9:24                   ` René Rebe
2025-11-19  9:39                     ` John Paul Adrian Glaubitz
2025-11-19 15:00                       ` Jens Axboe
2025-11-19  8:58   ` John Paul Adrian Glaubitz
2025-11-17 15:23 ` Jens Axboe
2025-11-22 10:28 ` Gregor Riepl

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=c8cbccc1-964c-43ce-a992-624d2efcfd4a@kernel.dk \
    --to=axboe@kernel.dk \
    --cc=efremov@linux.com \
    --cc=linux-block@vger.kernel.org \
    --cc=rene@exactco.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.