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 A3642C4332F for ; Tue, 29 Nov 2022 04:38:43 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S235302AbiK2Eim (ORCPT ); Mon, 28 Nov 2022 23:38:42 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:58950 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S234820AbiK2Eii (ORCPT ); Mon, 28 Nov 2022 23:38:38 -0500 Received: from mail-pj1-x102e.google.com (mail-pj1-x102e.google.com [IPv6:2607:f8b0:4864:20::102e]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 27CE629C88 for ; Mon, 28 Nov 2022 20:38:37 -0800 (PST) Received: by mail-pj1-x102e.google.com with SMTP id hd14-20020a17090b458e00b0021909875bccso311297pjb.1 for ; Mon, 28 Nov 2022 20:38:37 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=chromium.org; s=google; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:cc:to:from:date:from:to:cc:subject:date:message-id:reply-to; bh=48Xm3VfV4sx0+bUZmYTNZIpSa0XzNl3vvIQW42o7jJQ=; b=T5LUfnFRWiWAdf7zeRpoyRCNSY164AYnoRT7heMBmwvQh/rkonGTMP2fDaxZ3cb3zq WgnsezEnwq9KAb5FRfzcc5muJkJxXkVwjBgn2+VHTj+wotmFhoJq5rNh+hOLZk0LZ3g/ Ozt9Ev52HQoPAwOc9bKAd0REmzrYFGjcYLOh4= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:cc:to:from:date:x-gm-message-state:from:to:cc:subject:date :message-id:reply-to; bh=48Xm3VfV4sx0+bUZmYTNZIpSa0XzNl3vvIQW42o7jJQ=; b=2nbxR2MC5eOSxLeyRdTOrAd4ZsWhexmUcQlNtcaNLVayZwsqNV/DVAA5wb+P26BY5J t85NqVgvSmeubws7AJ6O5MOtxnGXnbfGCpNB3RKfNpzzlyZcX5eUe0ldiMtn9vsJWcgr DYh4c5XQ8LuLkP29vj8/0tNlQTmU7VOjpWYzFl0Jhott3yakLgT+XwlQiWiioNbf0cbn AXw9QKhbub5P2EpUrFUpgrCog3LFk/dS258W/Kl1mLnQU++D1aHtNNxKWl3CvHYo3ovA x8ydbayCGxaBCOO75pYVOZKMkHSzaXbKvLAt3x2Qgkla63AhZfttEyFb+TRkitVOYHJy VGFQ== X-Gm-Message-State: ANoB5pnR9/v7QfFqv62A6DNPnKnzNQWw/IM6BO086KTwZ7sXkyG3sNT+ oybRQTgyJo777MKCQ07qmIPWP58DTzKF+A== X-Google-Smtp-Source: AA0mqf5c3WV2DuftkVuXZ0Ps8inmw7FchDxrXziCDRwmtaUhnUDq6si8XtaqqqnfHmFIrk0qg4O0fg== X-Received: by 2002:a17:90a:fb86:b0:219:26b5:d41e with SMTP id cp6-20020a17090afb8600b0021926b5d41emr12318785pjb.20.1669696716694; Mon, 28 Nov 2022 20:38:36 -0800 (PST) Received: from google.com ([240f:75:7537:3187:2565:b2f5:cacd:a5d9]) by smtp.gmail.com with ESMTPSA id o42-20020a17090a0a2d00b00219133d0f4esm321809pjo.9.2022.11.28.20.38.33 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Mon, 28 Nov 2022 20:38:36 -0800 (PST) Date: Tue, 29 Nov 2022 13:38:30 +0900 From: Sergey Senozhatsky To: Petr Vorel Cc: Martin Doucha , Sergey Senozhatsky , Minchan Kim , ltp@lists.linux.it, linux-block@vger.kernel.org, linux-kernel@vger.kernel.org, linux-kselftest@vger.kernel.org, Nitin Gupta , Jens Axboe , OGAWA Hirofumi , Yang Xu Subject: Re: [PATCH 0/1] Possible bug in zram on ppc64le on vfat Message-ID: References: <20221107191136.18048-1-pvorel@suse.cz> <3ac740c0-954b-5e68-b413-0adc7bc5a2b5@suse.cz> <9489dd1c-012c-8b5d-b670-a27213da287a@suse.cz> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On (22/11/22 16:07), Petr Vorel wrote: > > On 11. 11. 22 1:48, Sergey Senozhatsky wrote: > > > On (22/11/10 15:29), Martin Doucha wrote: [..] > > > Can you try using /dev/urandom for dd, not /dev/zero? > > > Do you still see zeroes in sysfs output or some random values? > > > After 50 test runs on a kernel where the issue is confirmed, I could not > > reproduce the failure while filling the device from /dev/urandom instead of > > /dev/zero. The test reported compression ratio around 1.8-2.5 which means > > the memory usage reported by mm_stat was 10-13MB. > > Martin, thanks a lot for reruning tests. I wonder problems on /dev/zero is a > kernel bug or just problem which should be workarounded. Hmm. Does CONFIG_KASAN show anything interesting?