Changes in Makefile

bc5b533b - rust: block: add rnull, Rust null_blk implementation

Tue, 11 Jun 2024 11:45:50 +0000

rust: block: add rnull, Rust null_blk implementationThis patch adds an initial version of the Rust null block driver.Signed-off-by: Andreas Hindborg Reviewed-by: Benno Lossin Link: https://lore.kernel.org/r/20240611114551.228679-3-nmi@metaspace.dkSigned-off-by: Jens Axboe List of files: /linux-6.15/drivers/block/Makefile

4b83e99e - Revert "pktcdvd: remove driver."

Wed, 04 Jan 2023 21:44:13 +0000

Revert "pktcdvd: remove driver."This reverts commit f40eb99897af665f11858dd7b56edcb62c3f3c67.There are apparently still users out there of this driver. While we'dlove to remove it to ease the maintenance burden, let's reinstate itfor now until better (userspace) solutions can be developed.Link: https://lore.kernel.org/lkml/20230104190115.ceglfefco475ev6c@pali/Reported-by: Pali Rohár Signed-off-by: Jens Axboe List of files: /linux-6.15/drivers/block/Makefile

f40eb998 - pktcdvd: remove driver.

Fri, 02 Dec 2022 18:27:58 +0000

pktcdvd: remove driver.Way back in 2016 in commit 5a8b187c61e9 ("pktcdvd: mark as unmaintainedand deprecated") this driver was marked as "will be removed soon". 5years seems long enough to have it stick around after that, so finallyremove the thing now.Reported-by: Christoph Hellwig Cc: Jens Axboe Cc: Thomas Maier Cc: Peter Osterlund Cc: linux-block@vger.kernel.orgSigned-off-by: Greg Kroah-Hartman Link: https://lore.kernel.org/r/20221202182758.1339039-1-gregkh@linuxfoundation.orgSigned-off-by: Jens Axboe List of files: /linux-6.15/drivers/block/Makefile

d13bc4d8 - remove the sx8 block driver

Thu, 21 Jul 2022 06:41:02 +0000

remove the sx8 block driverThis driver is for fairly obscure hardware, and has only seen randomdrive-by changes after the maintainer stopped working on it in 2005(about a year and a half after it was introduced). It has some"interesting" block layer interactions, so let's just drop it unlessanyone complains.Signed-off-by: Christoph Hellwig Link: https://lore.kernel.org/r/20220721064102.1715460-1-hch@lst.de[axboe: fix date typo, it was in 2005, not 2015]Signed-off-by: Jens Axboe List of files: /linux-6.15/drivers/block/Makefile

71f28f31 - ublk_drv: add io_uring based userspace block driver

Wed, 13 Jul 2022 14:07:10 +0000

ublk_drv: add io_uring based userspace block driverThis is the driver part of userspace block driver(ublk driver), the otherpart is userspace daemon part(ublksrv)[1].The two parts communicate by io_uring's IORING_OP_URING_CMD with oneshared cmd buffer for storing io command, and the buffer is read only forublksrv, each io command is indexed by io request tag directly, and iswritten by ublk driver.For example, when one READ io request is submitted to ublk block driver,ublk driver stores the io command into cmd buffer first, then completesone IORING_OP_URING_CMD for notifying ublksrv, and the URING_CMD is issuedto ublk driver beforehand by ublksrv for getting notification of any newio request, and each URING_CMD is associated with one io request by tag.After ublksrv gets the io command, it translates and handles the ublk iorequest, such as, for the ublk-loop target, ublksrv translates the requestinto same request on another file or disk, like the kernel loop blockdriver. In ublksrv's implementation, the io is still handled by io_uring,and share same ring with IORING_OP_URING_CMD command. When the target iorequest is done, the same IORING_OP_URING_CMD is issued to ublk driver forboth committing io request result and getting future notification of newio request.Another thing done by ublk driver is to copy data between kernel iorequest and ublksrv's io buffer:1) before ubsrv handles WRITE request, copy the request's data into ublksrv's userspace io buffer, so that ublksrv can handle the write request2) after ubsrv handles READ request, copy ublksrv's userspace io buffer into this READ request, then ublk driver can complete the READ requestZero copy may be switched if mm is ready to support it.ublk driver doesn't handle any logic of the specific user space driver,so it is small/simple enough.[1] ublksrvhttps://github.com/ming1/ubdsrvSigned-off-by: Ming Lei Link: https://lore.kernel.org/r/20220713140711.97356-2-ming.lei@redhat.comSigned-off-by: Jens Axboe List of files: /linux-6.15/drivers/block/Makefile

