From: Jens Axboe <axboe@kernel.dk>
To: "John Paul Adrian Glaubitz" <glaubitz@physik.fu-berlin.de>,
"René Rebe" <rene@exactco.de>
Cc: linux-block@vger.kernel.org, efremov@linux.com,
Nick Bowler <nbowler@draconx.ca>
Subject: Re: [PATCH] fix floppy for PAGE_SIZE != 4KB
Date: Wed, 19 Nov 2025 08:00:42 -0700 [thread overview]
Message-ID: <8cc33afa-8017-4e24-96d0-9c580c992301@kernel.dk> (raw)
In-Reply-To: <792a2d8cc1204c5b3fee76826ab24569c1fa152e.camel@physik.fu-berlin.de>
On 11/19/25 2:39 AM, John Paul Adrian Glaubitz wrote:
> Hi,
>
> On Wed, 2025-11-19 at 10:24 +0100, Ren? Rebe wrote:
>> Hi,
>>
>>> On 19. Nov 2025, at 10:22, John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de> wrote:
>>>
>>> On Wed, 2025-11-19 at 10:12 +0100, Ren? Rebe wrote:
>>>>>> 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
>>>>>
>>>>> Yes, Nick Bowler (CC'ed) bisected it to this commit in [1].
>>>>
>>>> Nice, thanks!
>>>>
>>>> Carefully, it appears to be another commit though:
>>>>
>>>>> I bisected the failure to this old commit:
>>>>>
>>>>> commit 74d46992e0d9dee7f1f376de0d56d31614c8a17a
>>>>> Author: Christoph Hellwig <hch@lst.de>
>>>>> Date: Wed Aug 23 19:10:32 2017 +0200
>>>>> block: replace bi_bdev with a gendisk pointer and partitions index
>>>
>>> Yes, you're right. I was briefly distracted when writing this mail.
>>
>> No worries, just checking. Should I send a new patch with the Fixes:
>> or can Jens just add it?
>
> Jens picked the patch up for his block tree already [1], but he could still take
> a version 2 from you and force-push the new patch to his tree.
>
> The proper tag would be:
>
> Fixes: 74d46992e0d9 ("block: replace bi_bdev with a gendisk pointer and partitions index")
>
> It's up to Jens in any case.
Yeah not doing that for something that went unfixed for 8 years. It's
clearly not that important. Rene will see stable bot rejects as the
author, so I'd suggest just watching for those in a few weeks and
sending in a modified patch. It should go into 5.4, 5.10, 5.15, 6.1,
6.6, and 6.12. Possibly 6.17 unless that gets deprecated before then.
--
Jens Axboe
next prev parent reply other threads:[~2025-11-19 15:00 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
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 [this message]
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=8cc33afa-8017-4e24-96d0-9c580c992301@kernel.dk \
--to=axboe@kernel.dk \
--cc=efremov@linux.com \
--cc=glaubitz@physik.fu-berlin.de \
--cc=linux-block@vger.kernel.org \
--cc=nbowler@draconx.ca \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox