Debian Bug report logs - #910074
linux-image-4.9.0-8-amd64: BTRFS data loss - kernel BUG at .../linux-4.9.110/fs/btrfs/ctree.c:3178

version graph

Package: src:linux; Maintainer for src:linux is Debian Kernel Team <debian-kernel@lists.debian.org>;

Reported by: Michael Firth <mfirth@nevion.com>

Date: Tue, 2 Oct 2018 10:51:01 UTC

Severity: important

Found in version linux/4.9.110-3+deb9u4

Reply or subscribe to this bug.

Toggle useless messages

View this report as an mbox folder, status mbox, maintainer mbox

Report forwarded to debian-bugs-dist@lists.debian.org, Debian Kernel Team <debian-kernel@lists.debian.org>:
Bug#910074; Package src:linux. (Tue, 02 Oct 2018 10:51:03 GMT) (full text, mbox, link).

Acknowledgement sent to Michael Firth <mfirth@nevion.com>:
New Bug report received and forwarded. Copy sent to Debian Kernel Team <debian-kernel@lists.debian.org>. (Tue, 02 Oct 2018 10:51:03 GMT) (full text, mbox, link).

Message #5 received at submit@bugs.debian.org (full text, mbox, reply):

From: Michael Firth <mfirth@nevion.com>
To: Debian Bug Tracking System <submit@bugs.debian.org>
Subject: linux-image-4.9.0-8-amd64: BTRFS data loss - kernel BUG at .../linux-4.9.110/fs/btrfs/ctree.c:3178
Date: Tue, 02 Oct 2018 11:37:45 +0100
Package: src:linux
Version: 4.9.110-3+deb9u4
Severity: important

Dear Maintainer,

While extracting files over NFS into a BTRFS file system a kernel bug
report was triggered. I don't believe the bug is related to the fact
that the access was over NFS, but should declare that just in case.

After this, there was a file that was errored on the filesystem (as
reported by 'btrfs check'), and it seems BTRFS doesn't have any tools to
resolve the error. Deleting the file at the reported inode has cleared
the error from 'btrfs check', but I am not 100% sure that will have
fixed all the corruption.

This issue looks very like the bug described at:

https://www.spinics.net/lists/linux-btrfs/msg60984.html

And in bug report #708509 for a much older kernel (from 2013)

According to the BTRFS mailing list post above, there are patches
submitted to fix this issue (or one with the same symptoms).
Is there any way to easily determine if these patches are in the Debian
version of the V4.9.110 kernel?

If not, what is the route to get these patches incorporated? Do I need
to talk to the BTRFS people about getting the patches in to the stock
V4.9 kernel, or is this something that the Debian team would apply
directly?

Kernel bug report output included below, in case it is useful.

BTRFS may not be a filesystem that everyone uses, but I feel if it is in
the Debian kernel then bugs that can cause data loss should be fixed if
a patch already exists.

Thanks

Michael

-- Package-specific info:
** Version:
Linux version 4.9.0-8-amd64 (debian-kernel@lists.debian.org) (gcc version 6.3.0 20170516 (Debian 6.3.0-18+deb9u1) ) #1 SMP Debian 4.9.110-3+deb9u4 (2018-08-21)

** Command line:
BOOT_IMAGE=/vmlinuz-4.9.0-8-amd64 root=/dev/mapper/SysVG-RootVol ro net.ifnames=0 biosdevname=0 quiet

** Not tainted

** Kernel log:

