Xenial / Testing ====== modified --------
$ uname -rv 4.4.0-186-generic #216+lp1867916.1 SMP Mon Jul 6 18:45:47 -03 2020 $ sudo make-bcache --bdev $DEV --block 8k [ 60.860259] bcache: bcache_device_init() bcache0: sb/logical block size (8192) greater than page size (4096) falling back to device logical block size (512) [ 60.860312] bcache: register_bdev() registered backing device loop0 original -------- $ uname -rv 4.4.0-186-generic #216-Ubuntu SMP Wed Jul 1 05:34:05 UTC 2020 $ sudo make-bcache --bdev $DEV --block 8k [ 22.192801] bcache: register_bdev() registered backing device loop0 [ 22.197141] BUG: unable to handle kernel NULL pointer dereference at 0000000000000098 [ 22.198983] IP: [<ffffffff8125acb0>] bdev_read_page+0x10/0xb0 [ 22.200283] PGD 0 [ 22.200843] Oops: 0000 [#1] SMP [ 22.201796] Modules linked in: bcache isofs kvm_intel input_leds kvm irqbypass joydev serio_raw ib_iser rdma_cm iw_cm ib_cm ib_sa ib_mad ib_core ib_addr iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi autofs4 btrfs xor raid6_pq psmouse floppy [ 22.208162] CPU: 1 PID: 1301 Comm: systemd-udevd Not tainted 4.4.0-186-generic #216-Ubuntu [ 22.209642] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.10.2-1ubuntu1 04/01/2014 [ 22.211045] task: ffff8800b97ea700 ti: ffff8800b9b78000 task.ti: ffff8800b9b78000 [ 22.212244] RIP: 0010:[<ffffffff8125acb0>] [<ffffffff8125acb0>] bdev_read_page+0x10/0xb0 [ 22.213616] RSP: 0018:ffff8800b9b7ba80 EFLAGS: 00010283 [ 22.214513] RAX: 0000000000000004 RBX: 0000000000000000 RCX: 0000000000000004 [ 22.215730] RDX: ffffea0004e55280 RSI: fff8800b9b7bb580 RDI: 0000000000000000 [ 22.217220] RBP: ffff8800b9b7baa0 R08: ffff8800b9b7bbb8 R09: ffff8800b9b7bbb0 [ 22.218640] R10: ffff8800368b4df8 R11: fff8800b9b7bb580 R12: 0000000000000000 [ 22.220114] R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000 [ 22.221574] FS: 00007f5df7bd28c0(0000) GS:ffff88013fc80000(0000) knlGS:0000000000000000 [ 22.223416] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 22.224584] CR2: 0000000000000098 CR3: 00000000b9b76000 CR4: 0000000000000670 [ 22.225945] Stack: [ 22.226534] 0000000000000000 0000000000000000 0000000000000000 0000000000000000 [ 22.228516] ffff8800b9b7bb78 ffffffff81261bbe ffff8800368b4f80 ffff8800b9b7bba8 [ 22.230532] 0000000000000000 ffff8800b9b7bbb8 ffff8800b9b7bbb0 ffffffff8125a6b0 [ 22.232485] Call Trace: [ 22.233148] [<ffffffff81261bbe>] do_mpage_readpage+0x52e/0x7a0 [ 22.234384] [<ffffffff8125a6b0>] ? I_BDEV+0x20/0x20 [ 22.235487] [<ffffffff811abebe>] ? lru_cache_add+0xe/0x10 [ 22.236675] [<ffffffff81261f42>] mpage_readpages+0x112/0x190 [ 22.237903] [<ffffffff8125a6b0>] ? I_BDEV+0x20/0x20 [ 22.238960] [<ffffffff8125a6b0>] ? I_BDEV+0x20/0x20 [ 22.240025] [<ffffffff811f09dc>] ? alloc_pages_current+0x8c/0x110 [ 22.241308] [<ffffffff8125b1cd>] blkdev_readpages+0x1d/0x20 [ 22.242463] [<ffffffff811a9f39>] __do_page_cache_readahead+0x199/0x240 [ 22.243843] [<ffffffff811aa34a>] force_page_cache_readahead+0xaa/0x100 [ 22.245267] [<ffffffff811aa3df>] page_cache_sync_readahead+0x3f/0x50 [ 22.246572] [<ffffffff8119d0ba>] generic_file_read_iter+0x54a/0x6b0 [ 22.247876] [<ffffffff8125bcc5>] blkdev_read_iter+0x35/0x40 [ 22.249132] [<ffffffff8121e14e>] new_sync_read+0x9e/0xe0 [ 22.250312] [<ffffffff8121e1b9>] __vfs_read+0x29/0x40 [ 22.251460] [<ffffffff8121e926>] vfs_read+0x86/0x130 [ 22.252590] [<ffffffff8121f67c>] SyS_read+0x5c/0xe0 [ 22.253672] [<ffffffff8186991b>] entry_SYSCALL_64_fastpath+0x22/0xd0 [ 22.255015] Code: 83 f8 a1 0f 45 d8 89 d8 5b 41 5c 5d c3 0f 1f 40 00 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 55 48 89 e5 41 56 41 55 41 54 53 <48> 8b 87 98 00 00 00 4c 8b b0 c0 03 00 00 49 83 7e 10 00 74 7c [ 22.264489] RIP [<ffffffff8125acb0>] bdev_read_page+0x10/0xb0 [ 22.265778] RSP <ffff8800b9b7ba80> [ 22.266602] CR2: 0000000000000098 [ 22.267432] ---[ end trace ae0520addf7365b3 ]--- -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1867916 Title: Regression in kernel 4.15.0-91 causes kernel panic with Bcache Status in Linux: Confirmed Status in linux package in Ubuntu: Fix Committed Status in linux source package in Xenial: In Progress Status in linux source package in Bionic: In Progress Status in linux source package in Eoan: In Progress Status in linux source package in Focal: In Progress Status in linux source package in Groovy: Won't Fix Bug description: [Impact] * Users of bcache who manually specified a block size greater than the page size when creating the device with 'make-bcache' started to hit a kernel BUG/oops after kernel upgrades. (This is not widely used.) * The issue has been exposed with commit ad6bf88a6c19 ("block: fix an integer overflow in logical block size") because it increased the range of values accepted as logical block size, which used to overflow to zero, and thus receive a default of 512 via block layer. * The issue existed previously, but with fewer values exposed (e.g. 8k, 16k, 32k); the regression reports happened with larger values (512k) for RAID stripes. [Fix] * The upstream commit dcacbc1242c7 ("bcache: check and adjust logical block size for backing devices") checks the block size and adjusts it if needed, to the value of the underlying device's logical block size. * It is merged as of v5.8-rcN, and sent to v5.7 stable. [Test Case] * Run make-bcache with block size greater than page size. $ sudo make-bcache --bdev $DEV --block 8k * Expected results: bcache device registered; no BUG/oops. * Details steps on comment #43. [Regression Potential] * Restricted to users who specify a bcache block size greater than page size. * Regressions could theoretically manifest on bcache device probe/register, if the underlying device's logical block size for whatever triggers issues not seen previously with the overflow/default 512 bytes. [Other Info] * Unstable has the patch on both master/master-5.7. * Groovy should get it on rebase. [Original Bug Description] After upgrading from kernel 4.15.0-88 to 4.15.0-91 one of our systems does not boot any longer. It always crashes during boot with a kernel panic. I suspect that this crash might be related to Bcache because this is the only one of our systems where we use Bcache and the kernel panic appears right after Bcache initialization. I already checked that this bug still exists in the 4.15.0-92.93 kernel from proposed. Unfortunately, I cannot do a bisect because this is a critical production system and we do not have any other system with a similar configuration. I attached a screenshot with the trace of the kernel panic. The last message that appears before the kernel panic (or rather the last one that I can see - there is a rather long pause between that message and the panic and I cannot scroll up far enough to ensure that there are no other messages in between) is: bcache: register_bcache() error /dev/dm-0: device already registered When booting with kernel 4.15.0-88 that does not have this problem, the next message is bcache: register_bcache() error /dev/dm-12: device already registered (emitting change event) After that the next message is: Begin: Loading essential drivers ... done This message also appears after the kernel panic, but the boot process stalls and the system can only be recovered by doing a hardware reset. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-88-generic 4.15.0-88.88 ProcVersionSignature: Ubuntu 4.15.0-88.88-generic 4.15.18 Uname: Linux 4.15.0-88-generic x86_64 AlsaDevices: total 0 crw-rw---- 1 root audio 116, 1 Mar 17 21:08 seq crw-rw---- 1 root audio 116, 33 Mar 17 21:08 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.11 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Wed Mar 18 12:55:18 2020 HibernationDevice: RESUME=UUID=40512ea2-9fce-40f5-8362-5daf955cc26a InstallationDate: Installed on 2013-07-02 (2450 days ago) InstallationMedia: Ubuntu-Server 12.04.2 LTS "Precise Pangolin" - Release amd64 (20130214) MachineType: HP ProLiant DL160 G6 PciMultimedia: ProcFB: 0 mgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-88-generic root=/dev/mapper/vg0-root ro nosmt nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw RelatedPackageVersions: linux-restricted-modules-4.15.0-88-generic N/A linux-backports-modules-4.15.0-88-generic N/A linux-firmware 1.173.16 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: Upgraded to bionic on 2018-09-23 (541 days ago) dmi.bios.date: 11/06/2009 dmi.bios.vendor: HP dmi.bios.version: O33 dmi.chassis.asset.tag: 0191525 dmi.chassis.type: 23 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrO33:bd11/06/2009:svnHP:pnProLiantDL160G6:pvr:cvnHP:ct23:cvr: dmi.product.name: ProLiant DL160 G6 dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1867916/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
