Received: by 2002:ac0:946b:0:0:0:0:0 with SMTP id j40csp3537656imj; Tue, 19 Feb 2019 05:21:09 -0800 (PST) X-Google-Smtp-Source: AHgI3IZ8kYOk568L9dOBmn/da8nRiJWMXtrMDvvUQMmiZqXVzrFLk9XHgbMdnr7mqIfDl0DPZsFc X-Received: by 2002:a63:d301:: with SMTP id b1mr24091418pgg.61.1550582468941; Tue, 19 Feb 2019 05:21:08 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1550582468; cv=none; d=google.com; s=arc-20160816; b=fbSZPep7R2VVIyieAeY2VjxhXaXhbag8SjGTkNgyMFPr1BpV6b3GM+l2E8AiGa8nyJ smFnt9YGWK0RcGR+51TzfRpjL+AWD2FEEMFV+kbz9/Kx0wFcfL3p7JerO/MPhz8Ab07r qO7LRqif7R90mnWjmd4GK1uk00UlY/0VGY8QR+aWWwD67EX9fNIIUlN4YDIIlqtNcBvm 2imbu4P/AzycZ2ZAEywlbz/khzRNezKjnCX/E7XH2U0GpiN9VeKcp19RASj8qUk+G+tP EuPyqGm9fMatKkwMVRMkpeVacfuZCZEFXD5HS0S6vfIAvvlbcAAuC+fJeKzUMzOm0lTB TS+A== 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:message-id:subject:cc :to:from:date; bh=ZYZTnLbrqeA+bu8RZJkEStbaDCiakaQZ8WxxYegUySQ=; b=oZ6d0Zj/cj1MJ/QSlRVQtRX++5zRaMr5jm9Tpn6j5Q1WjRyXtFcXLjRoeuVV28qWVW LnIZpPIcJq2i3OsnAQOkTgqw+bthxHCGUJEEvlvYJq9zsNLur+3iG2DXkuRKS0TeieEv 41pD/1VizrDnaYuWZ9vK9tNUOiFL+fqjTMJGK4ccbo9St8yfkMorQ3696cqJAXu+P/tp JzKs9jANBbAvKWwfvrG1XyMbJCSPdWP5ft3I1hyNS9o5mB9WtVvt1UBqoHNAcfrN8IbZ 7aITCpO/27cRhdMuLE8wuBByTS3lQnZFG6nRMTOKG/miahnD1lKy9/Dou9Ct12pAqD/t aLOQ== 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 o188si8066936pfb.66.2019.02.19.05.20.54; Tue, 19 Feb 2019 05:21:08 -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 S1728722AbfBSNUa (ORCPT + 99 others); Tue, 19 Feb 2019 08:20:30 -0500 Received: from mx2.suse.de ([195.135.220.15]:52726 "EHLO mx1.suse.de" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1726426AbfBSNU2 (ORCPT ); Tue, 19 Feb 2019 08:20:28 -0500 X-Virus-Scanned: by amavisd-new at test-mx.suse.de Received: from relay2.suse.de (unknown [195.135.220.254]) by mx1.suse.de (Postfix) with ESMTP id 0C408AC8A; Tue, 19 Feb 2019 13:20:27 +0000 (UTC) Received: by quack2.suse.cz (Postfix, from userid 1000) id 3583A1E1570; Tue, 19 Feb 2019 14:20:26 +0100 (CET) Date: Tue, 19 Feb 2019 14:20:26 +0100 From: Jan Kara To: Meelis Roos Cc: Jan Kara , "Theodore Y. Ts'o" , linux-alpha@vger.kernel.org, LKML , linux-block@vger.kernel.org, linux-mm@kvack.org Subject: Re: ext4 corruption on alpha with 4.20.0-09062-gd8372ba8ce28 Message-ID: <20190219132026.GA28293@quack2.suse.cz> References: <1c26eab4-3277-9066-5dce-6734ca9abb96@linux.ee> <076b8b72-fab0-ea98-f32f-f48949585f9d@linux.ee> <20190216174536.GC23000@mit.edu> <20190218120209.GC20919@quack2.suse.cz> <4e015688-8633-d1a0-308b-ba2a78600544@linux.ee> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4e015688-8633-d1a0-308b-ba2a78600544@linux.ee> User-Agent: Mutt/1.10.1 (2018-07-13) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue 19-02-19 14:17:09, Meelis Roos wrote: > > > > > The result of the bisection is > > > > > [88dbcbb3a4847f5e6dfeae952d3105497700c128] blkdev: avoid migration stalls for blkdev pages > > > > > > > > > > Is that result relevant for the problem or should I continue bisecting between 4.20.0 and the so far first bad commit? > > > > > > > > Can you try reverting the commit and see if it makes the problem go away? > > > > > > Tried reverting it on top of 5.0.0-rc6-00153-g5ded5871030e and it seems > > > to make the kernel work - emerge --sync succeeded. > There is more to it. > > After running 5.0.0-rc6-00153-g5ded5871030e-dirty (with the revert of > that patch) successfully for Gentoo update, I upgraded the kernel to > 5.0.0-rc7-00011-gb5372fe5dc84-dirty (todays git + revert of this patch) > and it broke on rsync again: > > RepoStorageException: command exited with status -6: rsync -a --link-dest /usr/portage --exclude=/distfiles --exclude=/local --exclude=/lost+found --exclude=/packages --exclude /.tmp-unverified-download-quarantine /usr/portage/ /usr/portage/.tmp-unverified-download-quarantine/ > > Nothing in dmesg. > > This means the real root reason is somewhere deeper and reverting this > commit just made it less likely to happen. Thanks for information. Yeah, that makes somewhat more sense. Can you ever see the failure if you disable CONFIG_TRANSPARENT_HUGEPAGE? Because your findings still seem to indicate that there' some problem with page migration and Alpha (added MM list to CC). Honza -- Jan Kara SUSE Labs, CR