Oct  1 15:33:26 xxx kernel: [522324.107309] ------------[ cut here ]------------
Oct  1 15:33:26 xxx kernel: [522324.108854] kernel BUG at /build/linux-AcJpTp/linux-4.9.110/fs/btrfs/ctree.c:3178!
Oct  1 15:33:26 xxx kernel: [522324.110432] invalid opcode: 0000 [#1] SMP
Oct  1 15:33:26 xxx kernel: [522324.111945] Modules linked in: nfsv3 rpcsec_gss_krb5 nfsv4 dns_resolver nfs fscache evdev pcspkr joydev edac_core crct10dif_pclmul crc32_pclmul serio_raw ghash_clmulni_intel vmw_balloon intel_rapl_perf sg vmwgfx ttm shpchp drm_kms_helper drm ac button vmw_vsock_vmci_transport vsock vmw_vmci nfsd nfs_acl lockd grace drbd lru_cache libcrc32c auth_rpcgss oid_registry sunrpc ip_tables x_tables autofs4 ext4 crc16 jbd2 fscrypto ecb mbcache btrfs crc32c_generic xor raid6_pq hid_generic usbhid hid dm_mod sr_mod cdrom sd_mod ata_generic crc32c_intel aesni_intel aes_x86_64 glue_helper lrw gf128mul ablk_helper cryptd psmouse ahci ehci_pci ata_piix libahci uhci_hcd libata vmw_pvscsi ehci_hcd vmxnet3 usbcore scsi_mod usb_common i2c_piix4
Oct  1 15:33:26 xxx kernel: [522324.120155] CPU: 1 PID: 835 Comm: nfsd Not tainted 4.9.0-8-amd64 #1 Debian 4.9.110-3+deb9u4
Oct  1 15:33:26 xxx kernel: [522324.120742] Hardware name: VMware, Inc. VMware Virtual Platform/440BX Desktop Reference Platform, BIOS 6.00 07/28/2017
Oct  1 15:33:26 xxx kernel: [522324.121906] task: ffff8dbc26c48440 task.stack: ffffa7fac23e4000
Oct  1 15:33:26 xxx kernel: [522324.122485] RIP: 0010:[<ffffffffc04ede32>]  [<ffffffffc04ede32>] btrfs_set_item_key_safe+0x182/0x190 [btrfs]
Oct  1 15:33:26 xxx kernel: [522324.123667] RSP: 0018:ffffa7fac23e7568  EFLAGS: 00010246
Oct  1 15:33:26 xxx kernel: [522324.124243] RAX: 0000000000000000 RBX: ffff8dbaf6432070 RCX: 0000000000010000
Oct  1 15:33:26 xxx kernel: [522324.124818] RDX: 0000000000000000 RSI: ffffa7fac23e767e RDI: ffffa7fac23e757f
Oct  1 15:33:26 xxx kernel: [522324.125382] RBP: ffffa7fac23e756e R08: ffff8dba8aa280e0 R09: 0000000000001000
Oct  1 15:33:26 xxx kernel: [522324.125940] R10: 0000000000000000 R11: 0000000000000003 R12: ffff8dbac17f2000
Oct  1 15:33:26 xxx kernel: [522324.126502] R13: 000000000000000f R14: ffff8dba8aa28040 R15: ffffa7fac23e767e
Oct  1 15:33:26 xxx kernel: [522324.127052] FS: 0000000000000000(0000) GS:ffff8dbc3fc40000(0000) knlGS:0000000000000000
Oct  1 15:33:26 xxx kernel: [522324.127585] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Oct  1 15:33:26 xxx kernel: [522324.128049] CR2: 00007fd54fd9eab4 CR3: 000000041ae02000 CR4: 0000000000760670
Oct  1 15:33:26 xxx kernel: [522324.128539] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
Oct  1 15:33:26 xxx kernel: [522324.129002] DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Oct  1 15:33:26 xxx kernel: [522324.129451] PKRU: 55555554
Oct  1 15:33:26 xxx kernel: [522324.129904] Stack:
Oct  1 15:33:26 xxx kernel: [522324.130334]  c85000000000002d 006c000000000027 5000000000000100 6c000000000027c8
Oct  1 15:33:26 xxx kernel: [522324.130766]  0000000000010000 1d91fb7ce01d2bcc ffff8dbaf6432070 ffff8dba8aa28040
Oct  1 15:33:26 xxx kernel: [522324.131196]  0000000000003a60 0000000000000001 0000000000014000 0000000000000000
Oct  1 15:33:26 xxx kernel: [522324.131623] Call Trace: 
Oct  1 15:33:26 xxx kernel: [522324.132054]  [<ffffffffc052e7c6>] ? __btrfs_drop_extents+0xb06/0xdc0 [btrfs]
Oct  1 15:33:26 xxx kernel: [522324.132484]  [<ffffffffc055a8d6>] ? btrfs_log_changed_extents+0x2d6/0x610 [btrfs]
Oct  1 15:33:26 xxx kernel: [522324.132904]  [<ffffffffc055d280>] ? btrfs_log_all_xattrs+0x170/0x230 [btrfs]
Oct  1 15:33:26 xxx kernel: [522324.133331]  [<ffffffffc055e733>] ? btrfs_log_inode+0xd63/0x1260 [btrfs]
Oct  1 15:33:26 xxx kernel: [522324.133735]  [<ffffffff82e15d70>] ? __switch_to_asm+0x40/0x70
Oct  1 15:33:26 xxx kernel: [522324.134142]  [<ffffffffc055ef55>] ? btrfs_log_inode_parent+0x2b5/0x9b0 [btrfs]
Oct  1 15:33:26 xxx kernel: [522324.134537]  [<ffffffff829e6c7c>] ? kmem_cache_alloc+0xbc/0x530
Oct  1 15:33:26 xxx kernel: [522324.134932]  [<ffffffffc051610d>] ? wait_current_trans.isra.20+0x2d/0x110 [btrfs]
Oct  1 15:33:26 xxx kernel: [522324.135322]  [<ffffffffc056060b>] ? btrfs_log_dentry_safe+0x5b/0x80 [btrfs]
Oct  1 15:33:26 xxx kernel: [522324.135707]  [<ffffffffc0530a57>] ? btrfs_sync_file+0x297/0x3e0 [btrfs]
Oct  1 15:33:26 xxx kernel: [522324.136081]  [<ffffffffc0530f82>] ? btrfs_file_write_iter+0x3e2/0x4d0 [btrfs]
Oct  1 15:33:26 xxx kernel: [522324.136446]  [<ffffffff82a263ce>] ? iput+0x7e/0x210
Oct  1 15:33:26 xxx kernel: [522324.136793]  [<ffffffff82a0511a>] ? __check_object_size+0xfa/0x1d8
Oct  1 15:33:26 xxx kernel: [522324.137134]  [<ffffffff82a07d6b>] ? do_iter_readv_writev+0xbb/0x140
Oct  1 15:33:26 xxx kernel: [522324.137473]  [<ffffffff82a0928e>] ? do_readv_writev+0x19e/0x240
Oct  1 15:33:26 xxx kernel: [522324.137807]  [<ffffffffc0530ba0>] ? btrfs_sync_file+0x3e0/0x3e0 [btrfs]
Oct  1 15:33:26 xxx kernel: [522324.138125]  [<ffffffff828bba64>] ? __wake_up+0x34/0x50
Oct  1 15:33:26 xxx kernel: [522324.138442]  [<ffffffffc077efca>] ? nfsd_vfs_write+0xca/0x3b0 [nfsd]
Oct  1 15:33:26 xxx kernel: [522324.138755]  [<ffffffffc078ad2e>] ? nfsd4_write+0x19e/0x200 [nfsd]
Oct  1 15:33:26 xxx kernel: [522324.139057]  [<ffffffffc078ce26>] ? nfsd4_proc_compound+0x376/0x6d0 [nfsd]
Oct  1 15:33:26 xxx kernel: [522324.139358]  [<ffffffffc077a2a6>] ? nfsd_dispatch+0xc6/0x260 [nfsd]
Oct  1 15:33:26 xxx kernel: [522324.139661]  [<ffffffffc069f36a>] ? svc_process_common+0x47a/0x6c0 [sunrpc]
Oct  1 15:33:26 xxx kernel: [522324.139977]  [<ffffffffc0779c40>] ? nfsd_destroy+0x60/0x60 [nfsd]
Oct  1 15:33:26 xxx kernel: [522324.140283]  [<ffffffffc06a0496>] ? svc_process+0xf6/0x1a0 [sunrpc]
Oct  1 15:33:26 xxx kernel: [522324.140577]  [<ffffffffc0779d29>] ? nfsd+0xe9/0x150 [nfsd]
Oct  1 15:33:26 xxx kernel: [522324.140867]  [<ffffffff82899329>] ? kthread+0xd9/0xf0
Oct  1 15:33:26 xxx kernel: [522324.141150]  [<ffffffff82e15d64>] ? __switch_to_asm+0x34/0x70
Oct  1 15:33:26 xxx kernel: [522324.141431]  [<ffffffff82899250>] ? kthread_park+0x60/0x60
Oct  1 15:33:26 xxx kernel: [522324.141705]  [<ffffffff82e15df7>] ? ret_from_fork+0x57/0x70
Oct  1 15:33:26 xxx kernel: [522324.141979] Code: 7c 24 17 4c 89 fe 48 89 44 24 20 0f b6 44 24 0e 88 44 24 1f 48 8b 44 24 06 48 89 44 24 17 e8 d6 f2 ff ff 85 c0 0f 8f 3a ff ff ff <0f> 0b 0f 0b e8 a5 b3 38 c2 0f 1f 44 00 00 0f 1f 44 00 00 41 55
Oct  1 15:33:26 xxx kernel: [522324.142900] RIP [<ffffffffc04ede32>] btrfs_set_item_key_safe+0x182/0x190 [btrfs]
Oct  1 15:33:26 xxx kernel: [522324.143220]  RSP <ffffa7fac23e7568>
Oct  1 15:33:26 xxx kernel: [522324.144117] ---[ end trace a992e7e6f5a4aa78 ]---


** Model information
sys_vendor: VMware, Inc.
product_name: VMware Virtual Platform
product_version: None
chassis_vendor: No Enclosure
chassis_version: N/A
bios_vendor: Phoenix Technologies LTD
bios_version: 6.00
board_vendor: Intel Corporation
board_name: 440BX Desktop Reference Platform
board_version: None

** Loaded modules:
rpcsec_gss_krb5
joydev
edac_core
crct10dif_pclmul
crc32_pclmul
pcspkr
ghash_clmulni_intel
serio_raw
evdev
vmw_balloon
intel_rapl_perf
sg
shpchp
vmwgfx
ttm
drm_kms_helper
drm
ac
button
vmw_vsock_vmci_transport
vsock
vmw_vmci
nfsd
nfs_acl
lockd
grace
drbd
lru_cache
libcrc32c
auth_rpcgss
oid_registry
sunrpc
ip_tables
x_tables
autofs4
ext4
crc16
jbd2
fscrypto
ecb
mbcache
btrfs
crc32c_generic
xor
raid6_pq
hid_generic
usbhid
hid
dm_mod
sr_mod
cdrom
sd_mod
ata_generic
crc32c_intel
aesni_intel
aes_x86_64
glue_helper
lrw
gf128mul
ablk_helper
cryptd
psmouse
ahci
uhci_hcd
ehci_pci
ata_piix
libahci
ehci_hcd
libata
vmw_pvscsi
usbcore
vmxnet3
usb_common
scsi_mod
i2c_piix4

** PCI devices:
00:00.0 Host bridge [0600]: Intel Corporation 440BX/ZX/DX - 82443BX/ZX/DX Host bridge [8086:7190] (rev 01)
	Subsystem: VMware Virtual Machine Chipset [15ad:1976]
	Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
	Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0
	Kernel driver in use: agpgart-intel

00:01.0 PCI bridge [0604]: Intel Corporation 440BX/ZX/DX - 82443BX/ZX/DX AGP bridge [8086:7191] (rev 01) (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=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0
	Bus: primary=00, secondary=01, subordinate=01, sec-latency=64
	Secondary status: 66MHz+ FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- <SERR- <PERR-
	BridgeCtl: Parity- SERR- NoISA+ VGA- MAbort- >Reset- FastB2B+
		PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
	Kernel modules: shpchp

00:07.0 ISA bridge [0601]: Intel Corporation 82371AB/EB/MB PIIX4 ISA [8086:7110] (rev 08)
	Subsystem: VMware Virtual Machine Chipset [15ad:1976]
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
	Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0

00:07.1 IDE interface [0101]: Intel Corporation 82371AB/EB/MB PIIX4 IDE [8086:7111] (rev 01) (prog-if 8a [Master SecP PriP])
	Subsystem: VMware Virtual Machine Chipset [15ad:1976]
	Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
	Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 64
	Region 0: [virtual] Memory at 000001f0 (32-bit, non-prefetchable) [size=8]
	Region 1: [virtual] Memory at 000003f0 (type 3, non-prefetchable)
	Region 2: [virtual] Memory at 00000170 (32-bit, non-prefetchable) [size=8]
	Region 3: [virtual] Memory at 00000370 (type 3, non-prefetchable)
	Region 4: I/O ports at 1060 [size=16]
	Kernel driver in use: ata_piix
	Kernel modules: ata_piix, ata_generic

00:07.3 Bridge [0680]: Intel Corporation 82371AB/EB/MB PIIX4 ACPI [8086:7113] (rev 08)
	Subsystem: VMware Virtual Machine Chipset [15ad:1976]
	Control: I/O+ Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
	Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Interrupt: pin ? routed to IRQ 9
	Kernel modules: i2c_piix4

00:07.7 System peripheral [0880]: VMware Virtual Machine Communication Interface [15ad:0740] (rev 10)
	Subsystem: VMware Virtual Machine Communication Interface [15ad:0740]
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
	Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 64 (1500ns min, 63750ns max)
	Interrupt: pin A routed to IRQ 16
	Region 0: I/O ports at 1080 [size=64]
	Region 1: Memory at febfe000 (64-bit, non-prefetchable) [size=8K]
	Capabilities: <access denied>
	Kernel driver in use: vmw_vmci
	Kernel modules: vmw_vmci

00:0f.0 VGA compatible controller [0300]: VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA controller])
	Subsystem: VMware SVGA II Adapter [15ad:0405]
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
	Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 64, Cache Line Size: 32 bytes
	Interrupt: pin A routed to IRQ 16
	Region 0: I/O ports at 1070 [size=16]
	Region 1: Memory at e8000000 (32-bit, prefetchable) [size=128M]
	Region 2: Memory at fe000000 (32-bit, non-prefetchable) [size=8M]
	[virtual] Expansion ROM at 000c0000 [disabled] [size=128K]
	Capabilities: <access denied>
	Kernel driver in use: vmwgfx
	Kernel modules: vmwgfx

