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 vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id B6A80C77B7F for ; Wed, 3 May 2023 15:24:36 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S230318AbjECPYf (ORCPT ); Wed, 3 May 2023 11:24:35 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:50314 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S230294AbjECPYe (ORCPT ); Wed, 3 May 2023 11:24:34 -0400 Received: from mail-yw1-x112e.google.com (mail-yw1-x112e.google.com [IPv6:2607:f8b0:4864:20::112e]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 68E75526B for ; Wed, 3 May 2023 08:24:32 -0700 (PDT) Received: by mail-yw1-x112e.google.com with SMTP id 00721157ae682-55a64f0053fso48983997b3.3 for ; Wed, 03 May 2023 08:24:32 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20221208; t=1683127471; x=1685719471; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:from:to:cc:subject:date :message-id:reply-to; bh=3u3xUQKsQtY5MjJU7KWdFVlKdUwGfS6WMFqIdWoJCIo=; b=unFkvF+6wudO45usQ0U6AfJIfqhGP+H5/IVYvEVNkvB69qXh+JOZzYWL6W8iypwR8u WXtxZSQf4t68zEHXsPc28NiwHPUvvwS/M344xQ3tBObhdP7U9FItGEykPkPqu+eEbFFp okusA4UwcrZWf8Z51Zm29/RE04pDrtNIp/vD2aJp+XpBdU2UkRkKKny9uq/isdNkl+oO Skjuy9Oo1eMbcdvkjUdB3P7K+oZHaS/9IHtfkJQayp0An2kmfxp7oACjbZtN8XRdwT2w lxjzvHFT+zOFmdZqKIHE6BDxnTC8QY7tAueSdS/QBzC33/doZv3G/USW3EuK7WLdlbGW qF+g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1683127471; x=1685719471; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=3u3xUQKsQtY5MjJU7KWdFVlKdUwGfS6WMFqIdWoJCIo=; b=SCdLcCQXb5JyJW71/GrjsU1FIJjHsEveE9BPf3KqXjLDhqeSLtgvCFzWfYh2iVYOKa CLRgpmtvtwshw75SVp2x/STtloyAVpXby5rQVd/vKVDBXMul5chBTuGtzDwE7gCCG7uz pH8fsIGl7y+PqxxW9SPJ4HC1BF+XdiBrPpIaXLqAMoX7pydhphMAvkAHYTX4RnNRTzop fV6p/1+JprSvahIO3gXK/dBRoDw9oKpqFn5PHRUlM8hs4/chcBCOBNubOwx9Pn/GRaf0 wbCaB7LxYlfOXcerdrF5Z+f6Hd6XkdVfmnMUKmpOWHa2dxeA2NcKQ/f5nWn31nnwSGIv UO4Q== X-Gm-Message-State: AC+VfDw4nktSUVwZOOyT8VQ71VudD3qVExKVfQx6joTOt61JuVPoWwNn jaD69wVtZkWjvKgsNHWlrbQ2MmoPSOtYY1MEq549Kw== X-Google-Smtp-Source: ACHHUZ4QRO+chfCfz5/jv+a2xol9xihN+1wt+nUNWo6jdaruLvTBoFlz5eyhSEYcB7ZOQZ60IsdoPkHuL2yRnd5FS3c= X-Received: by 2002:a0d:e296:0:b0:55a:4109:7f5a with SMTP id l144-20020a0de296000000b0055a41097f5amr11315408ywe.12.1683127470672; Wed, 03 May 2023 08:24:30 -0700 (PDT) MIME-Version: 1.0 References: <20230501165450.15352-1-surenb@google.com> <20230501165450.15352-36-surenb@google.com> In-Reply-To: From: Suren Baghdasaryan Date: Wed, 3 May 2023 08:24:19 -0700 Message-ID: Subject: Re: [PATCH 35/40] lib: implement context capture support for tagged allocations To: Michal Hocko Cc: akpm@linux-foundation.org, kent.overstreet@linux.dev, vbabka@suse.cz, hannes@cmpxchg.org, roman.gushchin@linux.dev, mgorman@suse.de, dave@stgolabs.net, willy@infradead.org, liam.howlett@oracle.com, corbet@lwn.net, void@manifault.com, peterz@infradead.org, juri.lelli@redhat.com, ldufour@linux.ibm.com, catalin.marinas@arm.com, will@kernel.org, arnd@arndb.de, tglx@linutronix.de, mingo@redhat.com, dave.hansen@linux.intel.com, x86@kernel.org, peterx@redhat.com, david@redhat.com, axboe@kernel.dk, mcgrof@kernel.org, masahiroy@kernel.org, nathan@kernel.org, dennis@kernel.org, tj@kernel.org, muchun.song@linux.dev, rppt@kernel.org, paulmck@kernel.org, pasha.tatashin@soleen.com, yosryahmed@google.com, yuzhao@google.com, dhowells@redhat.com, hughd@google.com, andreyknvl@gmail.com, keescook@chromium.org, ndesaulniers@google.com, gregkh@linuxfoundation.org, ebiggers@google.com, ytcoode@gmail.com, vincent.guittot@linaro.org, dietmar.eggemann@arm.com, rostedt@goodmis.org, bsegall@google.com, bristot@redhat.com, vschneid@redhat.com, cl@linux.com, penberg@kernel.org, iamjoonsoo.kim@lge.com, 42.hyeyoo@gmail.com, glider@google.com, elver@google.com, dvyukov@google.com, shakeelb@google.com, songmuchun@bytedance.com, jbaron@akamai.com, rientjes@google.com, minchan@google.com, kaleshsingh@google.com, kernel-team@android.com, linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org, iommu@lists.linux.dev, linux-arch@vger.kernel.org, linux-fsdevel@vger.kernel.org, linux-mm@kvack.org, linux-modules@vger.kernel.org, kasan-dev@googlegroups.com, cgroups@vger.kernel.org Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Precedence: bulk List-ID: X-Mailing-List: linux-arch@vger.kernel.org On Wed, May 3, 2023 at 12:39=E2=80=AFAM Michal Hocko wrot= e: > > On Mon 01-05-23 09:54:45, Suren Baghdasaryan wrote: > [...] > > +struct codetag_ctx *alloc_tag_create_ctx(struct alloc_tag *tag, size_t= size) > > +{ > > + struct alloc_call_ctx *ac_ctx; > > + > > + /* TODO: use a dedicated kmem_cache */ > > + ac_ctx =3D kmalloc(sizeof(struct alloc_call_ctx), GFP_KERNEL); > > You cannot really use GFP_KERNEL here. This is post_alloc_hook path and > that has its own gfp context. I missed that. Would it be appropriate to use the gfp_flags parameter of post_alloc_hook() here? > -- > Michal Hocko > SUSE Labs