Changes in Makefile

d6800634 - nvme: rework NVME_AUTH Kconfig selection

Thu, 12 Oct 2023 12:22:48 +0000

nvme: rework NVME_AUTH Kconfig selectionHaving a single Kconfig symbol NVME_AUTH conflates the selectionof the authentication functions from nvme/common and nvme/host,causing kbuild robot to complain when building the nvme targetonly. So introduce a Kconfig symbol NVME_HOST_AUTH for the nvmehost bits and use NVME_AUTH for the common functions only.And move the CRYPTO selection into nvme/common to make iteasier to read.Reported-by: kernel test robot Closes: https://lore.kernel.org/oe-kbuild-all/202310120733.TlPOVeJm-lkp@intel.com/Signed-off-by: Hannes Reinecke Signed-off-by: Keith Busch List of files: /linux-6.15/drivers/nvme/host/Makefile

942e21c0 - nvme: move sysfs code to a dedicated sysfs.c file

Mon, 24 Apr 2023 21:12:42 +0000

nvme: move sysfs code to a dedicated sysfs.c fileThe core.c file became long and hard to maintain. Create a dedicatedfile to centralize the sysfs functionality. This is a common practice toseparate sysfs/configfs related logic from the main driver logic .c file.For example, in the nvmet module the configfs interface has its owndedicated file.This patch does not include any functional changes.Reviewed-by: Keith Busch Reviewed-by: Christoph Hellwig Reviewed-by: Jens Axboe Reviewed-by: Hannes Reinecke Signed-off-by: Max Gurtovoy [merged dhchap memleak fixes, include nvme-auth.h]Signed-off-by: Keith Busch List of files: /linux-6.15/drivers/nvme/host/Makefile

b668f2f5 - nvme: Move pr code to it's own file

Fri, 07 Apr 2023 20:05:42 +0000

nvme: Move pr code to it's own fileThis patch moves the pr code to it's own file because I'm going to beadding more functions and core.c is getting bigger.Signed-off-by: Mike Christie Link: https://lore.kernel.org/r/20230407200551.12660-10-michael.christie@oracle.comReviewed-by: Chaitanya Kulkarni Reviewed-by: Keith Busch Reviewed-by: Christoph Hellwig Signed-off-by: Martin K. Petersen List of files: /linux-6.15/drivers/nvme/host/Makefile

eb7e2d92 - nvme: don't always build constants.o

Mon, 18 Jul 2022 05:07:26 +0000

nvme: don't always build constants.oThe entire content of constants.c if guarded by an ifdef, so switch tojust building the file conditionally instead.Signed-off-by: Christoph Hellwig Reviewed-by: Keith Busch Reviewed-by: Chaitanya Kulkarni Reviewed-by: Sagi Grimberg Signed-off-by: Jens Axboe List of files: /linux-6.15/drivers/nvme/host/Makefile

f50fff73 - nvme: implement In-Band authentication

Mon, 27 Jun 2022 09:52:02 +0000

nvme: implement In-Band authenticationImplement NVMe-oF In-Band authentication according to NVMe TPAR 8006.This patch adds two new fabric options 'dhchap_secret' to specify thepre-shared key (in ASCII respresentation according to NVMe 2.0 section8.13.5.8 'Secret representation') and 'dhchap_ctrl_secret' to specifythe pre-shared controller key for bi-directional authentication of boththe host and the controller.Re-authentication can be triggered by writing the PSK into the newcontroller sysfs attribute 'dhchap_secret' or 'dhchap_ctrl_secret'.Signed-off-by: Hannes Reinecke Reviewed-by: Sagi Grimberg Signed-off-by: Christoph Hellwig [axboe: fold in clang build fix]Signed-off-by: Jens Axboe List of files: /linux-6.15/drivers/nvme/host/Makefile

5bd2927a - nvme-apple: Add initial Apple SoC NVMe driver

Sun, 01 May 2022 14:55:12 +0000

