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 X-Spam-Level: X-Spam-Status: No, score=-5.8 required=3.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI, SPF_HELO_NONE,SPF_PASS autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 117EDC433E0 for ; Thu, 11 Feb 2021 16:41:21 +0000 (UTC) Received: from kanga.kvack.org (kanga.kvack.org [205.233.56.17]) by mail.kernel.org (Postfix) with ESMTP id BE18564DD7 for ; Thu, 11 Feb 2021 16:41:20 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org BE18564DD7 Authentication-Results: mail.kernel.org; dmarc=fail (p=quarantine dis=none) header.from=suse.com Authentication-Results: mail.kernel.org; spf=pass smtp.mailfrom=owner-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix) id 28B816B0127; Thu, 11 Feb 2021 11:41:20 -0500 (EST) Received: by kanga.kvack.org (Postfix, from userid 40) id 23AC86B0128; Thu, 11 Feb 2021 11:41:20 -0500 (EST) X-Delivered-To: int-list-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix, from userid 63042) id 1032D6B0129; Thu, 11 Feb 2021 11:41:20 -0500 (EST) X-Delivered-To: linux-mm@kvack.org Received: from forelay.hostedemail.com (smtprelay0161.hostedemail.com [216.40.44.161]) by kanga.kvack.org (Postfix) with ESMTP id EEA856B0127 for ; Thu, 11 Feb 2021 11:41:19 -0500 (EST) Received: from smtpin18.hostedemail.com (10.5.19.251.rfc1918.com [10.5.19.251]) by forelay05.hostedemail.com (Postfix) with ESMTP id BCF51181AEF10 for ; Thu, 11 Feb 2021 16:41:19 +0000 (UTC) X-FDA: 77806552278.18.E118528 Received: from mx2.suse.de (mx2.suse.de [195.135.220.15]) by imf01.hostedemail.com (Postfix) with ESMTP id 097862000D8C for ; Thu, 11 Feb 2021 16:41:18 +0000 (UTC) X-Virus-Scanned: by amavisd-new at test-mx.suse.de DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=suse.com; s=susede1; t=1613061677; h=from:from:reply-to:date:date:message-id:message-id:to:to:cc:cc: mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=49277//KwxbjQ405XwayXDeBcBaVqNsLWaTMf3MliEo=; b=YV5YY0wNG1juqlUn4dbLg5e38JEvoh38LhXzPWw7qoeQqD4eW6kYuna41RTqh46JN+/Mry 5awcoW5BM4BtWa4GjbgXfx6pzlWQm1G/96w08Tmo16oMjOTkVb74Y8m4+5necwrZ+bpTJk JUcMDs3qmoMDTdlggXe5mSkmOda7ZSY= Received: from relay2.suse.de (unknown [195.135.221.27]) by mx2.suse.de (Postfix) with ESMTP id C4B87AC43; Thu, 11 Feb 2021 16:41:17 +0000 (UTC) Date: Thu, 11 Feb 2021 17:41:16 +0100 From: Michal Hocko To: Matthew Wilcox Cc: Jan Kara , Dmitry Vyukov , syzbot , Jan Kara , linux-ext4@vger.kernel.org, LKML , syzkaller-bugs , Theodore Ts'o , Linux-MM Subject: Re: possible deadlock in start_this_handle (2) Message-ID: References: <20210211104947.GL19070@quack2.suse.cz> <20210211121020.GO19070@quack2.suse.cz> <20210211125717.GH308988@casper.infradead.org> <20210211132533.GI308988@casper.infradead.org> <20210211142630.GK308988@casper.infradead.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20210211142630.GK308988@casper.infradead.org> X-Stat-Signature: phgu5tf6ba9eszwtfswmz9sdpm6d76jj X-Rspamd-Server: rspam02 X-Rspamd-Queue-Id: 097862000D8C Received-SPF: none (suse.com>: No applicable sender policy available) receiver=imf01; identity=mailfrom; envelope-from=""; helo=mx2.suse.de; client-ip=195.135.220.15 X-HE-DKIM-Result: pass/pass X-HE-Tag: 1613061678-835973 X-Bogosity: Ham, tests=bogofilter, spamicity=0.000000, version=1.2.4 Sender: owner-linux-mm@kvack.org Precedence: bulk X-Loop: owner-majordomo@kvack.org List-ID: On Thu 11-02-21 14:26:30, Matthew Wilcox wrote: > On Thu, Feb 11, 2021 at 03:20:41PM +0100, Michal Hocko wrote: > > On Thu 11-02-21 13:25:33, Matthew Wilcox wrote: > > > On Thu, Feb 11, 2021 at 02:07:03PM +0100, Michal Hocko wrote: > > > > On Thu 11-02-21 12:57:17, Matthew Wilcox wrote: > > > > > > current->flags should be always manipulated from the user context. But > > > > > > who knows maybe there is a bug and some interrupt handler is calling it. > > > > > > This should be easy to catch no? > > > > > > > > > > Why would it matter if it were? > > > > > > > > I was thinking about a clobbered state because updates to ->flags are > > > > not atomic because this shouldn't ever be updated concurrently. So maybe > > > > a racing interrupt could corrupt the flags state? > > > > > > I don't think that's possible. Same-CPU races between interrupt and > > > process context are simpler because the CPU always observes its own writes > > > in order and the interrupt handler completes "between" two instructions. > > > > I have to confess I haven't really thought the scenario through. My idea > > was to simply add a simple check for an irq context into ->flags setting > > routine because this should never be done in the first place. Not only > > for scope gfp flags but any other PF_ flags IIRC. > > That's not automatically clear to me. There are plenty of places > where an interrupt borrows the context of the task that it happens to > have interrupted. Specifically, interrupts should be using GFP_ATOMIC > anyway, so this doesn't really make a lot of sense, but I don't think > it's necessarily wrong for an interrupt to call a function that says > "Definitely don't make GFP_FS allocations between these two points". Not sure I got your point. IRQ context never does reclaim so anything outside of NOWAIT/ATOMIC is pointless. But you might be refering to a future code where GFP_FS might have a meaning outside of the reclaim context? Anyway if we are to allow modifying PF_ flags from an interrupt contenxt then I believe we should make that code IRQ aware at least. I do not feel really comfortable about async modifications when this is stated to be safe doing in a non atomic way. But I suspect we have drifted away from the original issue. I thought that a simple check would help us narrow down this particular case and somebody messing up from the IRQ context didn't sound like a completely off. -- Michal Hocko SUSE Labs