3427f2b2 - block: remove the rsxx driver

Thu, 16 Dec 2021 08:42:44 +0000

block: remove the rsxx driverThis driver was for rare and shortlived high end enterprise hardwareand hasn't been maintained since 2014, which also means it never gotconverted to use blk-mq.Signed-off-by: Christoph Hellwig Signed-off-by: Jens Axboe List of files: /linux-6.15/drivers/block/Makefile

47e96246 - block: remove support for cryptoloop and the xor transfer

Tue, 19 Oct 2021 07:56:39 +0000

block: remove support for cryptoloop and the xor transferSupport for cyrptoloop has been officially marked broken and deprecatedin favor of dm-crypt (which supports the same broken algorithms ifneeded) in Linux 2.6.4 (released in March 2004), and support for it hasbeen entirely removed from losetup in util-linux 2.23 (released in April2013). The XOR transfer has never been more than a toy to demonstratethe transfer in the bad old times of crypto export restrictions.Remove them as they have some nasty interactions with loop device lifetimes due to the iteration over all loop devices inloop_unregister_transfer.Suggested-by: Milan Broz Signed-off-by: Christoph Hellwig Link: https://lore.kernel.org/r/20211019075639.2333969-1-hch@lst.deSigned-off-by: Jens Axboe List of files: /linux-6.15/drivers/block/Makefile

14d97622 - drivers/block: remove the umem driver

Tue, 23 Mar 2021 19:07:10 +0000

drivers/block: remove the umem driverThis removes the driver on the premise that it has been unused for a longtime. This is a better approach compared to changing untestable codenobody cares about in the first place. Similarly, the umem.com website nowshows a mere Godaddy parking add.Acked-by: NeilBrown Suggested-by: Christoph Hellwig Signed-off-by: Davidlohr Bueso Signed-off-by: Jens Axboe List of files: /linux-6.15/drivers/block/Makefile

2907f851 - xsysace: Remove SYSACE driver

Mon, 09 Nov 2020 10:59:41 +0000

xsysace: Remove SYSACE driverSysace IP is no longer used on Xilinx PowerPC 405/440 and Microblazesystems. The driver is not regularly tested and very likely not working forquite a long time that's why remove it.Signed-off-by: Michal Simek Signed-off-by: Jens Axboe List of files: /linux-6.15/drivers/block/Makefile

d9b2a2bb - block: Add n64 cart driver

Sat, 23 Jan 2021 07:53:27 +0000

block: Add n64 cart driverThis adds support for the Nintendo 64 console's carts. Carts are aread-only media ranging from 8mb to 64mb.Only one cart can be connected at once, and switching it requires areboot.No module support to save RAM, as the target has 8mb RAM.Signed-off-by: Lauri Kasanen Reviewed-by: Chaitanya Kulkarni Reviewed-by: Christoph Hellwig Acked-by: Jens Axboe Signed-off-by: Thomas Bogendoerfer List of files: /linux-6.15/drivers/block/Makefile

ee8f353b - block: remove skd driver

Thu, 04 Feb 2021 08:43:42 +0000

block: remove skd driverThe STEC S1220 PCIe SSD cards are EOL since 2014 and not supported bythe vendor anymore. As the skd driver for this SSD is starting to causeproblems with improvements to the block layer, stop supporting it innewer kernel versions.Signed-off-by: Damien Le Moal Signed-off-by: Jens Axboe List of files: /linux-6.15/drivers/block/Makefile

eebf34a8 - null_blk: Move driver into its own directory

Fri, 20 Nov 2020 01:55:19 +0000

null_blk: Move driver into its own directoryMove null_blk driver code into the new sub-directorydrivers/block/null_blk.Suggested-by: Bart Van Assche Signed-off-by: Damien Le Moal Reviewed-by: Johannes Thumshirn Signed-off-by: Jens Axboe List of files: /linux-6.15/drivers/block/Makefile

bc018853 - block/rnbd: include client and server modules into kernel compilation

Mon, 11 May 2020 13:51:29 +0000

block/rnbd: include client and server modules into kernel compilationAdd rnbd Makefile, Kconfig and also corresponding lines into upper blocklayer files.Link: https://lore.kernel.org/r/20200511135131.27580-24-danil.kipnis@cloud.ionos.comSigned-off-by: Danil Kipnis Signed-off-by: Jack Wang Reviewed-by: Bart Van Assche Acked-by: Jens Axboe Signed-off-by: Jason Gunthorpe List of files: /linux-6.15/drivers/block/Makefile

c51d0419 - null_blk: add tracepoint helpers for zoned mode

