linux-ext4 - [Bug 198923] Linux 4.15.4+: Write on Ext4 causes system block

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <bug-198923-13602-O0ZzbKLzw4@https.bugzilla.kernel.org/>
Date:   Sat, 24 Feb 2018 18:54:42 +0000
From:   bugzilla-daemon@...zilla.kernel.org
To:     linux-ext4@...nel.org
Subject: [Bug 198923] Linux 4.15.4+: Write on Ext4 causes system block

https://bugzilla.kernel.org/show_bug.cgi?id=198923

Theodore Tso (tytso@....edu) changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |tytso@....edu

--- Comment #1 from Theodore Tso (tytso@....edu) ---
This looks like it's a SCSI issue.  The first soft lockup complaint is:

[  246.760015] INFO: task kworker/u16:2:220 blocked for more than 120 seconds.
[  246.760020]       Tainted: G        W        4.16.0-1-mainline #1
[  246.760021] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this
message.
[  246.760023] kworker/u16:2   D    0   220      2 0x80000000
[  246.760029] Workqueue: events_freezable_power_ disk_events_workfn
[  246.760031] Call Trace:
[  246.760037]  ? __schedule+0x24b/0x8a0
[  246.760039]  ? __clear_rsb+0x15/0x3d
[  246.760042]  ? preempt_count_add+0x68/0xa0
[  246.760046]  schedule+0x32/0x90
[  246.760056]  scsi_block_when_processing_errors+0x4a/0x100 [scsi_mod]
[  246.760059]  ? wait_woken+0x80/0x80
[  246.760063]  sd_check_events+0x75/0x1a0 [sd_mod]
[  246.760069]  disk_check_events+0x69/0x150
[  246.760072]  process_one_work+0x1ce/0x3f0
[  246.760074]  worker_thread+0x2b/0x3d0
[  246.760076]  ? process_one_work+0x3f0/0x3f0
[  246.760078]  kthread+0x113/0x130
[  246.760079]  ? kthread_create_on_node+0x70/0x70
[  246.760081]  ret_from_fork+0x22/0x40

Before that there is a RCU warning which might or might not be related:

[   82.065830] WARNING: CPU: 6 PID: 54 at kernel/rcu/tree.c:2713
rcu_do_batch.isra.29+0x231/0x250
[   82.065833] Modules linked in: tun cmac rfcomm input_leds joydev led_class
bnep it87 hwmon_vid btusb btrtl btbcm btintel bluetooth amdkfd amd_iommu_v2
ecdh_generic nls_iso8859_1 cdc_acm rfkill nls_cp437 vfat fat amdgpu
edac_mce_amd mousedev ext4 kvm_amd ccp crc16 mbcache mxm_wmi jbd2 kvm fscrypto
snd_hda_codec_realtek snd_hda_codec_generic snd_hda_codec_hdmi irqbypass
crct10dif_pclmul chash gpu_sched ghash_clmulni_intel ttm snd_hda_intel pcbc
snd_hda_codec drm_kms_helper snd_hda_core aesni_intel aes_x86_64 drm
crypto_simd snd_hwdep glue_helper snd_pcm cryptd sp5100_tco agpgart r8169
fam15h_power snd_timer syscopyarea sysfillrect sysimgblt k10temp snd mii
fb_sys_fops i2c_piix4 i2c_algo_bit soundcore evdev wmi shpchp rtc_cmos
acpi_cpufreq mac_hid sch_fq_codel ecryptfs cbc encrypted_keys trusted tpm
[   82.065935]  rng_core sg crypto_user ip_tables x_tables hid_generic usbhid
hid btrfs xor zstd_decompress zstd_compress xxhash raid6_pq sr_mod cdrom sd_mod
ohci_pci ahci xhci_pci ehci_pci libahci firewire_ohci xhci_hcd ehci_hcd
ohci_hcd libata firewire_core crc_itu_t usbcore scsi_mod usb_common
crc32_pclmul libcrc32c crc32c_generic crc32c_intel
[   82.065984] CPU: 6 PID: 54 Comm: rcuc/6 Not tainted 4.16.0-1-mainline #1
[   82.065986] Hardware name: Gigabyte Technology Co., Ltd. To be filled by
O.E.M./990FXA-UD3, BIOS F3i 10/07/2014
[   82.065992] RIP: 0010:rcu_do_batch.isra.29+0x231/0x250
[   82.065994] RSP: 0018:ffffac3f41a8fe50 EFLAGS: 00010002
[   82.065997] RAX: ffffffffffffd800 RBX: ffff8a28beda24c0 RCX:
0000000100200001
[   82.065999] RDX: 0000000000000006 RSI: ffffac3f41a8fe50 RDI:
ffff8a28beda24f8
[   82.066004] RBP: ffff8a28beda24f8 R08: 0000000000000001 R09:
ffffffff860efe39
[   82.066006] R10: ffffac3f41a97e30 R11: 0000000000000001 R12:
0000000000000246
[   82.066008] R13: ffffffff87052410 R14: ffffffffffffffff R15:
ffffffff8609e850
[   82.066012] FS:  0000000000000000(0000) GS:ffff8a28bed80000(0000)
knlGS:0000000000000000
[   82.066014] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[   82.066019] CR2: 00007f6674e81000 CR3: 00000003cfb8e000 CR4:
00000000000406e0
[   82.066022] Call Trace:
[   82.066033]  ? rcu_cpu_kthread+0x49/0x2d0
[   82.066039]  ? sort_range+0x20/0x20
[   82.066044]  rcu_cpu_kthread+0x10d/0x2d0
[   82.066050]  ? sort_range+0x20/0x20
[   82.066062]  smpboot_thread_fn+0x19e/0x240
[   82.066064]  kthread+0x113/0x130
[   82.066065]  ? kthread_create_on_node+0x70/0x70
[   82.066067]  ret_from_fork+0x22/0x40
[   82.066069] Code: 48 83 6c 24 18 01 e9 e8 fe ff ff 48 3b 15 50 25 f6 00 0f
8f 6b ff ff ff 48 8b 05 53 25 f6 00 48 89 83 b0 00 00 00 e9 58 ff ff ff <0f> 0b
eb 8d 0f 0b e9 65 fe ff ff e8 7f b3 f8 ff 0f 1f 44 00 00 
[   82.066091] ---[ end trace e53b91b9c6245d1c ]---

Since this reliably reproduces for you with 4.15.4, if 4.15.3 was the last good
version, I'd suggest doing a kernel bisection to see if you can isolate the
commit which introduced the regression.

-- 
You are receiving this mail because:
You are watching the assignee of the bug.