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 Received: from kanga.kvack.org (kanga.kvack.org [205.233.56.17]) by smtp.lore.kernel.org (Postfix) with ESMTP id 0E1EFC43334 for ; Wed, 8 Jun 2022 08:24:22 +0000 (UTC) Received: by kanga.kvack.org (Postfix) id 6B0948D0013; Wed, 8 Jun 2022 04:24:21 -0400 (EDT) Received: by kanga.kvack.org (Postfix, from userid 40) id 660118D0009; Wed, 8 Jun 2022 04:24:21 -0400 (EDT) X-Delivered-To: int-list-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix, from userid 63042) id 5273F8D0013; Wed, 8 Jun 2022 04:24:21 -0400 (EDT) X-Delivered-To: linux-mm@kvack.org Received: from relay.hostedemail.com (smtprelay0014.hostedemail.com [216.40.44.14]) by kanga.kvack.org (Postfix) with ESMTP id 442978D0009 for ; Wed, 8 Jun 2022 04:24:21 -0400 (EDT) Received: from smtpin31.hostedemail.com (a10.router.float.18 [10.200.18.1]) by unirelay06.hostedemail.com (Postfix) with ESMTP id 1334B3533D for ; Wed, 8 Jun 2022 08:24:21 +0000 (UTC) X-FDA: 79554381522.31.269A6F7 Received: from mail-lj1-f181.google.com (mail-lj1-f181.google.com [209.85.208.181]) by imf01.hostedemail.com (Postfix) with ESMTP id B176A4006F for ; Wed, 8 Jun 2022 08:24:20 +0000 (UTC) Received: by mail-lj1-f181.google.com with SMTP id l18so14568569lje.13 for ; Wed, 08 Jun 2022 01:24:20 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=qn1e9UAfXz5aNABeJOAzysJEyHPbsjfCU7HdITnS84k=; b=Zf/rY8UPfUil7LCo0AmPL0ktcOejRjNbVkLs6BfbQEG0tklgICY+14UzNT7D2l+FDP kd/C58CeMvLCk8v3OokScSeoWleedGL2pCuZ4fpDA/Jq1KQDZNs4yJvNeRq2uK5ohQfv x4JYv71VyLAWcCv/E2Q2Aj30ajf43xjO6xVU0l7ZmWZuCFV8Mab02uK+G5KxWVWLxWab pz3zN5y+pykDMGv075WbOy8vrLxMM7b81TO1CCsC2Cjxlj6PBZkA0QWRSCsNtnZJpAjf OGONEqGxWA91wAD7DPtau1HbAdjZEXl/4fttRzwneXCGvy6jRrNp4vyt+nqKNTR9wue/ xJKA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=qn1e9UAfXz5aNABeJOAzysJEyHPbsjfCU7HdITnS84k=; b=FLzjVrcViUJ+NxNSzXX4crghFDlM/qw2aJPG++wwxJ6VbBVZzkvgkyylxNE4KIAVum tvlNCY/h9C5Remnx+tqTLLUmHUtogkT3cEMLUoHFdWBnDE1Twg/PP7zo92fJFaFrcAi/ 4ERYXe9d0+4/XbsxErE+jss1bMAPnmLeMm/eYOKxD5G3/4H/BZT81QqoRlEYZ1POrw73 WRp6R/aMyw7AyMJIMq6ieiSw31c5WC5f1NZi0lChAn/FQDrmXJxW9PRcRFx7Sxt5oJc3 3/T5v3TErO/eiHMWCFXQJSjXMmjzOQaQRg0bKc1qVTCjSP/AMZRgzh82BIgUQJbt5Mc3 ramA== X-Gm-Message-State: AOAM532J5MrKZ3AdtPCLBnMcLf7FtLxO2cKefxsyhk8h2r4jwGCkh3W4 nBGGlq9Rk7q5+Eyaq+h44CFoZ4gKLPkP+7ry8xCZbQ== X-Google-Smtp-Source: ABdhPJwud0+3E/Q29u9oy+kzSCNdY14guBqBmA0Hqpt4c+PmhIEHReOxdmFrIBDqbHdvMdQZbHcRxllXIDLHtj3hagQ= X-Received: by 2002:a2e:bf14:0:b0:255:b789:576b with SMTP id c20-20020a2ebf14000000b00255b789576bmr3093006ljr.47.1654676659002; Wed, 08 Jun 2022 01:24:19 -0700 (PDT) MIME-Version: 1.0 References: <000000000000bb7f1c05da29b601@google.com> <00000000000010b7d305e08837c8@google.com> <20220606123839.GW2146@kadam> In-Reply-To: From: Dmitry Vyukov Date: Wed, 8 Jun 2022 10:24:07 +0200 Message-ID: Subject: Re: [syzbot] general protection fault in __device_attach To: Matthew Wilcox Cc: Dan Carpenter , Greg KH , Alan Stern , Andy Shevchenko , syzbot , hdanton@sina.com, lenb@kernel.org, linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org, rafael.j.wysocki@intel.com, rafael@kernel.org, rjw@rjwysocki.net, syzkaller-bugs@googlegroups.com, linux-usb@vger.kernel.org, Linux-MM Content-Type: text/plain; charset="UTF-8" X-Stat-Signature: wx8og7q9wih1agm13rdxz9miq6z6fps9 Authentication-Results: imf01.hostedemail.com; dkim=pass header.d=google.com header.s=20210112 header.b="Zf/rY8UP"; dmarc=pass (policy=reject) header.from=google.com; spf=pass (imf01.hostedemail.com: domain of dvyukov@google.com designates 209.85.208.181 as permitted sender) smtp.mailfrom=dvyukov@google.com X-Rspam-User: X-Rspamd-Server: rspam11 X-Rspamd-Queue-Id: B176A4006F X-HE-Tag: 1654676660-731876 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 Wed, 8 Jun 2022 at 10:20, Dmitry Vyukov wrote: > > On Tue, Jun 07, 2022 at 09:15:09AM +0200, Dmitry Vyukov wrote: > > > On Mon, 6 Jun 2022 at 14:39, Dan Carpenter wrote: > > > > > > > > On Sat, Jun 04, 2022 at 10:32:46AM +0200, 'Dmitry Vyukov' via syzkaller-bugs wrote: > > > > > On Fri, 3 Jun 2022 at 18:12, Greg KH wrote: > > > > > > > > > > > > But again, is this a "real and able to be triggered from userspace" > > > > > > problem, or just fault-injection-induced? > > > > > > > > > > Then this is something to fix in the fault injection subsystem. > > > > > Testing systems shouldn't be reporting false positives. > > > > > What allocations cannot fail in real life? Is it <=page_size? > > > > > > > > > > > > > Apparently in 2014, anything less than *EIGHT?!!* pages succeeded! > > > > > > > > https://lwn.net/Articles/627419/ > > > > > > > > I have been on the look out since that article and never seen anyone > > > > mention it changing. I think we should ignore that and say that > > > > anything over PAGE_SIZE can fail. Possibly we could go smaller than > > > > PAGE_SIZE... > > > > > > +linux-mm for GFP expertise re what allocations cannot possibly fail > > > and should be excluded from fault injection. > > > > > > Interesting, thanks for the link. > > > > > > PAGE_SIZE looks like a good start. Once we have the predicate in > > > place, we can refine it later when/if we have more inputs. > > > > > > But I wonder about GFP flags. They definitely have some impact on allocations. > > > If GFP_ACCOUNT is set, all allocations can fail, right? > > > If GFP_DMA/DMA32 is set, allocations can fail, right? What about other zones? > > > If GFP_NORETRY is set, allocations can fail? > > > What about GFP_NOMEMALLOC and GFP_ATOMIC? > > > What about GFP_IO/GFP_FS/GFP_DIRECT_RECLAIM/GFP_KSWAPD_RECLAIM? At > > > least some of these need to be set for allocations to not fail? Which > > > ones? > > > Any other flags are required to be set/unset for allocations to not fail? > > > > I'm not the expert on page allocation, but ... > > > > I don't think GFP_ACCOUNT makes allocations fail. It might make reclaim > > happen from within that cgroup, and it might cause an OOM kill for > > something in that cgroup. But I don't think it makes a (low order) > > allocation more likely to fail. > > Interesting. > I was thinking of some malicious specifically crafted configurations > with very low limit and particular pattern of allocations. Also what > if there is just 1 process (current)? Is it possible to kill and > reclaim the current process when a thread is stuck in the middle of > the kernel on a kmalloc? > Also I see e.g.: > Tasks with the OOM protection (oom_score_adj set to -1000) > are treated as an exception and are never killed. > > I am not an expert on this either, but I think it may be hard to fight > with a specifically crafted attack. > > > > There's usually less memory avilable in DMA/DMA32 zones, but we have > > so few allocations from those zones, I question the utility of focusing > > testing on those allocations. > > > > GFP_ATOMIC allows access to emergency pools, so I would say _less_ likely > > to fail. KSWAPD_RECLAIM has no effect on whether _this_ allocation > > succeeds or fails; it kicks kswapd to do reclaim, rather than doing > > reclaim directly. DIRECT_RECLAIM definitely makes allocations more likely > > to succeed. GFP_FS allows (direct) reclaim to happen from filesystems. > > GFP_IO allows IO to start (ie writeback can start) in order to clean > > dirty memory. > > > > Anyway, I hope somebody who knows the page allocator better than I do > > can say smarter things than this. Even better if they can put it into > > Documentation/ somewhere ;-) > > Even better to put this into code as a predicate function that fault > injection will use. It will also serve as precise up-to-date > documentation. Also at the end of kmalloc as: WARN_ON(!ret && !cant_fail(size, gfp)); ! > > https://www.kernel.org/doc/html/latest/core-api/memory-allocation.html > > exists but isn't quite enough to answer this question.