[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#841144: marked as done (base: kernel BUG at linux-4.7.5/fs/ocfs2/alloc.c:1514!)

Your message dated Sun, 2 May 2021 09:13:31 +0200
with message-id <YI5RG5FfkWu+GsM/@eldamar.lan>
and subject line Re: Bug#841144: Info received (kernel BUG at linux-4.7.5/fs/ocfs2/alloc.c:1514!)
has caused the Debian Bug report #841144,
regarding base: kernel BUG at linux-4.7.5/fs/ocfs2/alloc.c:1514!
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
841144: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841144
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: base
Severity: grave
Justification: renders package unusable

Dear Maintainer,

   * What led up to the situation?

Two-host virtualization cluster with DRBD mirrored volume and OCFS2 filesystem.

   * What exactly did you do (or not do) that was effective (or
     ineffective)?

Simply writing data to the volume exposed a kernel bug in OCFS2.

   * What was the outcome of this action?

Oct 17 09:57:38 vhost002 kernel: ------------[ cut here ]------------
Oct 17 09:57:38 vhost002 kernel: kernel BUG at /build/linux-rAvIHq/linux-4.7.5/fs/ocfs2/alloc.c:1514!
Oct 17 09:57:38 vhost002 kernel: invalid opcode: 0000 [#1] SMP
Oct 17 09:57:38 vhost002 kernel: Modules linked in: vhost_net vhost macvtap macvlan tun ocfs2 quota_tree cfg80211 rfkill iptable_filter ip_tables x_tables nfsd auth_rpcgss nfs_acl nfs lockd grace fscache ocfs2_dlmfs ocfs2_stack_o2cb sunrpc ocfs2_dlm ocfs2_nodemanager ocfs2_stackglue configfs bridge stp llc bonding ipmi_watchdog intel_rapl sb_edac edac_core x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm irqbypass crct10dif_pclmul crc32_pclmul ghash_clmulni_intel hmac drbg ansi_cprng igb iTCO_wdt ast iTCO_vendor_support mxm_wmi ttm evdev drm_kms_helper aesni_intel drm aes_x86_64 lrw xhci_pci gf128mul glue_helper xhci_hcd ablk_helper cryptd ehci_pci dca ehci_hcd e1000e i2c_algo_bit pcspkr usbcore ptp mei_me lpc_ich i2c_i801 sg mei shpchp mfd_core usb_common pps_core fjes wmi ipmi_si ipmi_poweroff ipmi_devintf
Oct 17 09:57:38 vhost002 kernel:  ipmi_msghandler tpm_tis tpm acpi_power_meter acpi_pad button fuse drbd lru_cache libcrc32c crc32c_generic autofs4 ext4 crc16 jbd2 mbcache dm_mod md_mod sd_mod ahci libahci libata crc32c_intel scsi_mod
Oct 17 09:57:38 vhost002 kernel: CPU: 7 PID: 17663 Comm: qemu-system-x86 Not tainted 4.7.0-0.bpo.1-amd64 #1 Debian 4.7.5-1~bpo8+2
Oct 17 09:57:38 vhost002 kernel: Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./EPC612D4I, BIOS P2.10 03/31/2016
Oct 17 09:57:38 vhost002 kernel: task: ffff8802547d9040 ti: ffff880257640000 task.ti: ffff880257640000
Oct 17 09:57:38 vhost002 kernel: RIP: 0010:[<ffffffffc09f4221>]  [<ffffffffc09f4221>] ocfs2_grow_tree+0x6f1/0x770 [ocfs2]
Oct 17 09:57:38 vhost002 kernel: RSP: 0018:ffff880257643618  EFLAGS: 00010246
Oct 17 09:57:38 vhost002 kernel: RAX: 0000000000000000 RBX: 000000000000000d RCX: ffff880257643790
Oct 17 09:57:38 vhost002 kernel: RDX: ffff8802576436bc RSI: ffff880257643968 RDI: ffff8801803473f0
Oct 17 09:57:38 vhost002 kernel: RBP: ffff880257643678 R08: 0000000000000000 R09: 0000000000390ce8
Oct 17 09:57:38 vhost002 kernel: R10: 0000000002a15008 R11: ffff880257d9a030 R12: 0000000000000001
Oct 17 09:57:38 vhost002 kernel: R13: ffff880257643828 R14: ffff8802622020c0 R15: 0000000000000002
Oct 17 09:57:38 vhost002 kernel: FS:  00007f718f75d700(0000) GS:ffff88103f3c0000(0000) knlGS:0000000000000000
Oct 17 09:57:38 vhost002 kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Oct 17 09:57:38 vhost002 kernel: CR2: 00007f7ba6591e4c CR3: 00000002825db000 CR4: 00000000001426e0
Oct 17 09:57:38 vhost002 kernel: Stack:
Oct 17 09:57:38 vhost002 kernel:  ffff880257643728 ffff880257643728 ffffffffc0a612a5 ffff88025da1a880
Oct 17 09:57:38 vhost002 kernel:  ffff8801803fd340 ffffffffb2c2fd37 000000008a1a0f55 000000000000000d
Oct 17 09:57:38 vhost002 kernel:  0000000000000001 ffff880257643828 ffff880257643968 ffff88025da1a880
Oct 17 09:57:38 vhost002 kernel: Call Trace:
Oct 17 09:57:38 vhost002 kernel:  [<ffffffffc0a612a5>] ? ocfs2_set_buffer_uptodate+0x35/0x4a0 [ocfs2]
Oct 17 09:57:38 vhost002 kernel:  [<ffffffffb2c2fd37>] ? __find_get_block+0xa7/0x110
Oct 17 09:57:38 vhost002 kernel:  [<ffffffffc09f6067>] ? ocfs2_split_and_insert+0x307/0x490 [ocfs2]
Oct 17 09:57:38 vhost002 kernel:  [<ffffffffc09fc51d>] ? ocfs2_split_extent+0x3ed/0x560 [ocfs2]
Oct 17 09:57:38 vhost002 kernel:  [<ffffffffc09fc903>] ? ocfs2_change_extent_flag+0x273/0x450 [ocfs2]
Oct 17 09:57:38 vhost002 kernel:  [<ffffffffc09fcbf0>] ? ocfs2_mark_extent_written+0x110/0x1d0 [ocfs2]
Oct 17 09:57:38 vhost002 kernel:  [<ffffffffc0a0100d>] ? ocfs2_dio_end_io_write+0x44d/0x600 [ocfs2]
Oct 17 09:57:38 vhost002 kernel:  [<ffffffffc0a27a50>] ? ocfs2_allocate_extend_trans+0x180/0x180 [ocfs2]
Oct 17 09:57:38 vhost002 kernel:  [<ffffffffc0a011fb>] ? ocfs2_dio_end_io+0x3b/0x60 [ocfs2]
Oct 17 09:57:38 vhost002 kernel:  [<ffffffffb2c35934>] ? dio_complete+0x64/0x160
Oct 17 09:57:38 vhost002 kernel:  [<ffffffffb2c386fa>] ? do_blockdev_direct_IO+0x1f5a/0x2350
Oct 17 09:57:38 vhost002 kernel:  [<ffffffffc0a04ed0>] ? ocfs2_write_end_nolock+0x560/0x560 [ocfs2]
Oct 17 09:57:38 vhost002 kernel:  [<ffffffffc0a00714>] ? ocfs2_direct_IO+0x84/0x90 [ocfs2]
Oct 17 09:57:38 vhost002 kernel:  [<ffffffffb2b7c893>] ? generic_file_direct_write+0xb3/0x180
Oct 17 09:57:38 vhost002 kernel:  [<ffffffffb2b7ca16>] ? __generic_file_write_iter+0xb6/0x1e0
Oct 17 09:57:38 vhost002 kernel:  [<ffffffffc0a1f8ad>] ? ocfs2_file_write_iter+0x44d/0xae0 [ocfs2]
Oct 17 09:57:38 vhost002 kernel:  [<ffffffffb2ae87c0>] ? hrtimer_init+0xf0/0xf0
Oct 17 09:57:38 vhost002 kernel:  [<ffffffffb2bf8f20>] ? do_iter_readv_writev+0xb0/0x130
Oct 17 09:57:38 vhost002 kernel:  [<ffffffffb2bf9c92>] ? do_readv_writev+0x1a2/0x240
Oct 17 09:57:38 vhost002 kernel:  [<ffffffffc0a1f460>] ? ocfs2_check_range_for_refcount+0x130/0x130 [ocfs2]
Oct 17 09:57:38 vhost002 kernel:  [<ffffffffb2bfa0dc>] ? do_pwritev+0x8c/0xc0
Oct 17 09:57:38 vhost002 kernel:  [<ffffffffb2fde3f6>] ? system_call_fast_compare_end+0xc/0x96
Oct 17 09:57:38 vhost002 kernel: Code: 24 28 48 c7 c1 b0 72 a8 c0 ba 1c 06 00 00 48 c7 c6 b0 99 a7 c0 31 c0 44 89 4c 24 18 e8 79 33 d5 ff 44 8b 4c 24 18 e9 27 fc ff ff <0f> 0b 48 8b 04 24 48 83 38 00 75 6c f0 ff 43 60 48 8b 04 24 45
Oct 17 09:57:38 vhost002 kernel: RIP  [<ffffffffc09f4221>] ocfs2_grow_tree+0x6f1/0x770 [ocfs2]
Oct 17 09:57:38 vhost002 kernel:  RSP <ffff880257643618>
Oct 17 09:57:38 vhost002 kernel: ---[ end trace 7692d04456f49f33 ]---

   * What outcome did you expect instead?

The code should work, not bomb.

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

Kernel: Linux 4.7.0-0.bpo.1-amd64 (SMP w/12 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

--- End Message ---
--- Begin Message --- 
Source: linux
Source-Version: 4.16~rc5-1~exp1

Hi,

On Mon, Jan 15, 2018 at 04:51:24PM -0600, John Lightsey wrote:
> The problem turned out to be slightly more complicated than I initially
> imagined.
> 
> In addition to calculating the number of extents in the write
> incorrectly, the directio write logic can truncate the extent tree
> while the write is taking place.
> 
> Changwei Ge came up with fully functional patches for the issue.
> 
> 
> I'm attaching versions of the upstream patches that have been
> backported for the Debian 4.9.0-5 kernel.

Those wre applied upstream a while back in 4.16-rc1 AFAICS. So closing
this bugreport.

Regards,
Salvatore

--- End Message ---
Reply to: