Bug#1027921: linux-image-5.10.0-20-amd64: aacraid's expose_physicals=-1 is not functional

2023-01-05 Thread Andrey Melnikov
Try revert 
https://github.com/torvalds/linux/commit/948e922fc44611ee2de0c89583ca958cb5307d36
("scsi: core: map PQ=1, PDT=other values to SCSI_SCAN_TARGET_PRESENT")



Bug#1027921: linux-image-5.10.0-20-amd64: aacraid's expose_physicals=-1 is not functional

2023-01-04 Thread Diederik de Haas
On Wednesday, 4 January 2023 15:38:32 CET Tim Düsterhus wrote:
> Unfortunately the setting `1` allows direct write access to the devices,
> whereas the previous and to my understanding the default setting of `-1`
> only allows read access, making this a safer option.
> 
> It appears that aacraid's `expose_physicals=-1` option got broken
> somewhere between Linux 4.19 and 5.10.

https://git.kernel.org/linus/e3cc268fe4a0ad1cbefbc53cee35c80281e609b8 seems 
relevant, although I do not fully understand it.
One thing that stood out for me is the check `expose_physicals > 0` instead of 
`expose_physicals != 0`. But that commit exists since 2.6.35 ...

This very much looks like an upstream kernel issue and therefor it's better to 
bring it to the attention of those maintainers.

Those are:
$ scripts/get_maintainer.pl drivers/scsi/aacraid/aachba.c 
Adaptec OEM Raid Solutions  (supporter:AACRAID SCSI 
RAID DRIVER)
"James E.J. Bottomley"  (maintainer:SCSI SUBSYSTEM)
"Martin K. Petersen"  (maintainer:SCSI SUBSYSTEM)
linux-s...@vger.kernel.org (open list:AACRAID SCSI RAID DRIVER)
linux-ker...@vger.kernel.org (open list)

When you do forward your question, please inform this bug report of the URL.

HTH

signature.asc
Description: This is a digitally signed message part.


Bug#1027921: linux-image-5.10.0-20-amd64: aacraid's expose_physicals=-1 is not functional

2023-01-04 Thread Tim

Hi Renato

On 1/4/23 16:39, Renato Gallo wrote:

5.10 should be EOL by now


According to https://www.kernel.org/category/releases.html, Linux 5.10 
is supported until 2026.


Whether a fix for this bug qualifies as an "important bugfix" acceptable 
for a LTS kernel I can't tell.


In any case, 5.10 is the stock kernel for Debian Bullseye and thus I 
wanted to report the issue, if only to ensure it is tracked, even if 
the/a fix doesn't make the cut for Bullseye.


Best regards
Tim Düsterhus
Developer WoltLab GmbH

--

WoltLab GmbH
Nedlitzer Str. 27B
14469 Potsdam

Tel.: +49 331 96784338

duester...@woltlab.com
www.woltlab.com

Managing director:
Marcel Werk

AG Potsdam HRB 26795 P



Bug#1027921: linux-image-5.10.0-20-amd64: aacraid's expose_physicals=-1 is not functional

2023-01-04 Thread Diederik de Haas
On Wednesday, 4 January 2023 16:39:33 CET Renato Gallo wrote:
> 5.10 should be EOL by now

Please refrain from comments like that.
It doesn't help at all and is also plain false.

signature.asc
Description: This is a digitally signed message part.


Bug#1027921: linux-image-5.10.0-20-amd64: aacraid's expose_physicals=-1 is not functional

2023-01-04 Thread Renato Gallo
5.10 should be EOL by now

On Wed, Jan 4, 2023 at 3:51 PM Tim Düsterhus  wrote:

> Package: src:linux
> Version: 5.10.158-2
> Severity: normal
> X-Debbugs-Cc: duester...@woltlab.com
>
> Dear Maintainer,
>
> after upgrading my server from Debian Buster to Debian Bullseye, I
> noticed that the underlying devices attached to the Adaptec 6405E raid
> controller were no longer exposed via the /dev/sgX devices and thus
> reading the SMART values was no longer possible:
>
> $ lsscsi
> [0:0:0:0]diskAdaptec  *redacted*   V1.0  /dev/sda
> [0:3:0:0]enclosu ADAPTEC  Virtual SGPIO  -
>
> Booting into the Linux 4.19 kernel from Debian Buster correctly exposed
> the devices with the new userland, indicating a Kernel issue.
>
> I was able to work around the issue by adding the following
> configuration to /etc/modprobe.d/:
>
> options aacraid expose_physicals=1
>
> After setting this configuration and rebooting the server the devices
> are properly visible as they were before:
>
> $ lsscsi
> [0:0:0:0]diskAdaptec  *redacted*   V1.0  /dev/sda
> [0:1:0:0]diskATA  *redacted*     /dev/sdb
> [0:1:1:0]diskATA  *redacted*     /dev/sdc
> [0:3:0:0]enclosu ADAPTEC  Virtual SGPIO  -
>
> Unfortunately the setting `1` allows direct write access to the devices,
> whereas the previous and to my understanding the default setting of `-1`
> only allows read access, making this a safer option.
>
> It appears that aacraid's `expose_physicals=-1` option got broken
> somewhere between Linux 4.19 and 5.10.
>
> Best regards
>
>
> -- Package-specific info:
> ** Version:
> Linux version 5.10.0-20-amd64 (debian-kernel@lists.debian.org) (gcc-10
> (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2)
> #1 SMP Debian 5.10.158-2 (2022-12-13)
>
> ** Command line:
> BOOT_IMAGE=/vmlinuz-5.10.0-20-amd64 root=ZFS=rpool/ROOT/debian ro boot=zfs
> swapaccount=1 quiet
>
> ** Tainted: POE (12289)
>  * proprietary module was loaded
>  * externally-built ("out-of-tree") module was loaded
>  * unsigned module was loaded
>
> ** Kernel log:
> Unable to read kernel log; any relevant messages should be attached
>
> ** Model information
> sys_vendor: Supermicro
> product_name: X10SLH-F/X10SLM+-F
> product_version: 0123456789
> chassis_vendor: Supermicro
> chassis_version: 0123456789
> bios_vendor: American Megatrends Inc.
> bios_version: 3.2a
> board_vendor: Supermicro
> board_name: X10SLH-F/X10SLM+-F
> board_version: 1.02
>
> ** Loaded modules:
> nft_reject_inet
> nf_reject_ipv4
> nf_reject_ipv6
> nft_reject
> nft_counter
> intel_rapl_msr
> intel_rapl_common
> ipmi_ssif
> nft_ct
> nf_conntrack
> nf_defrag_ipv6
> nf_defrag_ipv4
> x86_pkg_temp_thermal
> intel_powerclamp
> coretemp
> kvm_intel
> kvm
> ext4
> irqbypass
> ghash_clmulni_intel
> crc16
> mbcache
> jbd2
> aesni_intel
> libaes
> crypto_simd
> cryptd
> ast
> glue_helper
> drm_vram_helper
> drm_ttm_helper
> rapl
> ttm
> intel_cstate
> intel_uncore
> drm_kms_helper
> pcspkr
> joydev
> at24
> intel_pch_thermal
> evdev
> mei_me
> cec
> iTCO_wdt
> mei
> intel_pmc_bxt
> sg
> iTCO_vendor_support
> watchdog
> ie31200_edac
> acpi_ipmi
> ipmi_si
> ipmi_devintf
> ipmi_msghandler
> acpi_pad
> button
> nf_tables
> libcrc32c
> crc32c_generic
> nfnetlink
> drm
> fuse
> configfs
> ip_tables
> x_tables
> autofs4
> hid_generic
> usbhid
> hid
> zfs(POE)
> zunicode(POE)
> zzstd(OE)
> zlua(OE)
> zavl(POE)
> icp(POE)
> zcommon(POE)
> znvpair(POE)
> spl(OE)
> ses
> enclosure
> sd_mod
> scsi_transport_sas
> t10_pi
> crc_t10dif
> crct10dif_generic
> ahci
> libahci
> xhci_pci
> libata
> xhci_hcd
> ehci_pci
> crct10dif_pclmul
> crct10dif_common
> ehci_hcd
> aacraid
> crc32_pclmul
> lpc_ich
> igb
> i2c_i801
> usbcore
> i2c_smbus
> scsi_mod
> crc32c_intel
> i2c_algo_bit
> dca
> ptp
> pps_core
> usb_common
> fan
> video
>
> ** PCI devices:
> 00:00.0 Host bridge [0600]: Intel Corporation Xeon E3-1200 v3 Processor
> DRAM Controller [8086:0c08] (rev 06)
> Subsystem: Super Micro Computer Inc Xeon E3-1200 v3 Processor DRAM
> Controller [15d9:0803]
> Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
> ParErr- Stepping- SERR- FastB2B- DisINTx-
> Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort-
> SERR-  Latency: 0
> IOMMU group: 0
> Capabilities: [e0] Vendor Specific Information: Len=0c 
> Kernel driver in use: ie31200_edac
> Kernel modules: ie31200_edac
>
> 00:01.0 PCI bridge [0604]: Intel Corporation Xeon E3-1200 v3/4th Gen Core
> Processor PCI Express x16 Controller [8086:0c01] (rev 06) (prog-if 00
> [Normal decode])
> Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
> ParErr- Stepping- SERR- FastB2B- DisINTx+
> Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort-
> SERR-  Latency: 0, Cache Line Size: 64 bytes
> Interrupt: pin A routed to IRQ 25
> IOMMU 

Bug#1027921: linux-image-5.10.0-20-amd64: aacraid's expose_physicals=-1 is not functional

2023-01-04 Thread Tim

Dear Maintainer,

Forgot to include in my initial report that I found the workaround using 
this (German) thread in the Proxmox Support Forum:


https://forum.proxmox.com/threads/adaptec-aacraid-expose_physicals-kernelbug.63256/

The thread is fairly light on details, but it appears to indicate the 
the issue already existed with Linux 5.3.


Best regards
Tim Düsterhus
Developer WoltLab GmbH

--

WoltLab GmbH
Nedlitzer Str. 27B
14469 Potsdam

Tel.: +49 331 96784338

duester...@woltlab.com
www.woltlab.com

Managing director:
Marcel Werk

AG Potsdam HRB 26795 P



Bug#1027921: linux-image-5.10.0-20-amd64: aacraid's expose_physicals=-1 is not functional

2023-01-04 Thread Tim Düsterhus
Package: src:linux
Version: 5.10.158-2
Severity: normal
X-Debbugs-Cc: duester...@woltlab.com

Dear Maintainer,

after upgrading my server from Debian Buster to Debian Bullseye, I
noticed that the underlying devices attached to the Adaptec 6405E raid
controller were no longer exposed via the /dev/sgX devices and thus
reading the SMART values was no longer possible:

$ lsscsi
[0:0:0:0]diskAdaptec  *redacted*   V1.0  /dev/sda
[0:3:0:0]enclosu ADAPTEC  Virtual SGPIO  -

Booting into the Linux 4.19 kernel from Debian Buster correctly exposed
the devices with the new userland, indicating a Kernel issue.

I was able to work around the issue by adding the following
configuration to /etc/modprobe.d/:

options aacraid expose_physicals=1

After setting this configuration and rebooting the server the devices
are properly visible as they were before:

$ lsscsi
[0:0:0:0]diskAdaptec  *redacted*   V1.0  /dev/sda 
[0:1:0:0]diskATA  *redacted*     /dev/sdb 
[0:1:1:0]diskATA  *redacted*     /dev/sdc 
[0:3:0:0]enclosu ADAPTEC  Virtual SGPIO  -

Unfortunately the setting `1` allows direct write access to the devices,
whereas the previous and to my understanding the default setting of `-1`
only allows read access, making this a safer option.

It appears that aacraid's `expose_physicals=-1` option got broken
somewhere between Linux 4.19 and 5.10.

Best regards


-- Package-specific info:
** Version:
Linux version 5.10.0-20-amd64 (debian-kernel@lists.debian.org) (gcc-10 (Debian 
10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2) #1 SMP 
Debian 5.10.158-2 (2022-12-13)

** Command line:
BOOT_IMAGE=/vmlinuz-5.10.0-20-amd64 root=ZFS=rpool/ROOT/debian ro boot=zfs 
swapaccount=1 quiet

** Tainted: POE (12289)
 * proprietary module was loaded
 * externally-built ("out-of-tree") module was loaded
 * unsigned module was loaded

** Kernel log:
Unable to read kernel log; any relevant messages should be attached

** Model information
sys_vendor: Supermicro
product_name: X10SLH-F/X10SLM+-F
product_version: 0123456789
chassis_vendor: Supermicro
chassis_version: 0123456789
bios_vendor: American Megatrends Inc.
bios_version: 3.2a
board_vendor: Supermicro
board_name: X10SLH-F/X10SLM+-F
board_version: 1.02 

** Loaded modules:
nft_reject_inet
nf_reject_ipv4
nf_reject_ipv6
nft_reject
nft_counter
intel_rapl_msr
intel_rapl_common
ipmi_ssif
nft_ct
nf_conntrack
nf_defrag_ipv6
nf_defrag_ipv4
x86_pkg_temp_thermal
intel_powerclamp
coretemp
kvm_intel
kvm
ext4
irqbypass
ghash_clmulni_intel
crc16
mbcache
jbd2
aesni_intel
libaes
crypto_simd
cryptd
ast
glue_helper
drm_vram_helper
drm_ttm_helper
rapl
ttm
intel_cstate
intel_uncore
drm_kms_helper
pcspkr
joydev
at24
intel_pch_thermal
evdev
mei_me
cec
iTCO_wdt
mei
intel_pmc_bxt
sg
iTCO_vendor_support
watchdog
ie31200_edac
acpi_ipmi
ipmi_si
ipmi_devintf
ipmi_msghandler
acpi_pad
button
nf_tables
libcrc32c
crc32c_generic
nfnetlink
drm
fuse
configfs
ip_tables
x_tables
autofs4
hid_generic
usbhid
hid
zfs(POE)
zunicode(POE)
zzstd(OE)
zlua(OE)
zavl(POE)
icp(POE)
zcommon(POE)
znvpair(POE)
spl(OE)
ses
enclosure
sd_mod
scsi_transport_sas
t10_pi
crc_t10dif
crct10dif_generic
ahci
libahci
xhci_pci
libata
xhci_hcd
ehci_pci
crct10dif_pclmul
crct10dif_common
ehci_hcd
aacraid
crc32_pclmul
lpc_ich
igb
i2c_i801
usbcore
i2c_smbus
scsi_mod
crc32c_intel
i2c_algo_bit
dca
ptp
pps_core
usb_common
fan
video

** PCI devices:
00:00.0 Host bridge [0600]: Intel Corporation Xeon E3-1200 v3 Processor DRAM 
Controller [8086:0c08] (rev 06)
Subsystem: Super Micro Computer Inc Xeon E3-1200 v3 Processor DRAM 
Controller [15d9:0803]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: ie31200_edac
Kernel modules: ie31200_edac

00:01.0 PCI bridge [0604]: Intel Corporation Xeon E3-1200 v3/4th Gen Core 
Processor PCI Express x16 Controller [8086:0c01] (rev 06) (prog-if 00 [Normal 
decode])
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities: [88] Subsystem: Super Micro Computer Inc Xeon E3-1200 
v3/4th Gen Core Processor PCI Express x16 Controller [15d9:0803]
Capabilities: [80] Power Management version 3
Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA 
PME(D0+,D1-,D2-,D3hot+,D3cold+)
Status: D0 NoSoftRst+ PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [90] MSI: Enable+ Count=1/1 Maskable- 64bit-
Address: fee00218  Data: 
Capabilities: [a0] Express (v2) Root Port (Slot+), MSI 00
DevCap: MaxPayload 256