Wed, 25 Mar 2020 17:49:55 +0000

null_blk: add tracepoint helpers for zoned modeThis patch adds two new tracpoints for null_blk_zoned.c that allows usto trace report-zones, zone-mgmt-op and zone-write operations which hasdirect effect on the zone condition state machine.Also, we update drivers/block/Makefile so that new null_blk relatedtracefiles can be compiled.Signed-off-by: Chaitanya Kulkarni Reviewed-by: Damien Le Moal Signed-off-by: Jens Axboe List of files: /linux-6.15/drivers/block/Makefile

6956b956 - drivers/block: Remove DAC960 driver

Wed, 17 Oct 2018 15:25:13 +0000

drivers/block: Remove DAC960 driverThe DAC960 driver has been obsoleted by the myrb/myrs drivers,so it can be dropped.Signed-off-by: Hannes Reinecke Reviewed-by: Christoph Hellwig Signed-off-by: Jens Axboe List of files: /linux-6.15/drivers/block/Makefile

76f17d8b - block: Rename the null_blk_mod kernel module back into null_blk

Mon, 23 Jul 2018 21:18:33 +0000

block: Rename the null_blk_mod kernel module back into null_blkCommit ca4b2a011948 ("null_blk: add zone support") breaks severalblktests scripts because it renamed the null_blk kernel module intonull_blk_mod. Hence rename null_blk_mod back into null_blk.Fixes: ca4b2a011948 ("null_blk: add zone support")Signed-off-by: Bart Van Assche Cc: Matias Bjorling Cc: Christoph Hellwig Cc: Ming Lei Cc: Damien Le Moal Signed-off-by: Jens Axboe List of files: /linux-6.15/drivers/block/Makefile

ca4b2a01 - null_blk: add zone support

Fri, 06 Jul 2018 17:38:39 +0000

null_blk: add zone supportAdds support for exposing a null_blk device through the zone deviceinterface.The interface is managed with the parameters zoned and zone_size.If zoned is set, the null_blk instance registers as a zoned blockdevice. The zone_size parameter defines how big each zone will be.Signed-off-by: Matias Bjørling Signed-off-by: Bart Van Assche Signed-off-by: Damien Le Moal Signed-off-by: Jens Axboe List of files: /linux-6.15/drivers/block/Makefile

b2441318 - License cleanup: add SPDX GPL-2.0 license identifier to files with no license

Wed, 01 Nov 2017 14:07:57 +0000