nvme-apple: Add initial Apple SoC NVMe driverApple SoCs such as the M1 come with an embedded NVMe controller thatis not attached to any PCIe bus. Additionally, it doesn't conformto the NVMe specification and requires a bunch of changes to commandsubmission and IOMMU configuration to work.Reviewed-by: Christoph Hellwig Reviewed-by: Arnd Bergmann Signed-off-by: Sven Peter List of files: /linux-6.15/drivers/nvme/host/Makefile

bd83fe6f - nvme: add verbose error logging

Thu, 03 Feb 2022 08:11:53 +0000

nvme: add verbose error loggingImproves logging of NVMe errors. If NVME_VERBOSE_ERRORS is configured,a verbose description of the error is logged, otherwise only statuscodes/bits is logged.Signed-off-by: Chaitanya Kulkarni [kch]: fix several nits, cosmetics, and trim down code.Signed-off-by: Martin K. Petersen Signed-off-by: Alan Adamson Reviewed-by: Himanshu Madhani Reviewed-by: Keith Busch Signed-off-by: Christoph Hellwig List of files: /linux-6.15/drivers/nvme/host/Makefile

9ea9b9c4 - remove the lightnvm subsystem

Thu, 12 Aug 2021 13:23:08 +0000

remove the lightnvm subsystemLightnvm supports the OCSSD 1.x and 2.0 specs which were early attemptsto produce Open Channel SSDs and never made it into the NVMe specproper. They have since been superceeded by NVMe enhancements suchas ZNS support. Remove the support per the deprecation schedule.Signed-off-by: Christoph Hellwig Link: https://lore.kernel.org/r/20210812132308.38486-1-hch@lst.deReviewed-by: Matias Bjørling Reviewed-by: Javier González Signed-off-by: Jens Axboe List of files: /linux-6.15/drivers/nvme/host/Makefile

daf6e8c9 - Revert "nvme-tcp-offload: ULP Series"

Wed, 09 Jun 2021 10:49:18 +0000

Revert "nvme-tcp-offload: ULP Series"This reverts commits:- 762411542050dbe27c7c96f13c57f93da5d9b89a nvme: NVME_TCP_OFFLOAD should not default to m- 5ff5622ea1f16d535f1be4e478e712ef48fe183b: Merge branch 'NVMeTCP-Offload-ULP'As requested on the mailing-list: https://lore.kernel.org/netdev/SJ0PR18MB3882C20793EA35A3E8DAE300CC379@SJ0PR18MB3882.namprd18.prod.outlook.com/This patch will revert the nvme-tcp-offload ULP from net-next.The nvme-tcp-offload ULP series will continue to be considered only onlinux-nvme@lists.infradead.org.Signed-off-by: Prabhakar Kushwaha Signed-off-by: Michal Kalderon Signed-off-by: Ariel Elior Signed-off-by: Shai Malin Signed-off-by: David S. Miller List of files: /linux-6.15/drivers/nvme/host/Makefile

f0e8cb61 - nvme-tcp-offload: Add nvme-tcp-offload - NVMeTCP HW offload ULP

Wed, 02 Jun 2021 18:42:39 +0000

nvme-tcp-offload: Add nvme-tcp-offload - NVMeTCP HW offload ULPThis patch will present the structure for the NVMeTCP offload commonlayer driver. This module is added under "drivers/nvme/host/" and futureoffload drivers which will register to it will be placed under"drivers/nvme/hw".This new driver will be enabled by the Kconfig "NVM Express over FabricsTCP offload commmon layer".In order to support the new transport type, for host mode, no change isneeded.Each new vendor-specific offload driver will register to this ULP duringits probe function, by filling out the nvme_tcp_ofld_dev->ops andnvme_tcp_ofld_dev->private_data and calling nvme_tcp_ofld_register_devwith the initialized struct.The internal implementation:- tcp-offload.h: Includes all common structs and ops to be used and shared by offload drivers.- tcp-offload.c: Includes the init function which registers as a NVMf transport just like any other transport.Acked-by: Igor Russkikh Signed-off-by: Dean Balandin Signed-off-by: Prabhakar Kushwaha Signed-off-by: Omkar Kulkarni Signed-off-by: Michal Kalderon Signed-off-by: Ariel Elior Signed-off-by: Shai Malin Reviewed-by: Hannes Reinecke Reviewed-by: Himanshu Madhani Signed-off-by: David S. Miller List of files: /linux-6.15/drivers/nvme/host/Makefile

