From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id E84CFC19F2D for ; Tue, 9 Aug 2022 07:59:13 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S238067AbiHIH7L (ORCPT ); Tue, 9 Aug 2022 03:59:11 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:43844 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S237963AbiHIH7G (ORCPT ); Tue, 9 Aug 2022 03:59:06 -0400 Received: from mail-ej1-f46.google.com (mail-ej1-f46.google.com [209.85.218.46]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 55C3621814; Tue, 9 Aug 2022 00:59:05 -0700 (PDT) Received: by mail-ej1-f46.google.com with SMTP id m4so20837778ejr.3; Tue, 09 Aug 2022 00:59:05 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=content-transfer-encoding:in-reply-to:references:cc:to:from :content-language:subject:user-agent:mime-version:date:message-id :x-gm-message-state:from:to:cc; bh=MOiVsG6N2305FWXn7+KygIrlcaoyw/mCsKiNqQgBVVc=; b=My8sLWbKQgU4DSfeY2mV8z75zIcP9mleNUTSxZ+g0/lttyL3od60zjI2lYmcTXcGvL ZBdX5vZ96bMk959AXGaZK/uMg6qGpJF6uTKhhVEmC92BA1j1ILrU5raqMSfwT+ewBOq4 a6neDjTSXYQzeEWVir6RWKqcxqKlyQVxXBWsPCp055KqSxXef2o1O25mG2cWkzhLiq4W JD6ZROkKJVu0uBMelXVqgxUlJz67lgTwO6RKxYF50O1+3ctVRGwYxXPThq6a6LQ597JP h04auW+i6BVFQle2HdC+gNdRznK0qOq+RdnixkWaD8Lc8m7fV2qZeBnFsP7sbYE2+N5n g7Xw== X-Gm-Message-State: ACgBeo3WC7YYJAQIgPMoSzvK9V7hHWTzY7r+uNKx3GM/rtTQdUaCLr// FW6nItiHWci5wkZgmumB2kY0wwCTcjY= X-Google-Smtp-Source: AA6agR6ulyi3zM/eERPPlpaZhfaqceXNg0zRtZHQUQ6DKMie8+E/QIfZRQm0j2cSp6JloIRL9S/EWA== X-Received: by 2002:a17:907:97cd:b0:731:5d0:4434 with SMTP id js13-20020a17090797cd00b0073105d04434mr11854879ejc.603.1660031943480; Tue, 09 Aug 2022 00:59:03 -0700 (PDT) Received: from ?IPV6:2a0b:e7c0:0:107::70f? ([2a0b:e7c0:0:107::70f]) by smtp.gmail.com with ESMTPSA id i25-20020a50fc19000000b0043a85d7d15esm5587792edr.12.2022.08.09.00.59.02 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Tue, 09 Aug 2022 00:59:02 -0700 (PDT) Message-ID: Date: Tue, 9 Aug 2022 09:59:01 +0200 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.1.0 Subject: Re: ext2/zram issue [was: Linux 5.19] Content-Language: en-US From: Jiri Slaby To: Linus Torvalds , Linux Kernel Mailing List Cc: minchan@kernel.org, ngupta@vflare.org, Sergey Senozhatsky , Jan Kara , Ted Ts'o , Andreas Dilger , Ext4 Developers List , avromanov@sberdevices.ru, ddrokosov@sberdevices.ru, ngupta@vflare.org References: <702b3187-14bf-b733-263b-20272f53105d@kernel.org> In-Reply-To: <702b3187-14bf-b733-263b-20272f53105d@kernel.org> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 09. 08. 22, 8:03, Jiri Slaby wrote: > Hi, > > On 31. 07. 22, 23:43, Linus Torvalds wrote: >> So here we are, one week late, and 5.19 is tagged and pushed out. >> >> The full shortlog (just from rc8, obviously not all of 5.19) is below, >> but I can happily report that there is nothing really interesting in >> there. A lot of random small stuff. > > Note: I originally reported this downstream for tracking at: > https://bugzilla.suse.com/show_bug.cgi?id=1202203 > > 5.19 behaves pretty weird in openSUSE's openQA (opposing to 5.18, or > 5.18.15). It's all qemu-kvm "HW"¹⁾: > https://openqa.opensuse.org/tests/2502148 > loop2: detected capacity change from 0 to 72264 > EXT4-fs warning (device zram0): ext4_end_bio:343: I/O error 10 writing > to inode 57375 starting block 137216) > Buffer I/O error on device zram0, logical block 137216 > Buffer I/O error on device zram0, logical block 137217 > ... > SQUASHFS error: xz decompression failed, data probably corrupt > SQUASHFS error: Failed to read block 0x2e41680: -5 > SQUASHFS error: xz decompression failed, data probably corrupt > SQUASHFS error: Failed to read block 0x2e41680: -5 > Bus error > > > > https://openqa.opensuse.org/tests/2502145 > FS-Cache: Loaded > begin 644 ldconfig.core.pid_2094.sig_7.time_1659859442 > > > > https://openqa.opensuse.org/tests/2502146 > FS-Cache: Loaded > begin 644 Xorg.bin.core.pid_3733.sig_6.time_1659858784 > > > > https://openqa.opensuse.org/tests/2502148 > EXT4-fs warning (device zram0): ext4_end_bio:343: I/O error 10 writing > to inode 57375 starting block 137216) > Buffer I/O error on device zram0, logical block 137216 > Buffer I/O error on device zram0, logical block 137217 > > > > https://openqa.opensuse.org/tests/2502154 > [   13.158090][  T634] FS-Cache: Loaded > ... > [  525.627024][    C0] sysrq: Show State > > > > Those are various failures -- crashes of ldconfig, Xorg; I/O failures on > zram; the last one is a lockup likely, something invoked sysrq after > 500s stall. > > Interestingly, I've also hit this twice locally: > > init[1]: segfault at 18 ip 00007fb6154b4c81 sp 00007ffc243ed600 error > 6 in libc.so.6[7fb61543f000+185000] > > Code: 41 5f c3 66 0f 1f 44 00 00 42 f6 44 10 08 01 0f 84 04 01 00 00 > 48 83 e1 fe 48 89 48 08 49 8b 47 70 49 89 5f 70 66 48 0f 6e c0 <48> 89 > 58 18 0f 16 44 24 08 48 81 fd ff 03 00 00 76 08 66 0f ef c9 > > ***  signal 11 *** > > malloc(): unsorted double linked list corrupted > > traps: init[1] general protection fault ip:7fb61543f8b9 > sp:7ffc243ebf40 error:0 in libc.so.6[7fb61543f000+185000] > > Kernel panic - not syncing: Attempted to kill init! exitcode=0x0000000b > > CPU: 0 PID: 1 Comm: init Not tainted 5.19.0-1-default #1 openSUSE > Tumbleweed e1df13166a33f423514290c702e43cfbb2b5b575 > > KASAN is not helpful either, so it's unlikely a memory corruption > (unless it is "HW" related; should I try to turn on IOMMU in qemu?): >> kasan: KernelAddressSanitizer initialized >> ... >> zram: module verification failed: signature and/or required key >> missing - tainting kernel >> zram: Added device: zram0 >> zram0: detected capacity change from 0 to 2097152 >> EXT4-fs (zram0): mounting ext2 file system using the ext4 subsystem >> EXT4-fs (zram0): mounted filesystem without journal. Quota mode: none. >> EXT4-fs warning (device zram0): ext4_end_bio:343: I/O error 10 writing >> to inode 16386 starting block 159744) >> Buffer I/O error on device zram0, logical block 159744 >> Buffer I/O error on device zram0, logical block 159745 > > > > They all occur to me like a zram failure. The installer apparently > creates an ext2 FS and after it mounts it using ext4 module, the issue > starts occurring. > > Any tests I/you could run on 5.19 to exercise zram and ext2? Otherwise I > am unable to reproduce easily, except using the openSUSE installer :/. Ah, now I can. It's easy when one lowers memory available to qemu. -m 800M in this case: echo $((1000*1024*1024)) > /sys/block/zram0/disksize mkfs.ext2 /dev/zram0 mount /dev/zram0 /mnt/a/ dd if=/dev/urandom of=/mnt/a/stuff [ 200.334277][ T8] EXT4-fs warning (device zram0): ext4_end_bio:343: I/O error 10 writing to inode 12 starting block 8192) [ 200.340198][ T8] Buffer I/O error on device zram0, logical block 8192 So currently, I blame: commit e7be8d1dd983156bbdd22c0319b71119a8fbb697 Author: Alexey Romanov Date: Thu May 12 20:23:07 2022 -0700 zram: remove double compression logic /me needs to confirm. > Any other ideas? Or is this known already? > > ¹⁾ main are uefi boot and virtio-blk (it likely happens with virtio-scsi > too). The cmdline _I_ use: qemu-kvm -device intel-hda -device hda-duplex > -drive file=/tmp/pokus.qcow2,if=none,id=hd -device > virtio-blk-pci,drive=hd -drive > if=pflash,format=raw,unit=0,readonly=on,file=/usr/share/qemu/ovmf-x86_64-opensuse-code.bin -drive if=pflash,format=raw,unit=1,file=/tmp/vars.bin -cdrom /tmp/cd1.iso  -m 1G -smp 1 -net user -net nic,model=virtio -serial pty -device virtio-rng-pci -device qemu-xhci,p2=4,p3=4 -usbdevice tablet > > > thanks, -- js suse labs