mirror of
https://git.kernel.org/pub/scm/linux/kernel/git/chenhuacai/linux-loongson
synced 2025-08-28 00:19:36 +00:00
833542b3e3
After commit653d7825c1("dcssblk: mark DAX broken, remove FS_DAX_LIMITED support") moved the "select DAX" from config DCSSBLK to the new config DCSSBLK_DAX, randconfig tests could result in build errors like this: s390-linux-ld: drivers/s390/block/dcssblk.o: in function `dcssblk_shared_store': drivers/s390/block/dcssblk.c:417: undefined reference to `kill_dax' s390-linux-ld: drivers/s390/block/dcssblk.c:418: undefined reference to `put_dax' This is because it's now possible to have CONFIG_DCSSBLK=y, but CONFIG_DAX=m. Fix this by adding "depends on DAX || DAX=n" to config DCSSBLK, to make it explicit that we want either no DAX, or the same "y/m" for both config DAX and DCSSBLK, similar to config BLK_DEV_DM. This also requires removing the "select DAX" from config DCSSBLK_DAX, or else there would be a recursive dependency detected. DCSSBLK_DAX is marked as BROKEN at the moment, and won't work well with DAX anyway, so it doesn't really matter if it is selected. Fixes:653d7825c1("dcssblk: mark DAX broken, remove FS_DAX_LIMITED support") Reported-by: kernel test robot <lkp@intel.com> Closes: https://lore.kernel.org/oe-kbuild-all/202504291604.pvjonhWX-lkp@intel.com/ Signed-off-by: Gerald Schaefer <gerald.schaefer@linux.ibm.com> Signed-off-by: Heiko Carstens <hca@linux.ibm.com>
82 lines
2.1 KiB
Plaintext
82 lines
2.1 KiB
Plaintext
# SPDX-License-Identifier: GPL-2.0
|
|
comment "S/390 block device drivers"
|
|
depends on S390 && BLOCK
|
|
|
|
config DCSSBLK
|
|
def_tristate m
|
|
prompt "DCSSBLK support"
|
|
depends on S390 && BLOCK && (DAX || DAX=n)
|
|
help
|
|
Support for dcss block device
|
|
|
|
config DCSSBLK_DAX
|
|
def_bool y
|
|
depends on DCSSBLK
|
|
# requires S390 ZONE_DEVICE support
|
|
depends on BROKEN
|
|
prompt "DCSSBLK DAX support"
|
|
help
|
|
Enable DAX operation for the dcss block device
|
|
|
|
config DASD
|
|
def_tristate y
|
|
prompt "Support for DASD devices"
|
|
depends on CCW && BLOCK
|
|
help
|
|
Enable this option if you want to access DASDs directly utilizing
|
|
S/390s channel subsystem commands. This is necessary for running
|
|
natively on a single image or an LPAR.
|
|
|
|
config DASD_PROFILE
|
|
def_bool y
|
|
prompt "Profiling support for dasd devices"
|
|
depends on DASD
|
|
help
|
|
Enable this option if you want to see profiling information
|
|
in /proc/dasd/statistics.
|
|
|
|
config DASD_ECKD
|
|
def_tristate y
|
|
prompt "Support for ECKD Disks"
|
|
depends on DASD
|
|
help
|
|
ECKD devices are the most commonly used devices. You should enable
|
|
this option unless you are very sure to have no ECKD device.
|
|
|
|
config DASD_FBA
|
|
def_tristate y
|
|
prompt "Support for FBA Disks"
|
|
depends on DASD
|
|
help
|
|
Select this option to be able to access FBA devices. It is safe to
|
|
say "Y".
|
|
|
|
config DASD_DIAG
|
|
def_tristate y
|
|
prompt "Support for DIAG access to Disks"
|
|
depends on DASD
|
|
help
|
|
Select this option if you want to use Diagnose250 command to access
|
|
Disks under VM. If you are not running under VM or unsure what it is,
|
|
say "N".
|
|
|
|
config DASD_EER
|
|
def_bool y
|
|
prompt "Extended error reporting (EER)"
|
|
depends on DASD
|
|
help
|
|
This driver provides a character device interface to the
|
|
DASD extended error reporting. This is only needed if you want to
|
|
use applications written for the EER facility.
|
|
|
|
config SCM_BLOCK
|
|
def_tristate m
|
|
prompt "Support for Storage Class Memory"
|
|
depends on S390 && BLOCK && EADM_SCH && SCM_BUS
|
|
help
|
|
Block device driver for Storage Class Memory (SCM). This driver
|
|
provides a block device interface for each available SCM increment.
|
|
|
|
To compile this driver as a module, choose M here: the
|
|
module will be called scm_block.
|