Received: by 2002:a05:6a10:8c0a:0:0:0:0 with SMTP id go10csp2091543pxb; Thu, 11 Feb 2021 04:15:44 -0800 (PST) X-Google-Smtp-Source: ABdhPJy4CrNymJGq5mqXJacSkjLyvaUDd5/vliKb+QeLAVWfuEe2ZFPawSheS3Z70sMSF+hKQhAd X-Received: by 2002:a17:906:9a06:: with SMTP id ai6mr8202934ejc.463.1613045744010; Thu, 11 Feb 2021 04:15:44 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1613045744; cv=none; d=google.com; s=arc-20160816; b=ClQbURBbVbzYRNgjl/hcVXOZwMrl4AiSBLhKCnvi4taiXLTGlLUK+2/0Jwp0iZWapz R95qyYn8n738uDpmbfF+/BR8o5cyVUUcXC8gwiD7OvIsuqIw7KJYI2XuR1UzUWGV5UT+ YWShK9pNq0rq+w8dBZ+LbKlHQGKDG9/E2+CqrrLiRV1rXbOymp8K5TfdkamXIruluiXU GCg6ZK5Gd22dw9P9qLsQwZSeHhLFnkpie+Kuc/6HGpwkwIAT+4xdIE4QG9WizF/J8mtg AMrFNIEzUzOtmlTl4VDfR+b6BRhqk46MS5blCf2kozDvB9xM80t2QHyAMVH1Z4Op/S1H n+FQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:user-agent:in-reply-to:content-disposition :mime-version:references:message-id:subject:cc:to:from:date; bh=3Na9AF9126HHANmNWj8jrTf7AmpICAsi2ifIs6gjJQ0=; b=w2uQiQdbabia4OhEAOzdDV9xC85P5s0a7jWIROb711us8ls9d+r22jyqXIO3lQY1Cc Cz2he/f88DTNAPOCoApDz1n+KPwpNmkVbw/bUbbWoLPzaaQ8WO2vzwgCKKxJspXrHcCp 8vxqj/+mPEe0geyBZwTLTVJZ1zFp3MHqXmXgr8vEuifHpM10pRTnAQIPnDdyouqrS9g6 91ChbvF+o+xOzj8qICmObI+vG8JSng4D7P89sDDA287XQepRdsQOZ3+w98K4uvf8JUB5 +fKmnAgFOssNtLEMPXAroYw5/nxRFjFGUuC1I3gAKNMkoa5VBWWJpQganGrh7rev1FzW AAmg== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-ext4-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-ext4-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id z9si3938646edb.204.2021.02.11.04.15.19; Thu, 11 Feb 2021 04:15:43 -0800 (PST) Received-SPF: pass (google.com: domain of linux-ext4-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-ext4-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-ext4-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S230011AbhBKMOr (ORCPT + 99 others); Thu, 11 Feb 2021 07:14:47 -0500 Received: from mx2.suse.de ([195.135.220.15]:34764 "EHLO mx2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S230436AbhBKMMo (ORCPT ); Thu, 11 Feb 2021 07:12:44 -0500 X-Virus-Scanned: by amavisd-new at test-mx.suse.de Received: from relay2.suse.de (unknown [195.135.221.27]) by mx2.suse.de (Postfix) with ESMTP id 80C01ACD4; Thu, 11 Feb 2021 12:12:02 +0000 (UTC) Received: by quack2.suse.cz (Postfix, from userid 1000) id 1B4BA1E14B2; Thu, 11 Feb 2021 13:12:02 +0100 (CET) Date: Thu, 11 Feb 2021 13:12:02 +0100 From: Jan Kara To: Hillf Danton Cc: Jan Kara , syzbot , "linux-ext4@vger.kernel.org" , "linux-kernel@vger.kernel.org" , "syzkaller-bugs@googlegroups.com" , Tahsin Erdogan Subject: Re: possible deadlock in fs_reclaim_acquire (2) Message-ID: <20210211121202.GP19070@quack2.suse.cz> References: <00000000000086723c05bb056425@google.com> <20210211040729.12804-1-hdanton@sina.com> <20210211102225.GK19070@quack2.suse.cz> <20210211120424.86857A3B85@relay2.suse.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20210211120424.86857A3B85@relay2.suse.de> User-Agent: Mutt/1.10.1 (2018-07-13) Precedence: bulk List-ID: X-Mailing-List: linux-ext4@vger.kernel.org On Thu 11-02-21 20:04:14, Hillf Danton wrote: > On Thu 11-02-21 12:07:29, Jan Kara wrote: > >> Fix 71b565ceff37 ("ext4: drop ext4_kvmalloc()") by restoring the > >> GFP_NOFS introduced in dec214d00e0d ("ext4: xattr inode deduplication"). > >> > >> Note this may be the fix also to possible deadlock > >> Reported-by: syzbot+bfdded10ab7dcd7507ae@syzkaller.appspotmail.com > >> https://lore.kernel.org/linux-ext4/000000000000563a0205bafb7970@google.com/ > > > >Please no. Ext4 is using scoping API to limit allocations to GFP_NOFS > >inside transactions. In this case something didn't work which seems like a > >lockdep bug at the first sight but I'll talk to mm guys about it. > >Definitely to problem doesn't seem to be in ext4. > > Feel free to elaborate why we can find ext4 in the report? > Why is ext4 special in this case? Please read my reply to the syzbot report [1]. It has all the details. [1] https://lore.kernel.org/lkml/20210211104947.GL19070@quack2.suse.cz Honza -- Jan Kara SUSE Labs, CR