Your message dated Wed, 05 Feb 2025 14:53:04 +0000
with message-id <e1tfgm0-007zta...@fasolo.debian.org>
and subject line Bug#1093127: fixed in rapiddisk 9.1.0-5
has caused the Debian Bug report #1093127,
regarding rapiddisk-dkms: module fails to build for Linux 6.11
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1093127: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1093127
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: rapiddisk-dkms
Version: 9.1.0-3
Severity: serious
Tags: upstream
Control: forwarded -1 https://github.com/pkoutoupis/rapiddisk/issues/190
DKMS make.log for rapiddisk-9.1.0 for kernel 6.11-rc5-amd64 (x86_64)
Thu Sep 12 11:51:16 UTC 2024
make: Entering directory '/usr/src/linux-headers-6.11-rc5-amd64'
CC [M] /var/lib/dkms/rapiddisk/9.1.0/build/rapiddisk.o
CC [M] /var/lib/dkms/rapiddisk/9.1.0/build/rapiddisk-cache.o
/var/lib/dkms/rapiddisk/9.1.0/build/rapiddisk-cache.c:166:5: warning: no
previous prototype for 'dm_io_async_bvec' [-Wmissing-prototypes]
166 | int dm_io_async_bvec(unsigned int num_regions, struct dm_io_region
*where,
| ^~~~~~~~~~~~~~~~
/var/lib/dkms/rapiddisk/9.1.0/build/rapiddisk-cache.c:260:6: warning: no
previous prototype for 'rc_io_callback' [-Wmissing-prototypes]
260 | void rc_io_callback(unsigned long error, void *context)
| ^~~~~~~~~~~~~~
/var/lib/dkms/rapiddisk/9.1.0/build/rapiddisk-cache.c:376:5: warning: no
previous prototype for 'rc_do_complete' [-Wmissing-prototypes]
376 | int rc_do_complete(struct kcached_job *job)
| ^~~~~~~~~~~~~~
/var/lib/dkms/rapiddisk/9.1.0/build/rapiddisk-cache.c:418:6: warning: no
previous prototype for 'kcached_client_destroy' [-Wmissing-prototypes]
418 | void kcached_client_destroy(struct cache_context *dmc)
| ^~~~~~~~~~~~~~~~~~~~~~
/var/lib/dkms/rapiddisk/9.1.0/build/rapiddisk-cache.c:826:5: warning: no
previous prototype for 'rc_map' [-Wmissing-prototypes]
826 | int rc_map(struct dm_target *ti, struct bio *bio)
| ^~~~~~
/var/lib/dkms/rapiddisk/9.1.0/build/rapiddisk-cache.c:1274:12: warning: no
previous prototype for 'rc_init' [-Wmissing-prototypes]
1274 | int __init rc_init(void)
| ^~~~~~~
/var/lib/dkms/rapiddisk/9.1.0/build/rapiddisk-cache.c:1294:6: warning: no
previous prototype for 'rc_exit' [-Wmissing-prototypes]
1294 | void rc_exit(void)
| ^~~~~~~
/var/lib/dkms/rapiddisk/9.1.0/build/rapiddisk.c: In function 'attach_device':
/var/lib/dkms/rapiddisk/9.1.0/build/rapiddisk.c:824:9: error: implicit
declaration of function 'blk_queue_logical_block_size'; did you mean
'queue_logical_block_size'? [-Wimplicit-function-declaration]
824 | blk_queue_logical_block_size(disk->queue, BYTES_PER_SECTOR);
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~
| queue_logical_block_size
/var/lib/dkms/rapiddisk/9.1.0/build/rapiddisk.c:825:9: error: implicit
declaration of function 'blk_queue_physical_block_size'; did you mean
'queue_physical_block_size'? [-Wimplicit-function-declaration]
825 | blk_queue_physical_block_size(disk->queue, PAGE_SIZE);
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~
| queue_physical_block_size
/var/lib/dkms/rapiddisk/9.1.0/build/rapiddisk.c:832:9: error: too many
arguments to function 'blk_queue_write_cache'
832 | blk_queue_write_cache(disk->queue, false, false);
| ^~~~~~~~~~~~~~~~~~~~~
In file included from /var/lib/dkms/rapiddisk/9.1.0/build/rapiddisk.c:30:
/usr/src/linux-headers-6.11-rc5-common/include/linux/blkdev.h:1322:20: note:
declared here
1322 | static inline bool blk_queue_write_cache(struct request_queue *q)
| ^~~~~~~~~~~~~~~~~~~~~
/var/lib/dkms/rapiddisk/9.1.0/build/rapiddisk.c:848:9: error: implicit
declaration of function 'blk_queue_max_discard_sectors'; did you mean
'bdev_max_discard_sectors'? [-Wimplicit-function-declaration]
848 | blk_queue_max_discard_sectors(disk->queue, 0);
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~
| bdev_max_discard_sectors
/var/lib/dkms/rapiddisk/9.1.0/build/rapiddisk.c:852:28: error:
'QUEUE_FLAG_NONROT' undeclared (first use in this function); did you mean
'QUEUE_FLAG_NOMERGES'?
852 | blk_queue_flag_set(QUEUE_FLAG_NONROT, disk->queue);
| ^~~~~~~~~~~~~~~~~
| QUEUE_FLAG_NOMERGES
/var/lib/dkms/rapiddisk/9.1.0/build/rapiddisk.c:852:28: note: each undeclared
identifier is reported only once for each function it appears in
make[2]: ***
[/usr/src/linux-headers-6.11-rc5-common/scripts/Makefile.build:249:
/var/lib/dkms/rapiddisk/9.1.0/build/rapiddisk.o] Error 1
make[2]: *** Waiting for unfinished jobs....
make[1]: *** [/usr/src/linux-headers-6.11-rc5-common/Makefile:1950:
/var/lib/dkms/rapiddisk/9.1.0/build] Error 2
make: *** [/usr/src/linux-headers-6.11-rc5-common/Makefile:236: __sub-make]
Error 2
make: Leaving directory '/usr/src/linux-headers-6.11-rc5-amd64'
blk_queue_logical_block_size etc. were removed in Linux v6.11-rc1 by
torvalds/linux@1652b0b
QUEUE_FLAG_NONROT was replaced in Linux v6.11-rc1 by torvalds/linux@bd4a633
@Augusto7743
Augusto7743 commented Nov 8, 2024
Only reporting information.
I have done an test in kernel liquorix 6.11 and not is possible compile being
showed the errors below
make -C module
make[1]: Entering directory '/home/user/rd/module'
make -C /lib/modules/6.11.5-1-liquorix-amd64/build M=/home/user/rd/module
make[2]: Entering directory '/usr/src/linux-headers-6.11.5-1-liquorix-amd64'
CC [M] /home/user/rd/module/rapiddisk.o
/home/user/rd/module/rapiddisk.c: In function ‘attach_device’:
/home/user/rd/module/rapiddisk.c:824:9: error: implicit declaration of function
‘blk_queue_logical_block_size’; did you mean ‘queue_logical_block_size’?
[-Werror=implicit-function-declaration]
824 | blk_queue_logical_block_size(disk->queue, BYTES_PER_SECTOR);
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~
| queue_logical_block_size
/home/user/rd/module/rapiddisk.c:825:9: error: implicit declaration of function
‘blk_queue_physical_block_size’; did you mean ‘queue_physical_block_size’?
[-Werror=implicit-function-declaration]
825 | blk_queue_physical_block_size(disk->queue, PAGE_SIZE);
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~
| queue_physical_block_size
/home/user/rd/module/rapiddisk.c:832:9: error: too many arguments to function
‘blk_queue_write_cache’
832 | blk_queue_write_cache(disk->queue, false, false);
| ^~~~~~~~~~~~~~~~~~~~~
In file included from /home/user/rd/module/rapiddisk.c:30:
./include/linux/blkdev.h:1322:20: note: declared here
1322 | static inline bool blk_queue_write_cache(struct request_queue *q)
| ^~~~~~~~~~~~~~~~~~~~~
/home/user/rd/module/rapiddisk.c:848:9: error: implicit declaration of function
‘blk_queue_max_discard_sectors’; did you mean ‘bdev_max_discard_sectors’?
[-Werror=implicit-function-declaration]
848 | blk_queue_max_discard_sectors(disk->queue, 0);
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~
| bdev_max_discard_sectors
/home/user/rd/module/rapiddisk.c:852:28: error: ‘QUEUE_FLAG_NONROT’ undeclared
(first use in this function); did you mean ‘QUEUE_FLAG_NOMERGES’?
852 | blk_queue_flag_set(QUEUE_FLAG_NONROT, disk->queue);
| ^~~~~~~~~~~~~~~~~
| QUEUE_FLAG_NOMERGES
/home/user/rd/module/rapiddisk.c:852:28: note: each undeclared identifier is
reported only once for each function it appears in
cc1: some warnings being treated as errors
make[4]: *** [scripts/Makefile.build:244: /home/user/rd/module/rapiddisk.o]
Error 1
make[3]: *** [/usr/src/linux-headers-6.11.5-1-liquorix-amd64/Makefile:1937:
/home/user/rd/module] Error 2
make[2]: *** [Makefile:224: __sub-make] Error 2
make[2]: Leaving directory '/usr/src/linux-headers-6.11.5-1-liquorix-amd64'
make[1]: *** [Makefile:37: all] Error 2
make[1]: Leaving directory '/home/user/rd/module'
make: *** [Makefile:29: module] Error 2
Andreas
--- End Message ---
--- Begin Message ---
Source: rapiddisk
Source-Version: 9.1.0-5
Done: Andreas Beckmann <a...@debian.org>
We believe that the bug you reported is fixed in the latest version of
rapiddisk, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 1093...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Andreas Beckmann <a...@debian.org> (supplier of updated rapiddisk package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Format: 1.8
Date: Wed, 05 Feb 2025 15:33:57 +0100
Source: rapiddisk
Architecture: source
Version: 9.1.0-5
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group <packa...@qa.debian.org>
Changed-By: Andreas Beckmann <a...@debian.org>
Closes: 1093127
Changes:
rapiddisk (9.1.0-5) unstable; urgency=medium
.
* QA upload.
.
[ Paolo Pisati ]
* Fix FTBFS with Linux 6.11. (Closes: #1093127)
Checksums-Sha1:
cd38ca04ad5d7724152e30a22be88579c880f56d 2039 rapiddisk_9.1.0-5.dsc
888353b609167c48ba9851f68dec97c6157c419c 8068 rapiddisk_9.1.0-5.debian.tar.xz
4810f3e4dcd40a07c829e1288d96b922a719d14f 6412
rapiddisk_9.1.0-5_source.buildinfo
Checksums-Sha256:
505b0072c267de747d165b197fcdc69cf5760b308fe6282adc0e7f9fde34002d 2039
rapiddisk_9.1.0-5.dsc
41810fe804d347fa6fccbaa3bc55df205c4862ce615935a17cdb88bb81d90051 8068
rapiddisk_9.1.0-5.debian.tar.xz
9cb9ad10e11d9c0b2f91989dac807554a6a3c4db9bcdc84506afd33831ca8895 6412
rapiddisk_9.1.0-5_source.buildinfo
Files:
334bf2a4458416d633c934d6da40a77b 2039 kernel optional rapiddisk_9.1.0-5.dsc
2abc0ad77969721504a544ebf97544e6 8068 kernel optional
rapiddisk_9.1.0-5.debian.tar.xz
f276404c679f4dc3fde1a9c5eba94f17 6412 kernel optional
rapiddisk_9.1.0-5_source.buildinfo
-----BEGIN PGP SIGNATURE-----
iQJEBAEBCAAuFiEE6/MKMKjZxjvaRMaUX7M/k1np7QgFAmejd2IQHGFuYmVAZGVi
aWFuLm9yZwAKCRBfsz+TWentCLoPD/9C6P40C7MsaEWVN+JQtE9YRmPkulpfuHv/
KoNrSNyet/XkI4k0fn02GzeX59Vh7J2uIdvy8BFHui8N1OC7qhhZ2tgdmE2GY8bC
U8G/ik8e7GNMvJeF9GEhHxbHwlBrI6TOHPauYZvfYlUyBavmCNjBY45zeLvG6eZp
sFFHwJQktMuUFqIkK6cVhE5CA/3S6XVJFF1Rr1eqMbdH0D9+uMqPLeaXYzwsB4DI
NgS3mTAr8WKhLX6xenFsRB0tLSVPM3a+xRwMBTSJqiCMmkFZ7LcD96Fy8L2UQDDo
8c4AwJtwVRF3JAz2lWIA4kG0qey8bAaf9XBRAYkScezTL/x0QPi8SNE7xMktBrhd
kcqYuxNSMOHkSPE5TrKtI70Yh5sVQm/CpIVhjfytuo6qgHeNmojxYpy5Pid9P5ct
PsMwwzRHnt3zIiaMAnyuryK1hj7YIiOkwiYS11sP5rjvs5mdNeF28mIBuhgqfyQU
40IZNZ7bPT15ywWV/TMOc1dfrO7Ptc3lJwbmNPjnUA80y/f7Ljuma+tykXwX02q7
+uLJhu9L+gagvXOqOkPW49DtZOkBzeIaTlKFHi5dRNLS4scad1vk9oNeGMtqhx2K
ENUKmas8ntKT9sEu7TF/3EsiCoirqghhUIy/ZsDs9iqBVtR++G0tQIwHzzbHPqjs
f+GloJyJmQ==
=QxN1
-----END PGP SIGNATURE-----
pgpgCml3d8x0M.pgp
Description: PGP signature
--- End Message ---
