Received: by 2002:ad5:474a:0:0:0:0:0 with SMTP id i10csp1730942imu; Sat, 10 Nov 2018 00:07:38 -0800 (PST) X-Google-Smtp-Source: AJdET5dLZXzcrlUh0ka5a/Xhp7xMIdRAGYe+qgVs2dzvHIyfs2r7ZqGIbvMQTbLPafBwpRg4KSxh X-Received: by 2002:a62:b9b:: with SMTP id 27-v6mr8864435pfl.235.1541837258461; Sat, 10 Nov 2018 00:07:38 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1541837258; cv=none; d=google.com; s=arc-20160816; b=HQJPmU/2Vo5nm3ZijV0zVbCirqq/YOvRAF9z6toPvAF3QMd0Vco5dCqVX0upRZ0JdU SvRRkpS+8v9fzxfbQZiue+iU4mUkzUw3pQ87PV+ne8pDeRecNZEviLtAt7TfzWtukUKw u3eP2urJH0/pZGuHhNKeOMf5doqJNYkLLSQygO2qBZpIkAd6enHT3zQVkOv2+LZHbvE9 Be9QFi9qiMrj9L5mU9XVcZbwQPbJU8uiB6hMskVUl8KUKsyAByFHqpEwHR9BkZcprX34 xQBQ+CUDg8at/afmJ5ZxxTYgjfMIFTK4qGiLQ1djgbMUxyIUBkhcmo5L3Qijd8Qs9jOY DZEQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:content-disposition :mime-version:message-id:subject:cc:to:from:date; bh=3IvzjdhvJD/R+Q4EpOcSBbnrUuFI6NILPvZoxUjwlB4=; b=qpP8tG2UVePHone2nXpswIRsE2JJlzM90LOnMv5fW9ATSRpwh8yFnlxvwe+9KkBAVV 5u2t5pPQntFK+B+RIRuXj+vphYmmlzPv+UbwIDL/hjipsN7Un57vbcwV4eSsp5QObxel x0F53rPZN7CDkVD8pJ1+bZx1ZhZk76PGQ31epCUW8XMT30gcqmFVTNBUwMgl9jFvhIb+ y+6o1zPUsSu9W7IMk9KyFhuOFt/aOapWEQTe7IYPlhavKOZwa+zhMEZ1kLnUOundL0S1 +x3XsAnGrHxsC0Hz2Ui9IIEWCVjoiYFEYOJFDHOi/8FFtrqJrksI8cZCb/ISaw9myq3v nXQg== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id 30-v6si11073787pla.56.2018.11.10.00.07.09; Sat, 10 Nov 2018 00:07:38 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728949AbeKJRum (ORCPT + 99 others); Sat, 10 Nov 2018 12:50:42 -0500 Received: from shells.gnugeneration.com ([66.240.222.126]:54086 "EHLO shells.gnugeneration.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1728659AbeKJRum (ORCPT ); Sat, 10 Nov 2018 12:50:42 -0500 Received: by shells.gnugeneration.com (Postfix, from userid 1000) id 186061A402A4; Sat, 10 Nov 2018 00:06:36 -0800 (PST) Date: Sat, 10 Nov 2018 00:06:35 -0800 From: Vito Caputo To: linux-kernel Cc: ming.lei@redhat.com, snitzer@redhat.com, hch@lst.de, xni@redhat.com, mariusz.dabrowski@intel.com, axboe@kernel.dk Subject: Does the discard bug introduced in 4.19 by 744889b7cbb56a6 and fixed by 1adfc5e4136f5967 have potential for fstrim-caused corruption? Message-ID: <20181110080635.wvlg6o34vtgndshw@shells.gnugeneration.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: NeoMutt/20170113 (1.7.2) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org I ask because I recently performed some fstrims on my 4.19-running laptop after a good house cleaning, and things started going rather haywire today at the filesystem level, on different filesystems of differing types (ext2 and ext4) but sharing the same underlying lvm pv+dmcrypt on an SSD. At the time I needed to get work done and couldn't investigate. So I crossed my fingers and rebooted back into 4.18, let some ugly fscks complete, and carried on like nothing happened. This all seems to be a software bug, not a genuine SSD failure of any sort. My filesystems are now all in a questionable state, though the machine seems usable enough for the moment while I prepare for rebuilding. Should I assume this was all caused by the fstrims and 744889b7cbb56a6? Or does it not explain how this happened and we may have a different problem on our hands? I had been running 4.19-rc[178], but am uncertain if I performed fstrims in any of those, I definitely did in 4.18 though and had no trouble. 744889b7cbb56a6 is especially suspect to me as it was in none of the 4.19 RCs but for some reason landed in 4.19 to fix a22c4d7e34402ccdf3, even though a22c4d7e34402ccdf3 has been there since 4.3, that's left a bad taste in my mouth but maybe I'm missing something. Thanks, Vito Caputo