Received: by 2002:a25:ab43:0:0:0:0:0 with SMTP id u61csp5023141ybi; Tue, 28 May 2019 06:23:55 -0700 (PDT) X-Google-Smtp-Source: APXvYqyGYx2gwSITX4/lSrc4Ng9dn9eWE4XCtiUNPkm3hJkEZbznzytZLko9xvrHJoWQn0/zvrzq X-Received: by 2002:a17:90a:d3d7:: with SMTP id d23mr5762538pjw.26.1559049835219; Tue, 28 May 2019 06:23:55 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1559049835; cv=none; d=google.com; s=arc-20160816; b=akteLPyaeyB45o1VwF7/3/cNhGwkIuoTRjgGK5Z87S5Hl3kbiaSPvUJbV0jXGXqs35 mncLa4CbY/5lFFm/sICwf5Bn4TRIZGyLH417c3IXA21sCNHPL6HvJi7RZqIZ/9HX5/Ti g0Y71JaIgH3DDH7Mh6JuEiKGt+3/aEJLIASxnMX5brjliqrPKtyWUh3ejX/088yJSQxu GaMzLhJ5oL3VVg4ZGpmFMf2DqkJmW8NaFFhSSVHkdm7qMObe5j634+a1m0rRAPE+GsB4 EtkWLdVxETQw1QDRsjx2omFB/aAZ3OkMFVC9yuxFZj+ZX8M9M8cGs5i+iUsyy1Q08Vls S9Aw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:mail-followup-to :message-id:subject:cc:to:from:date; bh=KLjhESj//PGinmickgmzjUM3HxTn4o1R1a7BLCwBaSk=; b=Yt+4yYjn7YZFweGSRZm0WMDjbDSK80qevYurOD0YuuZk/N9CuOciolv4qQbNlm3Ab/ hOtoWsm5R4oUef42oG8ZFe+vlGWd7kj7KutpQDw6gHunELc6iH6zwsCbYedI3covBg5d eaCk2aYzlH8RS80zmc3Qcz9HXV9+SpzgQij7xDj+A7NzHuOxl7hUxJuM6kX6fFQM2DCu rzPAcm6xVfmi3lKD4Y9uf5Tm6nAp2BC5Vs1CS6ns/dVH6UlSDzK6zYHX59bKgRx0ukcM G2arSTvzGtOV5rKB60uudhRDbbN4AJQC60Fx37FB1ZhKi9jpSAJWzavVWVUcN9OY6bFf mI/w== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-ext4-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-ext4-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 b7si24297224pgk.553.2019.05.28.06.23.37; Tue, 28 May 2019 06:23:55 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-ext4-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-ext4-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-ext4-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727039AbfE1NXd (ORCPT + 99 others); Tue, 28 May 2019 09:23:33 -0400 Received: from outgoing-auth-1.mit.edu ([18.9.28.11]:49784 "EHLO outgoing.mit.edu" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1726924AbfE1NXd (ORCPT ); Tue, 28 May 2019 09:23:33 -0400 Received: from callcc.thunk.org ([66.31.38.53]) (authenticated bits=0) (User authenticated as tytso@ATHENA.MIT.EDU) by outgoing.mit.edu (8.14.7/8.12.4) with ESMTP id x4SDNRUl004130 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Tue, 28 May 2019 09:23:28 -0400 Received: by callcc.thunk.org (Postfix, from userid 15806) id 8A8C1420481; Tue, 28 May 2019 09:23:27 -0400 (EDT) Date: Tue, 28 May 2019 09:23:27 -0400 From: "Theodore Ts'o" To: Mikhail Gavrilov Cc: Linux List Kernel Mailing , linux-ext4@vger.kernel.org Subject: Re: [bugreport] kernel 5.2 pblk bad header/extent: invalid extent entries Message-ID: <20190528132327.GC19149@mit.edu> Mail-Followup-To: Theodore Ts'o , Mikhail Gavrilov , Linux List Kernel Mailing , linux-ext4@vger.kernel.org References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.10.1 (2018-07-13) Sender: linux-ext4-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-ext4@vger.kernel.org On Tue, May 28, 2019 at 10:58:03AM +0500, Mikhail Gavrilov wrote: > On Mon, 27 May 2019 at 21:16, Mikhail Gavrilov > wrote: > > > > I am bisected issue. I hope it help understand what is happened on my computer. > > > > Why no one answers? > Even if the problem is known and already fixed, I would be nice to > know that I spent 10 days for searching a problem commit not in vain > and someone reads my messages. Sorry, I didn't see your earlier messages; I'm not sure why. In any case, yes, it's a known issue, and it's fixed in 5.2-rc2. This fix was commit 0a944e8a6c66. - Ted