2405252a - nvme: move the ioctl code to a separate file

Sat, 10 Apr 2021 06:42:03 +0000

nvme: move the ioctl code to a separate fileSplit out the ioctl code from core.c into a new file. Also updatecopyrights while we're at it.Signed-off-by: Christoph Hellwig Reviewed-by: Keith Busch Reviewed-by: Javier González Reviewed-by: Chaitanya Kulkarni List of files: /linux-6.15/drivers/nvme/host/Makefile

240e6ee2 - nvme: support for zoned namespaces

Mon, 29 Jun 2020 19:06:41 +0000

nvme: support for zoned namespacesAdd support for NVM Express Zoned Namespaces (ZNS) Command Set definedin NVM Express TP4053. Zoned namespaces are discovered based on theirCommand Set Identifier reported in the namespaces NamespaceIdentification Descriptor list. A successfully discovered ZonedNamespace will be registered with the block layer as a host managedzoned block device with Zone Append command support. A namespace thatdoes not support append is not supported by the driver.Reviewed-by: Martin K. Petersen Reviewed-by: Johannes Thumshirn Reviewed-by: Hannes Reinecke Reviewed-by: Sagi Grimberg Reviewed-by: Javier González Reviewed-by: Himanshu Madhani Signed-off-by: Hans Holmberg Signed-off-by: Dmitry Fomichev Signed-off-by: Ajay Joshi Signed-off-by: Aravind Ramesh Signed-off-by: Niklas Cassel Signed-off-by: Matias Bjørling Signed-off-by: Damien Le Moal Signed-off-by: Keith Busch Signed-off-by: Christoph Hellwig List of files: /linux-6.15/drivers/nvme/host/Makefile

400b6a7b - nvme: Add hardware monitoring support

Wed, 06 Nov 2019 14:35:18 +0000

nvme: Add hardware monitoring supportnvme devices report temperature information in the controller information(for limits) and in the smart log. Currently, the only means to retrievethis information is the nvme command line interface, which requiressuper-user privileges.At the same time, it would be desirable to be able to use NVMe temperatureinformation for thermal control.This patch adds support to read NVMe temperatures from the kernel using thehwmon API and adds temperature zones for NVMe drives. The thermal subsystemcan use this information to set thermal policies, and userspace can accessit using libsensors and/or the "sensors" command.Example output from the "sensors" command:nvme0-pci-0100Adapter: PCI adapterComposite: +39.0°C (high = +85.0°C, crit = +85.0°C)Sensor 1: +39.0°CSensor 2: +41.0°CReviewed-by: Christoph Hellwig Signed-off-by: Guenter Roeck Signed-off-by: Keith Busch List of files: /linux-6.15/drivers/nvme/host/Makefile

3f2304f8 - nvme-tcp: add NVMe over TCP host driver

Tue, 04 Dec 2018 01:52:17 +0000

nvme-tcp: add NVMe over TCP host driverThis patch implements the NVMe over TCP host driver. It can be used toconnect to remote NVMe over Fabrics subsystems over good old TCP/IP.The driver implements the TP 8000 of how nvme over fabrics capsules anddata are encapsulated in nvme-tcp pdus and exchaged on top of a TCP bytestream. nvme-tcp header and data digest are supported as well.To connect to all NVMe over Fabrics controllers reachable on a given tagetport over TCP use the following command: nvme connect-all -t tcp -a $IPADDRThis requires the latest version of nvme-cli with TCP support.Signed-off-by: Sagi Grimberg Signed-off-by: Roy Shterman Signed-off-by: Solganik Alexander Signed-off-by: Christoph Hellwig List of files: /linux-6.15/drivers/nvme/host/Makefile

