View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0001017 | channel: kernel/el7 | --kernel--request-for-enhancement-- | public | 2020-06-25 18:16 | 2020-06-26 12:22 |
| Reporter | sagigr | Assigned To | toracat | ||
| Priority | normal | Severity | tweak | Reproducibility | always |
| Status | closed | Resolution | no change required | ||
| Summary | 0001017: Need kernel 4.20.13-1 to have NVME_CORE=m and BLK_DEV_NVME=m and not NVME_CORE=y and BLK_DEV_NVME=y | ||||
| Description | This modules are often being updated, this is not possible with these config options being marked as =y and not =m. For reference in kernel 4.14.13-1 this was the case, and also fixed in later kernels. Hence the request is to change this also for kernel 4.13.20-1. I'm specifically referring to kernel-ml-4.20.13-1 but it also exists in kernel-ml-5.0.0-1 and some other versions... The specific rpm I am referring to is: http://mirrors.reposnap.com/elrepo/20190305204216/kernel/el7/x86_64/RPMS/kernel-ml-devel-4.20.13-1.el7.elrepo.x86_64.rpm http://mirrors.reposnap.com/elrepo/20190305204216/kernel/el7/x86_64/RPMS/kernel-ml-headers-5.0.0-1.el7.elrepo.x86_64.rpm | ||||
| Additional Information | The change needed is: -CONFIG_NVME_CORE=y -CONFIG_BLK_DEV_NVME=y +CONFIG_NVME_CORE=m +CONFIG_BLK_DEV_NVME=m | ||||
| Tags | No tags attached. | ||||
| related to | 0000946 | resolved | burakkucat | set CONFIG_NVME_CORE=m in el7 |
|
|
Here is the relevant section from .config: # # NVME Support # CONFIG_NVME_CORE=y CONFIG_BLK_DEV_NVME=y # CONFIG_NVME_MULTIPATH is not set CONFIG_NVME_FABRICS=m CONFIG_NVME_RDMA=m CONFIG_NVME_FC=m CONFIG_NVME_TARGET=m CONFIG_NVME_TARGET_LOOP=m CONFIG_NVME_TARGET_RDMA=m CONFIG_NVME_TARGET_FC=m CONFIG_NVME_TARGET_FCLOOP=m Request is to make: # # NVME Support # CONFIG_NVME_CORE=m CONFIG_BLK_DEV_NVME=m # CONFIG_NVME_MULTIPATH is not set CONFIG_NVME_FABRICS=m CONFIG_NVME_RDMA=m CONFIG_NVME_FC=m CONFIG_NVME_TARGET=m CONFIG_NVME_TARGET_LOOP=m CONFIG_NVME_TARGET_RDMA=m CONFIG_NVME_TARGET_FC=m CONFIG_NVME_TARGET_FCLOOP=m Should I open a bug for every kerenl-ml that suffers from this that I find? |
|
|
The current version of kernel-ml (5.7.4) has : # # NVME Support # CONFIG_NVME_CORE=m CONFIG_BLK_DEV_NVME=m CONFIG_NVME_MULTIPATH=y CONFIG_NVME_HWMON=y CONFIG_NVME_FABRICS=m CONFIG_NVME_RDMA=m CONFIG_NVME_FC=m CONFIG_NVME_TCP=m CONFIG_NVME_TARGET=m CONFIG_NVME_TARGET_LOOP=m CONFIG_NVME_TARGET_RDMA=m CONFIG_NVME_TARGET_FC=m CONFIG_NVME_TARGET_FCLOOP=m CONFIG_NVME_TARGET_TCP=m # end of NVME Support Please note that earlier versions are not supported. We can only make changes for future releases of kernel-ml/lt. |
|
|
Is it possible to release a new stable update 4.20.17-1 release where this is fixed? |
|
|
Sorry, that is something we cannot help with. We don't/cannot build such an old version. |
|
|
Now closing as 'not a bug'. |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2020-06-25 18:16 | sagigr | New Issue | |
| 2020-06-25 18:16 | sagigr | Status | new => assigned |
| 2020-06-25 18:16 | sagigr | Assigned To | => stindall |
| 2020-06-25 18:16 | sagigr | Reported upstream | => No, its not an upstream bug, but rather a distribution bug |
| 2020-06-25 19:14 | sagigr | Note Added: 0007014 | |
| 2020-06-25 22:46 | toracat | Note Added: 0007015 | |
| 2020-06-25 22:47 | toracat | Relationship added | related to 0000946 |
| 2020-06-26 05:28 | burakkucat | Project | channel: elrepo/el7 => channel: kernel/el7 |
| 2020-06-26 05:29 | burakkucat | Assigned To | stindall => toracat |
| 2020-06-26 05:29 | burakkucat | Category | --elrepo--OTHER-- => --kernel--request-for-enhancement-- |
| 2020-06-26 10:05 | sagigr | Note Added: 0007016 | |
| 2020-06-26 12:21 | toracat | Note Added: 0007020 | |
| 2020-06-26 12:22 | toracat | Note Added: 0007021 | |
| 2020-06-26 12:22 | toracat | Status | assigned => closed |
| 2020-06-26 12:22 | toracat | Resolution | open => no change required |