00:11.0 PCI bridge [0604]: VMware PCI bridge [15ad:0790] (rev 02) (prog-if 01 [Subtractive decode])
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
	Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 64, Cache Line Size: 32 bytes
	Bus: primary=00, secondary=02, subordinate=02, sec-latency=68
	I/O behind bridge: 00002000-00003fff
	Memory behind bridge: fd500000-fdffffff
	Prefetchable memory behind bridge: 00000000e7b00000-00000000e7ffffff
	Secondary status: 66MHz- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- <SERR- <PERR-
	BridgeCtl: Parity- SERR- NoISA+ VGA- MAbort- >Reset- FastB2B-
		PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
	Capabilities: <access denied>

00:15.0 PCI bridge [0604]: VMware PCI Express Root Port [15ad:07a0] (rev 01) (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- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0, Cache Line Size: 32 bytes
	Interrupt: pin ? routed to IRQ 24
	Bus: primary=00, secondary=03, subordinate=03, sec-latency=0
	I/O behind bridge: 00004000-00004fff
	Memory behind bridge: fd400000-fd4fffff
	Prefetchable memory behind bridge: 00000000c0000000-00000000c01fffff
	Secondary status: 66MHz- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- <SERR- <PERR-
	BridgeCtl: Parity- SERR- NoISA+ VGA- MAbort- >Reset- FastB2B-
		PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
	Capabilities: <access denied>
	Kernel driver in use: pcieport
	Kernel modules: shpchp

00:15.1 PCI bridge [0604]: VMware PCI Express Root Port [15ad:07a0] (rev 01) (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- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0, Cache Line Size: 32 bytes
	Interrupt: pin ? routed to IRQ 25
	Bus: primary=00, secondary=04, subordinate=04, sec-latency=0
	I/O behind bridge: 00008000-00008fff
	Memory behind bridge: fd000000-fd0fffff
	Prefetchable memory behind bridge: 00000000e7800000-00000000e78fffff
	Secondary status: 66MHz- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- <SERR- <PERR-
	BridgeCtl: Parity- SERR- NoISA+ VGA- MAbort- >Reset- FastB2B-
		PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
	Capabilities: <access denied>
	Kernel driver in use: pcieport
	Kernel modules: shpchp

00:15.2 PCI bridge [0604]: VMware PCI Express Root Port [15ad:07a0] (rev 01) (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- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0, Cache Line Size: 32 bytes
	Interrupt: pin ? routed to IRQ 26
	Bus: primary=00, secondary=05, subordinate=05, sec-latency=0
	I/O behind bridge: 0000c000-0000cfff
	Memory behind bridge: fcc00000-fccfffff
	Prefetchable memory behind bridge: 00000000e7400000-00000000e74fffff
	Secondary status: 66MHz- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- <SERR- <PERR-
	BridgeCtl: Parity- SERR- NoISA+ VGA- MAbort- >Reset- FastB2B-
		PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
	Capabilities: <access denied>
	Kernel driver in use: pcieport
	Kernel modules: shpchp

00:15.3 PCI bridge [0604]: VMware PCI Express Root Port [15ad:07a0] (rev 01) (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- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0, Cache Line Size: 32 bytes
	Interrupt: pin ? routed to IRQ 27
	Bus: primary=00, secondary=06, subordinate=06, sec-latency=0
	Memory behind bridge: fc800000-fc8fffff
	Prefetchable memory behind bridge: 00000000e7000000-00000000e70fffff
	Secondary status: 66MHz- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- <SERR- <PERR-
	BridgeCtl: Parity- SERR- NoISA+ VGA- MAbort- >Reset- FastB2B-
		PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
	Capabilities: <access denied>
	Kernel driver in use: pcieport
	Kernel modules: shpchp

00:15.4 PCI bridge [0604]: VMware PCI Express Root Port [15ad:07a0] (rev 01) (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- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0, Cache Line Size: 32 bytes
	Interrupt: pin ? routed to IRQ 28
	Bus: primary=00, secondary=07, subordinate=07, sec-latency=0
	Memory behind bridge: fc400000-fc4fffff
	Prefetchable memory behind bridge: 00000000e6c00000-00000000e6cfffff
	Secondary status: 66MHz- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- <SERR- <PERR-
	BridgeCtl: Parity- SERR- NoISA+ VGA- MAbort- >Reset- FastB2B-
		PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
	Capabilities: <access denied>
	Kernel driver in use: pcieport
	Kernel modules: shpchp

00:15.5 PCI bridge [0604]: VMware PCI Express Root Port [15ad:07a0] (rev 01) (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- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0, Cache Line Size: 32 bytes
	Interrupt: pin ? routed to IRQ 29
	Bus: primary=00, secondary=08, subordinate=08, sec-latency=0
	Memory behind bridge: fc000000-fc0fffff
	Prefetchable memory behind bridge: 00000000e6800000-00000000e68fffff
	Secondary status: 66MHz- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- <SERR- <PERR-
	BridgeCtl: Parity- SERR- NoISA+ VGA- MAbort- >Reset- FastB2B-
		PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
	Capabilities: <access denied>
	Kernel driver in use: pcieport
	Kernel modules: shpchp

00:15.6 PCI bridge [0604]: VMware PCI Express Root Port [15ad:07a0] (rev 01) (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- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0, Cache Line Size: 32 bytes
	Interrupt: pin ? routed to IRQ 30
	Bus: primary=00, secondary=09, subordinate=09, sec-latency=0
	Memory behind bridge: fbc00000-fbcfffff
	Prefetchable memory behind bridge: 00000000e6400000-00000000e64fffff
	Secondary status: 66MHz- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- <SERR- <PERR-
	BridgeCtl: Parity- SERR- NoISA+ VGA- MAbort- >Reset- FastB2B-
		PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
	Capabilities: <access denied>
	Kernel driver in use: pcieport
	Kernel modules: shpchp

00:15.7 PCI bridge [0604]: VMware PCI Express Root Port [15ad:07a0] (rev 01) (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- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0, Cache Line Size: 32 bytes
	Interrupt: pin ? routed to IRQ 31
	Bus: primary=00, secondary=0a, subordinate=0a, sec-latency=0
	Memory behind bridge: fb800000-fb8fffff
	Prefetchable memory behind bridge: 00000000e6000000-00000000e60fffff
	Secondary status: 66MHz- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- <SERR- <PERR-
	BridgeCtl: Parity- SERR- NoISA+ VGA- MAbort- >Reset- FastB2B-
		PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
	Capabilities: <access denied>
	Kernel driver in use: pcieport
	Kernel modules: shpchp

00:16.0 PCI bridge [0604]: VMware PCI Express Root Port [15ad:07a0] (rev 01) (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- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0, Cache Line Size: 32 bytes
	Interrupt: pin ? routed to IRQ 32
	Bus: primary=00, secondary=0b, subordinate=0b, sec-latency=0
	I/O behind bridge: 00005000-00005fff
	Memory behind bridge: fd300000-fd3fffff
	Prefetchable memory behind bridge: 00000000c0200000-00000000c03fffff
	Secondary status: 66MHz- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- <SERR- <PERR-
	BridgeCtl: Parity- SERR- NoISA+ VGA- MAbort- >Reset- FastB2B-
		PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
	Capabilities: <access denied>
	Kernel driver in use: pcieport
	Kernel modules: shpchp

00:16.1 PCI bridge [0604]: VMware PCI Express Root Port [15ad:07a0] (rev 01) (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- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0, Cache Line Size: 32 bytes
	Interrupt: pin ? routed to IRQ 33
	Bus: primary=00, secondary=0c, subordinate=0c, sec-latency=0
	I/O behind bridge: 00009000-00009fff
	Memory behind bridge: fcf00000-fcffffff
	Prefetchable memory behind bridge: 00000000e7700000-00000000e77fffff
	Secondary status: 66MHz- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- <SERR- <PERR-
	BridgeCtl: Parity- SERR- NoISA+ VGA- MAbort- >Reset- FastB2B-
		PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
	Capabilities: <access denied>
	Kernel driver in use: pcieport
	Kernel modules: shpchp

00:16.2 PCI bridge [0604]: VMware PCI Express Root Port [15ad:07a0] (rev 01) (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- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0, Cache Line Size: 32 bytes
	Interrupt: pin ? routed to IRQ 34
	Bus: primary=00, secondary=0d, subordinate=0d, sec-latency=0
	I/O behind bridge: 0000d000-0000dfff
	Memory behind bridge: fcb00000-fcbfffff
	Prefetchable memory behind bridge: 00000000e7300000-00000000e73fffff
	Secondary status: 66MHz- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- <SERR- <PERR-
	BridgeCtl: Parity- SERR- NoISA+ VGA- MAbort- >Reset- FastB2B-
		PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
	Capabilities: <access denied>
	Kernel driver in use: pcieport
	Kernel modules: shpchp

00:16.3 PCI bridge [0604]: VMware PCI Express Root Port [15ad:07a0] (rev 01) (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- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0, Cache Line Size: 32 bytes
	Interrupt: pin ? routed to IRQ 35
	Bus: primary=00, secondary=0e, subordinate=0e, sec-latency=0
	Memory behind bridge: fc700000-fc7fffff
	Prefetchable memory behind bridge: 00000000e6f00000-00000000e6ffffff
	Secondary status: 66MHz- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- <SERR- <PERR-
	BridgeCtl: Parity- SERR- NoISA+ VGA- MAbort- >Reset- FastB2B-
		PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
	Capabilities: <access denied>
	Kernel driver in use: pcieport
	Kernel modules: shpchp

00:16.4 PCI bridge [0604]: VMware PCI Express Root Port [15ad:07a0] (rev 01) (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- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0, Cache Line Size: 32 bytes
	Interrupt: pin ? routed to IRQ 36
	Bus: primary=00, secondary=0f, subordinate=0f, sec-latency=0
	Memory behind bridge: fc300000-fc3fffff
	Prefetchable memory behind bridge: 00000000e6b00000-00000000e6bfffff
	Secondary status: 66MHz- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- <SERR- <PERR-
	BridgeCtl: Parity- SERR- NoISA+ VGA- MAbort- >Reset- FastB2B-
		PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
	Capabilities: <access denied>
	Kernel driver in use: pcieport
	Kernel modules: shpchp

00:16.5 PCI bridge [0604]: VMware PCI Express Root Port [15ad:07a0] (rev 01) (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- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0, Cache Line Size: 32 bytes
	Interrupt: pin ? routed to IRQ 37
	Bus: primary=00, secondary=10, subordinate=10, sec-latency=0
	Memory behind bridge: fbf00000-fbffffff
	Prefetchable memory behind bridge: 00000000e6700000-00000000e67fffff
	Secondary status: 66MHz- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- <SERR- <PERR-
	BridgeCtl: Parity- SERR- NoISA+ VGA- MAbort- >Reset- FastB2B-
		PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
	Capabilities: <access denied>
	Kernel driver in use: pcieport
	Kernel modules: shpchp

00:16.6 PCI bridge [0604]: VMware PCI Express Root Port [15ad:07a0] (rev 01) (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- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0, Cache Line Size: 32 bytes
	Interrupt: pin ? routed to IRQ 38
	Bus: primary=00, secondary=11, subordinate=11, sec-latency=0
	Memory behind bridge: fbb00000-fbbfffff
	Prefetchable memory behind bridge: 00000000e6300000-00000000e63fffff
	Secondary status: 66MHz- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- <SERR- <PERR-
	BridgeCtl: Parity- SERR- NoISA+ VGA- MAbort- >Reset- FastB2B-
		PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
	Capabilities: <access denied>
	Kernel driver in use: pcieport
	Kernel modules: shpchp

00:16.7 PCI bridge [0604]: VMware PCI Express Root Port [15ad:07a0] (rev 01) (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- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0, Cache Line Size: 32 bytes
	Interrupt: pin ? routed to IRQ 39
	Bus: primary=00, secondary=12, subordinate=12, sec-latency=0
	Memory behind bridge: fb700000-fb7fffff
	Prefetchable memory behind bridge: 00000000e5f00000-00000000e5ffffff
	Secondary status: 66MHz- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- <SERR- <PERR-
	BridgeCtl: Parity- SERR- NoISA+ VGA- MAbort- >Reset- FastB2B-
		PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
	Capabilities: <access denied>
	Kernel driver in use: pcieport
	Kernel modules: shpchp

00:17.0 PCI bridge [0604]: VMware PCI Express Root Port [15ad:07a0] (rev 01) (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- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0, Cache Line Size: 32 bytes
	Interrupt: pin ? routed to IRQ 40
	Bus: primary=00, secondary=13, subordinate=13, sec-latency=0
	I/O behind bridge: 00006000-00006fff
	Memory behind bridge: fd200000-fd2fffff
	Prefetchable memory behind bridge: 00000000e7a00000-00000000e7afffff
	Secondary status: 66MHz- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- <SERR- <PERR-
	BridgeCtl: Parity- SERR- NoISA+ VGA- MAbort- >Reset- FastB2B-
		PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
	Capabilities: <access denied>
	Kernel driver in use: pcieport
	Kernel modules: shpchp

00:17.1 PCI bridge [0604]: VMware PCI Express Root Port [15ad:07a0] (rev 01) (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- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0, Cache Line Size: 32 bytes
	Interrupt: pin ? routed to IRQ 41
	Bus: primary=00, secondary=14, subordinate=14, sec-latency=0
	I/O behind bridge: 0000a000-0000afff
	Memory behind bridge: fce00000-fcefffff
	Prefetchable memory behind bridge: 00000000e7600000-00000000e76fffff
	Secondary status: 66MHz- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- <SERR- <PERR-
	BridgeCtl: Parity- SERR- NoISA+ VGA- MAbort- >Reset- FastB2B-
		PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
	Capabilities: <access denied>
	Kernel driver in use: pcieport
	Kernel modules: shpchp

00:17.2 PCI bridge [0604]: VMware PCI Express Root Port [15ad:07a0] (rev 01) (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- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0, Cache Line Size: 32 bytes
	Interrupt: pin ? routed to IRQ 42
	Bus: primary=00, secondary=15, subordinate=15, sec-latency=0
	I/O behind bridge: 0000e000-0000efff
	Memory behind bridge: fca00000-fcafffff
	Prefetchable memory behind bridge: 00000000e7200000-00000000e72fffff
	Secondary status: 66MHz- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- <SERR- <PERR-
	BridgeCtl: Parity- SERR- NoISA+ VGA- MAbort- >Reset- FastB2B-
		PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
	Capabilities: <access denied>
	Kernel driver in use: pcieport
	Kernel modules: shpchp

00:17.3 PCI bridge [0604]: VMware PCI Express Root Port [15ad:07a0] (rev 01) (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- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0, Cache Line Size: 32 bytes
	Interrupt: pin ? routed to IRQ 43
	Bus: primary=00, secondary=16, subordinate=16, sec-latency=0
	Memory behind bridge: fc600000-fc6fffff
	Prefetchable memory behind bridge: 00000000e6e00000-00000000e6efffff
	Secondary status: 66MHz- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- <SERR- <PERR-
	BridgeCtl: Parity- SERR- NoISA+ VGA- MAbort- >Reset- FastB2B-
		PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
	Capabilities: <access denied>
	Kernel driver in use: pcieport
	Kernel modules: shpchp

00:17.4 PCI bridge [0604]: VMware PCI Express Root Port [15ad:07a0] (rev 01) (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- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0, Cache Line Size: 32 bytes
	Interrupt: pin ? routed to IRQ 44
	Bus: primary=00, secondary=17, subordinate=17, sec-latency=0
	Memory behind bridge: fc200000-fc2fffff
	Prefetchable memory behind bridge: 00000000e6a00000-00000000e6afffff
	Secondary status: 66MHz- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- <SERR- <PERR-
	BridgeCtl: Parity- SERR- NoISA+ VGA- MAbort- >Reset- FastB2B-
		PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
	Capabilities: <access denied>
	Kernel driver in use: pcieport
	Kernel modules: shpchp

00:17.5 PCI bridge [0604]: VMware PCI Express Root Port [15ad:07a0] (rev 01) (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- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0, Cache Line Size: 32 bytes
	Interrupt: pin ? routed to IRQ 45
	Bus: primary=00, secondary=18, subordinate=18, sec-latency=0
	Memory behind bridge: fbe00000-fbefffff
	Prefetchable memory behind bridge: 00000000e6600000-00000000e66fffff
	Secondary status: 66MHz- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- <SERR- <PERR-
	BridgeCtl: Parity- SERR- NoISA+ VGA- MAbort- >Reset- FastB2B-
		PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
	Capabilities: <access denied>
	Kernel driver in use: pcieport
	Kernel modules: shpchp

00:17.6 PCI bridge [0604]: VMware PCI Express Root Port [15ad:07a0] (rev 01) (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- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0, Cache Line Size: 32 bytes
	Interrupt: pin ? routed to IRQ 46
	Bus: primary=00, secondary=19, subordinate=19, sec-latency=0
	Memory behind bridge: fba00000-fbafffff
	Prefetchable memory behind bridge: 00000000e6200000-00000000e62fffff
	Secondary status: 66MHz- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- <SERR- <PERR-
	BridgeCtl: Parity- SERR- NoISA+ VGA- MAbort- >Reset- FastB2B-
		PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
	Capabilities: <access denied>
	Kernel driver in use: pcieport
	Kernel modules: shpchp

00:17.7 PCI bridge [0604]: VMware PCI Express Root Port [15ad:07a0] (rev 01) (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- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0, Cache Line Size: 32 bytes
	Interrupt: pin ? routed to IRQ 47
	Bus: primary=00, secondary=1a, subordinate=1a, sec-latency=0
	Memory behind bridge: fb600000-fb6fffff
	Prefetchable memory behind bridge: 00000000e5e00000-00000000e5efffff
	Secondary status: 66MHz- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- <SERR- <PERR-
	BridgeCtl: Parity- SERR- NoISA+ VGA- MAbort- >Reset- FastB2B-
		PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
	Capabilities: <access denied>
	Kernel driver in use: pcieport
	Kernel modules: shpchp

00:18.0 PCI bridge [0604]: VMware PCI Express Root Port [15ad:07a0] (rev 01) (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- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0, Cache Line Size: 32 bytes
	Interrupt: pin ? routed to IRQ 48
	Bus: primary=00, secondary=1b, subordinate=1b, sec-latency=0
	I/O behind bridge: 00007000-00007fff
	Memory behind bridge: fd100000-fd1fffff
	Prefetchable memory behind bridge: 00000000e7900000-00000000e79fffff
	Secondary status: 66MHz- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- <SERR- <PERR-
	BridgeCtl: Parity- SERR- NoISA+ VGA- MAbort- >Reset- FastB2B-
		PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
	Capabilities: <access denied>
	Kernel driver in use: pcieport
	Kernel modules: shpchp

00:18.1 PCI bridge [0604]: VMware PCI Express Root Port [15ad:07a0] (rev 01) (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- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0, Cache Line Size: 32 bytes
	Interrupt: pin ? routed to IRQ 49
	Bus: primary=00, secondary=1c, subordinate=1c, sec-latency=0
	I/O behind bridge: 0000b000-0000bfff
	Memory behind bridge: fcd00000-fcdfffff
	Prefetchable memory behind bridge: 00000000e7500000-00000000e75fffff
	Secondary status: 66MHz- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- <SERR- <PERR-
	BridgeCtl: Parity- SERR- NoISA+ VGA- MAbort- >Reset- FastB2B-
		PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
	Capabilities: <access denied>
	Kernel driver in use: pcieport
	Kernel modules: shpchp

00:18.2 PCI bridge [0604]: VMware PCI Express Root Port [15ad:07a0] (rev 01) (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- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0, Cache Line Size: 32 bytes
	Interrupt: pin ? routed to IRQ 50
	Bus: primary=00, secondary=1d, subordinate=1d, sec-latency=0
	Memory behind bridge: fc900000-fc9fffff
	Prefetchable memory behind bridge: 00000000e7100000-00000000e71fffff
	Secondary status: 66MHz- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- <SERR- <PERR-
	BridgeCtl: Parity- SERR- NoISA+ VGA- MAbort- >Reset- FastB2B-
		PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
	Capabilities: <access denied>
	Kernel driver in use: pcieport
	Kernel modules: shpchp

00:18.3 PCI bridge [0604]: VMware PCI Express Root Port [15ad:07a0] (rev 01) (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- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0, Cache Line Size: 32 bytes
	Interrupt: pin ? routed to IRQ 51
	Bus: primary=00, secondary=1e, subordinate=1e, sec-latency=0
	Memory behind bridge: fc500000-fc5fffff
	Prefetchable memory behind bridge: 00000000e6d00000-00000000e6dfffff
	Secondary status: 66MHz- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- <SERR- <PERR-
	BridgeCtl: Parity- SERR- NoISA+ VGA- MAbort- >Reset- FastB2B-
		PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
	Capabilities: <access denied>
	Kernel driver in use: pcieport
	Kernel modules: shpchp

00:18.4 PCI bridge [0604]: VMware PCI Express Root Port [15ad:07a0] (rev 01) (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- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0, Cache Line Size: 32 bytes
	Interrupt: pin ? routed to IRQ 52
	Bus: primary=00, secondary=1f, subordinate=1f, sec-latency=0
	Memory behind bridge: fc100000-fc1fffff
	Prefetchable memory behind bridge: 00000000e6900000-00000000e69fffff
	Secondary status: 66MHz- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- <SERR- <PERR-
	BridgeCtl: Parity- SERR- NoISA+ VGA- MAbort- >Reset- FastB2B-
		PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
	Capabilities: <access denied>
	Kernel driver in use: pcieport
	Kernel modules: shpchp

00:18.5 PCI bridge [0604]: VMware PCI Express Root Port [15ad:07a0] (rev 01) (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- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0, Cache Line Size: 32 bytes
	Interrupt: pin ? routed to IRQ 53
	Bus: primary=00, secondary=20, subordinate=20, sec-latency=0
	Memory behind bridge: fbd00000-fbdfffff
	Prefetchable memory behind bridge: 00000000e6500000-00000000e65fffff
	Secondary status: 66MHz- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- <SERR- <PERR-
	BridgeCtl: Parity- SERR- NoISA+ VGA- MAbort- >Reset- FastB2B-
		PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
	Capabilities: <access denied>
	Kernel driver in use: pcieport
	Kernel modules: shpchp

00:18.6 PCI bridge [0604]: VMware PCI Express Root Port [15ad:07a0] (rev 01) (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- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0, Cache Line Size: 32 bytes
	Interrupt: pin ? routed to IRQ 54
	Bus: primary=00, secondary=21, subordinate=21, sec-latency=0
	Memory behind bridge: fb900000-fb9fffff
	Prefetchable memory behind bridge: 00000000e6100000-00000000e61fffff
	Secondary status: 66MHz- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- <SERR- <PERR-
	BridgeCtl: Parity- SERR- NoISA+ VGA- MAbort- >Reset- FastB2B-
		PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
	Capabilities: <access denied>
	Kernel driver in use: pcieport
	Kernel modules: shpchp

00:18.7 PCI bridge [0604]: VMware PCI Express Root Port [15ad:07a0] (rev 01) (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- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0, Cache Line Size: 32 bytes
	Interrupt: pin ? routed to IRQ 55
	Bus: primary=00, secondary=22, subordinate=22, sec-latency=0
	Memory behind bridge: fb500000-fb5fffff
	Prefetchable memory behind bridge: 00000000e5d00000-00000000e5dfffff
	Secondary status: 66MHz- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- <SERR- <PERR-
	BridgeCtl: Parity- SERR- NoISA+ VGA- MAbort- >Reset- FastB2B-
		PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
	Capabilities: <access denied>
	Kernel driver in use: pcieport
	Kernel modules: shpchp

02:00.0 USB controller [0c03]: VMware USB1.1 UHCI Controller [15ad:0774] (prog-if 00 [UHCI])
	Subsystem: VMware USB1.1 UHCI Controller [15ad:1976]
	Physical Slot: 32
	Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
	Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 64
	Interrupt: pin A routed to IRQ 18
	Region 4: I/O ports at 2000 [size=32]
	Capabilities: <access denied>
	Kernel driver in use: uhci_hcd
	Kernel modules: uhci_hcd

02:01.0 USB controller [0c03]: VMware USB2 EHCI Controller [15ad:0770] (prog-if 20 [EHCI])
	Subsystem: VMware USB2 EHCI Controller [15ad:0770]
	Physical Slot: 33
	Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
	Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 64 (1500ns min, 63750ns max)
	Interrupt: pin A routed to IRQ 19
	Region 0: Memory at fd5ff000 (32-bit, non-prefetchable) [size=4K]
	Capabilities: <access denied>
	Kernel driver in use: ehci-pci
	Kernel modules: ehci_pci

02:03.0 SATA controller [0106]: VMware SATA AHCI controller [15ad:07e0] (prog-if 01 [AHCI 1.0])
	Subsystem: VMware SATA AHCI controller [15ad:07e0]
	Physical Slot: 35
	Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
	Status: Cap+ 66MHz+ UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 64
	Interrupt: pin A routed to IRQ 66
	Region 5: Memory at fd5fe000 (32-bit, non-prefetchable) [size=4K]
	[virtual] Expansion ROM at fd500000 [disabled] [size=64K]
	Capabilities: <access denied>
	Kernel driver in use: ahci
	Kernel modules: ahci

03:00.0 Serial Attached SCSI controller [0107]: VMware PVSCSI SCSI Controller [15ad:07c0] (rev 02)
	Subsystem: VMware PVSCSI SCSI Controller [15ad:07c0]
	Physical Slot: 160
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
	Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0
	Interrupt: pin A routed to IRQ 18
	Region 0: I/O ports at 4000 [size=8]
	Region 1: Memory at fd4f8000 (64-bit, non-prefetchable) [size=32K]
	[virtual] Expansion ROM at fd400000 [disabled] [size=64K]
	Capabilities: <access denied>
	Kernel driver in use: vmw_pvscsi
	Kernel modules: vmw_pvscsi

0b:00.0 Ethernet controller [0200]: VMware VMXNET3 Ethernet Controller [15ad:07b0] (rev 01)
	Subsystem: VMware VMXNET3 Ethernet Controller [15ad:07b0]
	Physical Slot: 192
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
	Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0, Cache Line Size: 32 bytes
	Interrupt: pin A routed to IRQ 19
	Region 0: Memory at fd3fc000 (32-bit, non-prefetchable) [size=4K]
	Region 1: Memory at fd3fd000 (32-bit, non-prefetchable) [size=4K]
	Region 2: Memory at fd3fe000 (32-bit, non-prefetchable) [size=8K]
	Region 3: I/O ports at 5000 [size=16]
	[virtual] Expansion ROM at fd300000 [disabled] [size=64K]
	Capabilities: <access denied>
	Kernel driver in use: vmxnet3
	Kernel modules: vmxnet3


** USB devices:
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub
Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub


-- System Information:
Debian Release: 9.5
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.9.0-8-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages linux-image-4.9.0-8-amd64 depends on:
ii  initramfs-tools [linux-initramfs-tool]  0.130
ii  kmod                                    23-2
ii  linux-base                              4.5

Versions of packages linux-image-4.9.0-8-amd64 recommends:
ii  firmware-linux-free  3.4
ii  irqbalance           1.1.0-2.3

Versions of packages linux-image-4.9.0-8-amd64 suggests:
pn  debian-kernel-handbook  <none>
ii  grub-pc                 2.02~beta3-5
pn  linux-doc-4.9           <none>

Versions of packages linux-image-4.9.0-8-amd64 is related to:
pn  firmware-amd-graphics     <none>
pn  firmware-atheros          <none>
pn  firmware-bnx2             <none>
pn  firmware-bnx2x            <none>
pn  firmware-brcm80211        <none>
pn  firmware-cavium           <none>
pn  firmware-intel-sound      <none>
pn  firmware-intelwimax       <none>
pn  firmware-ipw2x00          <none>
pn  firmware-ivtv             <none>
pn  firmware-iwlwifi          <none>
pn  firmware-libertas         <none>
pn  firmware-linux-nonfree    <none>
pn  firmware-misc-nonfree     <none>
pn  firmware-myricom          <none>
pn  firmware-netxen           <none>
pn  firmware-qlogic           <none>
pn  firmware-realtek          <none>
pn  firmware-samsung          <none>
pn  firmware-siano            <none>
pn  firmware-ti-connectivity  <none>
pn  xen-hypervisor            <none>

-- no debconf information

Information forwarded to debian-bugs-dist@lists.debian.org, Debian Kernel Team <debian-kernel@lists.debian.org>:
Bug#910074; Package src:linux. (Tue, 02 Oct 2018 20:12:03 GMT) (full text, mbox, link).

Acknowledgement sent to Nicholas D Steeves <nsteeves@gmail.com>:
Extra info received and forwarded to list. Copy sent to Debian Kernel Team <debian-kernel@lists.debian.org>. (Tue, 02 Oct 2018 20:12:03 GMT) (full text, mbox, link).

Message #10 received at submit@bugs.debian.org (full text, mbox, reply):

From: Nicholas D Steeves <nsteeves@gmail.com>
To: Michael Firth <mfirth@nevion.com>, 910074@bugs.debian.org
Cc: Debian Bug Tracking System <submit@bugs.debian.org>
Subject: Re: Bug#910074: linux-image-4.9.0-8-amd64: BTRFS data loss - kernel BUG at .../linux-4.9.110/fs/btrfs/ctree.c:3178
Date: Tue, 2 Oct 2018 16:08:39 -0400
[Message part 1 (text/plain, inline)]
Hi Michael,

On Tue, Oct 02, 2018 at 11:37:45AM +0100, Michael Firth wrote:
> 
> After this, there was a file that was errored on the filesystem (as
> reported by 'btrfs check'), and it seems BTRFS doesn't have any tools to
> resolve the error. Deleting the file at the reported inode has cleared
> the error from 'btrfs check', but I am not 100% sure that will have
> fixed all the corruption.
>

As far as I know, if 'btrfs check' is clean then you're in the clear
for any known issues involving the fs structure.  Of course, a 'btrfs
scrub' is necessary to check for data and metadata corruption...  BTW,
if you're using an ssd, make sure you're mounting with -o nossd,
because as far as I know linux-4.9.x still hasn't been patched.
P.S. that requires a full rebalance to take effect.  Make up-to-date
backups before running that rebalance...

> This issue looks very like the bug described at:
> 
> https://www.spinics.net/lists/linux-btrfs/msg60984.html
> 
> And in bug report #708509 for a much older kernel (from 2013)
> 
> According to the BTRFS mailing list post above, there are patches
> submitted to fix this issue (or one with the same symptoms).
> Is there any way to easily determine if these patches are in the Debian
> version of the V4.9.110 kernel?

The last time I checked I couldn't find any btrfs-specific ones in
Debian; I used apt-get source and expected to find a quilt series.

> If not, what is the route to get these patches incorporated? Do I need
> to talk to the BTRFS people about getting the patches in to the stock
> V4.9 kernel, or is this something that the Debian team would apply
> directly?

The first of the two patches from that 29 Nov 2016 linux-btrfs email
appears to be queued for linux-4.9.119:
  https://lore.kernel.org/patchwork/patch/972419/

I wasn't able to find status of the second one wrt linux-4.9.x.

> Kernel bug report output included below, in case it is useful.
> 
> BTRFS may not be a filesystem that everyone uses, but I feel if it is in
> the Debian kernel then bugs that can cause data loss should be fixed if
> a patch already exists.

In principle I agree; although I think it would be safer to coordinate
with Greg Kroah-Harman about getting them applied upstream before
importing them into Debian, since (afaik) we don't have any btrfs
specialists working on our kernel...people who would know if importing
one of these patches will introduce unintended side-effects or a
rabbit hole of patches.  Maybe it would be safer to look at the delta
between btrfs in 4.9.x and 4.14.x and ask for backported fixes from
4.14.x to 4.9.x? (eg: more than six months of testing in 4.14.x, like
the -o ssd bug that is still present in 4.9.x)

Cheers,
Nicholas

[signature.asc (application/pgp-signature, inline)]

Information forwarded to debian-bugs-dist@lists.debian.org, Debian Kernel Team <debian-kernel@lists.debian.org>:
Bug#910074; Package src:linux. (Tue, 02 Oct 2018 20:12:04 GMT) (full text, mbox, link).

Acknowledgement sent to Nicholas D Steeves <nsteeves@gmail.com>:
Extra info received and forwarded to list. Copy sent to Debian Kernel Team <debian-kernel@lists.debian.org>. (Tue, 02 Oct 2018 20:12:04 GMT) (full text, mbox, link).

Information forwarded to debian-bugs-dist@lists.debian.org, Debian Kernel Team <debian-kernel@lists.debian.org>:
Bug#910074; Package src:linux. (Tue, 02 Oct 2018 22:15:03 GMT) (full text, mbox, link).

Acknowledgement sent to Hans van Kranenburg <hans@knorrie.org>:
Extra info received and forwarded to list. Copy sent to Debian Kernel Team <debian-kernel@lists.debian.org>. (Tue, 02 Oct 2018 22:15:03 GMT) (full text, mbox, link).

Message #20 received at 910074@bugs.debian.org (full text, mbox, reply):

From: Hans van Kranenburg <hans@knorrie.org>
To: Nicholas D Steeves <nsteeves@gmail.com>, 910074@bugs.debian.org, Michael Firth <mfirth@nevion.com>
Subject: Re: Bug#910074: linux-image-4.9.0-8-amd64: BTRFS data loss - kernel BUG at .../linux-4.9.110/fs/btrfs/ctree.c:3178
Date: Wed, 3 Oct 2018 00:05:31 +0200
[Message part 1 (text/plain, inline)]
Hi,

On 10/02/2018 10:08 PM, Nicholas D Steeves wrote:
> Hi Michael,
> 
> On Tue, Oct 02, 2018 at 11:37:45AM +0100, Michael Firth wrote:
>>
>> After this, there was a file that was errored on the filesystem (as
>> reported by 'btrfs check'), and it seems BTRFS doesn't have any tools to
>> resolve the error. Deleting the file at the reported inode has cleared
>> the error from 'btrfs check', but I am not 100% sure that will have
>> fixed all the corruption.
>>
> 
> As far as I know, if 'btrfs check' is clean then you're in the clear
> for any known issues involving the fs structure.  Of course, a 'btrfs
> scrub' is necessary to check for data and metadata corruption...  BTW,
> if you're using an ssd, make sure you're mounting with -o nossd,
> because as far as I know linux-4.9.x still hasn't been patched.
> P.S. that requires a full rebalance to take effect.  Make up-to-date
> backups before running that rebalance...
> 
>> This issue looks very like the bug described at:
>>
>> https://www.spinics.net/lists/linux-btrfs/msg60984.html
>>
>> And in bug report #708509 for a much older kernel (from 2013)
>>
>> According to the BTRFS mailing list post above, there are patches
>> submitted to fix this issue (or one with the same symptoms).
>> Is there any way to easily determine if these patches are in the Debian
>> version of the V4.9.110 kernel?
> 
> The last time I checked I couldn't find any btrfs-specific ones in
> Debian; I used apt-get source and expected to find a quilt series.
> 
>> If not, what is the route to get these patches incorporated? Do I need
>> to talk to the BTRFS people about getting the patches in to the stock
>> V4.9 kernel, or is this something that the Debian team would apply
>> directly?
> 
> The first of the two patches from that 29 Nov 2016 linux-btrfs email
> appears to be queued for linux-4.9.119:
>   https://lore.kernel.org/patchwork/patch/972419/
> 
> I wasn't able to find status of the second one wrt linux-4.9.x.
> 
>> Kernel bug report output included below, in case it is useful.
>>
>> BTRFS may not be a filesystem that everyone uses, but I feel if it is in
>> the Debian kernel then bugs that can cause data loss should be fixed if
>> a patch already exists.
> 
> In principle I agree; although I think it would be safer to coordinate
> with Greg Kroah-Harman about getting them applied upstream before
> importing them into Debian, since (afaik)

> we don't have any btrfs
> specialists working on our kernel...people who would know if importing
> one of these patches will introduce unintended side-effects or a
> rabbit hole of patches.

This is not a debian specific issue. The upstream btrfs team does not
have enough work capacity to do this, and mainly focuses on going
forward instead of looking back. And I don't think there's really
someone who would know the things mentioned above except for the authors
of the patches themselves (who tag them for stable if it's data
corruption and if they know it will work (tm)), or the btrfs maintainer
who knows which ones to put together in which order to prepare the next
kernel release.

>  Maybe it would be safer to look at the delta
> between btrfs in 4.9.x and 4.14.x and ask for backported fixes from
> 4.14.x to 4.9.x? (eg: more than six months of testing in 4.14.x, like
> the -o ssd bug that is still present in 4.9.x)

For the -o ssd issue, in hindsight, it was a mistake to not get that
into 4.9 earlier.

Every user who wants to try out btrfs on his/her computer with Stretch
and uses it as the root filesystem on a disk which is not too large is
still affected by this sub-optimal behaviour.

So I guess that's a TODO for me, to still get it done now. It's 951e7966
and 583b723151 with a few small changes to make it apply. At least it
has had enough testing, and the amount of users with out-of-space
filesystems has decreased notably in the last year in #btrfs IRC. :)

Hans


[signature.asc (application/pgp-signature, attachment)]

Information forwarded to debian-bugs-dist@lists.debian.org, Debian Kernel Team <debian-kernel@lists.debian.org>:
Bug#910074; Package src:linux. (Wed, 03 Oct 2018 09:57:07 GMT) (full text, mbox, link).

Acknowledgement sent to Michael Firth <MFirth@nevion.com>:
Extra info received and forwarded to list. Copy sent to Debian Kernel Team <debian-kernel@lists.debian.org>. (Wed, 03 Oct 2018 09:57:07 GMT) (full text, mbox, link).

Message #25 received at submit@bugs.debian.org (full text, mbox, reply):

From: Michael Firth <MFirth@nevion.com>
To: Nicholas D Steeves <nsteeves@gmail.com>, "910074@bugs.debian.org" <910074@bugs.debian.org>
Cc: Debian Bug Tracking System <submit@bugs.debian.org>
Subject: RE: Bug#910074: linux-image-4.9.0-8-amd64: BTRFS data loss - kernel BUG at .../linux-4.9.110/fs/btrfs/ctree.c:3178
Date: Wed, 3 Oct 2018 09:56:13 +0000
Hi,

> -----Original Message-----
> 
> Hi Michael,
> 
> On Tue, Oct 02, 2018 at 11:37:45AM +0100, Michael Firth wrote:
> >
> > After this, there was a file that was errored on the filesystem (as
> > reported by 'btrfs check'), and it seems BTRFS doesn't have any tools
> > to resolve the error. Deleting the file at the reported inode has
> > cleared the error from 'btrfs check', but I am not 100% sure that will
> > have fixed all the corruption.
> >
> 
> As far as I know, if 'btrfs check' is clean then you're in the clear for any known
> issues involving the fs structure.  Of course, a 'btrfs scrub' is necessary to
> check for data and metadata corruption...  BTW, if you're using an ssd, make
> sure you're mounting with -o nossd, because as far as I know linux-4.9.x still
> hasn't been patched.
> P.S. that requires a full rebalance to take effect.  Make up-to-date backups
> before running that rebalance...

That is good to know. I will run a "scrub" on the partition soon to check for any
other issues. I am running on a VM on top of a hardware RAID array of
spinning disks, so hopefully the SSD issue doesn't apply.

> 
> > This issue looks very like the bug described at:
> >
> > https://www.spinics.net/lists/linux-btrfs/msg60984.html
> >
> > And in bug report #708509 for a much older kernel (from 2013)
> >
> > According to the BTRFS mailing list post above, there are patches
> > submitted to fix this issue (or one with the same symptoms).
> > Is there any way to easily determine if these patches are in the
> > Debian version of the V4.9.110 kernel?
> 
> The last time I checked I couldn't find any btrfs-specific ones in Debian; I used
> apt-get source and expected to find a quilt series.

There was a BTRFS patch in the update that became available an hour after my
crash:

linux (4.9.110-3+deb9u5) stretch-security; urgency=high
.
.
.
  * btrfs: relocation: Only remove reloc rb_trees if reloc control has been
    initialized (CVE-2018-14609)

I'm not sure if that is a Debian specific patch or whether it is a Debian specific 
merge from another version

> 
> > If not, what is the route to get these patches incorporated? Do I need
> > to talk to the BTRFS people about getting the patches in to the stock
> > V4.9 kernel, or is this something that the Debian team would apply
> > directly?
> 
> The first of the two patches from that 29 Nov 2016 linux-btrfs email appears
> to be queued for linux-4.9.119:
>   https://lore.kernel.org/patchwork/patch/972419/
> 

So I guess the related question that I should have asked is whether there is
information on how upstream changes are merged into the Debian kernel, and
what the likely delay between (for example) the 4.9.119 mainline kernel being
released, and the Debian version following it?

> I wasn't able to find status of the second one wrt linux-4.9.x.

Though the description is similar, I don't think patch 972419 is actually either of
the two patches referenced from that mail. I think I will ask on the BTRFS mailing
list what the current status of all of these patches is.

> 
> > Kernel bug report output included below, in case it is useful.
> >
> > BTRFS may not be a filesystem that everyone uses, but I feel if it is
> > in the Debian kernel then bugs that can cause data loss should be
> > fixed if a patch already exists.
> 
> In principle I agree; although I think it would be safer to coordinate with Greg
> Kroah-Harman about getting them applied upstream before importing them
> into Debian, since (afaik) we don't have any btrfs specialists working on our
> kernel...people who would know if importing one of these patches will
> introduce unintended side-effects or a rabbit hole of patches.  Maybe it
> would be safer to look at the delta between btrfs in 4.9.x and 4.14.x and ask
> for backported fixes from 4.14.x to 4.9.x? (eg: more than six months of
> testing in 4.14.x, like the -o ssd bug that is still present in 4.9.x)
> 
I agree with this, and with Hans's comment that because it isn't a Debian specific
issue it should be handled upstream. I guess the question comes partly from not
knowing if/how/when upstream V4.9.X kernel changes are merged into the Debian
Stretch kernel.

> Cheers,
> Nicholas


Regards

Michael

Information forwarded to debian-bugs-dist@lists.debian.org, Debian Kernel Team <debian-kernel@lists.debian.org>:
Bug#910074; Package src:linux. (Wed, 03 Oct 2018 10:09:02 GMT) (full text, mbox, link).

Acknowledgement sent to Michael Firth <MFirth@nevion.com>:
Extra info received and forwarded to list. Copy sent to Debian Kernel Team <debian-kernel@lists.debian.org>. (Wed, 03 Oct 2018 10:09:02 GMT) (full text, mbox, link).

Information forwarded to debian-bugs-dist@lists.debian.org, Debian Kernel Team <debian-kernel@lists.debian.org>:
Bug#910074; Package src:linux. (Tue, 09 Oct 2018 01:06:03 GMT) (full text, mbox, link).

Acknowledgement sent to Nicholas D Steeves <nsteeves@gmail.com>:
Extra info received and forwarded to list. Copy sent to Debian Kernel Team <debian-kernel@lists.debian.org>. (Tue, 09 Oct 2018 01:06:03 GMT) (full text, mbox, link).

Message #35 received at 910074@bugs.debian.org (full text, mbox, reply):

From: Nicholas D Steeves <nsteeves@gmail.com>
To: Hans van Kranenburg <hans@knorrie.org>, 910074@bugs.debian.org
Cc: Michael Firth <mfirth@nevion.com>
Subject: Re: Bug#910074: linux-image-4.9.0-8-amd64: BTRFS data loss - kernel BUG at .../linux-4.9.110/fs/btrfs/ctree.c:3178
Date: Mon, 8 Oct 2018 21:02:50 -0400
[Message part 1 (text/plain, inline)]
Hi Hans,

On Wed, Oct 03, 2018 at 12:05:31AM +0200, Hans van Kranenburg wrote:
> Hi,
> 
> On 10/02/2018 10:08 PM, Nicholas D Steeves wrote:
> > Hi Michael,
> > 
> > On Tue, Oct 02, 2018 at 11:37:45AM +0100, Michael Firth wrote:
> >>
> >> BTRFS may not be a filesystem that everyone uses, but I feel if it is in
> >> the Debian kernel then bugs that can cause data loss should be fixed if
> >> a patch already exists.
> > 
> > In principle I agree; although I think it would be safer to coordinate
> > with Greg Kroah-Harman about getting them applied upstream before
> > importing them into Debian, since (afaik)
> 
> > we don't have any btrfs
> > specialists working on our kernel...people who would know if importing
> > one of these patches will introduce unintended side-effects or a
> > rabbit hole of patches.
> 
> This is not a debian specific issue. The upstream btrfs team does not
> have enough work capacity to do this, and mainly focuses on going
> forward instead of looking back. And I don't think there's really
> someone who would know the things mentioned above except for the authors
> of the patches themselves (who tag them for stable if it's data
> corruption and if they know it will work (tm)), or the btrfs maintainer
> who knows which ones to put together in which order to prepare the next
> kernel release.

Agreed!  Also, acknowledging when issues aren't Debian-specific and
then working with upstream so everyone can benefit is one reason we
have a great reputation for giving back to the larger community :-)

> 
> >  Maybe it would be safer to look at the delta
> > between btrfs in 4.9.x and 4.14.x and ask for backported fixes from
> > 4.14.x to 4.9.x? (eg: more than six months of testing in 4.14.x, like
> > the -o ssd bug that is still present in 4.9.x)
> 
> For the -o ssd issue, in hindsight, it was a mistake to not get that
> into 4.9 earlier.
> 
> Every user who wants to try out btrfs on his/her computer with Stretch
> and uses it as the root filesystem on a disk which is not too large is
> still affected by this sub-optimal behaviour.
> 
> So I guess that's a TODO for me, to still get it done now. It's 951e7966
> and 583b723151 with a few small changes to make it apply. At least it
> has had enough testing, and the amount of users with out-of-space
> filesystems has decreased notably in the last year in #btrfs IRC. :)

Thank you!  I updated our wiki page within a week of learning about
the patch, but in the future would you prefer if I file a bug?  I
don't imagine it will be more than two bugs a year ;-)  Btw, would you
please forward the bug to me for the 951e7966 and 583b723151 backport?

Sincerely,
Nicholas

[signature.asc (application/pgp-signature, inline)]

Information forwarded to debian-bugs-dist@lists.debian.org, Debian Kernel Team <debian-kernel@lists.debian.org>:
Bug#910074; Package src:linux. (Tue, 09 Oct 2018 01:21:02 GMT) (full text, mbox, link).

Acknowledgement sent to Nicholas D Steeves <nsteeves@gmail.com>:
Extra info received and forwarded to list. Copy sent to Debian Kernel Team <debian-kernel@lists.debian.org>. (Tue, 09 Oct 2018 01:21:03 GMT) (full text, mbox, link).

Message #40 received at submit@bugs.debian.org (full text, mbox, reply):

From: Nicholas D Steeves <nsteeves@gmail.com>
To: Michael Firth <MFirth@nevion.com>, 910074@bugs.debian.org
Cc: Debian Bug Tracking System <submit@bugs.debian.org>
Subject: Re: Bug#910074: linux-image-4.9.0-8-amd64: BTRFS data loss - kernel BUG at .../linux-4.9.110/fs/btrfs/ctree.c:3178
Date: Mon, 8 Oct 2018 21:16:10 -0400
On Wed, Oct 03, 2018 at 09:56:13AM +0000, Michael Firth wrote:
> > 
> > As far as I know, if 'btrfs check' is clean then you're in the clear for any known
> > issues involving the fs structure.  Of course, a 'btrfs scrub' is necessary to
> > check for data and metadata corruption...  BTW, if you're using an ssd, make
> > sure you're mounting with -o nossd, because as far as I know linux-4.9.x still
> > hasn't been patched.
> > P.S. that requires a full rebalance to take effect.  Make up-to-date backups
> > before running that rebalance...
> 
> That is good to know. I will run a "scrub" on the partition soon to check for any
> other issues. I am running on a VM on top of a hardware RAID array of
> spinning disks, so hopefully the SSD issue doesn't apply.

To find out:

  cat /sys/block/your_hardware_raid_block_device/queue/rotational

If it returns "0" then you're affected by the -o ssd bug, but if it
returns "1" then there is nothing to worry about. :-)  While this
issue will become obsolete when the fix is backported I'm curious to
learn if hardware RAID registers as nonrotational, so please let me
know.  I suspect it will register as nonrotational, because then the
kernel will let the RAID controller merge and reorder IO as it sees
fit.

> 
> There was a BTRFS patch in the update that became available an hour after my
> crash:
> 
> linux (4.9.110-3+deb9u5) stretch-security; urgency=high
> .
> .
> .
>   * btrfs: relocation: Only remove reloc rb_trees if reloc control has been
>     initialized (CVE-2018-14609)
> 
> I'm not sure if that is a Debian specific patch or whether it is a Debian specific 
> merge from another version

Oh Nice!  I'm really happy to see this.  Thank you Ben and kernel team!

> > I wasn't able to find status of the second one wrt linux-4.9.x.
> 
> Though the description is similar, I don't think patch 972419 is actually either of
> the two patches referenced from that mail. I think I will ask on the BTRFS mailing
> list what the current status of all of these patches is.

Thanks.

> > In principle I agree; although I think it would be safer to coordinate with Greg
> > Kroah-Harman about getting them applied upstream before importing them
> > into Debian, since (afaik) we don't have any btrfs specialists working on our
> > kernel...people who would know if importing one of these patches will
> > introduce unintended side-effects or a rabbit hole of patches.  Maybe it
> > would be safer to look at the delta between btrfs in 4.9.x and 4.14.x and ask
> > for backported fixes from 4.14.x to 4.9.x? (eg: more than six months of
> > testing in 4.14.x, like the -o ssd bug that is still present in 4.9.x)
> > 
> I agree with this, and with Hans's comment that because it isn't a Debian specific
> issue it should be handled upstream. I guess the question comes partly from not
> knowing if/how/when upstream V4.9.X kernel changes are merged into the Debian
> Stretch kernel.

The version number is a hint.  Looking at the changelog for the
package, you'll see stretch released with 4.9.30-2, was updated with
security fixes in 4.9.30-2+deb9u1, was updated from upstream LTS in
4.9.47-1, etc, and is now at 4.9.110-3+deb9u6.


Cheers,
Nicholas

Information forwarded to debian-bugs-dist@lists.debian.org, Debian Kernel Team <debian-kernel@lists.debian.org>:
Bug#910074; Package src:linux. (Tue, 09 Oct 2018 01:21:04 GMT) (full text, mbox, link).

Acknowledgement sent to Nicholas D Steeves <nsteeves@gmail.com>:
Extra info received and forwarded to list. Copy sent to Debian Kernel Team <debian-kernel@lists.debian.org>. (Tue, 09 Oct 2018 01:21:04 GMT) (full text, mbox, link).

Send a report that this bug log contains spam.

Debian bug tracking system administrator <owner@bugs.debian.org>. Last modified: Thu Jul 23 23:05:17 2020; Machine Name: buxtehude

Debian Bug tracking system

Debbugs is free software and licensed under the terms of the GNU Public License version 2. The current version can be obtained from https://bugs.debian.org/debbugs-source/.

Copyright © 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson, 2005-2017 Don Armstrong, and many other contributors.