b9e03857 - nvme: Add fault injection feature

Thu, 08 Feb 2018 18:38:29 +0000

nvme: Add fault injection featureLinux's fault injection framework provides a systematic way to supporterror injection via debugfs in the /sys/kernel/debug directory. Thispatch uses the framework to add error injection to NVMe driver. Thefault injection source code is stored in a separate file and only linkedif CONFIG_FAULT_INJECTION_DEBUG_FS kernel config is selected.Once the error injection is enabled, NVME_SC_INVALID_OPCODE with noretry will be injected into the nvme_end_request. Users can changethe default status code and no retry flag via debufs. Following exampleshows how to enable and inject an error. For more examples, refer toDocumentation/fault-injection/nvme-fault-injection.txtHow to enable nvme fault injection:First, enable CONFIG_FAULT_INJECTION_DEBUG_FS kernel config,recompile the kernel. After booting up the kernel, do thefollowing.How to inject an error:mount /dev/nvme0n1 /mntecho 1 > /sys/kernel/debug/nvme0n1/fault_inject/timesecho 100 > /sys/kernel/debug/nvme0n1/fault_inject/probabilitycp a.file /mntExpected Result:cp: cannot stat ‘/mnt/a.file’: Input/output errorMessage from dmesg:FAULT_INJECTION: forcing a failure.name fault_inject, interval 1, probability 100, space 0, times 1CPU: 0 PID: 0 Comm: swapper/0 Not tainted 4.15.0-rc8+ #2Hardware name: innotek GmbH VirtualBox/VirtualBox,BIOS VirtualBox 12/01/2006Call Trace: dump_stack+0x5c/0x7d should_fail+0x148/0x170 nvme_should_fail+0x2f/0x50 [nvme_core] nvme_process_cq+0xe7/0x1d0 [nvme] nvme_irq+0x1e/0x40 [nvme] __handle_irq_event_percpu+0x3a/0x190 handle_irq_event_percpu+0x30/0x70 handle_irq_event+0x36/0x60 handle_fasteoi_irq+0x78/0x120 handle_irq+0xa7/0x130 ? tick_irq_enter+0xa8/0xc0 do_IRQ+0x43/0xc0 common_interrupt+0xa2/0xa2 RIP: 0010:native_safe_halt+0x2/0x10RSP: 0018:ffffffff82003e90 EFLAGS: 00000246 ORIG_RAX: ffffffffffffffddRAX: ffffffff817a10c0 RBX: ffffffff82012480 RCX: 0000000000000000RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000RBP: 0000000000000000 R08: 000000008e38ce64 R09: 0000000000000000R10: 0000000000000000 R11: 0000000000000000 R12: ffffffff82012480R13: ffffffff82012480 R14: 0000000000000000 R15: 0000000000000000 ? __sched_text_end+0x4/0x4 default_idle+0x18/0xf0 do_idle+0x150/0x1d0 cpu_startup_entry+0x6f/0x80 start_kernel+0x4c4/0x4e4 ? set_init_arg+0x55/0x55 secondary_startup_64+0xa5/0xb0 print_req_error: I/O error, dev nvme0n1, sector 9240EXT4-fs error (device nvme0n1): ext4_find_entry:1436:inode #2: comm cp: reading directory lblock 0Signed-off-by: Thomas Tai Reviewed-by: Eric Saint-Etienne Signed-off-by: Karl Volz Reviewed-by: Keith Busch Signed-off-by: Sagi Grimberg Signed-off-by: Jens Axboe List of files: /linux-6.15/drivers/nvme/host/Makefile

3d030e41 - nvme: add tracepoint for nvme_setup_cmd