License cleanup: add SPDX GPL-2.0 license identifier to files with no licenseMany source files in the tree are missing licensing information, whichmakes it harder for compliance tools to determine the correct license.By default all files without license information are under the defaultlicense of the kernel, which is GPL version 2.Update the files which contain no license information with the 'GPL-2.0'SPDX license identifier. The SPDX identifier is a legally bindingshorthand, which can be used instead of the full boiler plate text.This patch is based on work done by Thomas Gleixner and Kate Stewart andPhilippe Ombredanne.How this work was done:Patches were generated and checked against linux-4.14-rc6 for a subset ofthe use cases: - file had no licensing information it it. - file was a */uapi/* one with no licensing information in it, - file was a */uapi/* one with existing licensing information,Further patches will be generated in subsequent months to fix up caseswhere non-standard license headers were used, and references to licensehad to be inferred by heuristics based on keywords.The analysis to determine which SPDX License Identifier to be applied toa file was done in a spreadsheet of side by side results from of theoutput of two independent scanners (ScanCode & Windriver) producing SPDXtag:value files created by Philippe Ombredanne. Philippe prepared thebase worksheet, and did an initial spot review of a few 1000 files.The 4.13 kernel was the starting point of the analysis with 60,537 filesassessed. Kate Stewart did a file by file comparison of the scannerresults in the spreadsheet to determine which SPDX license identifier(s)to be applied to the file. She confirmed any determination that was notimmediately clear with lawyers working with the Linux Foundation.Criteria used to select files for SPDX license identifier tagging was: - Files considered eligible had to be source code files. - Make and config files were included as candidates if they contained >5 lines of source - File already had some variant of a license header in it (even if <5 lines).All documentation files were explicitly excluded.The following heuristics were used to determine which SPDX licenseidentifiers to apply. - when both scanners couldn't find any license traces, file was considered to have no license information in it, and the top level COPYING file license applied. For non */uapi/* files that summary was: SPDX license identifier # files ---------------------------------------------------|------- GPL-2.0 11139 and resulted in the first patch in this series. If that file was a */uapi/* path one, it was "GPL-2.0 WITH Linux-syscall-note" otherwise it was "GPL-2.0". Results of that was: SPDX license identifier # files ---------------------------------------------------|------- GPL-2.0 WITH Linux-syscall-note 930 and resulted in the second patch in this series. - if a file had some form of licensing information in it, and was one of the */uapi/* ones, it was denoted with the Linux-syscall-note if any GPL family license was found in the file or had no licensing in it (per prior point). Results summary: SPDX license identifier # files ---------------------------------------------------|------ GPL-2.0 WITH Linux-syscall-note 270 GPL-2.0+ WITH Linux-syscall-note 169 ((GPL-2.0 WITH Linux-syscall-note) OR BSD-2-Clause) 21 ((GPL-2.0 WITH Linux-syscall-note) OR BSD-3-Clause) 17 LGPL-2.1+ WITH Linux-syscall-note 15 GPL-1.0+ WITH Linux-syscall-note 14 ((GPL-2.0+ WITH Linux-syscall-note) OR BSD-3-Clause) 5 LGPL-2.0+ WITH Linux-syscall-note 4 LGPL-2.1 WITH Linux-syscall-note 3 ((GPL-2.0 WITH Linux-syscall-note) OR MIT) 3 ((GPL-2.0 WITH Linux-syscall-note) AND MIT) 1 and that resulted in the third patch in this series. - when the two scanners agreed on the detected license(s), that became the concluded license(s). - when there was disagreement between the two scanners (one detected a license but the other didn't, or they both detected different licenses) a manual inspection of the file occurred. - In most cases a manual inspection of the information in the file resulted in a clear resolution of the license that should apply (and which scanner probably needed to revisit its heuristics). - When it was not immediately clear, the license identifier was confirmed with lawyers working with the Linux Foundation. - If there was any question as to the appropriate license identifier, the file was flagged for further research and to be revisited later in time.In total, over 70 hours of logged manual review was done on thespreadsheet to determine the SPDX license identifiers to apply to thesource files by Kate, Philippe, Thomas and, in some cases, confirmationby lawyers working with the Linux Foundation.Kate also obtained a third independent scan of the 4.13 code base fromFOSSology, and compared selected files where the other two scannersdisagreed against that SPDX file, to see if there was new insights. TheWindriver scanner is based on an older version of FOSSology in part, sothey are related.Thomas did random spot checks in about 500 files from the spreadsheetsfor the uapi headers and agreed with SPDX license identifier in thefiles he inspected. For the non-uapi files Thomas did random spot checksin about 15000 files.In initial set of patches against 4.14-rc6, 3 files were found to havecopy/paste license identifier errors, and have been fixed to reflect thecorrect identifier.Additionally Philippe spent 10 hours this week doing a detailed manualinspection and review of the 12,461 patched files from the initial patchversion early this week with: - a full scancode scan run, collecting the matched texts, detected license ids and scores - reviewing anything where there was a license detected (about 500+ files) to ensure that the applied SPDX license was correct - reviewing anything where there was no detection but the patch license was not GPL-2.0 WITH Linux-syscall-note to ensure that the applied SPDX license was correctThis produced a worksheet with 20 files needing minor correction. Thisworksheet was then exported into 3 different .csv files for thedifferent types of files to be modified.These .csv files were then reviewed by Greg. Thomas wrote a script toparse the csv files and add the proper SPDX tag to the file, in theformat that the file expected. This script was further refined by Gregbased on the output to detect more types of files automatically and todistinguish between header and source .c files (which need differentcomment types.) Finally Greg ran the script using the .csv files togenerate the patches.Reviewed-by: Kate Stewart Reviewed-by: Philippe Ombredanne Reviewed-by: Thomas Gleixner Signed-off-by: Greg Kroah-Hartman List of files: /linux-6.15/drivers/block/Makefile

253d2464 - scsi: cciss: Drop obsolete driver

Tue, 15 Aug 2017 06:58:08 +0000

scsi: cciss: Drop obsolete driverThe hpsa driver now has support for all boards the cciss driverused to support, so this patch removes the cciss driver andmake hpsa an alias to cciss.Signed-off-by: Hannes Reinecke Acked-by: Don Brace Signed-off-by: Martin K. Petersen List of files: /linux-6.15/drivers/block/Makefile

10081552 - block: remove the osdblk driver

Wed, 12 Apr 2017 16:01:06 +0000

block: remove the osdblk driverThis was just a proof of concept user for the SCSI OSD library, andnever had any real users.Signed-off-by: Christoph Hellwig Acked-by: Boaz Harrosh Signed-off-by: Jens Axboe List of files: /linux-6.15/drivers/block/Makefile