Fri, 26 Jan 2018 10:21:37 +0000

nvme: add tracepoint for nvme_setup_cmdAdd tracepoints for nvme_setup_cmd() for tracing admin and/or nvm commands.Examples of the two tracepoints are as follows for trace_nvme_setup_admin_cmd():kworker/u8:0-5 [003] .... 2.998792: nvme_setup_admin_cmd: cmdid=14, flags=0x0, meta=0x0, cmd=(nvme_admin_create_cq cqid=1, qsize=1023, cq_flags=0x3, irq_vector=0)and trace_nvme_setup_nvm_cmd():dd-205 [001] .... 3.503929: nvme_setup_nvm_cmd: qid=1, nsid=1, cmdid=989, flags=0x0, meta=0x0, cmd=(nvme_cmd_read slba=4096, len=2047, ctrl=0x0, dsmgmt=0, reftag=0)Signed-off-by: Johannes Thumshirn Reviewed-by: Hannes Reinecke Reviewed-by: Martin K. Petersen Reviewed-by: Keith Busch Reviewed-by: Sagi Grimberg Signed-off-by: Christoph Hellwig List of files: /linux-6.15/drivers/nvme/host/Makefile

32acab31 - nvme: implement multipath access to nvme subsystems

Thu, 02 Nov 2017 11:59:30 +0000

nvme: implement multipath access to nvme subsystemsThis patch adds native multipath support to the nvme driver. For eachnamespace we create only single block device node, which can be usedto access that namespace through any of the controllers that refer to it.The gendisk for each controllers path to the name space still existsinside the kernel, but is hidden from userspace. The character devicenodes are still available on a per-controller basis. A new link fromthe sysfs directory for the subsystem allows to find all controllersfor a given subsystem.Currently we will always send I/O to the first available path, this willbe changed once the NVMe Asynchronous Namespace Access (ANA) TP isratified and implemented, at which point we will look at the ANA statefor each namespace. Another possibility that was prototyped is touse the path that is closes to the submitting NUMA code, which will bemostly interesting for PCI, but might also be useful for RDMA or FCtransports in the future. There is not plan to implement round robinor I/O service time path selectors, as those are not scalable withthe performance rates provided by NVMe.The multipath device will go away once all paths to it disappear,any delay to keep it alive needs to be implemented at the controllerlevel.Signed-off-by: Christoph Hellwig Reviewed-by: Keith Busch Reviewed-by: Martin K. Petersen Reviewed-by: Hannes Reinecke Signed-off-by: Jens Axboe List of files: /linux-6.15/drivers/nvme/host/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/nvme/host/Makefile

a2b93775 - nvme: Makefile: remove dead build rule

Thu, 29 Jun 2017 06:59:07 +0000

nvme: Makefile: remove dead build ruleRemove dead build rule for drivers/nvme/host/scsi.c which has beenremoved by commit ("nvme: Remove SCSI translations").Signed-off-by: Valentin Rothberg Reviewed-by: Johannes Thumshirn Reviewed-by: Christoph Hellwig Reviewed-by: Keith Busch Signed-off-by: Jens Axboe List of files: /linux-6.15/drivers/nvme/host/Makefile

e399441d - nvme-fabrics: Add host support for FC transport

Fri, 02 Dec 2016 08:28:42 +0000

nvme-fabrics: Add host support for FC transportImplements the FC-NVME T11 definition of how nvme fabric capsules areperformed on an FC fabric. Utilizes a lower-layer API to FC host adaptersto send/receive FC-4 LS operations and FCP operations that comprise NVMEover FC operation.The T11 definitions for FC-4 Link Services are implemented which createNVMeOF connections. Implements the hooks with blk-mq to then submit adminand io requests to the different connections.Signed-off-by: James Smart Reviewed-by: Jay Freyensee Reviewed-by: Johannes Thumshirn Signed-off-by: Christoph Hellwig List of files: /linux-6.15/drivers/nvme/host/Makefile